[00:32] <mwhudson> woohoooo inbox zero
[00:39] <jml> mwhudson, grats
[00:50] <lifeless> is there any chance we could get rid of the 'no new merge proposal while one is outstanding' limit of code reviews?
[00:51] <lifeless> I'm having to lie to the system at the moment
[00:53] <jml> lifeless, perhaps...
[00:54] <lifeless> so my work flow is
[00:54] <jml> lifeless, what are you trying to do?
[00:54] <lifeless> hack on a branch a lot
[00:54] <lifeless> send of bits to be reviewed when I stop
[00:54] <lifeless> like this morning, did an hour on the test suite
[00:54] <lifeless> sent it off
[00:54] <lifeless> code-reviews complained at me that there was a MP already open
[00:54] <lifeless> so I go to that MP https://code.edge.launchpad.net/~lifeless/bzr/test-speed/+merge/10720
[00:55] <lifeless> tell it its merged (its not, just approved)
[00:55] <lifeless> http://pqm.bazaar-vcs.org/ is busy merging it
[00:55] <lifeless> then send in my new mp
[00:55] <lifeless> https://code.edge.launchpad.net/~lifeless/bzr/test-speed/+merge/10775
[00:55] <jml> I see.
[00:56] <jml> sounds not entirely dissimilar to a race condition
[00:56] <lifeless> with BB we just said 'send -r -2..'
[00:58] <jml> hmm.
[00:58] <jml> putting the constraint on branches, rather than on, say, revision ids, seems to be the mistake here.
[01:00] <lifeless> I think its fluid
[01:01] <lifeless> but yes, thats part of the thing driving the issue
[01:02] <lifeless> If I were to put it as a use case, it would be: 'a cherry pick merge submission sent while an earlier submission on the same branch is active should be accepted and shown separately'
[01:02] <lifeless> hmm
[01:02] <lifeless> two scenarios actually
[01:02] <lifeless> the second is
[01:02] <lifeless> 'a merge subission sent while an earlier submission on the same branch is active adds to that (or resubmits automatically?) rather than being rejected'
[01:15] <lifeless> jml: ^ what to do with this
[01:16] <jml> lifeless, sorry, the phone rang...
[01:16] <jml> brain occupied at present :)
[01:22] <spiv> jml: yes, I agree, I mentally think of merge proposals as being for revisions not branches (as branches can change, but the diffs (and reviews!) don't automatically change with them).
[01:22] <wgrant> Diffs will start changing soon, won't they?
[01:22] <thumper> wgrant: yes
[01:22]  * mwhudson lunches
[01:22] <lifeless> spiv: the followon changes can either be an extension (fixups) or new (different change)
[01:22] <spiv> jml: and I've also wanted what I think lifeless is asking for here, to be able to file a series of merge proposals off one branch.
[01:23] <lifeless> I'd be wary of keying too closely into revision id
[01:23] <spiv> lifeless: agreed.
[01:23] <lifeless> spiv: uick call?
[01:23] <spiv> lifeless: sure
[01:24] <spiv> I'd be happy for LP to make it obvious that there are more revs since the diff was generated, for instance.
[01:24] <spiv> And for LP to make it easy to refile for the new revs.
[01:26] <binarymutant> is this the right irc channel for mailing list administration?
[01:26] <jml> it's close enough :)
[01:27] <binarymutant> jml, my loco is having problems with it's list :(
[01:27] <binarymutant> we can't access it
[01:32] <jml> what's actually happening?
[01:34] <wgrant> binarymutant: Aren't LoCo mailing lists on lists.ubuntu.com?
[01:34] <wgrant> Launchpad has nothing to do with lists.ubuntu.com.
[01:34] <binarymutant> ty for the info wgrant :)
[01:35] <wgrant> Maybe #canonical-sysadmin, but I'm not sure.
[01:35] <wgrant> Or #ubuntu-locoteams.
[01:35] <binarymutant> thank you
[02:30]  * mwhudson reappears
[02:31] <mwhudson> spm: hello
[02:31] <spm> mwhudson: heyo
[02:32] <mwhudson> spm: can i get you to run some queries?
[02:32] <spm> mwhudson: only if you use the magic word
[02:33] <mwhudson> spm: select count(*) from codeimport where git_repo_url like '%sourceforge%';
[02:33] <mwhudson> spm: please
[02:33] <spm> bzt. wrong. word is "NOW!!!!" :-)
[02:33] <mwhudson> :)
[02:50] <jml> sinzui, you around?
[02:50] <sinzui> I am
[03:47] <wgrant> Does anybody else find 3.0 text to be very squished? It's all a lot closer together and less readable than 2.0.
[03:50] <jml> wgrant, it's hard for me to say, since Firefox 3.5 seems to have different font behaviour to Firefox 3
[03:50] <jml> got a couple of URLs to compare and contrast?
[03:53] <wgrant> jml: Look at the comment at https://code.edge.launchpad.net/~wgrant/launchpad/structural-subscription-security/+merge/10776/comments/28159/+reply. But it affects non-monospaced text as well.
[03:53]  * wgrant finds a good example.
[03:56] <wgrant> (does anybody want to land that branch for me, since gary_poster's concerns are unfounded and he's gone?)
[03:57] <mwhudson> wgrant: sure
[04:01] <wgrant> mwhudson: Thanks.
[04:05] <jml> mwhudson, oh, and not having the actual failures in the buildbot failure emails :)
[04:06] <jml> kfogel, hello
[04:06] <kfogel> jml: hey
[04:06] <mwhudson> and in other news, if people could stop pushing over non lefthand parents to lp-dev-utils trunk...
[04:07] <kfogel> mwhudson: ?
[04:07] <wgrant> mwhudson: I noticed that going on in lazr.restful a lot.
[04:07] <mwhudson> kfogel: revno's of lp:lp-dev-utils are a bit useless
[04:07] <mwhudson> because people merge their branches by merging from trunk, then pushing over trunk
[04:08] <wgrant> It also results in "Merge from trunk" commits down the LHS of trunk.
[04:08] <mwhudson> right
[04:08] <kfogel> mwhudson: it's hard for most people to remain that conscious of the ins and outs of their vc system, I think.
[04:09] <jml> mwhudson, I don't recall doing that, but my sincere apologies if I did
[04:09] <mwhudson> jml: i don't think it was you
[04:25]  * mwhudson lays down the law on the mailing list
[04:27] <thumper> mwhudson: did you get the query run to see how many git imports from sourceforge we have?
[04:27] <mwhudson> thumper: yes
[04:27] <mwhudson> thumper: there were 11, i think i fixed all of them
[04:27] <thumper> mwhudson: cool
[04:27] <mwhudson> well, we had some where someone had requested the new form already
[04:34] <mwhudson> fscking bzrtools
[04:35] <jml> phew. all read.
[04:36] <jml> now I need to incorporate the "Build Branch to Archive" thread into the spec
[04:53] <mwhudson> wgrant: seeing as you were asking earlier: https://dev.launchpad.net/BuildEngineer
[04:53] <jtv> wgrant: right ho, I'm on it.
[04:54] <wgrant> jtv: Thanks.
[04:55] <jtv> wgrant: good thing we're in similar timezones!
[04:56] <wgrant> jtv: Indeed!
[04:57] <mwhudson> jtv: oh i meant to ask, have you been using staging codehosting over the last two weeks?
[04:57] <jtv> mwhudson: no
[04:57] <jtv> why?
[04:57] <jtv> (It can't be much longer than two weeks, but I'm sure it's been two)
[04:58] <mwhudson> jtv: because you were trying to use it when i left, and i was trying to fix it
[04:58] <mwhudson> wgrant: btw, do you have a commit message for https://code.edge.launchpad.net/~wgrant/launchpad/structural-subscription-security/+merge/10776? ?
[04:58] <mwhudson> (sorry got horribly distracted)
[04:59] <jtv> mwhudson: thanks for asking... there were some more problems, but those were clear from production logs so we could fix, cherrypick, and see that the problem was gone.
[04:59] <wgrant> mwhudson: I don't. Feel free to make something up, or convince me to.
[04:59] <mwhudson> jtv: the answer i was hoping for was "yes, we used staging codehosting a lot and it all worked fine"
[04:59] <jtv> wgrant: does that latest revision fix both failures?
[04:59] <jtv> mwhudson: sorry to disappoint!
[04:59] <wgrant> jtv: It does.
[05:00] <jtv> wgrant: great, I'll send it back in
[05:00] <jtv> nice little three-way series of conversations here...
[05:00] <mwhudson> wgrant: "move structural subscription security checking into the model code" ?
[05:00] <jml> mwhudson, wgrant: a thing I'd like (and might do myself), is write a simple script to make an ec2test submission given only the merge proposal URL.
[05:00] <wgrant> mwhudson: Sounds fine!
[05:00] <wgrant> jtv: Thanks.
[05:01] <wgrant> jml: That would be good.
[05:01] <wgrant> And public ec2test even better.
[05:04] <wgrant> mwhudson: Thanks for making that page public.
[05:15] <jml> mwhudson, do you want me to file bugs for any of the things I mentioned earlier re pain points?
[05:15] <mwhudson> jml: yes please
[05:25] <wgrant> jtv, mwhudson: Are both my branches happily ec2testing?
[05:25]  * jtv checks
[05:26]  * wgrant is about to vanish for a couple of hours.
[05:26] <jtv> wgrant: not detached yet, but still working
[05:26] <jml> heh "
[05:26] <jml> Moving to launchpad since lp-devel-infra project is deprecated.
[05:26] <jml> "
[05:26] <jml> https://bugs.edge.launchpad.net/launchpad-foundations/+bug/106936
[05:26] <mup> Bug #106936: daily review mails <email> <infrastructure> <Launchpad Foundations:Confirmed> <https://launchpad.net/bugs/106936>
[05:27] <wgrant> jml: Bah. Sounds like it needs reviving.
[05:27] <mwhudson> wgrant: the one i'm doing is
[05:27] <wgrant> jtv, mwhudson: Great, thanks.
[05:27] <mwhudson> wgrant: it's not detached yet, but nearly there
[05:28] <jtv> wgrant: mine just detached
[05:28] <jtv> mwhudson: race you!
[05:30] <jml> mwhudson, I've updated the BE wiki page with links to tags, and have moved a few bugs to be b-i tagged
[05:30] <mwhudson> jml: thank you
[05:30] <jml> mwhudson, I've probably let some junk through
[05:54] <jml> mwhudson, and now I've filed a large number of b-i bugs
[05:54] <mwhudson> jml: if only you could subscribe to a tag
[05:55]  * mwhudson is reading buildbot code, please send chocolate
[05:55]  * thumper sends mwhudson chocolate
[06:29] <jtv> wgrant: Jesus loves you, but He doesn't seem to care for your branch much.  Got the same failures. Did you push?  The test run was on 9235, not 9238, and that was right off the LP branch not off my copy.
[06:31] <wgrant> jtv: Huh.
[06:31]  * wgrant checks LP.
[06:31] <wgrant> jtv: I see 9238 on LP.
[06:31] <wgrant> jtv: Maybe you caught it before it was mirrored.
[06:32] <jtv> wgrant: hm, maybe...  Was some time after you pinged me though.  :(
[06:32] <wgrant> Strange.
[06:32] <jtv> I'll just try again.
[06:32] <wgrant> Thanks.
[06:34] <jtv> wgrant: ha!  That was an old email.  The new one is still running.
[06:34] <wgrant> jtv: Ahhh. That makes more sense.
[06:40] <thumper> \o/
[06:40] <thumper> finally!!!
[06:40] <thumper> got person-product active reviews working
[06:40]  * thumper goes back to the old failing pagetest
[06:46] <thumper> some reviewer is going to hate me
[06:46]  * thumper wanks the 2000 line review limit back
[06:46] <thumper> oops
[06:47] <thumper> typo
[06:47] <wgrant> hahaha.
[06:47] <thumper> damn muscle memory
[06:47] <thumper> my branch is getting bigish
[06:47]  * wgrant just got a 1400 line refactor branch down to 800ish.
[06:48] <wgrant> Meant replaying the revisions doing bzr mvs slightly differently, though :(
[06:48] <thumper> this branch fixes activereviews for people, and adds project, source package, distro source package and person product active reviews
[06:48] <wgrant> Impressive.
[06:48] <thumper> well
[06:49] <thumper> most of the new ones were pretty simple
[06:49] <thumper> most of the work is done in branch collection
[06:49] <thumper> one of jml's great ideas
[07:06] <jml> mwhudson, have you eod'd?
[07:07] <lifeless> thekorn: grats
[07:08] <lifeless> meh
[07:08] <lifeless> thumper: grats
[07:30] <mwhudson> jml: more or less
[07:30] <jml> mwhudson, ok.
[08:08] <thumper> lifeless: for
[08:08] <thumper> ?
[08:10] <lifeless> 15:48 < thumper> this branch fixes activereviews for people, and adds project, source package, distro source package and person product active reviews
[08:10] <jml> anyone here use dchroot a lot?
[08:10] <thumper> lifeless: ah, ok :)
[08:11] <jml> I have this problem where I constantly have to manually update my /etc/resolv.conf
[08:11] <jml> hmm
[08:11] <lifeless> jml: I have been known to
[08:11] <lifeless> jml: the one in the chroot?
[08:11] <jml> lifeless, right.
[08:12] <lifeless> what updates your external resolv.conf
[08:12] <lifeless> whatever that is, hook into that and write to your chroots
[08:13] <jml> NetworkManager
[08:13] <jml> hmm.
[08:20] <lifeless> jml: welcome to the house of fun
[08:20] <lifeless> la-de-la-de-da
[08:22] <jml> :)
[08:28] <adeuring> good morning
[08:29] <jml> hi
[08:31] <jml> adeuring, I've just started getting errors like these whenever I run any tests:
[08:31] <jml> There were 1 imports of names not appearing in the __all__.
[08:31] <jml> You should not import export_destructor_operation from lazr.restful.declarations:
[08:31] <jml>     canonical.launchpad.interfaces.hwdb
[08:31] <jml> adeuring, know anything about it?
[08:32] <lifeless> jml: version mismatch?
[08:32] <lifeless> jml: I'm thinking a change to lazr.restful that you don't have yet, to make that public.
[08:33] <jml> lifeless, lazr.restful is managed in buildout, and my buildout is up-to-date.
[08:34] <jml> which doesn't preclude a mismatch in some version controlled config file, of course.
[08:43] <adeuring> jml: as lifeless said: you are using an lod version of lazr.restful. I I landed a lazr.restful branch  that includes export_destrutcor_operation in __all__
[08:43] <adeuring> s/lod/old/
[08:44] <maxb> I've just seen lp-dev-utils mentioned for the first time on list. Is that something intrinsically Canonical-internal, or should it be public but isn't?
[08:47] <jml> ok, so it's _not_ in buildout
[08:47] <jml> adeuring, thanks
[08:47] <jml> maxb, it's in the process of being made public
[08:48] <jml> maxb, some stuff will be kept private
[09:16] <jml> bigjools, hi
[09:16] <bigjools> morning!
[09:16] <gmb> Morning peoples.
[09:16] <jml> gmb, good morning
[09:17] <jml> bigjools, I've got a bunch of stuff I'd like to chat with you about
[09:18] <bigjools> jml: sure thing
[09:18] <jml> bigjools, but I'm not sure I have brain left today
[09:19] <bigjools> jml: what time will you be back in your morning?
[09:19] <henninge> staging does not let me do QA ... ;(
[09:20] <henninge> it times out
[09:20] <jml> bigjools, UTC 21:30
[09:20]  * henninge is amazed what a little complaining can achieve ... ;)
[09:21] <bigjools> jml: heh, not sure *I'll* have brain left then.  Tell you what, I'll see how I feel tonight else I can get up early tomorrow
[09:22] <mrevell> Morning
[09:23]  * jml tries anyway
[09:23] <jml> I have a note that says ProductSeries.sourcepackages is buggy.
[09:23] <jml> I now want to slap myself for making notes like that.
[09:23] <bigjools> :)
[09:23]  * bigjools looks
[09:23] <jml> mrevell, g'day
[09:24] <bigjools> jml: my eyes are bleeding looking at it, and it's only 8 lines
[09:24] <jml> it's not that bad :)
[09:25] <jml> actually that reminds me.
[09:26] <jml> I have a branch that extracts out verify_acl's logic that works, modulo some easily-fixed error message differences
[09:26] <jml> there's still some more stuff I need to do on top of that, but it's a nice milestone.
[09:27] <bigjools> fab
[09:27] <jml> and it turns out that eyeblood stains wash out of carpet really easily
[09:27] <jml> bigjools, you said I should ask you on IRC why branches are associated with distro and not sourcepackage in breadcrumbs
[09:28] <bigjools> jml: indeed, and if only I could remember what I was thinking when I wrote that
[09:28] <jml> bigjools, ok. you can get back to me then :)
[09:29] <jml> bigjools, I was looking at the package navigation thread today (first time since I got back from leave) -- how's all that going?
[09:29] <bigjools> jml: somewhat underwhelmingly
[09:29] <bigjools> some pages I wanted to trash were apparently important to some people
[09:30] <jml> right, I saw you mention that you wanted to get a longer list of use-cases.
[09:31] <bigjools> right now I am going for the tactic of improving the pages we said we would and then coming back later with the removal questions
[09:31] <jml> bigjools, good plan.
[09:31] <bigjools> jml: so for the breadcrumbs, what are the relative pros and cons
[09:32] <jml> bigjools, sourcepackage is more consistent with the way product branches work
[09:33] <jml> bigjools, and it's more consistent with the code
[09:33] <jml> bigjools, but I don't find either of these to be compelling
[09:34] <gmb> Hmm. So, maybe pasting a huuuuuge list into an iharness session wasn't the best idea I've ever had.
[09:34] <jml> bigjools, you can also navigate from the sourcepackage to distro, distroseries, and distributionsourcepackage more easily
[09:34] <mac_v> hi... when a branch is created how do i make the branch private?
[09:34] <jml> (btw, lets rename SourcePackage)
[09:35] <bigjools> fuck yes
[09:35] <bigjools> jml: so, the breadcrumbs would look like -> Ubuntu/Karmic/source/branch ?
[09:36] <jml> bigjools, visually? I would have guessed "Ubuntu" -> "source in karmic" -> branch
[09:36] <bigjools> yeah
[09:36] <bigjools> one page that is under my heavy removal scrutiny is the SourcePackage page
[09:37] <jml> bigjools, currently it's Ubuntu -> 9.10 -> "hotwire" package
[09:37] <bigjools> and I don't want that to block on anything branch-related if it comes to it
[09:37] <bigjools> oh yeah there's a little debate about what to write for a distroseries title
[09:38] <bigjools> in my DSP page I use series.title.  it doesn't include the vesion, maybe it should
[09:38] <jml> bigjools, removing the SourcePackage page would probably not be a good thing for branches
[09:39] <bigjools> jml: it's a useless page :(  go look at one
[09:39] <jml> bigjools, https://code.edge.launchpad.net/ubuntu/karmic/+source/hotwire
[09:39] <bigjools> jml: how would one navigate to that page usually?
[09:40] <jml> bigjools, it's reached by the Code tab from a source package branch
[09:40] <bigjools> I wonder if I can add links to it in the new DSP page?  (example here: https://dogfood.launchpad.net/ubuntu/+source/amarok)
[09:40] <jml> bigjools, have you seen https://code.edge.launchpad.net/ubuntu/+source/hotwire
[09:41] <bigjools> yes
[09:41] <jml> good.
[09:42] <jml> bigjools, one of the rationales for linking branches to SourcePackages instead of DistributionSourcePackages was so that there'd be a relevant listing of branches in each cycle of Ubuntu development
[09:42] <jml> bigjools, maybe we can achieve this without a SourcePackage page
[09:42] <bigjools> yep
[09:42] <jml> bigjools, but it needs at least a little thought.
[09:43] <bigjools> one of the problems with the package navigation is that there's waaaay too many pages with info spread all over them
[09:44] <bigjools> it does need more thought
[09:44] <bigjools> we should get together with Curtis
[09:46] <jml> bigjools, indeed
[09:47] <bigjools> jml: coming to Europe soon?  you must be due, you haven't been here for a week :)
[09:47] <jml> bigjools, haha
[09:50]  * jml has to go now
[09:50] <jml> g'night all
[09:51] <bigjools> jml: g'night, and I think +1 for your suggestion on breadcrumbs
[09:51] <jml> cool.
[10:08] <jtv> wgrant: Jesus feels a lot better about your branch now than I thought earlier.  It's landed.
[10:08] <wgrant> jtv: Did you have some trigger for when I became unaway?
[10:09] <wgrant> Because I got that message about a second after my screen reattached.
[10:11] <jtv> wgrant: once Jesus gets involved, all bets are off.
[10:12] <jtv> (Have I pissed off enough people today yet?)
[10:12] <wgrant> jtv: Heh.
[10:12] <wgrant> jtv: Thanks for the landing.
[10:12] <bigjools> mrevell: will you be able to do this? https://bugs.edge.launchpad.net/soyuz/+bug/392239
[10:12] <mup> Bug #392239: [PPA] "Read about uploading" link doesn't go to the anchor bookmark #Uploading <ppa> <Soyuz:Triaged by matthew.revell> <https://launchpad.net/bugs/392239>
[10:13]  * mrevell looks
[10:14] <mrevell> bigjools: yes, no problem
[10:14] <bigjools> mrevell: super thanks
[10:14] <jtv> wgrant: no worries... the next task is Q/A.
[10:14] <wgrant> mwhudson: What happened to my other branch?
[10:15] <jtv> gmb, can I get you to Q/A wgrant's export-bug-nominations branch?
[10:15] <gmb> jtv: Sure; I can take a look in about half an hour if that's okay.
[10:15] <jtv> gmb: that'd be swell, thanks.
[10:17] <wgrant> jtv: We don't wait for edge?
[10:17] <jtv> wgrant: for actually performing Q/A, yes, you.  But gmb is having his first look in half an hour.
[10:18] <wgrant> jtv: OK.
[10:52] <gmb> jtv, wgrant: So, which branch is it I need to look at?
[10:52] <gmb> well, branch / commit / bug/ item on the QA page
[10:53] <jtv> gmb: lp:~wgrant/launchpad/export-bug-nominations will need QA when it shows up on edge.
[10:53] <gmb> Ok.
[10:57] <jtv> gmb: thanks.
[11:06] <deryck> Morning, all.
[11:16] <bigjools> hey deryck
[12:29] <gary_poster> wgrant: did you get someone to merge your structural-subscription-security branch?
[12:32] <wgrant> gary_poster: mwhudson started an ec2test of it several hours ago, and another of my branches started around the same time landed 2.5 hours ago, so I think something went wrong.
[12:33] <gary_poster> wgrant: ok.  yeah, I see your other one.  probably should wait for feedback to you from Michael then.
[12:34] <wgrant> gary_poster: Yep, I'll hopefully find something out tomorrow.
[12:34] <gary_poster> ok cool
[12:35] <gary_poster> I'll note that Michael tried to land the branch on the MP so anyone following along there knows we aren't ignoring you ;-)
[12:36] <wgrant> Thanks.
[12:52] <bigjools> I am going to shoot the next person who uses regular expressions in a test >:(
[12:59] <wgrant> bigjools: You just wait until you start using renormalizer to get traceback tests working on 2.5...
[15:35] <leonardr> barry, can you help me with a python problem?
[15:35] <leonardr> i'm getting a metaclass conflict even though i'm pretty sure all my classes have the same metaclass
[15:39] <leonardr> here's the code that's causing the problem
[15:39] <leonardr> https://pastebin.canonical.com/21549/
[15:39] <leonardr> i pass the result of make_configuration_superclass into make_configuration and get the error when it tries to use the superclass as a superclass of a new class
[15:39] <leonardr> but i'm using type() everywhere, and __metaclass__ = type in all affected files
[15:41]  * barry looks
[15:43] <barry> leonardr: do you have a full traceback as well as the offending code?
[15:43] <leonardr> barry, sure
[15:43] <barry> leonardr: or maybe better, a branch
[15:44] <leonardr> barry, i'll push the branch
[15:44] <leonardr> give me just a minute to clean up
[15:44] <barry> no worries, i'll be here :)
[15:45] <leonardr> actually, maybe i can just make it simpler and destroy the problem that way
[15:50] <matsubara> stub, Chex, gary_poster, rockstar, bigjools, henninge_, sinzui, intellectronica, Ursinha-afk: meeting in 10 min @ #launchpad-meeting
[15:51] <matsubara> s/meeting/LP production meeting/
[15:51] <sinzui> barry:  can you stand in for me in the LP product meeting ^
[15:52] <intellectronica> matsubara: thanks for the reminder
[15:52] <barry> matsubara, sinzui sure
[16:01] <matsubara> henninge_, meeting
[16:01] <matsubara> actually now danilos attends the production meeting, right?
[16:10] <henninge> matsubara: at least today, I am about to leave
[16:10] <matsubara> henninge, ok. danilos showed up. thanks!
[17:05] <abentley> danilos: Any idea why this would fail this way?  Is order important? http://pastebin.ubuntu.com/260413/
[17:06] <barry> leonardr: good to see you figured it out
[17:07] <danilos> abentley: it's a recent commit by jtv, I'd have to take a closer look
[17:08] <leonardr> barry, thanks for your potential help
[17:10] <barry> leonardr: i'm always potentially helpful.  sadly, the converse is often true too :)
[17:22] <danilos> abentley: can you fix the problem using assertContentEquals and that should be fine (if you are submitting something to pqm)
[17:23] <abentley> danilos: checking it now...
[17:24] <danilos> abentley: every other test works with only one so it's not a problem right now, but if this works for you, please email jtv@canonical.com (CCing me) mentioning what you had to do, and then the two of us can figure out what's the best way forward
[17:26] <abentley> danilos: self.assertContentEquals isn't defined, and I'm not sure what you mean.
[17:27] <abentley> danilos: Found it: assertContentEqual
[17:28] <abentley> danilos: This does work for me.  I'll include it in the branch I land.
[17:29] <danilos> abentley: thanks, please do still email jtv@ and danilo@ with this; thanks and sorry for it causing a problem like this!
[18:23] <bac> hi bigjools
[18:31] <mrevell> night all
[18:35] <intellectronica> are people seeing failures in lib/lp/app/browser/tests/menu.txt ?
[18:35] <intellectronica> i just got failures from ec2 and i don't think it has anything to do with my changes
[18:36] <salgado> intellectronica, I just saw a landing that changed something there
[19:07] <bac> intellectronica: barry has a testfix branch running now
[19:08] <intellectronica> bac: cool, thanks
[19:24] <barry> beuno: ping
[19:24] <barry> intellectronica, bac that should already be landed in devel
[19:25] <beuno> barry, hi
[19:25] <barry> beuno: i have a quick u/i-ish question for you related to bug 51735
[19:25] <intellectronica> barry: it has indeed. i got the failure from a branch i sent to ec2 (number of hours it takes to run the full test suite) earlier
[19:25] <mup> Bug #51735: top level distros page could be improved <ui> <Launchpad Registry:Triaged by barry> <https://launchpad.net/bugs/51735>
[19:25] <barry> intellectronica: the joys of a long test suite
[19:26] <beuno> barry, sure, what's up?
[19:26] <barry> beuno: at the bottom of that bug report sinzui suggests changing the way the read-only asterisk is displayed, but that also (i think) subtly changes the semantics of that star
[19:26] <barry> beuno: right now the ui says about that footnote: * Read-only distribution. Can be browsed in Launchpad, but not altered or managed, and its information might be out of date.
[19:27] <barry> beuno: but with sinzui's suggested change it really means "does not use Launchpad in any way"
[19:27] <sinzui> barry: it does change it.  if you read the code, we have a hack in it
[19:27] <barry> sinzui: yep, i've seen that
[19:28]  * beuno looks at the bug
[19:48] <beuno> so, has anyone tried LP on karmic?
[19:48] <beuno> will I be shooting myself in the foot (again) if I upgrade my work laptop as well
[19:48] <beuno> ?
[19:49] <barry> beuno: not yet, though i did install karmic on a vm last night.  haven't tried building lp on it yet
[19:50] <beuno> barry, I think we don't have the deps in the PPA for karmic
[19:50] <beuno> actually, it seems we do
[19:50] <beuno> I'll bite
[21:13] <mwhudson> wgrant: that ec2test run hung, it seems :(
[21:29] <thumper> sinzui: are you around?
[21:30] <sinzui> I am
[21:30] <thumper> ok, just checking
[21:30] <thumper> 1 hour
[21:30] <sinzui> thumper: I am on vacation
[21:30] <thumper> sinzui: then why are you around?
[21:31] <sinzui> Do you want to talk about pygtk hacking?
[21:31] <thumper> sinzui: so our call is off?
[21:31] <thumper> not really
[21:31] <thumper> sorry
[21:31] <thumper> I'll grab rockstar then :)
[21:33] <rockstar> thumper, hi
[21:34] <mwhudson> gary_poster: hello
[21:34] <gary_poster> mwhudson: hiya :-)
[21:35] <mwhudson> gary_poster: so do you remember what the problem was with the force build button when you turned it on?
[21:35] <gary_poster> mwhudson: I'm pretty sure that it simply did nothing.
[21:36] <gary_poster> It *possibly* was worse than nothing--causing some kind of glitch, but I lean towards nothing.
[21:39] <mwhudson> ok
[21:39]  * mwhudson is reading buildbot source code
[21:39] <mwhudson> and as usually, i'm getting a little dizzy
[21:39] <gary_poster> heh
[21:42] <gary_poster> kfogel: did you happen to propose to flacoste that we put lp-dev-tools in the lp tree?  if not, would you mind sending a note to the list proposing that, pointing out that they use launchpadlib and we don't have anything else that uses launchpadlib in the tree right now?  I don't care personally, and like the idea of our dev tools being in the tree, so I'd like to see if anyone objects.
[21:43] <kfogel> gary_poster: will do right now
[21:43] <gary_poster> thx!
[21:48] <kfogel> gary_poster: why the nick change?
[21:48] <kfogel> gary_poster: note that the lp-dev-tools should then get whatever license the other scripts in there have.  If it's AGPLv3, then so be it.
[21:48] <gary_poster> kfogel: somebody claimed "gary" on freenode a long time ago
[21:48] <kfogel> gary_poster: oh, I didn't notice we're on freenode
[21:48] <gary_poster> I'm still gary on canonical.com
[21:49] <gary_poster> ("gary" will still ping me in my client though, just in case)
[21:50] <kfogel> barry: is 'bip' an irc client?
[21:50] <barry> kfogel: it is
[21:51] <barry> kfogel: it runs in the background and connects to multiple irc servers.  then i use erc (in emacs 'natch) to connect to localhost's irc server from bip's daemon
[21:51] <barry> kfogel: it generally works well, except for some warts in both bip and erc that have not yet been worth hacking on yet
[21:51] <kfogel> barry: someday I should watch you use ERC.
[21:52] <kfogel> I tried to use some Emacs IRC client (maybe it was erc, not sure) a while back and just wasn't happy, so went to XChat.
[21:52] <barry> kfogel: modulo warts, it's changed my life :)
[21:52] <kfogel> But I still long for Emacs editing in IRC.
[21:52] <barry> kfogel: xchat irsii etc all drove me nuts
[21:52] <kfogel> xchat does drive me nuts, yes :-)
[21:52] <barry> kfogel: erc+bip has not yet driving me nuts
[21:53] <barry> kfogel: there are two irc clients for emacs iiuc.  erc seems to work pretty well, though there are some changes i'd make if i had the swine flu
[21:53] <kfogel> beuno: ping
[21:54] <beuno> kfogel, hi
[21:54] <kfogel> beuno: privchat, one sec
[21:56] <gary_poster> maxb: I saw your reply to bug 413335.  It would be awesome to have a fuller description and an example.  Will you have a chance to do either of those soonish--like by early next week?  If so, I'll wait for you.
[21:56] <mup> Bug #413335: Figure out what to do about zope.sendmail incompatibility with Python >= 2.5.1 <python-upgrade> <Launchpad Foundations:Triaged> <https://launchpad.net/bugs/413335>
[21:58] <maxb> gary_poster: yes, I'll definitely sort it over the weekend if I don't before
[21:59] <gary_poster> maxb: awesome.  ok, thanks
[21:59] <thumper> rockstar: skype?
[22:00] <rockstar> thumper, sure.  Early 1-1 then?
[22:00] <thumper> rockstar: I actually wanted to talk to you about a review :)
[22:01] <rockstar> Are you sure you can take that much rockstar in one day?
[22:02] <barry> kfogel: btw, irc + dabbrev ftw!
[22:03] <rockstar> thumper, 2 min and I'll be ready
[22:03] <thumper> ok
[22:03] <kfogel> barry: I totally believe it
[22:05] <rockstar> thumper, ready
[22:16] <wgrant> mwhudson: Are you trying again?
[22:16] <mwhudson> wgrant: not yet
[22:16] <mwhudson> wgrant: i think i may be being hated by my router, let's get someone else to run it
[22:17] <mwhudson> thumper: can you run "~/canonical/repos/lp-dev-utils/trunk/ec2test.py --headless -s "[r=gary][ui=none] move structural subscription security checking into the model code" lp:~wgrant/launchpad/structural-subscription-security --email=me@williamgrant.id.au" please?
[22:17] <thumper> mwhudson: ok
[22:19] <wgrant> Huh. Lots of people going on leave and leaving and changing position right now.
[22:19] <mwhudson> hey wouldn't it be nice if i could click force build on buildbot now
[22:19] <mwhudson> spm: there?
[22:19] <mwhudson> or mthaddon
[22:20] <mthaddon> mwhudson: 0/
[22:21] <mwhudson> mthaddon: can you edit line 267 of buildbot's master.cfg to pass allowForce=True and bounce buildbot pls?
[22:21] <mthaddon> mwhudson: what does that do?
[22:21] <mwhudson> mthaddon: it makes the force build button appear on the ui
[22:22] <mwhudson> mthaddon: which doesn't work, but i'd like to fix that, so debugging info would be useful
[22:22] <mthaddon> mwhudson: is currently: c['status'].append(html.WebStatus(http_port=8010)) # , allowForce=True))
[22:22] <mthaddon> mwhudson: so what should that be?
[22:22] <mwhudson> mthaddon: also, are the buildbot twistd.log files copied anywhere currently?
[22:23] <mthaddon> mwhudson: they aren't currently no - can you RT that?
[22:23] <mwhudson> mthaddon: c['status'].append(html.WebStatus(http_port=8010), allowForce=True)
[22:23] <mwhudson> mthaddon: sure
[22:24] <wgrant> mwhudson: Misplaced paren.
[22:24] <mwhudson> ah yes
[22:24] <mwhudson> c['status'].append(html.WebStatus(http_port=8010, allowForce=True))
[22:25] <mthaddon> mwhudson: 	exceptions.SyntaxError: invalid syntax (master.cfg, line 267)
[22:25] <mthaddon> mwhudson: nm, paste fail
[22:25] <mwhudson> :)
[22:26] <mwhudson> mthaddon: rt #35484 btw
[22:26] <mup> Bug #35484: Won't load X  <Ubuntu:Invalid by ubuntu-x-swat> <https://launchpad.net/bugs/35484>
[22:26] <mwhudson> mup: shut it
[22:26] <mthaddon> thx
[22:32] <mwhudson> mthaddon: is the patched buildbot running?
[22:32] <mthaddon> mwhudson: I've made that config change and restarted buildbot, yep
[22:32] <mwhudson> hmm
[22:33] <mwhudson> oh right
[22:33] <mwhudson> latent buildslaves appear to be disconnected the whole time
[22:33] <mwhudson> i guess we'll be needing to patch buildbot a bit then
[22:35] <mwhudson> gary_poster: is there a buildbot irc channel or anything?
[22:35] <mwhudson> ah, the obvious answer works :)
[22:35] <gary_poster> :-)
[22:36] <jml> hello all
[22:38] <spm> hey jml
[22:39] <jml> spm, hello :)
[22:39] <jml> beuno, hi
[22:39] <beuno> jml, hai
[22:40] <jml> beuno, I'm working through your email now
[22:40] <beuno> jml, it's starting to feel more like a wiki than an email   ;)
[22:41] <jml> beuno, yeah, I know.
[22:41] <jml> beuno, one more round from me :)
[22:42] <spm> mwhudson: am now. but I gather tom's assisted?
[22:42] <mwhudson> spm: yes, thanks
[22:42] <spm> cool
[22:42] <beuno> jml, give me your best shot, it's fun
[22:43] <jml> beuno, I was thinking just that -- it's quite fun :)
[22:44] <beuno> jml, I think that this is what google wave will be all about
[22:44] <beuno> real multiplayer email
[22:47] <wgrant> I think the alignment of the main branding heading is a bit strange. Would it look better if it was aligned with the LHS of the Overview button, rather than the text, I wonder?
[22:55] <rockstar> barry, do we have a standard where our pagetests now need to be restructured text?
[22:59] <barry> rockstar: yes
[23:00] <barry> rockstar: w/conversion as you go
[23:00] <rockstar> barry, thanks.
[23:12] <intellectronica> i'm getting lots of errors in test_breadcrumbs. is that a known problem?
[23:28] <jml> mwhudson, https://bugs.edge.launchpad.net/launchpad-foundations/+bug/420198
[23:28] <mup> Bug #420198: ec2test --headless takes way too long to detach <Launchpad Foundations:Triaged> <https://launchpad.net/bugs/420198>
[23:28] <lifeless> jml: hi
[23:28] <lifeless> jml: I'm guessing you make test bzr servers in the codehosting tests
[23:28] <lifeless> you may find http://bazaar.launchpad.net/~lifeless/bzr/test-speed/revision/4661 relevant
[23:30] <jml> lifeless, a little.
[23:30]  * jml is reminded of other
[23:30] <jml> code
[23:30] <lifeless> spiv: I wonder if ChrootServer should take a server on its setUp rather than a transport on its __init__ (we could make a server that just claims to be at an arbitrary url)
[23:30] <lifeless> spiv: that would be more consistent with other Servers
[23:33] <mwhudson> yeah, we do that sort of thing a fair bit
[23:33] <jml> lifeless, we have a function in our base TestCase that does foo.setUp(); self.addCleanup(foo.tearDown)
[23:34] <mwhudson> TestCase.installFixture woo
[23:34] <lifeless> jml: thats close to this indeed
[23:34] <jml> but I don't think we use backing servers in quite the same way
[23:34] <jml> there's also a base class called Fixture
[23:34] <lifeless> jml: this is preparation for another change that will deny all access to urls that aren't registered with the test case
[23:34] <jml> which has its own addCleanup implementation
[23:35] <lifeless> jml: so the reason I'm headsuping you and mwhudson et al
[23:35] <jml> is you're going to break our test suite?
[23:35] <lifeless> is that when you start grabbing from the post 2.0 releases, its going to be brutal
[23:35] <lifeless> assuming it gets through review
[23:36] <lifeless> I'm changing from a 'setup things so that bad code is contained' to 'contain bad code by interception'
[23:36] <lifeless> model for the test isolation code
[23:36] <lifeless> less work++
[23:36] <jml> lifeless, http://bazaar.launchpad.net/~launchpad-pqm/launchpad/devel/annotate/head%3A/lib/lp/codehosting/scanner/fixture.py
[23:42] <lifeless> nice
[23:42] <lifeless> uhm, might want to split the zope stuff from the support stuff
[23:42] <lifeless> just a thought
[23:44] <jml> yeah
[23:44] <jml> it's totally in the wrong place
[23:44] <jml> but it's a whole lot better than thinking about it how good it would be to have something like that :)
[23:54] <jml> man, filing all of these bugs for the build system has made me want to do something about them
[23:55] <mwhudson> oop
[23:55] <mwhudson> s