[07:01] <doko_> Subscribe somebody else ... ev ... Please enter at least three characters ... this is INSANE!
[07:11] <dieck> doko_: you want to subscribe someone with a 2-char-username?
[07:11] <doko_> dieck, yes, I tried :-/
[07:15] <wgrant> doko: It's misguided and not ideal, but it's been that way for more than two years and this is only the second time I've seen someone complain about it. You can work around it by using the non-AJAX form.
[07:32] <doko_> wgrant, non-AJAX?
[07:33] <wgrant> doko_: Middle click on the link, or right click and open link in a new tab.
[07:34] <doko_> wgrant, ok thanks, a bit handicapped with midle-click on a MacBook
[09:48] <mvo> is it just me or is LP currently timing out really often? I got three timeouts in the last ~30min or so doing bug triage/reassign work on software-center
[10:32] <jtv> cjwatson: where do you get the installer translations from again?  Not from Launchpad, right?
[10:34] <gumara> jtv: Hi
[10:34] <jtv> hi gumara
[10:34] <gumara> Just ask Colin ?
[10:36] <gumara> jtv: No Colin here?
[10:36] <jtv> gumara: I guess not.
[10:36] <gumara> :P
[10:44] <jtv> dpm: maybe you can help with this.  I forgot how/where the installer's translations are gathered.
[10:45] <dpm> jtv, they are distributed in the 5 top templates there: https://translations.launchpad.net/ubuntu/oneiric/+lang/ca
[10:46] <dpm> the main ones are debian-installer and ubiquity-debconf (graphical installer)
[10:46] <jtv> What I mean is, do we use the translations from there to put on the CD?  IIRC there was some unusual process.
[10:52] <gumara> dpm: Hi, I have some problem with translation in installer.
[10:53] <dpm> jtv, the translations cannot be used in langpacks, so the developers export them and commit them in the code directly
[10:53] <dpm> the other unusual bit is debian-installer
[10:53] <jtv> dpm: I'm asking because gumara ^^ is having some trouble with a translation fix from May that hasn't worked its way into alpha3.
[10:54] <cjwatson> jtv: most installer translations need to happen in Debiain
[10:54] <dpm> jtv, gumara got his/her question answered on #ubuntu-translators
[10:54] <cjwatson> er, Debian
[10:55] <jtv> Ah, thanks.
[10:55] <gumara> Trouble is this one https://translations.launchpad.net/ubuntu/oneiric/+source/ubiquity/+pots/ubiquity-debconf/th/+translate?batch=10&show=all&search=Something
[10:55] <cjwatson> OK, Ubuntu-specific strings are an exception
[10:55] <cjwatson> probably just a matter of doing a fresh manual export
[10:55] <cjwatson> I'll have a look
[10:56] <cjwatson> and yes, those *do* come from Launchpad, just not automatically
[10:56] <jtv> It looks like a fairly important fix.  The previous translation seems very wrong.
[11:12] <doko> assume I have a bug_target object. How can I find out the associated series?
[11:16] <cjwatson> gumara,jtv: ubiquity 2.7.16 will have the updated translation.  Thanks for the note.
[11:20] <jtv> thanks cjwatson!
[11:22] <geser> doko: isn't the bug_target the distro series itself?
[11:23] <doko> geser: no
[11:23] <doko> XXX https://api.launchpad.net/1.0/ubuntu/+source/rootskel https://api.launchpad.net/1.0/ubuntu/oneiric
[11:23] <doko> XXX https://api.launchpad.net/1.0/ubuntu/oneiric/+source/rootskel https://api.launchpad.net/1.0/ubuntu/oneiric
[11:23] <doko> first is the bug_target, second the series
[11:27] <soren> doko: Well, if the bug target doesn't have a distroseries attribute (ie if the bug task isn't targeted), you can go through .distribution.current_series.
[11:28] <geser> doko: is that from existing bugs?
[11:30] <doko> geser, existing bugs? no, creating them
[11:30] <doko> it looks like the bug_nomination has a distroseries link
[11:33] <geser> doko: depending on what you want to file the bug on you need different bug_targets: you first example if you only want to file it against the "rootskel" source package and the second one if you want to file it "rootskel" and nominate for Oneiric
[11:34] <doko> geser: right, I want it for the distroseries
[11:40] <geser> doko: lp.distributions['ubuntu'].getSeries(name_or_version='oneiric') to get a distro_series object and on it use getSourcePackage(name='rootskel') and use this object as bug_target for your new bug
[11:43] <doko> geser: trying to fix http://bazaar.launchpad.net/~linaro-infrastructure/svammel/trunk/view/head:/bug_reporting.py
[11:50] <geser> doko: what is not working?
[12:17] <apw> are we aware that PPA builds at least are dying and droping to CHROOTWAIT.  Looks to be glibc detecting memory corruption in sudo
[12:18] <apw> https://launchpadlibrarian.net/77593315/buildlog_ubuntu-lucid-i386.linux_2.6.32-34.74~pre201108190906_CHROOTWAIT.txt.gz
[14:25] <xaprb> I have done "bzr branch" to get a working copy.  How can I change it to a newer branch that exists on launchpad?  I just threw away and re-branched, but it seems there must be a better way.
[14:36] <deryck> adeuring, I'll take IRC now.
[14:36] <adeuring> deryck: thanks!
[15:12] <CarlFK> how do I search for a PPA for alsa? I want to try alsa 1.0.24 on 11.04
[15:18] <deryck> CarlFK, I usually type "alsa ppa" into our search on launchpad.net or into Google....
[15:18] <bigjools> https://launchpad.net/ubuntu/+ppas
[15:18] <bigjools> it's even linked from the front page
[15:18] <deryck> CarlFK, however, I'm on 11.04 and I have alsa-base at 1.0.24+dfsg-0ubuntu1.  Is this what you want?
[15:19] <CarlFK> there is a front page? :)
[15:19] <CarlFK> deryck: yes... I think...
[15:19] <deryck> yeah, seriously, bigjools, we have a front page? ;)
[15:19] <CarlFK> test box, will re-install os once I am done hacking it to pieces
[15:20] <bigjools> on the /ubuntu/+source/<package> pages it also links to PPAs containing that source
[15:20] <bigjools> deryck: fancy that :)
[15:20] <deryck> :)
[15:21] <deryck> CarlFK, FWIW, I don't think you need to reinstall the whole OS to get the right alsa. ;)
[15:21] <deryck> but obviously, that's not a Launchpad problem. :)  Good luck with it!
[15:22] <CarlFK> huh... Installed: 1.0.24+dfsg-0ubuntu1
[15:22] <CarlFK> bigjools: thanks for the url
[17:44] <ahasenack> OOPS-2057CBB594
[17:44] <ahasenack> for this url: http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/annotate/head:/tools/write-mime-multipart (repeatable)
[17:45] <deryck> ahasenack, ok, will have to wait for the OOPS to appear and then will take a closer look.
[17:46] <ahasenack> deryck: ok
[17:47] <deryck> abentley, handing off to you now.
[17:47] <abentley> deryck: ack.
[17:55] <kamal> hi LP people ...  I've been consistently getting "Timeout error" from LP for the past 3 days in these two (unrelated) situations:
[17:55] <kamal> 1. when I try to edit one of my PPA's description text https://launchpad.net/~kamalmostafa/+archive/linux-kamal-mjgbacklight
[17:55] <kamal> 2. when I try to view https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/807950
[17:59] <kamal> regarding (1.) ...  I can successfully edit one of my other PPA's description texts.  weird.
[18:29] <abentley> kamal: We treat timeouts seriously.  Please file a bug.
[20:30] <GTRsdk> hello
[20:31] <GTRsdk> can an administrator cancel a ppa build for me?
[20:31] <GTRsdk> I need this build canceled: https://launchpad.net/~gtrsdk/+archive/libreofficebuilds/+build/2732038
[20:32] <GTRsdk> lamont: can you cancel that build for me please?
[20:33] <GTRsdk> I think a recent upload will cancel it
[20:48] <mars> abentley, around?
[20:59] <abentley> mars: Hi.
[21:02] <slangasek> hi, can someone here explain to me how permissions to see private bugs are meant to work?
[21:03] <slangasek> I've recently filed a couple of bugs against the update-manager package in Ubuntu that were filed as 'private' due to a bug somewhere else, and mvo wasn't able to see them
[21:06] <bac> hi slangasek
[21:06] <slangasek> bac: hi there
[21:06] <bac> slangasek: private bugs are visible to members of the team assigned to be the bug supervisor
[21:06] <bac> and to anyone directly subscribed to the bug
[21:06] <slangasek> and in the distro, bug supervisors are done on per-package basis, or at the distro level?
[21:07] <bac> slangasek: er, distro i believe
[21:07] <bac> slangasek: but if you can see the bug, then all you need to do is subscribe mvo
[21:07] <slangasek> right, but that's not the point :)
[21:07] <bac> oh
[21:07] <slangasek> the point is that the only people who are in a position to fix the bug aren't seeing it
[21:07] <slangasek> so we have something misconfigured
[21:08] <bac> ah, ok
[21:08] <nigelb> woah, just got OOPS-2057AT170
[21:08] <bac> let me look
[21:08]  * nigelb hasn't seen LP timeoout in a while
[21:11] <bac> slangasek: so are those people in ~ubuntu-bugs?
[21:11] <slangasek> checking
[21:12] <slangasek> bac: yes, by way of ubuntu-core-dev
[21:12] <bac> hmm
[21:12] <GTRsdk> is it possible to have launchpad build packages in a PPA for Debian?\
[21:12] <nigelb> ok, interesting. so apport retracer serivice is what's letting me see private bugs.
[21:12] <nigelb> (it subscribes crash bug triagers)
[21:14] <bac> slangasek: could you file a bug with and example private bug and affected person?
[21:14] <slangasek> bac: when we were discussing this on #ubuntu-release, kirkland pointed out a related issue, which is that the bug supervisor for the 'qemu' project in LP, which uses LP bugs, was not receiving any notification of bugs flagged security/private
[21:14] <slangasek> bac: would you like me to switch one of my existing bugs back?
[21:15] <bac> you mean back to private?
[21:15] <nigelb> "Security-related bugs are by default private (visible only to their direct subscribers)"
[21:15] <nigelb> there.
[21:15] <nigelb> and the direct subscribers is only the security contact.
[21:15] <slangasek> bac: yes
[21:16] <bac> slangasek: well, not if it is going to impede your real work
[21:16] <slangasek> bac: it won't, now that I've talked to him out of band he already has the info on the bugs :)
[21:16] <bac> ok, sure then
[21:16] <bac> thanks and we'll look at it monday
[21:17] <slangasek> bac: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/828162; lp id mvo could not see it
[21:17] <slangasek> mvo: ^^ can you confirm you're blocked out of this bug again?
[21:17] <mvo> bac: I can not see this one
[21:17] <bac> but it is currently public
[21:17] <mvo> bac: and I maintain update-manager in ubuntu  (my name is in the Maintainer field of the package)
[21:18] <mvo> eh, sorry, I couldn't see it before slangasek made it public
[21:18] <slangasek> bac: hah! well, LP *told* me I'd made it private again...
[21:19] <slangasek> right, so, I'm getting timeouts trying to mark the bug private ;)
[21:21] <mvo> aha, I got timeouts a lot today/prev day
[21:24] <mvo> anyway, I call it a day now
[21:29] <slangasek> bac: ok, since the timeout blocks me from switching this bug back to private, and the ajax interface doesn't give me any OOPS to look at... where's the best place for me to file a test bug?  staging?
[21:30] <bac> slangasek: yes, but it is even more susceptible to time outs
[21:31] <slangasek> phooey, why does staging want me to log in with a password
[21:32] <slangasek> hah, and it's trying to insist that I change my password... pass.
[21:32] <bac> slangasek:  OOPS-2057D167
[21:32] <slangasek> oh, now I'm in
[21:32] <slangasek> magic
[21:34] <slangasek> bac: "Your search: 2057D167 didn't match any oops.
[21:34] <slangasek> "?
[21:34] <bac> slangasek: yeah, it isn't processed yet
[21:34] <slangasek> ok
[21:34] <bac> slangasek: i turned off javascript and got a real page in order to generate that
[21:34] <slangasek> right
[21:34] <bac> slangasek: i need to run, though.  i'll look for your bug on monday.
[21:35] <slangasek> understood, thanks :)
[21:35] <slangasek> https://bugs.staging.launchpad.net/ubuntu/+source/update-manager/+bug/824938