[00:00] <ScottK> So it's not my call if it gets on.
[00:00] <TheLordOfTime> any kubuntu bug  handlers/devs able to answer a question regarding a bug from -bugs
[00:00] <TheLordOfTime> https://launchpad.net/bugs/1172059
[00:01] <TheLordOfTime> question was whether that would be fixed by release.
[00:01] <TheLordOfTime> (in #ubuntu-bugs)
[00:01] <Noskcaj> TheLordOfTime, i asked that in many channels so everyone knew about the bug
[00:01] <TheLordOfTime> Noskcaj, then !crosspost
[00:02] <ScottK> Noskcaj: Please don't cross post like that.
[00:02] <Noskcaj> ok
[00:02] <TheLordOfTime> !crosspost > Noskcaj
[00:02] <ScottK> TheLordOfTime: "Maybe".
[00:02] <TheLordOfTime> ScottK, that's what I was going ot say, but I handle universe packages for bugs more, so... :P
[00:02] <TheLordOfTime> didn't feel adequately experienced with the bug/package to answer :)
[00:02] <ScottK> Sure.
[00:02]  * TheLordOfTime returns to poking php5-universe (a test package)
[00:03]  * TheLordOfTime returns to poking php5-universe (a test package, in a PPA)  *
[00:04] <smartboyhw> I think the ubiquity fix must get in before Thursday...
[00:04] <ScottK> We can debate it once we have a fix.
[00:05] <smartboyhw> OK.
[00:21] <shadeslayer> Riddell: what format is the .img file?
[00:21] <shadeslayer> ext4?
[00:21] <shadeslayer> because I can't mount it
[00:50]  * ScottK can't replicate Noskcaj's bug so far.
[00:52] <Noskcaj> ScottK, e.g. type "hello" as the first encryption code, "potato" as the next. i will tell you they are not matching, but you will still be able to click next
[00:53] <ScottK> Noskcaj: Is this for full disk encryption or home directory encryption?
[00:53] <Noskcaj> full disk
[00:53] <ScottK> No wonder I couldn't reproduce.
[00:53] <ScottK> I tried the wrong one.
[00:53] <Noskcaj> :)
[00:53] <Noskcaj> balloons found the bug originally, didn't have time to report
[04:01] <ScottK> Quintasan: Did you get a chance to look at fixing the password check bug?
[04:10] <kubotu> ::workspace-bugs:: [1171238] plasma-desktop randomely crashes - but only on 64 bit. @ https://bugs.launchpad.net/bugs/1171238 (by Søren Holm)
[04:22] <ScottK> If it's only on 64 bit, that's not entirely random, is it.
[05:22] <ScottK> apachelogger: I tested an installation in French and it worked out very nicely.
[05:27] <ScottK> Riddell: AFAIK,  bug 1172059 is the only hot item (that and more testing).  I'm off to bed.
[09:07] <Riddell> good morning happy testers
[09:08] <tazz> hey Riddell, how's life? :)
[09:08] <Riddell> pure dead radge
[09:09] <Riddell> tazz: able to help the image testing today for release tomorrow?
[09:10] <tazz> Riddell, I could try after I get home from work. Point is I don't know when I'll get home. :D Woes of working for a startup.
[09:10] <Riddell> any time you can is good
[09:11]  * tazz regularly feels guilty about not being able to contribute enough to kde/kubuntu.
[09:12] <sadandblue> Riddell: Is testing in virtualbox or something similar helpful?
[09:12] <Noskcaj> sadandblue, Yep
[09:13] <sadandblue> Noskcaj: Cool-thanks, will have a look in a bit
[09:13] <Noskcaj> sadandblue, if you run out of testing, try and work on bug 1172059. it's a rather big one
[09:14] <smartboyhw> Noskcaj: I think Quintasan is working on that bug.
[09:14] <Noskcaj> smartboyhw, oh yeah, i think he said something about that
[09:17] <xnox> Noskcaj: Quintasan: I have a patch for above ^ http://paste.ubuntu.com/5597866/ testing to see if that works.
[09:20] <sadandblue> Ah, the bug I reported yesterday happens when you cancel the Create Partition dialogue and open it again
[09:21] <Noskcaj> sadandblue, ???
[09:21] <xnox> nah. not enough.
[09:21] <Noskcaj> xnox, :(
[09:23] <sadandblue> Noskcaj: Just testing it again now, my bug report was a bit crappy so going to add more details - but if you go to partition manually, then click cancel and go to partition again, the Use as drop down has duplicates for each file system type.
[09:24] <xnox> Ok testing this patch now: http://paste.ubuntu.com/5597880/
[09:24] <Noskcaj> sadandblue, interesting, link me when you're done and add a screenshot. i had a similar thing earlier this cycle
[09:25] <sadandblue> Noskcaj: Thanks, will do
[09:26] <Noskcaj> xnox, please work, please work, please work.
[09:28] <smartboyhw> Noskcaj: Don't repeat:P
[09:34] <sadandblue> Noskcaj: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1171989
[09:34] <smartboyhw> :O
[09:38] <Noskcaj> sadandblue, i'll confirm it and add it to the iso tracker
[09:47] <xnox> This seems to work for bug 117259 http://paste.ubuntu.com/5597907/
[09:47] <xnox> This seems to work for bug 1172059 http://paste.ubuntu.com/5597907/
[09:47] <xnox> that is.
[09:49]  * Noskcaj does happy dance
[09:50] <smartboyhw> \o/
[09:53] <Riddell> cor, you rock xnox
[09:53] <Riddell> but now we have to decide about respinning
[09:53] <Riddell> xnox: any other ubiquity upload needs that you know of?
[09:55] <xnox> Riddell: not at the moment but we are debating other encryption bugs.
[09:55] <xnox> Riddell: let me merge propose the ubiquity fix, first.
[09:55] <xnox> Riddell: and then release team will decide.
[09:56] <smartboyhw_> Riddell: Any time for fix of https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1171989 too!
[09:56] <smartboyhw_> ?
[09:56] <smartboyhw_> xnox: ^
[09:57] <xnox> Riddell: you should join #ubuntu-installer tbh.
[10:09] <sadandblue> Noskcaj: maybe something like http://paste.ubuntu.com/5597947/ would fix it, but I don't know python really.
[10:12] <Noskcaj> i know very little python either, but that should work. can someone test it
[10:12] <Noskcaj> also, #ubuntu-installer might be a better place to discuss it
[10:16] <Noskcaj> i just double checked, the bug is kubuntu only
[10:19] <sadandblue> Noskcaj: Ah cool
[10:33] <kubotu> ::workspace-bugs:: [982889] X trying to start before plymouth has finished using the drm driver @ https://bugs.launchpad.net/bugs/982889 (by Tomas Vanderka)
[11:07] <apachelogger> ScottK: yay
[11:08] <smartboyhw_> apachelogger: Oh?
[11:15] <Riddell> ug, I try to test the upgrade and now do-release-upgrade doesn't think there is one :(
[11:17] <vista_killer> how can i upgrade to 13.04?
[11:17] <shadeslayer> Riddell: hah, that's fun
[11:17] <Riddell> vista_killer: what are you running?
[11:17] <vista_killer> the previous version
[11:18] <Riddell> vista_killer: put this into /etc/hosts   <IP_ADDRESS> changelogs.ubuntu.com
[11:18] <shadeslayer> 0.o
[11:18] <shadeslayer> Riddell: does the upgrader use IP's ? :O
[11:18] <shadeslayer> hardcoded IP's
[11:19] <Riddell> and run  kdesudo "do-release-upgrade -m desktop -f DistUpgradeViewKDE -d"
[11:19] <Riddell> shadeslayer: it checks changelogs.ubuntu.com for new releases
[11:19] <smartboyhw_> Riddell: :O
[11:19] <vista_killer> and after i have to remove this ip?
[11:19] <shadeslayer> uh, then why the IP?
[11:19] <Riddell> where it means muon or the muon-updater kded module
[11:20] <Riddell> shadeslayer: cos that makes it read from my server which I put a copy of meta-release with raring marked as released
[11:20] <shadeslayer> aha
[11:20] <Riddell> only way to test the whole thing
[11:20] <shadeslayer> I see
[11:20] <Riddell> nobody does it except me as noted by the breakage in muon I'm testing now
[11:20] <shadeslayer> all the meta-release stuff seems like magic to me
[11:20] <shadeslayer> hehe
[11:21] <shadeslayer> I can only test upgrades from do-release-upgrade using the command line installer
[11:21] <smartboyhw_> hehe
[11:21] <vista_killer> because i remember that in previous versions i have to run 'update-manager -c -d' and iot works
[11:21] <smartboyhw_> shadeslayer: That's a fail:P
[11:22] <vista_killer> now this is not working
[11:23] <Riddell> Mamarok: what's informant.kde.org ?
[11:24] <Mamarok> Riddell: why do you ask?
[11:25] <shadeslayer> seems like build.kde.org ?
[11:26] <Mamarok> ah, now I understand why, that is apparently the server for the ZNC bouncer, at least I guess so
[11:26] <shadeslayer> ah heh :P
[11:27] <Riddell> Mamarok: cos I'm nosey :)
[11:27] <Riddell> ZNC? some irc proxy thing?
[11:28] <Mamarok> an IRC bouncer, yes
[11:37] <Riddell> why the hell does `kdesudo "do-release-upgrade -m desktop -f DistUpgradeViewKDE"` work fine to upgrade but `do-release-upgrade -m desktop -f DistUpgradeViewKDE` doesn't?!
[11:37] <Riddell> kdesudo should hardly make a difference to whether it thinks there is an upgrade to be done or not
[11:39] <smartboyhw_> Riddell: I thought you MUST have sudo to run do-release-upgrade
[11:39] <shadeslayer> ^^
[11:50] <ScottK> BTW, the new installer looks very nice.
[11:50] <smartboyhw_> ScottL
[11:50] <smartboyhw_> Damn
[11:50] <Riddell> yes, good stuff from agateau and sheytan
[11:50] <smartboyhw_> ScottK: :)
[11:51] <Riddell> xnox: where's the ubiquity slideshow you wanted to have screenshots of it at?
[11:51] <smartboyhw_> A problem: ScottK is a Kubuntu Council member while ScottL is Ubuntu Studio's ex-project lead. I may get that wrong...
[11:52] <smartboyhw_> I mean when typing in IRC mobile
[11:52] <Riddell> just remember our Scott comes first, alphabetically, chronologically and awesomeically
[11:53] <smartboyhw_> Riddell: That's true:P
[11:53] <ScottK> Riddell: I should be able to retest i386 today if we respin.
[11:54] <Riddell> muon has a wee python script that checks for if version upgrades are there called releasechecker.  if I run `python3 releasechecker` it says no, if I run `sudo python3 releasechecker` it says yes
[11:54] <Riddell> what the hell?
[11:54] <ScottK> smartboyhw_: I was here first.
[11:54] <smartboyhw_> ScottK: Yeah:P
[11:55] <smartboyhw_> Riddell: I really think do-release-upgrade needs sudo
[11:55] <yofel> it does
[11:56] <Riddell> not to just check for the existance of an upgrade surely?
[11:56] <Riddell> it worked fine in muon yesterday
[11:56] <Riddell> and it hasn't been changed in JontheEchidna's patch
[11:57] <Riddell> sigh, anyone else on quantal able to test?
[11:57] <ScottK> Looking
[11:58] <ScottK> But it'll be a few minutes
[11:59] <sadandblue> Riddell: I can test in a vm if you'd like, will take a bit to download the quantal iso though
[12:00] <Riddell> sadandblue: would be good thanks
[12:03] <sadandblue> Riddell: Oki-will go dl the iso
[12:05] <yofel> Riddell: do I need your IP setting to test that?
[12:05] <Riddell> yofel: yep
[12:05] <Riddell> but I think I got it
[12:05] <Riddell> it's cached in /home/jr/.cache/update-manager-core/meta-release
[12:05] <Riddell> damn that's sneaky
[12:06] <yofel> why would it cache that o.O
[12:06] <smartboyhw_> o.O
[12:06] <smartboyhw_> O.o
[12:07] <Riddell> I found the cache in /var/lib/update-manager/ and thought that was my problem
[12:07] <Riddell> but there's a second cache hidden away
[12:07] <Riddell> what a mystery
[12:07] <Riddell> and wouldn't that affect everyone doing the upgrade for real?
[12:08] <ScottK> Riddell: Works for me either way.
[12:08] <Riddell> ScottK: using muon-updater?
[12:08] <Riddell> oh just the command line
[12:08] <ScottK> Yes.  Just the command line.
[12:24] <Riddell> xnox: are you into update-manager? any idea why it caches the meta-release file and wouldn't that affect the notification when the time comes?
[12:25] <shadeslayer> Riddell: I suspect cjwatson knows
[12:25] <xnox> Riddell: can you please ask on #ubuntu-release about that instead.
[12:30] <Riddell> 13:28 < cjwatson> It catches up eventually, and it's good to spread out the load a bit
[12:30] <Riddell> oh well
[12:33] <Riddell> umm
[12:33] <Riddell> kded(4969): The kded module name ' "muon-notifier" ' is invalid!
[12:33] <Riddell> sigh, another issue
[12:34] <xnox> Riddell: most of release team are not on this channel, and it's important
[12:34] <Riddell> xnox: the cache issue I think colin's answer is good enough, now I'm moving on to muon stuff
[12:35] <ScottK> Riddell: Is that a raring issue or a quantal issue?
[12:36] <Riddell> ScottK: which?
[12:36] <ScottK> The kded naming
[12:36] <Riddell> ScottK: that's quantal, testing the SRU, but it seems to have just fixed itself
[12:36] <ScottK> OK.
[12:36] <Riddell> maybe more caching, caches are so annoying to testers :)
[12:36] <ScottK> I'm doing the same.
[12:37] <ScottK> I've got the "A new version of Kubuntu" prompt.  Any reason I shouldn't dive in and upgrade (i.e. you think we need to fix it harder)?
[12:38] <ScottK> Riddell: ^^^
[12:39] <sadandblue> Weird, virtualbox seems to hang firefox 0.o
[12:39] <Riddell> ScottK: that's a good thing, go ahead and upgrade
[12:39] <ScottK> OK.
[12:45] <Riddell> JontheEchidna: no fix for raring?
[12:46] <ScottK> Riddell: Worked here.  Upgrade in progress.  If you can verify it works for you (in the bug please), I'll waive the 7 day wait and push it to updates.
[12:46] <Riddell> ScottK: done
[12:48] <ScottK> Riddell and JontheEchidna: muon update released for quantal.
[12:48] <Riddell> ScottK: I think I'll upload the same patch to raring, that'll only bite us next release if we miss it
[12:48] <Riddell> ScottK: yay, thanks!
[12:49] <ScottK> Riddell: Definitely, but let's leave it in queue until after release.
[12:49] <ScottK> Actually, we can just unblock it, no reason not to let it build.
[12:49] <ScottK> err ... not unblock ...
[12:49] <sadandblue> Riddell: Do you still need the upgrade testing? The 12.10 iso finally finished downloading
[12:50] <ScottK> More is better.
[12:50] <ScottK> sadandblue: There's an upgrade (image) test case that no one has done.
[12:50] <Riddell> sadandblue: yes please
[12:59] <sadandblue> ScottK, Riddell: Is it assumed that people will update from an up to date system?
[12:59] <ScottK> yes
[13:00] <BluesKaj> Hey all
[13:00] <Riddell> sadandblue: well it won't work if they don't but we will have to make that clear in the upgrade instructions
[13:02] <sadandblue> ScottK, Riddell: Cool thanks-I tried without updating and do-release-upgrade threw an exception, so I'll update and then do it
[13:16] <smartboyhw> What did I miss!
[13:16] <smartboyhw> ?
[13:22] <sadandblue> Hmm "Error: "/var/tmp/kdecache-richard" is owned by uid 1000 instead of uid 0." is that harmless?
[13:27] <yofel> you're running something as sudo and it's complaining that the cache folder isn't owned by root
[13:27] <yofel> using kdesudo should fix that
[13:29] <sadandblue> yofel: Hmm I ran the command through kdesudo - testing an upgrade
[13:30] <yofel> hm. ignore it then, it shouldn't break anything
[13:30] <sadandblue> yofel: Okay shall do
[13:47] <sadandblue> Riddell: I tested the AMD64 upgrade from 12.10-worked fine aside from the uid thing I mentioned earler.
[13:50] <smartboyhw> sadandblue: Report your result!
[13:51] <sadandblue> smartboyhw: Oki shall do
[13:58] <Riddell> sadandblue: yep add it to iso.qa.ubuntu.com thanks
[13:59] <ScottK> Seems I survived the upgrade.
[13:59] <Riddell> you should get a tshirt that says that
[14:01] <smartboyhw> Riddell: LOL
[14:03] <sadandblue> Riddell, smartboyhw: dumb question - I can't see the upgrade testcases, am I looking in the wrong spot?
[14:04] <Riddell> sadandblue: http://iso.qa.ubuntu.com/ -> final -> control-f upgrade
[14:04] <Riddell> should get them
[14:06] <sadandblue> Riddell: Ah thanks, I'd used the filter thing and set it to just kubuntu ><
[14:06] <Riddell> sadandblue, ScottK: I find the plasma theme is a bit broken after upgrade, yet another cache foo I guess, do you see the same?
[14:06] <ScottK> No.  Looks nice.
[14:08] <sadandblue> Riddell: Nope, it looked fine for me.
[14:08] <Riddell> hmm, must be my bad luck cache day
[14:08] <smartboyhw> Riddell: You have too many caches:P
[14:09] <Riddell> the downfall of many an economy
[14:09] <Riddell> but as I say you're welcome to get this Hong Kong gold I have cached away in my school attic any time :)
[14:10] <smartboyhw> Riddell: :O
[14:11] <ScottK> Probably not the best joke to make on a channel that's publicly logged in perpetuity.
[14:12] <smartboyhw> ScottK: +1
[18:13]  * Riddell out for a couple of hours
[18:18] <sadandblue> Wow, going back to c++ after a huge gap seems weird:/
[18:36] <ScottK> Can someone test this upgrade: http://iso.qa.ubuntu.com/qatracker/milestones/269/builds/42840/testcases/1498/results
[18:44] <sadandblue> ScottK: I should be able to in a bit-will need to download the iso for 12.10 first though
[18:45] <ScottK> sadandblue: Excellent.  Thanks.
[18:47] <superfly> btw, does anyone have any clues as to why plasma-desktop is crashing often? I've removed all my plasma configuration, and it still crashes
[18:49] <ScottK> I upgraded this morning and it hasn't crashed yet.
[18:49] <ScottK> Your best bet is to get a backtrace and file a bug on bugs.kde.org.
[18:49] <superfly> ScottK: been crashing for the last 2 months on both my home pc and work pc
[18:50] <superfly> started when I upgraded to 13.04
[18:50] <superfly> OK, I'll do that next time
[18:50] <ahoneybun> superfly: You'll need the packages to do that
[18:51] <superfly> ahoneybun: the debug packages?
[18:51] <ahoneybun> yes
[18:51] <ahoneybun> the symbols
[18:52] <superfly> yeah, I figured so (done it before)
[18:52] <superfly> I don't see a plasma-desktop-dbg package though... will look for some others
[18:53] <ahoneybun> oh ok
[18:53] <ahoneybun> Hey Riddell
[18:53] <ScottK> superfly: kde-workspace-dbg or so.
[18:54] <superfly> thanks ScottK
[18:59] <superfly> now watch it go without a crash for the rest of tonight -_-
[19:06] <yofel> ScottK: we cannot test the (image) upgrades, unless someone wrote the support for ubiquity's "upgrade" feature
[19:07] <ScottK> Oh.
[19:07] <ScottK> So the test case isn't applicable for us?
[19:08] <yofel> right:
[19:08] <yofel>     'Installation type' screen is displayed
[19:08] <yofel> Select the 'Upgrade ubuntu (or derivative name)' option
[19:08] <yofel> we don't have that
[19:10] <shadeslayer> \o/
[19:10] <shadeslayer> adb is up on the Nexus 10
[19:10] <shadeslayer> with the ubuntu rootfs
[19:10] <ScottK> yofel: Thanks.
[19:10] <ScottK> sadandblue: Nevermind.  That one isn't applicable for Kubuntu.
[19:11] <ScottK> yofel: Would you put something on trello about that for 13.10.
[19:11] <yofel> can do
[19:11] <ScottK> thanks
[19:16] <sadandblue> ScottK: Oh - okay:)
[19:18] <yofel> we should've removed the test case for that, but I guess everyone forgot about it
[19:18] <ahoneybun> shadeslayer: you got it working?
[19:18] <shadeslayer> kind of
[19:19] <shadeslayer> adb is up
[19:19] <ahoneybun> shadeslayer: progress is progress ;)
[19:19] <shadeslayer> Linux localhost.localdomain 3.4.5-gb44fbc0 #20 SMP PREEMPT Thu Apr 25 00:32:07 IST 2013 armv7l armv7l armv7l GNU/Linux
[19:19] <shadeslayer> yeah :)
[19:19] <ahoneybun> nice man
[19:19] <superfly> yay! crash!
[19:19] <shadeslayer> unfortunately, can't use sudo
[19:19] <shadeslayer> so worthless
[19:19] <ahoneybun> shadeslayer: can't install packages then
[19:20] <shadeslayer> yeah :(
[19:20] <ahoneybun> shadeslayer: well still nice work
[19:20] <shadeslayer> mmm
[19:21] <ahoneybun> shadeslayer: is there a android-tools package somewhere? so I can set it up to install the Kubuntu image on my Nexus 7
[19:22] <shadeslayer> not quite, there's various android tools that you can install
[19:22] <shadeslayer> but you have to flash manually
[19:23] <ahoneybun> I know but the ubuntu-nexus7-installer is downloading the images again
[19:24] <shadeslayer> yeah, that won't work
[19:24] <shadeslayer> that's for ubuntu-touch
[19:24] <Quintasan> shadeslayer: Can't you chroot into it , install sudo or modify the config?
[19:24] <ahoneybun> why is it in the wiki
[19:25] <shadeslayer> Quintasan: that's what I'm doing, it uses the uid 2000
[19:25] <shadeslayer> so need to somehow give that uid sudo priviliges
[19:25] <Quintasan> there is no username associated with 2000?
[19:25] <Quintasan> or add privledges to a group
[19:26] <Quintasan> duh
[19:26] <shadeslayer> nope
[19:26] <Quintasan> %sudo   ALL=(ALL:ALL) ALL
[19:26] <Quintasan> sup
[19:26] <ScottK> Quintasan: What could go wrong?
[19:26] <Quintasan> ScottK: Everything!
[19:27] <shadeslayer> pft
[19:27] <Quintasan> If you have a better idea then share it with us :P
[19:27] <shadeslayer> actually, hah : %sudo   ALL=(ALL:ALL) ALL
[19:27] <shadeslayer> that's in /etc/sudoers
[19:27] <Quintasan> is that user in sudo group?
[19:28] <Quintasan> or is that user in any group?
[19:28] <shadeslayer> but the uid 2000 is not in the sudo group
[19:28] <shadeslayer> I'm waiting for lilstevie to reply as to what they did
[19:28] <shadeslayer> because in his image it just worked
[19:29] <Quintasan> waiting for solution? boring
[19:29] <Quintasan> shadeslayer: try adding  "2000 ALL=(ALL:ALL) ALL"
[19:29] <Quintasan> Maybe you can refer to users by their ids
[19:29] <Quintasan> :P
[19:29] <ahoneybun> shadeslayer: right now I have the userdata being flashed
[19:29] <shadeslayer> heh
[19:29] <shadeslayer> worth a try
[19:30] <shadeslayer> ahoneybun: cool :)
[19:30] <shadeslayer> Quintasan: logs indicate X is started
[19:30] <shadeslayer> Quintasan: but I have nothing on the screen
[19:30] <shadeslayer> Quintasan: nope  sudo: unknown uid 2000: who are you?
[19:31] <Quintasan> hmmmm
[19:31] <ahoneybun> shadeslayer: heres hoping, so I just installed the android-tools-adb and android-tools-fastboot packages and I had the commands work anywhere
[19:31] <ahoneybun> now I'm waiting on the 717 MBs to be sent lol, so this will boot into Plasma Active and not Unity?
[19:32] <shadeslayer> depends on what you're flashing, if you used the GUI tools it'll most likely flash Unity
[19:32] <Quintasan> shadeslayer: ALL   ALL=(ALL) ALL
[19:32] <Quintasan> :P
[19:32] <Quintasan> That's not safe at all
[19:32] <Quintasan> but who cares
[19:33] <ahoneybun> I got the image from the Kubuntu images that Riddell gave me
[19:34] <shadeslayer> ahoneybun: Riddell would be a better person to ask
[19:34] <shadeslayer> I have no idea about the N7
[19:34] <ahoneybun> site says Kubuntu-Active so yes
[19:34] <ahoneybun> I know I just like to talk lol
[19:35]  * genii-around makes more coffee and continues tinkering in Gimp
[19:37] <shadeslayer> hah
[19:37] <shadeslayer> Quintasan: doesn't work :P
[19:37] <shadeslayer> anyway
[19:44] <ahoneybun> genii-around: I see the Kubuntu page on G+ is using my banner
[19:48] <Quintasan> HOW IT DOES NOT WORK
[19:48] <Quintasan> DURR
[19:49] <genii-around> ahoneybun: It's good work :)
[19:50] <Quintasan> shadeslayer: try ALL ALL=(ALL) NOPASSWD:ALL
[19:50] <shadeslayer> heh
[19:50] <shadeslayer> in a bit
[19:50] <shadeslayer> debugging why X doesn't start
[19:51] <genii-around> ahoneybun: My latest attempt  http://imagebin.org/255240
[19:51] <genii-around> shadeslayer: Put on the sunglasses first
[19:51] <Quintasan> genii-around: I wanted to say you have a very nice clock
[19:52] <Quintasan> [01:05:49] -*- genii-around 's clock tells him it's beer o' clock
[19:52]  * shadeslayer clicks and immediately goes blind
[19:52] <Quintasan> This be a great hour
[19:55] <genii-around> Quintasan: I like the logo in the tail like that like the lemur is hanging from it :)
[19:55] <genii-around> Although, yes, it does sort of look like one of those 1960s clocks a bit...
[20:16] <shadeslayer> Quintasan: sudo: unknown uid 2000: who are you?
[20:16] <shadeslayer> xD
[20:16] <Quintasan> ...
[20:16] <shadeslayer> anyway
[20:16] <shadeslayer> I've had enough of this for tday
[20:16] <shadeslayer> *today
[20:19] <Quintasan> shadeslayer: http://zupa.quintasan.pl/post/308308312/Image
[20:19] <shadeslayer> haha
[20:21] <shadeslayer> I'm completely lost on why X doesn't start though
[21:17] <Riddell> evening
[21:17] <Riddell> still no images?
[21:21] <ScottK> waiting for stuff to get published.
[21:21] <Riddell> ScottK: oh? what's still needed?
[22:04] <Riddell> ooh!
[22:37] <Riddell> ug, oversized http://cdimage.ubuntu.com/kubuntu-active/daily-live/20130424/
[22:59] <ScottK> Make the limit bigger.
[22:59] <ScottK> Who has a 1GB stick anyway.
[22:59]  * ScottK went and bought one recently and the smallest he could find was either 4 or 8.
[23:10] <genii-around> Meh. I have a box of the 1G sticks that I usually put images on and hand out at the release party.
[23:12] <ScottK> Probably not Kubuntu Active images.
[23:13] <genii-around> True, just the regular.
[23:15] <ScottK> Riddell: I'll be back in a few hours.
[23:22] <Riddell> yay!
[23:22] <Riddell> !testers | final ISO candidates!
[23:26] <Riddell> hi __dan__
[23:26] <__dan__> hi Riddell
[23:26] <Riddell> Please test Kubuntu 13.04 RCs in http://iso.qa.ubuntu.com/qatracker/milestones/269/builds
[23:27] <Riddell> all help appreciated
[23:27] <Riddell> real machine or virtual
[23:27] <__dan__> awesome :)
[23:27] <Riddell> upgrade too
[23:27] <tyrog> indeed
[23:29] <Riddell> hi smartboyhw, able to help testing?
[23:31] <__dan__> just reading about the muon upgrade bug, checking my version hehe
[23:32] <smartboyhw> Riddell: I am giving up this time. I have a damning Chinese History test tmr:(


[00:29] <rickspencer3> bdmurray: thanks
[00:29] <rickspencer3> in fact a work around was there
[00:30] <rickspencer3> 1. create a fresh bug: bug = self.launchpad.bugs[bug.id]
[00:30] <bdmurray> rickspencer3: right that's what I said ;-)
[00:30] <rickspencer3> 2. add a new tag list: bug.tags = bug.tags + ['needs-bug-squad']
[00:30] <rickspencer3> and then you can save it
[00:30] <rickspencer3> yeah, I guess I was saying "thanks"
[00:30] <bdmurray> okay, you're welcome!
[00:31] <rickspencer3> and putting the info here in case other people are interested
[02:20] <bac> hi wgrant
[02:24] <wgrant> bac: Hi.
[02:25] <wgrant> I just realised that Blueprint's UI has been redone, so things might have changed.
[02:25] <bac> wgrant: i'm still confused about bug 304627  -- looking at the code a private bug should not be displayed at all
[02:25] <wgrant> bac: Let me check on staging.
[02:25] <bac> wgrant: ah, ok
[02:25] <bac> wgrant: if you can find a representative blueprint please add it to the bug.  otherwise it looks like this is no longer an issue
[02:26] <wgrant> bac: Sure. I'll close it if I can't reproduce now.
[02:26] <bac> 'private bug' *does* appear in the +linkbug page but that's pretty trivial
[02:27] <wgrant> bac: ah, yes, the portlet no longer shows up on the main blueprint page. That's the portlet in question, but since it doesn't show up on the main page, it's not important.
[02:28] <bac> wgrant: ok, great
[02:28] <wgrant> bac: Sorry about that - I forgot about the redesign a couple of months ago.
[03:39] <wgrant> I never got bugmail for my dupe unmarking or comment on bug #378876 a couple of hours ago.
[03:44] <mwhudson> wgrant: bugmail is lagging
[03:49] <wgrant> mwhudson: I got other stuff from around the same time with only 20 minutes of lag in the Received trace.
[03:50] <mwhudson> wgrant: i guess that makes you lucky? :)
[03:50] <mwhudson> i don't know much more than you, IOW
[03:50] <wgrant> mwhudson: Heh. OK. I'll wait.
[04:06] <The_Tick> I'm trying to find all tickets on my project without a milestone, is there a way to do that?
[04:20] <jml> The_Tick: I don't think there's a way to do that on the UI.
[04:20] <jml> The_Tick: you might be able to write a script to do so (see https://help.launchpad.net/API)
[04:21] <wgrant> The API for IBugTarget.searchTasks isn't that great.
[04:21] <The_Tick> ugh
[04:21] <wgrant> I can't work out what those two milestone fields do,.
[04:22] <The_Tick> the only thing we're using lp for is a ticket logger
[04:22] <The_Tick> and I'm not sure if it's that great for it now
[04:22] <wgrant> The_Tick: It looks like you can order a bug search by milestone.
[04:22] <The_Tick> ooooh
[04:22] <jml> searching for "bugs without <thing>" has always been a weakness of Launchpad's IMO.
[04:22] <wgrant> Wasn't bug search meant to be totally redone for 3.0?
[04:22] <The_Tick> ok I go to bugs
[04:23] <jml> not that I know of :)
[04:23] <wgrant> The_Tick: If you go to the bug listing, and order by milestone, you'll find the bugs without a milestone at the end.
[04:23] <jml> wgrant: but hey, the plans are all public: https://dev.launchpad.net/VersionThreeDotO/Bugs
[04:23] <wgrant> To have them appear first, just replace the 'milestone' in the URL with '-milestone'
[04:23] <The_Tick> ya, I'm trying to find a view with milestones on the results
[04:24] <wgrant> The_Tick: A milestone is shown as a clockish-thing to the right of the summary.
[04:24] <wgrant> I'm not sure why they don't show the actual milestone name there.
[04:24] <The_Tick> wow, that's lame
[04:24] <The_Tick> thanks
[04:24] <wgrant> jml: There are a few search things there.
[04:24] <wgrant> Including customisable columns, which would resolve The_Tick's latest complaint.
[04:25] <wgrant> I guess none of them will make it, though.
[04:25] <The_Tick> I'm used to trac really
[04:25] <The_Tick> so just learning what this can and can't do is useful
[04:26] <wgrant> I suspect that things it can't do would be considered bugs.
[04:26] <The_Tick> what's the preferred way to complain nicely? :)
[04:26] <wgrant> https://bugs.launchpad.net/launchpad/+filebug
[04:27] <jml> The_Tick: also, the launchpad-users list can be a good proving ground for proto-bugs
[04:27] <wgrant> That too.
[04:27] <The_Tick> I'll just file bugs
[04:27] <The_Tick> we're a small project in the scope of things for you guys
[04:28] <jml> I've been pushing for feature parity with trac for some time now :)
[04:28] <The_Tick> dude trac's awesome except for the whole hosting it yourself thing
[04:28] <wgrant> Hopefully things will improve in a few months when fixes aren't entirely driven by Canonical.
[04:28] <jml> oh I don't know about that
[04:28] <The_Tick> and if lp used hg we'd use source control on lp too
[04:28] <wgrant> IMO Trac really sucks.
[04:28] <The_Tick> how so?
[04:29] <wgrant> The bug tracker seems clunky and generally painful. I'm not quite sure what exactly is wrong with it, though.
[04:29] <The_Tick> it is out of the box for end users
[04:29] <jml> it has a couple of really nice things
[04:29] <The_Tick> but then you go get the simpleticket plugin
[04:29] <The_Tick> the roadmap is really the nicest thing
[04:29] <The_Tick> and the timeline
[04:29] <wgrant> The timeline is something Launchpad is really lacking.
[04:29] <The_Tick> we really customized it for adium
[04:30] <wgrant> It was a pleasant surprise to find that Google Code had one. It's very useful.
[04:30] <The_Tick> ya, I have no clue what my growl project on lp is doing without it
[04:30] <The_Tick> ya, that was the biggest complaint they had
[04:30] <wgrant> I imagine you could probably rework the existing karma system to do a timeline in LP.
[04:37] <ajmitch> wgrant: karma for a person will only show a limited set of actions, won't it?
[04:37] <ajmitch> at least if you're just trying to reconstruct a timeline from karma
[04:39] <wgrant> ajmitch: It's not currently comprehensive, but it's not too bad. And there are bugs filed about tracking more things.
[05:17]  * ausimage wonders if buildd team member is da house?
[05:17] <ausimage> I have an issue building a package on my ppa that DOES build on my box :/
[05:25] <wgrant> ausimage: perhaps link to the build log?
[05:25] <ausimage> http://launchpadlibrarian.net/27718971/buildlog_ubuntu-jaunty-i386.soovee_1.06ppa2_FAILEDTOBUILD.txt.gz
[05:25] <ausimage> sorry :S
[05:26] <ausimage> wgrant: it says it can't find a file... that does exist and does appear in the local built package
[05:27] <wgrant> That's very probably a bug in the package. Possibly a race of some kind.
[05:27] <wgrant> How were you building it locally?
[05:28] <ausimage> dpkg-buildpackage -us -uc
[05:29] <ausimage> thats command I used
[05:29] <wgrant> That doesn't count. You need to use pbuilder or sbuild.
[05:29] <ausimage> ahhh...
[05:29] <wgrant> Otherwise you're building in an unclean environment.
[05:29] <wgrant> It might have missing build-dependencies, for example.
[05:30] <spm> wgrant: for this newbie builder here. which would you recommend of those two? or 6 of 1... ?
[05:30] <ausimage> yeah...
[05:30] <wgrant> spm: pbuilder unless you use LVM.
[05:30] <spm> 'k. ta!
[05:31] <wgrant> sbuild is much better and more like what the buildds use (failures will sometimes show up in sbuild and on the buildds, but not in pbuilder), but it's more heavyweight to set up.
[05:31] <ausimage> pbuilder... I will look at that tommorrow... and see if that helps
[05:31] <wgrant> ausimage: I can reproduce the build failure locally in sbuild.  Although that box has a habit of killing itself sometimes...
[05:35] <ausimage> really?
[05:37] <ausimage> wgrant: I pushed a new package with the fixed symlinks
[05:37]  * ausimage crosses fingers
[05:38]  * wgrant will check in 3 minutes.
[05:38] <ausimage> cool
[05:42] <wgrant> We'll see in a few seconds...
[05:42] <wgrant> Failed again.
[05:42] <wgrant> Same error.
[05:43] <ausimage> wgrant: how can I symlink then ?
[05:43] <wgrant> er, same issue. There are absolute paths in the symlinks.
[05:43] <wgrant> What are they meant to link to?
[05:43] <wgrant> the 'soovee' binary in the root of the package?
[05:44] <ausimage> I have a single script that can read its name
[05:44] <wgrant> ln -s soovee svterm
[05:44] <wgrant> ln -s soovee svview
[05:44] <wgrant> How were you linking them before?
[05:45] <ausimage> with nautilus drag :/
[05:45] <wgrant> Oh.
[05:47]  * ausimage did the links how you should and pushed a new package
[05:48] <ausimage> *showed
[05:48] <wgrant> OK. Let's see how this works.
[05:49] <ausimage> wgrant: I checked the dif between nautilus and ln -s *
[05:50] <ausimage> apparently nautilus uses the full path... and ln does not
[05:50] <wgrant> ausimage: ln uses whatever you tell it to - it will use an absolute path if you give it one, which is necessary sometimes.
[05:51] <ausimage> ahh
[05:52] <wgrant> dh_install: soovee-common missing files (debian/tmp/usr/lib/python2.6/dist-packages/soovee_app/pages/*), aborting
[05:52] <wgrant> It installed into python2.6/site-packages, though this is on Karmic...
[05:53] <ausimage> hmm not sure why that happened?
[05:53] <jrick> Somebody just said
[05:53] <wgrant> But it worked on Jaunty.
[05:53] <wgrant> So possibly some Karmic breakage.
[05:53] <jrick> sorry about that
[05:53] <wgrant> ausimage: So, it's fixed!
[05:54] <ausimage> it is :)
[05:54] <ausimage> cool
[05:54] <ausimage> now if only revu could stomach the package. it may have a chance at karmic, wgrant ;)
[05:55] <wgrant> ausimage: The first problem with that package is that it's native. That'll not be accepted into Ubuntu.
[05:55] <wgrant> But this is #ubuntu-motu talk.
[05:55] <ausimage> native?
[05:55] <wgrant> It has just a .dsc and .tar.gz, rather than a .dsc, .diff.gz and .orig.tar.gz.
[05:56] <wgrant> (and no '-' in the version)
[06:08] <ahn> Does VCSimports from a CVS repository preserve the full history during the import?
[06:09] <wgrant> ahn: Yes.
[07:58] <wgrant> One of my launchpadlib scripts died with a 401 at 06:13 UTC - but it worked for the three minutes before that, and works again now.
[07:58] <wgrant> I've not touched any of my OAuth tokens lately.
[08:00] <spm> wgrant: ~ 45 mins ago right?
[08:01] <wgrant> spm: Yes.
[08:10] <spm> wgrant: hrm. nothing obvious is showing up. none of the immediate suspects at any rate. :-/
[08:12] <wgrant> spm: Damn.
[08:12] <wgrant> spm: Should I file a bug, or just hope it doesn't happen again?
[08:13] <spm> hmmm. yes.
[08:14] <spm> my heart says file a bug, the head says we don't really have much beyond a transient to work with.
[08:14] <wgrant> Exactly.
[08:15] <spm> hmm. keep an eye out. if you see another soonish (days), get the UTC time and report them both. my 2c.
[08:16] <wgrant> Sure. Thanks.
[08:35] <wgrant> mwhudson: I finally got that bugmail I asked about.
[08:38] <wgrant> noodles775: In addition to bug #314370, it'd be easier for users to realise they need to select a different distroseries if it used the distroseries version instead of long codename.
[08:38] <wgrant> 'Ubuntu 9.04' is more recognisable and correct than 'The Jaunty Jackalope'
[08:39] <noodles775> wgrant: definitely. There's a bug somewhere to re-label distroseries throughout LP...
[08:46] <wgrant> noodles775: What does your 314370 branch do if it can't detect the distroseries? Select the latest one, like is done now?
[08:48] <noodles775> wgrant: if the user-agent distroseries doesn't match any of the valid series, yes, it uses the latest distroseries that has sources in the archive.
[08:49] <dhruba> Hi, I have installed Ubuntu Server 9.04 with NTP, DHCP, DNS and OpenLDAP on it. I have created a few users through phpLDAPAdmin. But while trying to login from the Ubuntu Client 9.04, it is giving a problem that the Home directory is not present. Again, it is giving that it is ignoring .dmrc file. But even through ls -la I could not find any .dmrc file
[08:49] <wgrant> noodles775: Would it be better to default to nothing instead?
[08:49] <wgrant> dhruba: You want #ubuntu, I suspect.
[08:50] <wgrant> noodles775: The detection should get most people, but then people are going to get lazy and forget to change it. Then when the detection fails, they're going to get the wrong packages.
[08:51] <noodles775> wgrant: good point... yep, that would be better...
[08:53] <wgrant> noodles775: Shall I file a bug?
[08:54] <noodles775> wgrant: yes, that would be great (as the branch has just landed as is). Thanks!
[08:55] <dhruba> Hi, I have installed Ubuntu Server 9.04 with NTP, DHCP, DNS and OpenLDAP on it. I have created a few users through phpLDAPAdmin. But while trying to login from the Ubuntu Client 9.04, it is giving a problem that the Home directory is not present. Again, it is giving that it is ignoring .dmrc file. But even through ls -la I could not find any .dmrc file
[08:55] <wgrant> noodles775: Plus it needs new UI changes and review and blah, so it would delay that branch quite a bit...
[08:55] <wgrant> dhruba: As i suggested earlier, you want to ask that in #ubuntu - this channel is for Launchpad, not Ubuntu, support.
[08:55] <noodles775> wgrant: exactly :)
[09:07] <wgrant> noodles775: Bug #385485
[09:07] <noodles775> Cheers wgrant
[09:32] <wgrant> bigjools: I just responded to that bug, but why don't you like a few percent of uses with alternate browsers having to select it manually?
[09:56] <maxb> 08:38 < wgrant> 'Ubuntu 9.04' is more recognisable and correct than 'The Jaunty Jackalope'
[09:56] <maxb> 08:39 < noodles775> wgrant: definitely. There's a bug somewhere to re-label distroseries throughout LP...
[09:56] <maxb> Yuck, I'd hate that
[09:56] <maxb> I find names vastly more recognizable and memorable than numbers
[09:57] <wgrant> maxb: You're not Joe Average User, though.
[09:57] <wgrant> Codenames aren't mentioned in more than a couple of places in releases of Ubuntu.
[09:57] <wgrant> They're not even on the default Firefox home page any more.
[10:00] <noodles775> or here http://www.ubuntu.com/
[10:01] <wgrant> Or releases.u.c.
[10:01]  * wgrant checks ShipIt CDs.
[10:01] <wgrant> Not there, either.
[10:01] <wgrant> So I don't know the codename unless I check sources.list.
[10:06] <persia> The codename is also present as part of the .disk/info file on the CDs, and in /etc/lsb-release
[10:15] <wgrant> persia: True, but I think users are even less likely to look there than sources.list.
[10:15] <persia> wgrant, I don't expect users to look in either of those places, but I do expect software to do so, and I'm not sure that the software won't present those strings to users.
[10:16] <wgrant> persia: Perhaps.
[10:17] <wgrant> But Ubuntu 9.04 is the official one, so Launchpad should probably use it in user-facing places.
[10:17] <persia> So, I agree with the general idea that "Ubuntu 9.04" is more recognisable and correct than "Jaunty Jackalope", but I'm unsure that it's accurate to say that the names aren't presented anywhere.
[10:17] <persia> Yes, very much so.  I mean to provide data, not to disagree with the intent.
[10:17] <wgrant> Right.
[10:52]  * wgrant thwacks Launchpad a bit for mandating authentication at some API URLs and not others.
[10:53] <persia> wgrant, Is the auth mandate not consistent with the data collection from the web UI?
[10:53] <wgrant> persia: Hm?
[10:54] <wgrant> they seem to be gratuitously making launchpadlib users authenticate.
[10:54] <wgrant> But a few lines of code later, it all magically works without an OAuth token.
[10:55] <persia> wgrant, Ah.  It's the gratuitous bit that I was asking about.  There's a larger and larger amount of information that seems to be user-customised, and I'd expect this to be reflected in the API, so auth would be mandated.
[10:55] <persia> On the other hand, if the information collected never contains private information, then I suppose that's annoying (or if one can collect the same information without an auth token)
[10:56] <wgrant> The browser UI already makes use of the API anonymously, which is how I realised launchpadlib could too.
[10:58] <persia> Ah.
[11:17] <maxb> It is rather irksome that you need to authenticate even to see things that you can screenscrape without a login
[11:24] <mwhudson> wgrant: hurrah
[12:37] <ricemark20> i need gwibber 1.0.1, 1.0.2 does not work with twitter client
[12:59] <cumulus007> Hi, I was wondering if the translations in Ubuntu get synchronized with Launchpad during the lifetime of a release?
[13:00] <cumulus007> and also, will translations from Jaunty be ported to the Karmic branche when there are no changes in the source?
[13:02] <dpm> cumulus007: I think you might mean the other way round: translations done through the Launchpad interface are released in Ubuntu regularly through language packs -> https://wiki.ubuntu.com/TranslatingUbuntu/LanguagePacks
[13:03] <cumulus007> hm, so the language packs are being updated during the lifetime of a release?
[13:03] <dpm> cumulus007: yes, although for Jaunty we have not had any updates yet
[13:04] <dpm> cumulus007: and yes, translations from Jaunty will be ported over to Karmic.
[13:04] <cumulus007> okay, that's what I wanted to know :)
[13:06] <dpm> good :)
[15:16] <fta> hi, anyone to consider a request for more space in a PPA? https://answers.edge.launchpad.net/soyuz/+question/73791
[15:17] <adeuring> fta: I have asked our admins to address your request
[15:17] <fta> thanks
[16:00] <ion_> Hi
[16:00] <ion_> What’s the actual effect of the “affects me too” thing? Is there a public list of people affected by each bug or something like that?
[16:02] <intellectronica> ion_: you can only get the list of affected users using the API for now. it's being used when collecting statistics to decide which bugs are most important to work on
[16:03] <ion_> Alright
[16:03] <intellectronica> there's still no visible ui for that. when  there will be one, it is likely to be a way of ordering bugs
[16:03] <ion_> Wouldn’t the list of subscribers be somewhat equivalent for a rough number of people who have an interest to the bug?
[16:13] <intellectronica> ion_: not really. people who have an interest in the bug are the people subscribed to the bug. people affected by the bug are people who actually get the bug on their system
[16:15] <stefanlsd> Im looking at launchpadlib.  Is there some documentation what constitutes private data and non-private data?
[16:15] <persia> stefanlsd, Loosely put, private data is bugs, teams, blueprints, branches, etc. that have the "private" flag set.
[16:16] <intellectronica> stefanlsd: private data is data you can't see :)
[16:17] <intellectronica> stefanlsd: there is no general privacy mechanism in launchpad. for bugs, you can set the private attribute of the bug to true, and then only people subscribed to the bug can see it
[16:19] <stefanlsd> intellectronica, persia: so - change non-private data - 'The application will be able to access Launchpad on your behalf for reading and changing non-private data.- this would mean the application has access to change anything (bugs, teams, blueprints etc) not marked as private?
[16:19]  * persia defers to someone who actually knows about the internals
[16:20] <intellectronica> stefanlsd: basically, launchpadlib, authenticating as you, gets exactly the same permissions you would get working with the web interface
[16:23] <stefanlsd> intellectronica: i get that (like launchpadlib wont be able to do something i wouldn't be able to do through the web interface, i suspect the authentication token stuff is to be more restrictive for the application). Although im still not entirely sure what this restricts... i guess the main distinction is read or change. and then private or non-private.
[16:24] <intellectronica> stefanlsd: the most important thing to remember is that you get exactly the same permissions using launchpadlib as you do with the web interface. that's all there is to it, really
[16:25] <stefanlsd> intellectronica: ok, i can accept that, but then why have this whole token authorization issue?
[16:25] <james_w> stefanlsd: the distinction for private/non-private is useful for when you are using someone else's script
[16:26] <james_w> you can choose "non-private" then, and be sure that even if the script is malicious they still couldn't access anything they couldn't access through the web UI authenticated as themselves
[16:26] <james_w> though they may still be able to make changes that they couldn't make as themselves
[16:26] <intellectronica> stefanlsd: i don't understand. that's just how it's implemented
[16:28] <stefanlsd> ok. thanks guys. im gonna play more with it and see if i can understand it better through implementation
[17:38] <fta> PPA exceeded its size limit (7628.00 of 7120.00 MiB).. again
[17:38] <fta> i'm getting tired of this, all my ppas are full :(
[17:39] <ion_> Hehe
[17:39] <fta> too bad for firefox 3.5 b99
[17:39] <elmo> fta: you should totally ask for a refund
[17:41] <ion_> fta: Couldn’t you get the new Firefox directly into karmic?
[17:41] <fta> needs some staging first
[17:41] <maxb> Re the earlier conversation, is it documented anywhere exactly what the API considers "private information"?
[17:41] <ion_> Ah, never mind, didn’t think of the ≤jaunty audience.
[17:41] <fta> and i'm still waiting for https://answers.edge.launchpad.net/soyuz/+question/73791
[17:43] <fta> and bug 381296
[18:17] <fta> Rejected: PPA exceeded its size limit (23084.00 of 20480.00 MiB) => boom, chromium out too
[18:46] <savvas> fta: it's just a developer preview, still not out :P
[18:46] <fta> savvas, ??
[18:46] <fta> savvas, it == ?
[18:47] <savvas> fta: ah sorry, I was talking about chromium
[18:49] <fta> savvas, yes, it is. but it's the only thing we have for linux, and plenty of people are requesting it, so i provide it in a ppa.. which is full every two days or so
[18:49] <savvas> you're doing a great job by the way :)
[19:00] <fta> savvas, thanks. most people are using PPAs without realizing there's someone working behind the scene to keep the thing alive
[19:12] <james_w> to just install a lazr package or wadllib/launchpadlib do I need buildout, or is that just for development?
[19:21] <mvo> hello! what can I do about: bzr: ERROR: Directory not empty: "/srv/bazaar.launchpad.net/push-branches/00/00/0c/50/.bzr/repository/lock/gxmtz4db2g.tmp": [Errno 39] Directory not empty
[19:27] <mvo> nevermind my last bzr question, I think its fine again
[19:44] <Peng_> How do you mark a merge proposal as superseded? Will it happen automatically?
[21:25] <bdmurray> Is there some way to find out the full list (or more than the top 10) of "Other Tags" for Ubuntu?
[21:41] <bdmurray> well viewing the source of +manage-official-tags had it but that seems ghetto
[21:47] <ahn> Is there a way to delete an empty bzr branch?
[21:50] <nhandler> ahn: Yes, go to https://code.launchpad.net/~USER/PROJECT/BRANCHNAME/+delete
[21:58] <ahn> nhandler: Thank you
[21:59] <ahn> Second question: when setting up a sub-project under a super-project, the bug tracking option include "In Launchpad" and "In the Super Project bug tracker (bugs.launchpad.net).  What is the difference?
[22:10] <salgado> ahn, looks like a bug in LP to me.  I think it somehow got tricked into thinking that the super project doesn't use Launchpad for bug tracking
[22:10] <salgado> ahn, what's the super project in question, btw?
[22:49] <ahn> salgado: netrek-project
[22:50] <ahn> It seems that there is no way for me to delete a vcs-import branch.
[22:50] <ahn> I actually need this branch renamed and assigned to a different subproject.  Do I need to email<EMAIL_ADDRESS>[22:51] <salgado> ahn, better to ask a question on the URL that's on the topic
[22:52] <salgado> that should be on the topic, at least
[22:52] <salgado> ahn, https://answers.launchpad.net/launchpad/+addquestion
[22:53] <ahn> Thank you.  After years of being SF, LP is a bit new.  I will try your link.


[09:59] <krytarik> genii: Missing exclamation mark, and iirc I told you this the last time too. >_<
[17:35] <Menzador> Yeah, otherwise if someone wanted to talk about their bionic ear somewhere else in the namespace, they'd get the Ubuntu 18.04 EOL message
[19:13] <krytarik> Well, no entirely true in this case, because the bot was addressed - but this makes it expect actual commands rather than a trigger like this, unless it's prefixed with the exclamation mark.
[19:28] <krytarik> Curiously enough, while I misspelled "not" for "no" above, the latter is of course another bit missing from the syntax. XD
[19:46] <Menzador> Yeah. In the past I submitted a few changes, specifically when GNOME was a separate flavor, and when I worked on Ubuntu MATE and parts of Lubuntu