[00:29] <LPCIBot> Project db-devel build (62): STILL FAILING in 4 hr 4 min: https://hudson.wedontsleep.org/job/db-devel/62/
[00:40] <wallyworld> thumper: found problem :-)
[00:40]  * wallyworld does happy dance
[01:25] <thumper> wallyworld: awesome
[01:27] <wallyworld> thumper: how's your stuff?
[01:31] <thumper> wallyworld: well, I've figured a way to at least stop the worst error
[01:31] <thumper> but thinking about better error handling
[01:31] <thumper> rob had an idea but I had to cut him short as I had someone arrive
[01:32] <thumper> but I think it is more of a future idea
[01:32] <lifeless> definitely
[01:32] <lifeless> way out there stuff
[01:32] <wallyworld> perhaps error handling patterns need to be looked at across the codebase, maybe unify any disparate implementations to use "best practice"
[01:33] <thumper> so...
[01:33] <thumper> I'm going to go for the nicer simple fix that avoids the crappy error message
[01:34] <thumper> possibly get that RCed into the branch we want to release
[01:34] <wallyworld> my thoughts were blue sky, future stuff
[01:34] <thumper> and move on to looking at the BranchRevision use cases
[01:34] <wallyworld> just thinking out loud
[01:34] <thumper> suer
[01:34] <thumper> sure
[01:36] <lifeless> wallyworld: refactoring +1; best practice mmm I prefer to say 'this works well, and let folk adopt it' - the poppendiecks had a quote about best practice - that it stops improvement & experimentation
[01:36] <wallyworld> "best practice" to me is defined to be whatever a particular project says it is
[01:37] <wallyworld> what whatever error handling patterns are deemed to work best for lp/bzr, they should be adopted more or less uniformly IMHO
[01:37] <spm> "best practice" to me, is often a fallacy ;-) http://www.nizkor.org/features/fallacies/appeal-to-common-practice.html
[01:38] <wallyworld> ok, so i hit a nerve with the bullshit bingo, overused cliche "-)
[01:38] <spm> :-P
[01:38] <wallyworld> all i meant was, i think we need, if not already there, a set of well defined patterns for various "things" that people are encouraged top adopt
[01:39] <wallyworld> :-P right back at ya
[01:39] <spm> heh
[01:42] <lifeless> wallyworld: we don't have uniform situations, so uniform handling doesn't make sense.
[01:43] <lifeless> wallyworld: documenting things that work well so that folk can use them is a good idea.
[01:43] <wallyworld> hmmm, not sure i agree about the lack of uniformity
[01:44] <lifeless> wallyworld: I'd like to reduce some of the variation we have because there is cognitive overhead there - I mean things like some bits being in twisted, some zope, some pop, some wsgi
[01:44] <wallyworld> +1
[01:45] <wallyworld> also, as a new person, i've found several ways to do stuff, i pick one, and people say "oh don't do it that way, that's bad"
[01:46] <wallyworld> i've need to get some of these new starter ramp up issues documented. it's on my todo list
[01:47] <lifeless> wallyworld: when someone says that, it may come from a couple of places
[01:47] <lifeless>  * stylistic thing - our code review looks at a lot of irrelevant stuff we should just ditch, IMO.
[01:47] <lifeless>  * functional issues - in which case the place you copied from needs fixing / and XXX would be appropriate.
[01:47] <lifeless>  * maintenance issues - ditto
[01:49] <wallyworld> one that comes to mind is design patterns used in "answers" - so not just simple stylistic stuff, but more substantial, legacy implementation issues
[01:51] <lifeless> sure, that would fit under 'maintenance issues' above, do you think?
[01:52] <wallyworld> yeah, suppose so, a form of technical debt
[01:53] <stub> spm: Can you please kick off a staging update? I've swapped the database we built on the weekend into place.
[01:53] <spm> stub: sure
[02:11] <lifeless> stub: so, cassandra, you know if you're going to stay for the extra days or not, yet ?
[02:12] <stub> lifeless: I don't think I can make it at all with the travel time :-(
[02:12] <lifeless> ok
[02:13] <lifeless> I'll book my tickets today/tomorrow then
[02:13] <lifeless> stub: perhaps we can get a video feed of the training for you
[02:13] <lifeless> or a DVD or something
[02:13] <stub> If we can, that would be cool for more people than just me
[02:13] <lifeless> indeed
[02:37] <stub> We are now on 2.6 everywhere? I have a 2.5 compatibility fix I'd rather not land.
[02:38] <stub> I'm not sure of the status of our last buildbots
[02:39] <lifeless> spm: ^
[02:39] <lifeless> stub: the db's are
[02:39] <lifeless> stub: like you I'm unsure of buildbot status; there was a zomg rt ticket about it
[05:33] <thumper> is devel shut off for landings?
[06:31] <lifeless> jml: I've fixed loading/running of story tests in testr. mp coming soon
[06:31] <poolie> lifeless: i put up a testscenarios mp
[06:33] <lifeless> thanks
[06:36] <stub> thumper: Any reason the revision karma allocater is a separate script rather than part of garbo?
[06:36] <lifeless> stub: no good reason
[06:36] <lifeless> stub: garbo was underadvertised
[06:42] <lifeless> jml: https://code.edge.launchpad.net/~lifeless/launchpad/doctest/+merge/38182
[06:43] <stub> lifeless, thumper: https://code.edge.launchpad.net/~stub/launchpad/bug-658124-revision-karma/+merge/38181 as it is, or I can move it to garbo after lunch. Might prefer as it is for rc?
[06:45] <lifeless> as is for rc
[06:48] <lifeless> stub: rc-reviewed. please let edwin know.
[06:48] <lifeless> stub: I've code reviewed too, though ec2land won't find it because I can only have one vote.
[06:49]  * thumper looks
[06:50] <lifeless> stub: I'm curious why 2 queries are needed though, seems like a pg regression ?
[06:51] <stub> Its one query assembled in two parts
[06:52] <stub> http://paste.ubuntu.com/511378/ is the query I wanted, but this was the closest we could get with storm (and performs identically)
[06:54] <lifeless> stub: ah, I see.
[06:55] <lifeless> still seems weird to need to move the limit inside the exists; I would have expected pg to optimise ;)
[06:55] <stub> By putting the limit inside, I'm requesting <= limit rows. If I put it outside, I get == limit rows.
[06:56] <stub> limit then filter dupes vs. filter dupes then limit
[06:58] <lifeless> anyhow, its faster. woo.
[07:41] <wgrant> The Debian BTS sync is working again?
[07:57] <StevenK> wgrant: I thought I heard a mumbling about it being turned on again, but I'm not sure
[09:08] <jml> lifeless: cool.
[09:08] <jml> lifeless: I'll check it once my inbox is empty. (soon now)
[09:33] <LPCIBot> Project db-devel build (63): STILL FAILING in 4 hr 8 min: https://hudson.wedontsleep.org/job/db-devel/63/
[09:38] <mrevell> Morning
[09:41] <jml> mrevell: hi
[09:52] <nigelb> wedontsleep.org - ha!
[09:53] <nigelb> StevenK: the caffine link is a nice touch :p
[10:06] <persia> StevenK, And you've two dead links on the page...
[10:06] <StevenK> Indeed
[10:08] <nigelb> "Way cheaper than a trip to Starbucks, Foosh Energy Mints are heavily caffeinated for an energy boost that takes effect quicker than monkeys chomp cheese. And they taste great! Try some now! Each mint contains more than 100 milligrams of caffeine...Wow" - RIGHT
[10:11] <persia> Clearly the authors of that slogan have never seen monkeys trying to explain to the stupid humans involved that cheese smells rotten (which humans call "having sophisticated tastes")
[11:17] <bigjools> does anyone know if it's possible to test that some code did a commit()?
[11:20] <lifeless> bzr or db commit?
[11:20] <bigjools> db
[11:20] <lifeless> the commit is seen by the storm tracer
[11:20] <bigjools> do we have any examples that you know of?
[11:21] <lifeless> I think so, possibly using the test tracer (rather than the webapp.adapter tracer)
[11:21] <lifeless> but 2321, I'm not going to try and find the example right now ;P
[11:21] <bigjools> see you in 6 hours then :)
[11:22] <lifeless> hah :P
[11:22] <bigjools> are you at UDS >
[11:22] <bigjools> ?
[11:23] <lifeless> I will be
[11:23] <lifeless> its 2 weeks from now
[11:23] <bigjools> yeah I know, I'm going too
[11:23] <lifeless> we'll have to have a beer ;)
[11:23] <bigjools> the magic word
[11:26] <bigjools> if I run "bin/test test_builder" I get circular import errors.  If I run "bin/test -t test_builder" I don't.  WTF.
[11:28] <wgrant> bigjools: I see that sometimes too, eg. -m lp.archivepublisher fails with an SPPH circular import.
[11:28] <bigjools> yes
[11:29] <bigjools> I think it's because lp.bugs is importing SPPHG
[11:29] <bigjools> SPPH
[11:29] <bigjools> which is wrong on many levels
[11:29] <wgrant> Well, I suspect c.l.d is involved too.
[11:30] <bigjools> which is wrong on many levels
[11:30] <wgrant> Heh.
[11:31] <wgrant> True.
[11:31] <bigjools> the Code guys solved this problem but I can't remember how - to get rid of c.l.{i,d} we need to make the API stuff see all the interfaces
[11:31] <wgrant> It's easy enough.
[11:31] <wgrant> Add a webservice module somewhere in your tree, import stuff into there.
[11:31] <wgrant> Then add the <webservice blah blah> ZCML pointing to that module.
[11:32] <bigjools> that's the badger
[11:32] <wgrant> That's more c.l.i than c.l.d, though, I think.
[11:32] <bigjools> btw the new buildd-manager is on DF
[11:32] <bigjools> seems to work :)
[11:32] <wgrant> The OMFG-5KLOC-DIFF one?
[11:32] <bigjools> 6k, yes
[11:32] <wgrant> Ah, it was only 4K when I last looked.
[11:33] <wgrant> I didn't extrapolate far enough :P
[11:33] <bigjools> bzr di -r submit:|wc -l
[11:33] <bigjools> 6286
[11:34] <wgrant> Owww.
[11:34] <wgrant> Hmm.
[11:34] <bigjools> as jml pointed out we should have started at the top instead of the bottom (wrapping calls in maybeDeferred) and we could have landed stuff sooner
[11:34] <wgrant> 2 hour downtime with a day's notice? :(
[11:39] <wgrant> bigjools: DistroSeries.checkLegalPocket refuses to publish binaries in non-Release pockets for a Development series (but Frozen is allowed). This seems fairly strange.
[11:39] <wgrant> I can't see a good reason for it.
[11:39] <bigjools> why would you need to do that?
[11:40] <wgrant> Well, I hit it in tests, but Ubuntu frequently uses -proposed and -security before release.
[11:40] <wgrant> It just happens to work now because the series is usually frozen beforehand.
[11:40] <bigjools> why would they do that when they can upload to -release?
[11:41] <wgrant> bigjools: It is desired that the Release pocket matches the images.
[11:41] <bigjools> then it should be frozen, no?
[11:41] <wgrant> And it's handy to get a head-start on SRUs by uploading to -proposed beforehand.
[11:41] <wgrant> True.
[11:42] <wgrant> But it seems odd to allow uploads to more when a series is frozen than when it's open.
[11:42] <bigjools> seems perfectly cromulent to me
[11:42] <wgrant> Still, the whole Frozen-as-a-status thing is crackful.
[11:43] <bigjools> why?
[11:46] <wgrant> I'm not entirely sure. It just doesn't seem right to have the series bouncing between Development and Frozen, particularly since we have other statuses (Future, Experimental) which don't have obvious freeze semantics.
[11:46] <wgrant> I think it would be nicer if there was a separate field for that.
[11:46] <wgrant> But anyway.
[11:46] <wgrant> My tests now work around the crazy restriction -- just thought it was a bit strange.
[11:47] <wgrant> (I'm fixing that hack I introduced last week, and making the related publisher tests more thorough and less sucky)
[11:47] <wgrant> (and removing the whole architecture[:7] madness)
[11:50] <bigjools> great
[12:02] <deryck> Morning, all.
[12:48] <maxb> How is RT 41738 ("lpbuildbot needs a Lucid production buildslave") going?
[12:49] <maxb> I was wondering if launchpad-database-dependencies could require strictly pg8.4 yet
[12:49] <wgrant> That seems like it sort of has to happen before Thursday...
[13:07] <jtv> bac discovered that Storm's sqlobject gets is_empty completely wrong.  Bug 659078.
[13:07] <_mup_> Bug #659078: sqlobject is_empty and __nonzero__ are incorrect <Storm:New> <https://launchpad.net/bugs/659078>
[13:11] <deryck> allenap, hi.  The kanban board seems to indicate Bug #650991 is qa-ok.  Is that right?
[13:11] <_mup_> Bug #650991: Add getSubscriptionsForBug to IStructuralSubscriptionTarget <qa-needstesting> <story-subscribe-to-search> <Launchpad Bugs:Fix Committed by allenap> <https://launchpad.net/bugs/650991>
[13:12] <allenap> deryck: There's one card remaining which I should probably QA on staging.
[13:12] <deryck> allenap, ah, ok.  Thanks.
[13:14] <jkakar> Are pop-ups (like to assign a bug or request a review) broken for other people on edge?  I consistently get 'Loading results failed.' and it's been this way for a few days.
[13:24] <jml> I agree w/ wgrant, I think. It would be good to have the control for what package uploads are allowed separate from status
[13:36] <bigjools> jml: we need to enumerate the pros and cons for that.  I'm neutral at the moment.
[13:39] <allenap> jkakar: Everything seems to be working fine here. Is anything else dumped to the js console?
[13:40] <jkakar> allenap: Let me check.
[13:40] <wgrant> Several people have seen timeouts in the person picker since the 8.4 migration.
[13:42] <wgrant> I wish a-f would return an error code upon encountering an error.
[13:42] <wgrant> Rather than just continuing and indicating success...
[13:43] <jkakar> allenap: Getting '503 Service Unavailable' when I try to search for 'jtv', to assign a bug, at https://bugs.edge.launchpad.net/storm/+bug/659078
[13:43] <_mup_> Bug #659078: sqlobject is_empty and __nonzero__ are incorrect <Storm:Fix Committed> <https://launchpad.net/bugs/659078>
[13:44] <allenap> jkakar: Ah, see wgrant's comment above. Time-outs it seems.
[13:45] <jkakar> allenap: It's really bad right now, I haven't been able to assign a bug or request a review for days. :/
[13:45] <jkakar> I've been using /+request-review on merge proposals.  Is there an equivalent for assigning bugs?
[13:46] <wgrant> jkakar: Expand the expandy thing with the button on the left of the task.
[13:46] <jkakar> wgrant: Ah, right, thanks.
[13:47] <allenap> jkakar: That's really bad. I haven't experienced anything nearly that bad. Are the problems consistent with other browsers?
[13:48] <jkakar> allenap: Dunno, just been trying in Firefox.
[13:48]  * jkakar tries with Chromium
[13:50] <jkakar> allenap: Same in Chrome.  I wouldn't expect the browser to make a difference though, given that it's a timeout on the server side.
[13:50] <allenap> jkakar: Oh, of course. Do you get an OOPS?
[13:51] <jkakar> allenap: Not obviously, just a message that says 'Loading results failed.' in red, in the person or branch picker dialog.
[13:52] <wgrant> jkakar: Firebug might be helpful.
[13:52] <wgrant> Since the JS isn't.
[13:52] <allenap> jkakar: Gah, bloody javascript!
[13:53] <allenap> (*Our* javascript; I don't mean to malign javascript in general.)
[13:53] <jkakar> wgrant: Yeah, I tried Firebug (how I discovered it was returning 503).  Didn't see anything obvious about OOPSes.
[13:53] <wgrant> jkakar: There's no X-Lazr-Oops response header?
[13:53] <jkakar> allenap: Javascript deserves some amount of general maligning.  It's too bad it's taking over the world and that, in 5 years, we'll be writing server code in it. :/
[13:53] <wgrant> It's sometimes there.
[13:53]  * jkakar looks more closely
[13:54] <jkakar> wgrant: Hah, now that I try again it's working. :/
[13:54] <wgrant> Awesome.
[14:58] <allenap> sinzui: Have you heard of any situations where a deactivated mailing list can't be reactivated? This is with regard to the last three comments in https://answers.edge.launchpad.net/malone/+question/58912
[14:59] <sinzui> allenap, yes, when the team is renamed, the list and it's email address are invalidated.
[15:00] <allenap> sinzui: Is there any way to know if a team has been renamed, or shall I just ask the user?
[15:00] <sinzui> allenap, I am not certain if a losa needs to delete mailman/monharc files or not but It would be mentioned in lphowto on the canonical wiki
[15:00] <sinzui> we would need to ask the user
[15:00] <allenap> sinzui: I'll do that. Thanks.
[15:02] <sinzui> allenap, actually, this team cannot be renamed because the existing list has not been purged
[15:03] <allenap> sinzui: Ah. Okay, I'll leave this one in the hands of the LOSAs then.
[15:11] <LPCIBot> Project devel build (103): STILL FAILING in 3 hr 46 min: https://hudson.wedontsleep.org/job/devel/103/
[16:10] <sinzui> EdwinGrubbs, bug 645702 is qa-ok. I think the registry is ready for release
[16:10] <_mup_> Bug #645702: oops in holdMessage storing large message  <mailing-lists> <oops> <qa-ok> <Launchpad Registry:Fix Committed by sinzui> <https://launchpad.net/bugs/645702>
[16:12] <EdwinGrubbs> sinzui: I'm still waiting on getting the cronscript run on staging for the job queue I added, but the web page didn't timeout when approving a bunch of proposed members, so it's looking good.
[16:14] <sinzui> Edwin and keep in mind that staging is super slow. Loading /gdp timed out 3 times.
[16:20] <EdwinGrubbs> jtv: ping
[16:20] <jtv> EdwinGrubbs: yes?
[16:21] <jtv> EdwinGrubbs: you called?
[16:21] <EdwinGrubbs> jtv: are you able to QA bug 650877?
[16:21] <_mup_> Bug #650877: Not generating TranslationTemplatesBuilds on staging <qa-needstesting> <Launchpad Translations:Fix Committed by jtv> <https://launchpad.net/bugs/650877>
[16:22] <jtv> EdwinGrubbs: if staging is finally running…  it's not been possible yesterday, or today during working hours.
[16:22] <EdwinGrubbs> jtv: staging is up
[16:22] <jtv> Then I'll try it.
[16:23] <EdwinGrubbs> allenap: ping
[16:23] <allenap> EdwinGrubbs: pong
[16:23] <allenap> Ah, okay, staging.
[16:23] <EdwinGrubbs> allenap: can you QA bug 650991?
[16:23] <_mup_> Bug #650991: Add getSubscriptionsForBug to IStructuralSubscriptionTarget <qa-needstesting> <story-subscribe-to-search> <Launchpad Bugs:Fix Committed by allenap> <https://launchpad.net/bugs/650991>
[16:23] <allenap> EdwinGrubbs: Sure.
[16:25] <EdwinGrubbs> lifeless: ping
[16:30] <mars> gary_poster, do we now know when we will officially be done with Python 2.5?
[16:31] <mars> gary_poster, and we can start writing Python 2.6 code? :)
[16:32] <gary_poster> mars, yes, earlier this morning.  I'm going to submit a branch to make sure that the setup is working, but everything here is Lucid: https://lpbuildbot.canonical.com/waterfall
[16:32] <mars> \o/
[16:32]  * mars cues the marching band!
[16:32] <gary_poster> :-)
[16:35] <jml> and we are 100% lucid on prod?
[16:36] <gary_poster> yes, jml.  that's what losas tell me. :-)
[16:36] <gary_poster> and stub
[16:36] <sinzui> allenap, is https://bugs.edge.launchpad.net/malone/+bug/551848 fix released or in progress?
[16:36] <_mup_> Bug #551848: X-Launchpad-Bug link on +subscribe pages links to wrong page <qa-ok> <trivial> <ui> <Launchpad Bugs:Fix Committed> <https://launchpad.net/bugs/551848>
[16:36] <jml> gary_poster: wonderful :)
[16:36] <gary_poster> definitely
[16:37] <jml> what are we doing on production for the psycopg thing?
[16:38] <gary_poster> an older version is the only option AFAIK.  stub will be working on the proper fix as one of his upcoming tasks.  Would you like me to verify with losas, jml?
[16:38] <jml> gary_poster: no, that's fine, just curious.
[16:38] <gary_poster> cool
[16:39] <jml> I guess the versioning/"can't install lp-deps" problems really only hit maverick.
[16:50] <allenap> sinzui: It says Fix Released, but why is there doubt?
[16:50] <allenap> s/Released/Committed/
[16:51] <sinzui> allenap, look at the date? The code from that date was released last month
[16:51] <sinzui> So did we release the fix, or should it be targeted to 10.10
[16:52]  * allenap looks.
[16:54] <allenap> sinzui: It's released. I've marked it as such and put it in the 10.09 milestone.
[16:54] <sinzui> thank allenap
[16:57] <abentley> james_w: I understand there was a bug related to nest-part/manifests in bzr-builder recently.  Is the fixed version in the PPA?
[16:58] <james_w> abentley, the bzr-builder ppa? yes.
[16:58] <abentley> james_w: great, thanks.
[16:58] <james_w> 0.6
[17:07] <maxb> james_w: What would the ETA be on there being a working nest-part instruction in *-cat-lpbuildd ?
[17:07] <james_w> maxb, no idea, sorry
[17:07] <james_w> abentley would probably know better than I
[17:09] <abentley> maxb: I've just requested it.  You'd have to ask lamont for an actual ETA.
[18:29] <LPCIBot> Project db-devel build (64): STILL FAILING in 2 hr 19 min: https://hudson.wedontsleep.org/job/db-devel/64/
[18:51] <jml> g'night
[18:53] <bdmurray> james_w: do you know if there is way to find out from a bug task if some one is allowed to upload the associated source package?
[18:57] <james_w> bdmurray, yes there will be a way, but it won't be particularly direct I think
[18:58] <bdmurray> james_w: I'd want to end up at isSourceUploadAllowed()?
[18:59] <james_w> bdmurray, ubuntu-archive-tools has an implementation of this, but I think IArchive.checkUpload might do it all now
[18:59] <james_w> bdmurray, I think, confusingly, that only takes in to account packagesets
[19:00] <james_w> bdmurray, http://bazaar.launchpad.net/~ubuntu-archive/ubuntu-archive-tools/trunk/annotate/head:/sync-helper.py#L67
[19:02] <bdmurray> james_w: okay, I'm trying to allow people to set milestones in Launchpad
[19:02] <james_w> bdmurray, ah, you are talking about inside the LP codebase?
[19:02] <fjlacoste> sinzui: hi!
[19:03] <bdmurray> james_w: right
[19:03] <sinzui> hi fjlacoste
[19:03] <james_w> bdmurray, in that case then checkUpload or verifyUpload or something is probably where you want to start looking
[19:04] <james_w> bdmurray, also look for lp.code's permission checking on package branches, as they have a similar need
[19:04] <jtv> Can anyone else push to staging codehosting?
[19:04] <bdmurray> james_w: okay, thanks!
[19:04] <james_w> bdmurray, it's complicated by having to deal with components etc., but you should be able to get close to "if this person uploaded a source package of that name to the current distroseries would it be rejected?"
[19:05] <james_w> bdmurray, I don't know if you want to deal with released series differently there
[19:42] <lifeless> losa ping
[19:44] <lifeless> I want to put a new feature rule on staging (for QA)
[19:45] <lifeless> hard_timeout pageid:BugTask:+index 1 5000
[20:30] <lifeless> gary_poster: ping
[20:30] <gary_poster> hey lifeless
[20:30] <lifeless> up for a brief call ?
[20:31] <gary_poster> lifeless, in 45 min ok with you?
[20:31] <lifeless> won't you be on a call with flacoste then ?
[20:31] <lifeless> (I mean, it would be ok for me)
[20:31]  * gary_poster though flacoste was out today
[20:31]  * gary_poster checks calendar
[20:31] <flacoste> gary_poster: i'm in :-)
[20:32] <gary_poster> :-) ok
[20:32] <gary_poster> lifeless: ok, we'll try again later; I'm stepping out in about 3 minutes though, and don't want our call to be *that* short :-)
[20:32] <lifeless> ok
[20:47] <EdwinGrubbs> lifeless: can you QA bug 627701?
[20:47] <_mup_> Bug #627701: Make it possible to use feature flags to override the global timeout for specific pages <qa-needstesting> <Launchpad Foundations:Fix Committed by lifeless> <https://launchpad.net/bugs/627701>
[20:47] <lifeless> EdwinGrubbs: see my losa ping above
[20:48] <lifeless> EdwinGrubbs: (no, *I* can't, needs a losa)
[20:48] <EdwinGrubbs> ok, thanks for getting the ball rolling.
[20:48] <mbarnett> lifeless: hello.  just got back from snacking
[20:49] <mbarnett> lifeless: so, new feature rule..
[20:51] <lifeless> mbarnett: yeah
[20:51] <lifeless> mbarnett: https://staging.launchpad.net/+feature-rules
[20:52] <mbarnett> lifeless: added
[21:09] <lifeless> gary_poster: hey, so whenever you want to chat, just ping me. I'm doing food now, then will be looking at parallel testing more.
[21:09] <gary_poster> cool thanks lifeless
[21:10] <rockstar> Woo! Four more windmill tests before a new lazr-js is ready!
[21:10] <lifeless> mbarnett: thanks was otp
[21:11] <lifeless> I'm trying now :)
[21:11] <mbarnett> lifeless: cool.
[21:11] <lifeless> great, the timeout is way low.
[21:11] <lifeless> please remove that rule now, or staging will be useless ;)
[21:22] <wallyworld> abentley rockstar thumper: standup?
[21:23] <thumper> wallyworld: aye
[21:23] <thumper> wallyworld: isn't it 6:30 where you are?
[21:23] <wallyworld> yeah, but i have to go to a breakfast at the kid's school
[21:24] <thumper> heh
[21:24] <thumper> breakfast at school?
[21:24] <wallyworld> there's a middle school orientation thing - he's going into grade 5 next year
[21:24] <abentley> wallyworld, thumper: sure.
[21:25] <lifeless> flacoste: oh, there was one thing
[21:25] <lifeless> flacoste: this ppa/open teams thing.
[21:25] <flacoste> lifeless: yep
[21:28] <lifeless> there seems to be a knee-jerk reaction happening, which is a bit unpleasant
[21:28] <lifeless> thats really all I had to say
[21:43] <rockstar> abentley, thumper, wallyworld, you guys still can't hear me, can you?
[21:43] <rockstar> Shite.
[21:43] <rockstar> abentley, that's because I'm messing with the gain.
[22:09] <lifeless> does stable still have test failures?
[22:29] <flacoste> thumper: i'm available
[22:29] <thumper> flacoste: just getting off with jam
[22:29] <lifeless> thumper: oh laa
[22:30] <mwhudson> ...
[22:35]  * lifeless guesses gary_poster is free now ;P
[22:44] <EdwinGrubbs> Ursinha-afk: ping
[22:48] <jcsackett> is there an easy way to set a projectgroup for launchpad.dev?
[23:11] <wgrant> jcsackett: /projectgroups/+new?
[23:14] <jcsackett> wgrant: and this is what i get for juggling too many things at once on too little sleep. thanks for pointing out the obvious.
[23:16] <wgrant> jcsackett: It's not exactly obvious any more, since it's no longer visible to normal users.
[23:16] <jcsackett> wgrant: that's what confused me. i saw the help state that you had to get an lp team member to do it, and assumed script.
[23:17] <jcsackett> didn't think about the fact that an lp member has different permissions on the site and could do it from there.
[23:17] <wgrant> Heh.
[23:26] <wgrant> bdmurray: Can you share code with the thing that allows uploaders to do release targetting?
[23:26] <wgrant> bdmurray: That code is wrong (doesn't take into account packageset permissions for teams, or something like that), but it should probably be shared.
[23:28] <lifeless> thumper: I'd like a chat when you have a few minutes
[23:28] <lifeless> thumper: not urgent, doesn't need to interrupt anything.
[23:29] <bdmurray> wgrant: I was looking at BugTask.userCanEditMilestone and _userIsPillarEditor but didn't get very far
[23:30] <wgrant> bdmurray: There's a reason I gave up on fixing that myself, I presume.
[23:31]  * wgrant looks.
[23:31] <wgrant> bdmurray: The current magic is BugNomination.canApprove.
[23:32] <bdmurray> wgrant: Isn't a nomination for a series not a milestone?
[23:32] <wgrant> Most of the logic should probably be moved onto a method on BugTask, with canApprove just checking if the user can edit any relevant BugTasks.
[23:32] <wgrant> bdmurray: Yes, but duplicating that code would be insane.
[23:34] <wgrant> bdmurray: So it looks like you want to call distribution.main_archive.verifyUpload
[23:34] <wgrant> Not checkUpload.
[23:35] <thumper> lifeless: I've got time now if you want to talk
[23:44] <maxb> Can someone tell me the current status of https://rt.admin.canonical.com/Ticket/Display.html?id=41738 ("lpbuildbot needs a Lucid production buildslave")
[23:44] <maxb> ?
[23:45] <lifeless> https://code.launchpad.net/~bzr/bzr-history-db/trunk
[23:45] <lifeless> maxb: resolved
[23:46] <maxb> yay
[23:46]  * maxb unholds the meta-lp-deps pg8.4 MP
[23:48] <maxb> jelmer: If you have a moment, could you nudge https://code.edge.launchpad.net/~maxb/meta-lp-deps/pg8.4/+merge/32200 to Approved now?
[23:54] <jelmer> maxb: otp, will have a look when I get back
[23:55] <wgrant> Ooh, buildd-slavescanner.txt has finally been killed \o/