[00:00] <mbarnett> who knows where you could find one of those!?
[06:49] <LPCIBot> Project db-devel build (278): FAILURE in 5 min 10 sec: https://hudson.wedontsleep.org/job/db-devel/278/
[07:01] <LPCIBot> Project db-devel build (279): STILL FAILING in 0.47 sec: https://hudson.wedontsleep.org/job/db-devel/279/
[07:16] <LPCIBot> Project db-devel build (280): STILL FAILING in 0.47 sec: https://hudson.wedontsleep.org/job/db-devel/280/
[07:31] <LPCIBot> Project db-devel build (281): STILL FAILING in 0.46 sec: https://hudson.wedontsleep.org/job/db-devel/281/
[07:46] <LPCIBot> Project db-devel build (282): STILL FAILING in 0.47 sec: https://hudson.wedontsleep.org/job/db-devel/282/
[08:01] <LPCIBot> Project db-devel build (283): STILL FAILING in 0.46 sec: https://hudson.wedontsleep.org/job/db-devel/283/
[08:16] <LPCIBot> Project db-devel build (284): STILL FAILING in 1.3 sec: https://hudson.wedontsleep.org/job/db-devel/284/
[08:31] <LPCIBot> Project db-devel build (285): STILL FAILING in 0.46 sec: https://hudson.wedontsleep.org/job/db-devel/285/
[08:46] <LPCIBot> Project db-devel build (286): STILL FAILING in 0.49 sec: https://hudson.wedontsleep.org/job/db-devel/286/
[09:01] <LPCIBot> Project db-devel build (287): STILL FAILING in 0.48 sec: https://hudson.wedontsleep.org/job/db-devel/287/
[09:16] <LPCIBot> Project db-devel build (288): STILL FAILING in 0.49 sec: https://hudson.wedontsleep.org/job/db-devel/288/
[09:31] <LPCIBot> Project db-devel build (289): STILL FAILING in 0.48 sec: https://hudson.wedontsleep.org/job/db-devel/289/
[09:46] <LPCIBot> Project db-devel build (290): STILL FAILING in 0.46 sec: https://hudson.wedontsleep.org/job/db-devel/290/
[10:01] <LPCIBot> Project db-devel build (291): STILL FAILING in 0.48 sec: https://hudson.wedontsleep.org/job/db-devel/291/
[10:16] <LPCIBot> Project db-devel build (292): STILL FAILING in 1.9 sec: https://hudson.wedontsleep.org/job/db-devel/292/
[10:31] <LPCIBot> Project db-devel build (293): STILL FAILING in 0.48 sec: https://hudson.wedontsleep.org/job/db-devel/293/
[10:46] <LPCIBot> Project db-devel build (294): STILL FAILING in 0.46 sec: https://hudson.wedontsleep.org/job/db-devel/294/
[11:01] <LPCIBot> Project db-devel build (295): STILL FAILING in 0.48 sec: https://hudson.wedontsleep.org/job/db-devel/295/
[11:16] <LPCIBot> Project db-devel build (296): STILL FAILING in 0.48 sec: https://hudson.wedontsleep.org/job/db-devel/296/
[11:31] <LPCIBot> Project db-devel build (297): STILL FAILING in 0.49 sec: https://hudson.wedontsleep.org/job/db-devel/297/
[11:46] <LPCIBot> Project db-devel build (298): STILL FAILING in 0.47 sec: https://hudson.wedontsleep.org/job/db-devel/298/
[12:01] <LPCIBot> Project db-devel build (299): STILL FAILING in 0.46 sec: https://hudson.wedontsleep.org/job/db-devel/299/
[12:16] <LPCIBot> Project db-devel build (300): STILL FAILING in 0.47 sec: https://hudson.wedontsleep.org/job/db-devel/300/
[12:31] <LPCIBot> Project db-devel build (301): STILL FAILING in 0.46 sec: https://hudson.wedontsleep.org/job/db-devel/301/
[12:46] <LPCIBot> Project db-devel build (302): STILL FAILING in 0.46 sec: https://hudson.wedontsleep.org/job/db-devel/302/
[13:01] <LPCIBot> Project db-devel build (303): STILL FAILING in 0.45 sec: https://hudson.wedontsleep.org/job/db-devel/303/
[13:16] <LPCIBot> Project db-devel build (304): STILL FAILING in 2.5 sec: https://hudson.wedontsleep.org/job/db-devel/304/
[13:31] <LPCIBot> Project db-devel build (305): STILL FAILING in 0.48 sec: https://hudson.wedontsleep.org/job/db-devel/305/
[13:34] <wgrant> Hmm.
[13:34] <wgrant> I wonder if telling it to wipe out its workspace will work.
[13:46] <LPCIBot> Project db-devel build (306): STILL FAILING in 0.45 sec: https://hudson.wedontsleep.org/job/db-devel/306/
[14:01] <LPCIBot> Project db-devel build (307): STILL FAILING in 0.46 sec: https://hudson.wedontsleep.org/job/db-devel/307/
[14:16] <LPCIBot> Project db-devel build (308): STILL FAILING in 0.49 sec: https://hudson.wedontsleep.org/job/db-devel/308/
[14:33] <LPCIBot> Project db-devel build (309): STILL FAILING in 0.47 sec: https://hudson.wedontsleep.org/job/db-devel/309/
[14:46] <LPCIBot> Project db-devel build (310): STILL FAILING in 0.46 sec: https://hudson.wedontsleep.org/job/db-devel/310/
[15:01] <LPCIBot> Project db-devel build (311): STILL FAILING in 0.47 sec: https://hudson.wedontsleep.org/job/db-devel/311/
[18:02] <Ursinha> lifeless, tell me four bugs that annoy you in qa-tagger
[18:06] <jelmer> thumper: niiiice
[18:07] <thumper> jelmer: there are some wording changes on the qastaging copy
[18:07] <thumper> but the view is the same
[18:08] <jelmer> like many of the other recipe builds it would be nice if the last successful build or at least whether the last build was successful could be shown
[18:17] <lifeless> Ursinha: 674829 671809 681099 688073(but really just about usability in the report)
[18:19] <Ursinha> lifeless, cool
[18:19] <Ursinha> bug 674829 bug 671809 bug 681099 bug 688073
[18:19] <_mup_> Bug #674829: Deployment report for db-stable is broken. <qa-tagger:Fix Committed by ursinha> < https://launchpad.net/bugs/674829 >
[18:19] <_mup_> Bug #671809: bug mail should use the header from the bug thread rather than 'Bug fixed by a commit' <qa-tagger:Triaged> < https://launchpad.net/bugs/671809 >
[18:19] <_mup_> Bug #681099: bug=1234 merges without lp metadata don't show up in the deployment report <qa-tagger:Triaged> < https://launchpad.net/bugs/681099 >
[18:19] <_mup_> Bug #688073: qa-needstesting revisions should not be greyed out <deployment-qa> <qa-tagger:Triaged> < https://launchpad.net/bugs/688073 >
[18:20] <Ursinha> lifeless, now the big ones
[18:20] <Ursinha> lifeless, I don't plan to abandon qa-tagger, it's my child :P
[18:52] <lifeless> Ursinha: \o/
[18:52] <lifeless> Ursinha: Hopefully you will welcome assistance from the team though :>
[19:04] <Ursinha> hehe, lifeless, of course :)
[19:49] <lifeless> wgrant: https://bugs.launchpad.net/launchpad/+bug/704585
[19:49] <_mup_> Bug #704585: canonical_url performs poorly <timeout> <Launchpad itself:Triaged> < https://launchpad.net/bugs/704585 >
[19:53] <jelmer> StevenK: https://code.launchpad.net/~jelmer/ubuntu/natty/paramiko/randompool+addressfamilies/+merge/46669
[20:08] <StevenK> jelmer: https://code.launchpad.net/~stevenk/launchpad/more-thunder/+merge/46406
[20:11] <gmb> gary_poster: http://pastebin.ubuntu.com/555534/
[20:11] <lifeless> gmb: sooooooooo
[20:11] <lifeless> gmb: there is a bug you should see
[20:11] <gmb> lifeless: Just one? Win.
[20:11] <gmb> Link me.
[20:11] <LPCIBot> Project db-devel build (312): STILL FAILING in 4 hr 55 min: https://hudson.wedontsleep.org/job/db-devel/312/
[20:14] <lifeless> gmb: bug 507603
[20:14] <_mup_> Bug #507603: checkwatches on non-debian debbugs instances do not work <bugwatch> <lp-bugs> <Launchpad itself:Triaged> < https://launchpad.net/bugs/507603 >
[20:14]  * gmb looks
[20:15] <gmb> lifeless: Noted. And thanks for pointing out that it's a different debbugs DB. I was apparently suffering from an acute uptake-grasping deficiency disorder on the day when I first responded to that bug.
[20:16] <lifeless> is that a hard thing to do
[20:16] <lifeless> like
[20:16] <lifeless> did we need special arrangements to sync the db
[20:17] <jml> thumper: reviewed your patch.
[20:20] <allenap> rvb: http://wiki.bazaar.canonical.com/BzrPipeline
[20:23] <lifeless> matsubara: hi
[20:23] <matsubara> hey lifeless
[20:23] <lifeless> https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1844B1523 is on disk on devpad, web ui is refusing to show it
[20:23] <lifeless> how do I debug whats going on ?
[20:23] <matsubara> working on it
[20:23] <matsubara> lifeless, I rolled out some code yesterday which broke the OopsLoader
[20:24] <lifeless> kk
[20:24] <wgrant> Ah, I was about to ask about that myself.
[20:28] <gmb> lifeless: Yes, we need to make arrangements to sync the DB to some place on loganberry. We don't support > 1 debbugs DB, either; the code is written for just the one of them.
[20:28] <lifeless> yeah
[20:28] <lifeless> so code change + a faq
[20:29] <gmb> lifeless: Yes.
[20:35] <gary_poster> mars, yoo hoo....  anyone seen a mars?
[20:35] <jml> gary_poster: he's here, getting trained in some hiring software
[20:41] <bigjools> jelmer: are you busy?
[20:48] <allenap> sinzui: Do you generate a web page of the XXXs in the code?
[20:48] <sinzui> I used to
[20:49] <sinzui> I may still
[20:49]  * sinzui looks
[20:49] <bigjools> it was on devpad IIRC
[20:49] <wgrant> There's a script in utilities/
[20:49] <wgrant> stub: Bug #526890 is probably fixed now that the auth store is gone, right?
[20:49] <_mup_> Bug #526890: Oops on export page: LocationError: (None, 'email') <lp-translations> <oops> <Launchpad itself:Triaged> < https://launchpad.net/bugs/526890 >
[20:50] <sinzui> allenap, I do not the script to create the xxx report is in./utilities
[20:51] <stub> closed
[20:52] <wgrant> Thanks.
[20:54] <jelmer> bigjools: hi
[20:55] <bigjools> jelmer: heyhey.  Can we talk about your outstanding bugs/branches?
[20:55] <jelmer> bigjools: yes, sure. where are you?
[20:55] <bigjools> jelmer: presidente
[21:05] <gmb> I want it noted that JS is hateful and should be shot.
[21:05] <gmb> Can we implement in-browser LISP at some point? It'd be more fun.
[21:07] <jtv> Did we just land any changes to how we tally Rosetta usage?  The translatable-projects listing on qastaging is over a thousand projects short.
[21:07] <dobey> gmb: http://kybernetikos.github.com/Javathcript/
[21:12] <mwhudson> dobey: i bet he started that because he came up with the project name and then couldn't resist implementing it
[21:13] <lifeless> gmb: oh also
[21:13] <lifeless> flags in the api; we need to talk- I think you're on crack
[21:13] <gmb> lifeless: I'm open to the idea of being on crack.
[21:14] <gmb> When I filed the bug I was feeling quite punchy about using feature flags with JS features. I haven't thought in depth about the arguments for not doing it, though.
[21:15] <lifeless> oh in js is great
[21:15] <lifeless> I'd just set the variables you need in the .pt
[21:16] <lifeless> or does that not work?
[21:20] <dobey> mwhudson: heh
[21:21] <gmb> lifeless: It works; it felt like a hack.
[21:22] <gmb> lifeless: But if you're happy for it to be done that way, let's do it that way. I'm all for uncomplicated solutions.
[21:22] <gmb> My frustration wasn't helped by bugtask_index.js shenanigans that I told you about on Sunday.
[21:22] <gmb> So feel free to mark that as BugTaskStatus.REPORTER_ON_CRACK.
[21:28] <matsubara> wgrant, lifeless: OopsLoader is fixed and it's now catching up. that oops should be available soon
[21:28] <wgrant> matsubara: Thanks.
[21:29] <matsubara> np
[21:30] <lifeless> matsubara: awesome thanks
[21:32] <lifeless> leonardr: hey
[21:32] <lifeless> leonardr: I'd like to learn a little more about how launchpadlib api authentication happens
[21:32] <lifeless> do you think you can spare a few minutes to teach me?
[21:35] <leonardr> lifeless: yes, i need a minute though
[21:35] <leonardr> we can do it on irc or irl
[21:39] <lifeless> I'm in the plenary room
[21:40] <leonardr> ok, be there soon
[21:53] <jtv> allenap: is there any innate ordering to bug subscriptions?  Seems I/we broke bugsubscription.txt line 866, in the ordering of getDirectBugSubscriptions() output.
[21:53] <jtv> rvb: interested in doing that translations bugfix I mentioned?
[21:54] <allenap> jtv: Interesting. Bug.getDirectSubscriptions() returns a newfangled BugSubscriptionSet object.
[21:55] <allenap> jtv: Which is a subclass of frozenset.
[21:55] <allenap> jtv: It has a .sorted property that might help you.
[21:55] <jtv> allenap: but the breakage is entirely arbitrary and the test is wrong to depend on the ordering of a frozenset, right?
[21:56] <allenap> jtv: Yes. I assume I missed the ordering problem when changing getDirectSubscriptions recently.
[21:56] <jtv> help(frozenset) doesn't tell me anything about "sort"
[21:56] <allenap> jtv: BugSubscriptionSet is special :)
[21:56]  * jtv winces at that word
[21:57] <allenap> jtv: It's special in a nice way.
[21:57] <rvb> jtv: sure
[21:59] <jtv> rvb: I'm in the plenary room… want to come over or do you have a better spot?
[21:59] <rvb> I'll come over in just a sec
[22:02] <jtv> jcsackett: find anything interesting in the translated-projects code?
[22:03] <jcsackett> jtv: haven't actually had a chance to look at it, to be honest, but as i need a break from what i'm doing i'll take a look right now.
[22:03] <jtv> jcsackett: cool, thanks!
[22:09] <rvb> jtv: I'm sorry it's taking longer than I tought ... I'm working on a bug with Julian
[22:10] <jtv> rvb: no worries—I can also just go ahead and get it done, if you don't feel you'll get around to it.
[22:10] <poolie> is it a known bug about 'POST /+request-token' failing with 403?
[22:10] <poolie> or maybe this is my bug
[22:10] <StevenK> poolie: Is it POSTing to edge?
[22:12] <wgrant> matsubara: Is the oops thingy still broken, or just not caught up yet?
[22:12] <matsubara> wgrant, not caught up. almost there.
[22:13] <rvb> jtv: If you have other things to do right now, I'll be happy to be on you side while you fixe this bug really
[22:13] <jtv> rvb: plenty of things to do… maybe I'll just concentrate on the workaround first.
[22:13] <jtv> (I'll ask an admin to grant the required extra database permission first)
[22:14] <poolie> StevenK, yes it was
[22:14] <poolie> i've updated it but it still seems like a bug
[22:14] <wgrant> poolie: Ugh what?
[22:14] <wgrant> launchpadlib?
[22:14] <poolie> yes
[22:15] <wgrant> Ugh.
[22:15] <poolie> bug 704664
[22:15] <_mup_> Bug #704664: 403 on post to edge /+request-token <Launchpad itself:New> < https://launchpad.net/bugs/704664 >
[22:15] <matsubara> wgrant, it's available now
[22:16]  * bigjools has Launchpadlurgy
[22:16] <wgrant> matsubara: Indeed, thanks.
[22:16] <wgrant> bigjools: Already? :(
[22:16] <bigjools> already
[22:16] <bigjools> the Berocca is not quite doing the trick
[22:18] <jml> are you pumped?
[22:31] <jml> are we running the latest bzr-builder on our slaves?
[22:32] <jml> (also, how would I find out without asking here)
[22:38] <bigjools> jml: ask a buildd admin (ie lamont)
[22:38] <Ursinha> is it possible to set a merge proposal to a status other than "approved" or "rejected" using the email interface?
[22:39] <jml> hmm.
[22:39] <Ursinha> jml, I totally forgot you used to be a code guy
[22:39] <jml> Ursinha: heh
[22:39] <jml> Ursinha: actually, I have no idea. I just looked at https://help.launchpad.net/Code/Review#Email%20interface :)
[22:40] <Ursinha> jml, :) that page only has approve and reject
[22:41] <bigjools> jml: he's responsible for what's installed on the builders
[22:48] <jml> bigjools: ok, thanks.
[22:50] <lifeless> how do we tell if karma isn't updating?
[22:52] <wgrant> scriptactivity spam is spammy.
[22:53] <spm> it should be silent.....
[23:07] <sinzui> wgrant, https://bugs.launchpad.net/launchpad/+bug/697441
[23:07] <_mup_> Bug #697441: buildmailman fails under natty <build-infrastructure> <mailing-lists> <python-upgrade> <Launchpad itself:Triaged> < https://launchpad.net/bugs/697441 >
[23:40] <allenap> lifeless: https://wiki.canonical.com/Launchpad/Strategy/DesignDiscussionDallas2011
[23:51] <wgrant> gmb: bin/kill-test-services
[23:52] <gmb> wgrant: Ooh, that's a start. Ta.
[23:52] <wgrant> Also, the librarian fixture branch that someone should be landing soon.
[23:56] <gmb> wgrant: Bum. No, that didn't help any. I'll leave it for now; I'm going square-eyed. Thanks anyway.