[00:00] <lifeless> does anyone know the rdf ontology used for our project metadata?
[00:03] <lifeless> found it, doap.
[00:33] <jml> mwhudson, fwiw, I have an ec2test run going that runs the code doctests in the DBFunctionalLayer
[00:33] <mwhudson> jml: which layer is that?
[00:34] <jml> mwhudson, the DatabaseFunctionalLayer
[00:34] <mwhudson> jml: is that the one that doesn't start the librarian?
[00:34] <jml> mwhudson, the one with zcml & the db and not much else
[00:34] <jml> mwhudson, yeah
[00:34] <mwhudson> jml: some code import tests may well fail
[00:34] <mwhudson> i guess you'll find out :)
[00:34] <jml> mwhudson, I expect so. :)
[00:34] <mwhudson> some diff related ones too, perhaps
[00:39] <jml> mwhudson, I'm also running tests that delete a lot of columns from ProductSeries
[00:39] <mwhudson> jml: \o/ for that
[00:39] <jml> mwhudson, all of which are related to vcs-imports, afaict.
[00:39] <mwhudson> yeah
[00:39] <mwhudson> they're long dead
[00:40] <jml> mwhudson, if the tests pass, can you please review the patch?
[00:40] <mwhudson> jml: sure
[01:15] <mwhudson> thumper: i just wrote https://bugs.edge.launchpad.net/launchpad-code/+bug/118625/comments/12 btw
[01:15] <mup> Bug #118625: codebrowse sometimes hangs <codebrowse> <Launchpad Bazaar Integration:Triaged> <https://launchpad.net/bugs/118625>
[01:19] <spm> mwhudson: fwiw, sounds sane to me; and would seem match observation. logs tho... hrm.
[01:21] <lifeless> wget -O- https://edge.launchpad.net/launchpad/+rdf | wc -l
[01:21] <lifeless> 1634
[01:37] <jml> thumper, btw, I have your 'active-branch-counts' still in my active reviews page
[01:47] <thumper> jml: yes, I've not done anything with it recently
[01:56]  * mwhudson lunches
[02:05] <jml> thumper, write better cover letters.
[02:44] <thumper> jml: yeah, I suppose
[02:44] <thumper> normally do
[02:44] <thumper> just frustrated
[02:45] <jml> thumper, page migration getting you down?
[02:46] <thumper> just a bit...
[02:46] <thumper> given that the breadcrumbs were broken for branches
[02:46] <thumper> again
[02:47] <thumper> s/were/are
[02:59] <jml> mwhudson, ping
[03:20] <mwhudson> jml: hi
[03:21] <jml> mwhudson, I'd like a second opinion on something. Got a moment for a short skype call?
[03:21] <mwhudson> jml: sure thing
[03:49] <jml> mwhudson,   lib/lp/code/tests/../doc/branch-merge-proposal-notifications.txt
[03:49] <jml>   lib/lp/code/tests/../doc/codeimport-result.txt
[03:49] <jml> mwhudson, those are the only ones that failed.
[03:49] <mwhudson> jml: my predictive powers are clearly working reasonably well today
[03:50] <jml> mwhudson, don't jinx it :)
[03:50] <mwhudson> (i just wish they were predicting more success with buildbot :/)
[03:52] <jml> haha
[03:53] <lifeless> mwhudson: you're having op trouble?
[03:53] <mwhudson> lifeless: op ?
[03:53] <lifeless> operational
[03:53] <mwhudson> ah
[03:53] <mwhudson> no, not really
[03:55] <mwhudson> lifeless: mostly trying to bash the model buildbot uses into my brain
[03:55] <lifeless> mwhudson: pb jelly + bidirectional callbacks around steps of activity.
[03:55] <lifeless> mwhudson: If you need a clue at any point gimme a shout
[03:56] <lifeless> mwhudson: I doubt its changed radically since I climbed all through it years ago
[03:56] <mwhudson> lifeless: well, it has changed somewhat because gary added 'latent builders' to it
[03:56] <lifeless> they being ec2 slaves
[03:56] <lifeless> which it can activate
[03:57] <lifeless> ?
[03:57] <mwhudson> yes
[03:57] <lifeless> Arbitrary number, or a slave-factory?
[03:57] <lifeless> [does this make buildbot a slave owner?]
[03:57] <mwhudson> the 'force build' button doesn't appear for them unless a build is running
[03:58] <lifeless> and thats the bug you're working on?
[03:58] <mwhudson> because the slave isn't 'connected' according to buildbot in this state
[03:58] <mwhudson> well
[03:58] <lifeless> yes
[03:58] <mwhudson> i have this niggling suspicion that if i can make it appear it then won't work
[03:58] <lifeless> thats to be expected. Uhm, I'd decouple that assumption [yes I realise thats what you're looking for the knobs of]
[03:58] <mwhudson> yes
[03:59] <lifeless> are the latent slaves all manuall configured?
[03:59] <lifeless> or does it act as a factory for them?
[03:59] <mwhudson> lifeless: i don't understand the question
[03:59] <mwhudson> lifeless: it starts an ec2 instance for each build
[04:00] <lifeless> so does the config say 'slave FOO; is latent; <various details>', 'slave BAR; is latent...', and then you can have 1 and only 1 build on FOO at a time, ditto BAR
[04:00] <lifeless> -or-
[04:00] <mwhudson> slaves are ~always configured manually in buildbot aren't they?
[04:00] <mwhudson> lifeless: yes
[04:01] <mwhudson> this is part of the terminology thing
[04:01] <lifeless> does the config say 'slave FOO is latent <factory details>', and then new slaves appear each time ec2 is prodded to do stuff, called FOO-<instanceid>
[04:01] <mwhudson> i have a hard time remembering the difference between builders and slaves
[04:01] <mwhudson> and build factories
[04:01] <lifeless> mwhudson: IIRC builders are 'code that knows how to perform an operation'
[04:01] <lifeless> build factories are 'code that parameterises a builder for a job'
[04:02] <jml> wuu, -1 actually seems to work these days.
[04:02] <jml> (it shows only the first failure in a doctest)
[04:02] <lifeless> mwhudson: so if its the first case, then all the slaves are static, the only interesting thing is that they connect on-demand.
[04:02] <lifeless> mwhudson: I'd consider two things;
[04:02] <lifeless>  - a 'connect this slave' button.
[04:03] <lifeless> this would work, unless the slave auto-disconnects instantly
[04:03] <lifeless> (and a connecting slave would want 'force build' to be available as a callback on connect completing)
[04:03] <lifeless>  - making force build trigger a connect implicitly
[04:04] <jml> hmm. the lp-dev-utils kerfuffle is stopping me from opportunistically coding.
[04:04] <jml> something to deal with when I return.
[04:04] <lifeless> jml: comefrom?
[04:04] <jml> lifeless, return from running a bunch of errands, which is what I'm about to do.
[04:42] <wgrant> mwhudson, thumper: Is lp:~wgrant/launchpad/structural-subscription-security cursed, or just unlucky?
[04:42] <wgrant> Three have tried to land it so far.
[04:42] <wgrant> I never heard back from the third attempt.
[04:54] <jml> wgrant, hmm.
[04:55] <jml> wow, the "Request another review" widget is broken as.
[04:55] <jml> wgrant, commit message?
[04:55] <jml> (I'll update the field on the MP page to have the commit message so you don't get asked again)
[04:56]  * jml writes out, "[r=gary][ui=none] (wgrant) Move structural subscription security to the model, rather than the view."
[04:57] <wgrant> jml: That sounds about right.
[04:57] <wgrant> Thanks.
[04:57] <wgrant> Hopefully this time it will work.
[05:01] <wgrant> You know, I really hate tests that fail due to obscure errors in a three-level-deep exception handler.
[05:01] <wgrant> I also really hate three-level-deep exception handlers, but particularly when they crash.
[05:02]  * jml sympathises
[05:02] <jml> sometimes it's a sign that there need to be unit tests for that third level layer.
[05:03] <jml> particularly in the Launchpad code base.
[05:14] <jml> mwhudson, thanks for replying to the RFC about package branchse.
[05:14]  * jml needs to reply to slangasek's email.
[05:14] <mwhudson> jml: np
[05:14]  * mwhudson doesn't think he's getting all the mails on this topic
[05:15] <jml> mwhudson, slangasek's mail was sent to launchpad-dev on the 29th.
[05:16] <mwhudson> jml: subject?
[05:16] <mwhudson> i don't seem to have it
[05:17] <jml> mwhudson, Re: [RFC] Taking source package branches to the next release
[05:17] <mwhudson> jml: nope, nothing from him
[05:17] <jml> mwhudson, hmm.
[05:17] <wgrant> It wasn't on the list.
[05:17] <wgrant> Or is stuck in moderation.
[05:18] <jml> stuck in moderation, I'll bet
[05:18]  * jml moderates in anger
[05:22]  * mwhudson receives lots of fairly old mail\
[05:23] <wgrant> Ah. That's filling in the gaps.
[05:24] <spm> mwhudson: jml: which list? I did the int one this morning, nought but spam.
[05:24] <jml> spm, the launchpad-dev list
[05:25] <jml> spm, as found on http://launchpad.net/~launchpad-dev
[05:25] <spm> hrm. nothing there either.
[05:26] <jml> spm, that's because I just moderated them all :)
[05:26] <spm> awesome. my problems just went away. ;-)
[05:29] <spm> heh. just noticed (and fixed) the lp-eng team membership of same was set to expire later this year. that would have been amusing to watch.
[05:34] <wgrant> spm: You seem to want https://launchpad.net/+announcements.
[05:35] <wgrant> That page was almost removed a week or two ago.
[05:35] <spm> wgrant: rofl. which just goes to show how well... advertised(?) the service that provides is :-)
[05:35] <wgrant> spm: I've never seen it linked.
[05:35] <wgrant> But it has a useful Atom feed too.
[05:36] <wgrant> (in fact, I only discovered that page by guessing the URL when I saw people pondering its removal)
[05:36] <spm> lol
[05:36] <mwhudson> now why the bleep isn't db_lp building??
[05:37] <wgrant> mwhudson: buildbot hates you.
[05:37] <mwhudson> wgrant: i hate it more
[05:37] <wgrant> alright. I am very confused.
[05:37] <wgrant> I have a test here that really should fail in python2.4, but only fails in python2.5.
[05:37] <wgrant> AFAICT.
[05:37] <wgrant> Basically, it's logging an exception.
[05:38] <wgrant> Said exception contains '%s' in the traceback.
[05:38] <mwhudson> exceptions are new style in 2.5, could it be that?
[05:38] <wgrant> So when the logger function attempts to use % on the string, it crashes.
[05:38] <wgrant> Possibly. Let's see what 2.4 exceptions look like.
[05:38] <mwhudson> python2.4 exceptions might look a little bit more like sequences to some parts of the code
[05:39] <wgrant> Hmmm.
[05:39] <mwhudson> or maybe not
[05:39] <mwhudson> wgrant: can you pastebin come code?
[05:41] <wgrant> mwhudson: http://paste.ubuntu.com/262311/
[05:42] <wgrant> The problematic exception is http://paste.ubuntu.com/262312/.
[05:42] <mwhudson> wgrant: oh gosh, mocklogger is terrible
[05:42] <wgrant> mwhudson: Heh, there is a comment in one of the callsites saying that it should be merged with FakeLogger.
[05:43]  * wgrant looks for any other callsites.
[05:43] <spm> FakeLogger? is that like an alias to /dev/null?
[05:43] <wgrant> Mm, there are a few.
[05:43] <mwhudson> there are so many dummy loggers lying around
[05:43] <mwhudson> it's really cruddy
[05:43] <spm> *why*!?!?!?
[05:43] <mwhudson> wgrant: i don't see why that would behave differently 2.4/2.5
[05:44] <wgrant> mwhudson: Neither.
[05:44] <wgrant> mwhudson: But the same exception is raised in both.
[05:44] <mwhudson> wgrant: but the mocklogger code is broken, please fix it :)
[05:44] <wgrant> And somehow crashes on 2.5...
[05:44] <mwhudson> wgrant: maybe format_exception does different things?
[05:44] <mwhudson> seems unlikely though
[05:44] <wgrant> mwhudson: Possibly. Let's see..
[05:44] <mwhudson> pdb ftw
[05:52] <wgrant> Oh.
[05:52] <wgrant> No.
[05:52] <wgrant> Surely not.
[05:53] <wgrant> mwhudson: I now know why.
[05:53] <wgrant> mwhudson: 2.4 prints the first line of the statement.
[05:53] <wgrant> 2.5 prints the last.
[05:53] <mwhudson> wgrant: ha ha
[05:53] <wgrant> How utterly stupid.
[05:54] <wgrant> I almost didn't bother to check that, it was such a silly idea.
[05:54] <lifeless> its bytecode data I think
[05:56] <wgrant> So, I think that was the only mysterious Python 2.5 failure.
[06:32] <wgrant> Anybody want to review https://code.edge.launchpad.net/~wgrant/launchpad/fix-mocklogger-format-string-crash/+merge/10902?
[06:54] <jml> wgrant, has anyone answered yet?
[06:56]  * mwhudson eods
[06:56] <wgrant> jml: No.
[06:57] <wgrant> jml: (has my accursed branch killed ec2test yet?)
[06:57] <jml> wgrant, ec2test went headless, still waiting for a reply
[06:57] <wgrant> jml: Great, thanks.
[06:58] <jml> wgrant, I don't fully grok your patch yet...
[06:58] <jml> wgrant,
[06:58]  * jml kicks xchat
[06:59] <jml> wgrant, specifically, I don't know what "2.4 seems to render the first line of each statement in tracebacks, while 2.5 renders the last" has to do with only doing string interpolation if arguments are provided.
[06:59] <wgrant> jml: Well, I half expected the reviewer to be somebody who had read the earlier discussion.
[07:00] <wgrant> jml: Basically, in the case of that test the last line of the statement contains '%s'.
[07:00] <wgrant> So MockLogger gets a string with a '%s' in it, without any arguments.
[07:00] <wgrant> Boom.
[07:00] <jml> ahh ok.
[07:01] <jml> (also, I'm extremely hungry)
[07:01] <wgrant> It is approximately way past lunchtime.
[07:06] <wgrant> jml: How would I best go about testing it? I can't exactly just use a mock logger and check the output for this one...
[07:08] <jml> wgrant, construct a MockLogger, temporarily replace sys.stdout with a StringIO object, call log() without args, check the contents of the StringIO, replace sys.stdout
[07:09] <wgrant> jml: OK. I was hoping there was some less bad way than replacing sys.stdout.
[07:09] <jml> by 'without args', I really mean "log('%s')" or something similar.
[07:09] <wgrant> Yep.
[07:09] <jml> wgrant, well I was about to get to that :)
[07:09] <jml> wgrant, the nicer way is to give MockLogger a constructor that takes an optional file-like object
[07:09] <jml> wgrant, if provided, use that; if not, use sys.stdout
[07:10] <wgrant> jml: Ah, of course.
[07:10] <jml> that would mean changing the print call to self._output.write or whatever, naturally.
[07:10] <wgrant> Yep.
[07:10] <wgrant> Thanks.
[07:10] <jml> np
[07:15] <spiv> wgrant: presumably the caller is buggy, and should be doing "log('%s', msg)" instead of "log(msg)" ?
[07:16] <jml> hmm...
[07:16] <spiv> (Making the logger robust against this misuse is still a good idea, though)
[07:16] <wgrant> spiv: stdlib logging says otherwise.
[07:16] <spiv> Huh?  Ok.
[07:16] <wgrant> spiv: Anyway, the problematic caller is actually the logger itself.
[07:17] <wgrant> spiv: The standard library logging module allows that kind of call.
[07:23] <lifeless> loggers are meant to lazy evaluate
[07:23] <lifeless> out of a sense of cheapness
[07:23] <lifeless> this is arguable
[07:34]  * jml jfdis
[07:39] <noodles775> Howdy
[07:50] <jtv> hi noodles775!
[07:50]  * noodles775 waves at jtv
[07:52] <jtv> noodles775: and since it's Monday morning for you... the "this site is running demo code" bar seems to be horribly broken on both 3.0 and pre-3.0 pages, but differently on dev and edge.  Saw something about it on the reviews list; is it being worked on?
[07:52] <noodles775> jtv: https://bugs.launchpad.net/bugs/421454
[07:52] <mup> Bug #421454: Filebug link on edge/staging header needs structure <trivial> <ui> <Launchpad Foundations:Fix Committed by michael.nelson> <https://launchpad.net/bugs/421454>
[07:53] <noodles775> yep, it's landed in devel... should be fixed on edge on the next rollout (hopefully soon).
[07:53] <jtv> noodles775: does that also cover the bar not showing up at all on dev?
[07:53] <noodles775> jtv: huh? it's never shown up on dev afaik?
[07:54] <jtv> noodles775: oh, that might well be it...  It's just that dev seemed to reserve space for it.
[07:54] <noodles775> (ie. you need to add the site_message config option to dev.
[07:55] <jtv> noodles775: sorry for the false alarms, but as I said, this _is_ Monday morning so bad things are supposed to happen.  :)
[07:55] <noodles775> jtv: np! fwiw, it was a case of a missing test (we'd never had a test for markup in the site_message, although we'd always used it on edge). When the site_message was moved to a template it was auto-escaped.
[07:56] <jtv> noodles775: tricky!
[08:02] <jml> noodles775, hello
[08:02] <jml> noodles775, did you manage to get that branch reviewed?
[08:02] <noodles775> Hi jml
[08:03] <noodles775> Yep, it's been through buildbot and waiting for the edge update.
[08:03] <jml> cool.
[08:03] <noodles775> jml: sorry, I was assuming that you were talking about the branch above - rather than your permissions branch?
[08:04] <jml> noodles775, the branch above.
[08:04] <jml> noodles775, bigjools got to my permissions branch.
[08:04] <noodles775> great.
[08:04]  * jml is eagerly awaiting the British morning.
[08:04] <noodles775> jml :(
[08:04] <noodles775> it's a public holiday there.
[08:04] <jml> they are always having public holidays
[08:05] <jml> I shall write a sternly worded letter to the Daily Mail.
[08:05] <noodles775> lol
[08:26] <adeuring> good morning
[08:41] <lifeless> jml: whats the name of the plugin/command you wrote to find merge, no-shelve, no-edit local branch|trees ?
[08:41] <jml> lifeless, bzr-removable
[08:42] <lifeless> is it packaged?
[08:42] <jml> lifeless, it probably doesn't even work any more
[08:42] <jml> lifeless, no, it's not.
[08:42] <lifeless> lp:bzr-removable?
[08:43] <jml> lifeless, yeah, I think so.
[08:44] <lifeless> thats doing something
[08:44] <lifeless> you should upgrade it to 2a
[08:45] <noodles775> Does anyone know if there is something similar to https://staging.launchpad.net/successful-updates.txt but for edge?
[08:46] <noodles775> spm: I don't suppose you could check why the daily update of edge hasn't happened yet... or am I too early?
[08:47] <spiv> I don't think bzr-removable has been updated for the new shelf in bzr.
[08:47] <jml> lifeless, I should certainly do _something_ to it.
[08:53]  * wgrant returns.
[08:53] <wgrant> jml: If you haven't EODed yet, can you have a look at my branch with added tests once I push it?
[08:53] <jml> sure
[08:54] <noodles775> spm: Either thanks or don't worry - edge just updated :)
[08:55]  * wgrant finds the new header a bit boring and colourless.
[08:55] <wgrant> I stumbled upon some UI 1.0 screenshots yesterday, and they are much more inviting than I remembered or 2.0/3.0 are.
[08:56] <noodles775> wgrant: I *think* the idea is that projects themselves can emphasize their own branding, like https://edge.launchpad.net/firefox
[08:57] <wgrant> noodles775: Right, and that's a good thing. But the facet links are all the same. They're boring, and hard to look through.
[08:57] <noodles775> Is it the lack of colour on the app-buttons specifically that you think is missing?
[08:57] <noodles775> yep.
[08:57] <wgrant> Right.
[08:58] <wgrant> I thought maybe facet colours were being eliminated, but the involvement portlet and titles suggest otherwise.
[08:58] <lifeless> jml: well, something yes. Anyhow I've just sent you a merge request.
[08:59] <noodles775> wgrant: yeah, I'm not sure what the reasoning is for removing them in the app-buttons, but guessing it's to avoid clashing with the product branding...
[08:59] <wgrant> noodles775: I thought that might be it.
[08:59] <noodles775> I'll check with beuno later - (or maybe he's still around)?
[08:59] <wgrant> noodles775: But it makes it all really really boring.
[09:00] <wgrant> noodles775: The bottom has that nice blue fade.
[09:00] <wgrant> s/fade/gradient/
[09:00] <noodles775> ... and a nice colourful lp branding (which isn't linked :/ ).
[09:01] <wgrant> My only other complaint about the branding/watermark is the alignment of the heading wrt. a selected Overview tab.
[09:01] <noodles775> Heh... so I know about that one - that's a specific request from Martin... that the first-letters line up (rather than the outline).
[09:02] <wgrant> noodles775: It looks pretty strange.
[09:02] <wgrant> Hm. although if the -0.5em margin is removed, it looks slightly strange when deselected.
[09:02] <wgrant> How unfortunate.
[09:02] <noodles775> wgrant: I agree - when the overview tab is selected - and for that reason the initial version had the background aligned.
[09:03] <wgrant> noodles775: I guess it will become less of a concern when the Overview tab dies.
[09:03] <noodles775> wgrant: well, the same issue will then hit the Code tab.
[09:03] <wgrant> noodles775: right, but that's not the default view.
[09:03] <noodles775> Right.
[09:04] <wgrant> And first impressions do count, a lot.
[09:07] <noodles775> I actually had the -0.5em margin removed only when the first li was selected - so it's possible to have both, but the decision was for the first letters to always align (and I just do what I'm told there ;) ).
[09:10] <lifeless> micro freshmeat
[09:10] <lifeless> http://simal.oss-watch.ac.uk/index.html
[09:18] <jml> lifeless, thanks for the patch.
[09:18] <jml> lifeless, the shape of it looks about right :)
[09:19]  * jml needs to figure out what all the words mean though ...
[09:28] <lifeless> jml: it works. Use it. Love it. Commit it.
[09:28] <lifeless> oh,and I didn't reduce test coverage.
[09:30] <jml> lifeless, heh heh
[09:30] <jml> lifeless, in terms of percentage, no.
[09:30] <lifeless> \o/
[09:36] <wgrant> noodles775: Any ideas on how PPA download stats could be shown?
[09:38] <noodles775> wgrant: sure - let's collect them at https://dev.launchpad.net/SoyuzPPAIndexPage
[09:39] <noodles775> wgrant: they'll be useful immediately to both the owner and potential users, so we'll probably want some general stats on the index page, and then developer/detailed stats on the /+packages page?
[09:40] <wgrant> noodles775: I suspect so.
[09:40] <noodles775> wgrant: what are your thoughts?
[09:41] <wgrant> noodles775: Not sure. It gets rather complicated, because there are different semantics associated with different sets of binaries. Some sources will produce binaries that will be installed disjointly, while others will always be installed together.
[09:42] <wgrant> So numbers are probably not meaningful except at the binary level.
[09:44] <noodles775> wgrant: maybe it would be helpful to identify (on the wiki page - or a separate one even, or even it's own blueprint spec) what we think the target users will want to see, and then adjust that with what's actually possible/meaningful.
[09:44] <noodles775> Once we've got that info, a lot more people would be able to comment too.
[09:45] <jml> wgrant, started the run on the mystery meat branch
[09:46] <noodles775> I'm not sure I caught how you'd get around the download count simply reflecting how often people update a package (without storing ip's etc.)
[09:46] <noodles775> s/you'd get/you got/
[09:46] <wgrant> jml: Thanks... I can't see anything even mildly suspicious
[09:47] <jml> wgrant, me neither.
[09:48] <jml> wgrant, not being able to reliably land code bothers me quite a lot, so I hope we can get to the bottom of this.
[09:48] <wgrant> noodles775: Except for daily builds, it should be fairly good, as every user should get every version if it's there for more than a few days.
[09:48] <wgrant> noodles775: And for daily builds, it is at least a reasonable way to judge between other PPAs and packages.
[09:48] <wgrant> noodles775: The raw numbers are probably not useful on their own.
[09:50] <noodles775> wgrant: yes, but what I meant is, I'm assuming a user of a PPA is most interested in how many downloads the ff package in PPA X has - irrespective of the version.
[09:51] <jml> tee hee
[09:51] <jml> I don't even have bzr-removable on my laptop :)
[09:51] <jml> oh wait, it's in my dropbox
[09:52] <wgrant> noodles775: Right. It should be possible to do that quite reliably for packages updated less frequently than weekly.
[09:52] <noodles775> Great.
[09:53] <wgrant> I have most of the backend code done, it just need to be split into threeish branches and tested properly.
[09:53] <noodles775> whoohoo! great stuff :)
[09:53] <wgrant> And then needs to be poked into the UI.
[09:54] <jml> lifeless, also, https://code.edge.launchpad.net/~lifeless/bzr-removable/merge hasn't got branch data :(
[09:54] <noodles775> wgrant: have you tried bzr pipeline? It's great for multiple-branch-spanning-functionality.
[09:54] <wgrant> noodles775: I started using it about a week ago for my latest four-branch effort.
[09:54] <wgrant> It is excellent.
[09:54] <noodles775> :)
[09:59] <lifeless> jml: code review merge-by-mail bug I guess.
[09:59] <lifeless> jml: I replied with the url i did push to
[09:59] <lifeless> which is ...treeless
[10:01] <jml> gah pycs and directory removal and bzr
[10:01] <wgrant> jml: +1
[10:09] <wgrant> maxb: So, the mysterious soyuz-set-of-uploads.txt failure is pretty much resolved.
[10:09] <wgrant> maxb: That just leaves the rest of the obvious (largely benign) failures.
[10:24] <ddaa> lifeless: ping
[10:25] <lifeless> hi
[10:25] <ddaa> lifeless: re twitter
[10:25] <lifeless> hai yes,
[10:25] <ddaa> the thing that does not work was bin/jstest
[10:26] <ddaa> as in "the test script freeze to start with, unless I fix an import bug, then it actually runs to completion but reports 3 failed test suites"
[10:26] <lifeless> ah, nifty. In a sad sad way.
[10:26] <lifeless> I thought you were referring to something in the web app :)
[10:26] <ddaa> fix for the import bug: http://python.pastebin.com/m34a9f134
[10:27] <lifeless> what python version?
[10:27] <ddaa> does not matter
[10:27] <lifeless> indeed, I see
[10:27] <lifeless> uhm, care to file a bug, or would you like meto?
[10:28] <ddaa> if I were you, I'd just trivial it
[10:28] <lifeless> Lp
[10:28] <lifeless> LP's landing process is a bit byzantine
[10:28] <lifeless> its easier for me to hand it off
[10:28] <lifeless> :(
[10:28] <ddaa> wow
[10:29] <ddaa> sounds to me like the process went a bit wrong if you can no longer trivial one-liners like that
[10:29] <lifeless> one can
[10:30] <ddaa> anyway, I do not care about the launchpad bug in itself
[10:30] <lifeless> I need to do a bunch of setup to be able to
[10:30] <lifeless> my laptop overflowed, and i've not cut code for lp in a couple years
[10:30] <ddaa> I was only checking this because I wanted to learn from how launchpad integrated with windmill
[10:30] <lifeless> ah :)
[10:30] <lifeless> and have you learnt?
[10:30] <ddaa> "not very well"
[10:31] <ddaa> "does not run headless, so is not part of the test suite run by pqm"
[10:31] <lifeless> anyhow, bug files.
[10:31] <ddaa> "still requires painful hard-coded waits in some places"
[10:31] <lifeless> [once cron takes care of mail]
[10:32] <wgrant> ddaa: Somebody here had it running headless.
[10:32] <wgrant> ddaa: It's close to buildbot integration.
[10:32] <wgrant> And hard-coded waits are meant to be removed.
[10:32] <wgrant> Lots were two weeks ago.
[10:32] <ddaa> wgrant: THAT sounds very interesting
[10:33] <ddaa> wgrant: anything else of the same kind that you think I might be interested in knowing about?
[10:34] <wgrant> ddaa: Mmm. Not sure.
[10:34] <wgrant> I don't know much more about that stuff.
[10:34] <ddaa> Fine then. I was just probing.
[10:35] <maxb> wgrant: Yay! And congratulations on your amazing detective work :-)
[10:35] <wgrant> maxb: It was more than a bit of a puzzle.
[10:35] <wgrant> maxb: Particularly as it was buried inside unlogged exception handlers...
[10:36] <maxb> It does strike me that the LP tests seem to have a tendency to throw away useful logging
[10:37] <wgrant> It's normally easy to get it back.
[10:37] <wgrant> Just not in this case.
[10:45] <lifeless> bug 421840
[10:45] <mup> Bug #421840: trivial bug in test support <Launchpad itself:New> <https://launchpad.net/bugs/421840>
[10:45] <lifeless> jtv: ^ if you're around, care to peek?
[10:45] <jtv> lifeless: peeking...
[10:46] <jtv> lifeless: greek to me
[10:47]  * thumper taps fingers while 'make build' runs
[10:47] <jtv> well, not greek, but...
[10:47] <lifeless> oh look thumper
[10:47] <lifeless> that bug is in your tests ;0
[10:47] <thumper> where?
[10:47] <jtv> lifeless: afaik we're still not running these tests as part of the regular test suite; mars was working on that
[10:48] <lifeless> https://launchpad.net/bugs/421840
[10:48] <mup> Bug #421840: trivial bug in test support <Launchpad itself:New> <https://launchpad.net/bugs/421840>
[10:48] <thumper> lifeless: I'll add it to my branch
[10:51] <lifeless> ddaa: ^
[10:51] <lifeless> thanks thumper
[10:51] <thumper> lifeless: I even added (ddaa) to the revision message :)
[10:52] <ddaa> thumper: thanks pal
[10:52] <thumper> ddaa: np
[10:54] <jtv> hi carlos!
[10:54] <jtv> hi ddaa!
[10:54] <carlos> jtv: morning
[10:54] <ddaa> jtv: hey buddy, how's life?
[10:54] <jtv> ddaa: overrated  :-P
[10:55] <ddaa> jtv: watch you for your attitude pal ;-)
[10:55] <ddaa> s/watch you/watch out/
[10:55] <jtv> oh, did it bite someone while I wasn't looking?
[10:55] <lifeless> thumper: https://edge.launchpad.net/pyjunitxml/+download
[10:55] <lifeless> search on that page for zz
[10:57] <thumper> lifeless: heh
[10:58] <jml> ok, now I can't download keys from the GPG server :(
[11:00] <lifeless> thumper: I figured you'd like it
[11:00] <lifeless> in a head slapping kinda way
[11:05] <deryck> Morning, all.
[11:07] <thumper> deryck: hi
[11:07] <thumper> deryck: I'd like to organise a short weekly call with you sometime
[11:07] <thumper> deryck: do you ever work *normal* hours for your TZ?
[11:07] <thumper> deryck: 'cause if you did, we could talk during the day time :)
[11:08] <deryck> thumper, a call would be cool.  And sorry, but I'm always 10-7 GMT.  But I could hang around later one day for a call.
[11:09] <thumper> may be a plan
[11:09] <thumper> deryck: lets organise this later though
[11:09] <thumper> I'm done
[11:09] <deryck> thumper, ok, cool.  have a good night.
[11:43] <wgrant> Ooh. lp-dev-utils stuff.
[11:44]  * jml looks all innocent
[11:45] <wgrant> Thanks jml.
[11:46] <jml> np.
[11:48] <wgrant> jml: Are you running that accursed branch without going headless, or should I try?
[11:49] <jml> wgrant, I am.
[11:49] <wgrant> jml: Great, thanks.
[11:49] <jml> wgrant, it's still going...
[11:49] <wgrant> jml: Damn.
[11:58]  * jml stops
[11:58] <jml> g'night all
[11:58] <jml> wgrant, I'll let you know how the run goes
[11:58] <wgrant> jml: Thanks.
[11:58] <wgrant> jml: I guess ec2test won't really work for non-Canonicalites without some hacking...
[11:58] <wgrant> It seems to use devpad a bit.
[12:16] <wgrant> RuntimeError: You don't have access to a test-runner image.
[12:16] <wgrant> Sad.
[12:36] <maxb> I have branches of meta-lp-deps ready for pushing. Any thoughts on the preferred bzr format for new stuff?
[12:36] <wgrant> maxb: 2a
[12:37] <maxb> I guess the chances of anyone who isn't already branching launchpad itself wanting to hack on meta-lp-deps are vanishingly remote, so makes sense
[12:37] <wgrant> Right.
[12:37] <wgrant> And 2.0 is coming RSN.
[12:37]  * maxb runs some bzr upgrades
[13:04] <wgrant> Who owns mailing lists? Both https://edge.launchpad.net/launchpad-foundations and https://edge.launchpad.net/launchpad-registry claim to.
[13:07] <salgado> wgrant, -registry
[13:08] <wgrant> salgado: That's what I suspected. I see that Foundations lays claim to Registry itself, too.
[13:23] <abentley> wgrant: The registry team is like a subteam of the foundations team.
[13:24] <wgrant> abentley: I see.
[13:25] <wgrant> salgado: You are lord of the Apache log parser, aren't you?
[13:25] <salgado> wgrant, I wrote the log parser that counts downloads of LibraryFileAliases
[13:27] <wgrant> salgado: Right. I've refactored and split it so it can be used to count PPA downloads too. Do you want to look at that, or will anybody do?
[13:27] <salgado> wgrant, I'd be happy to have a look
[13:29] <salgado> wgrant, how are you going to count PPA downloads? are PPAs served by the librarian now?
[13:30] <wgrant> salgado: No. There will be (well, I sort of have it mostly working already) an alternate script which works out the archive and package. It uses the same infrastructure as the librarian one, but uses different database stuff and path format.
[13:32] <salgado> I see
[13:32] <wgrant> salgado: It would actually be much harder if PPAs were served by the librarian.
[13:33] <wgrant> salgado: So, https://code.edge.launchpad.net/~wgrant/launchpad/refactor-librarian-log-parser and https://code.edge.launchpad.net/~wgrant/launchpad/refactor-librarian-log-parser-part-2 are what I have now. Can you advise me if I'm on the right track or have done something utterly stupid, as seems likely?
[13:38] <salgado> wgrant, can you give me an overview of the changes in each branch?
[13:40] <wgrant> salgado: Sure. Give me a sec.
[13:42] <wgrant> salgado: So, basically, all the non-LFA-specific code has moved into lp.services.apachelogparser. The first branch does everything except stuff from cronscripts/parse-librarian-apache-logs.py, while the second branch includes that.
[13:43] <wgrant> salgado: This leaves a fairly tiny amount of code in canonical.launchpad.scripts.librarian_apache_log_parser and cronscripts/parse-librarian-apache-logs.py, and a similarly small amount for PPAs later on.
[13:44] <sinzui> salgado: can you mark your bugs on https://edge.launchpad.net/launchpad-registry/+milestone/2.2.8 as FIX COMMITTED or move them to 3.0? I want to close the milestone
[13:46] <salgado> sinzui, done
[13:46] <sinzui> thanks
[14:04] <salgado> wgrant, the refactorings in the first branch look good. for the second I'll need more time
[14:04] <salgado> wgrant, why do you think you've done something stupid there?  are you seeing any test failures or unexpected behaviour?
[14:05] <wgrant> salgado: The second one has just one unique revision, with a 200 line diff.
[14:05] <wgrant> salgado: Oh, no, just guessing I've done something horribly wrong.
[14:06] <salgado> yeah, I'm looking at the 200-line diff here, but it seems to touch all the code of ParseLibrarianApacheLogs.main(), which I don't remember anything about
[14:07] <wgrant> salgado: Ah, right, that one is a bit big.
[14:09] <salgado> wgrant, anyway, I'll have a closer look at that.  will get back to you soon
[14:09] <wgrant> salgado: Thanks. The first one is sane enough to propose a merge?
[14:09] <salgado> wgrant, I think so
[14:10] <wgrant> salgado: Lovely. Thanks
[14:55] <sinzui> barry: bac: I'm going to convert the list of simple page conversions to bugs that the we can assign to ourselves at our own pace.
[15:02] <barry> sinzui: grat
[15:02] <barry> sinzui: er, great!
[15:28] <barry> danilos: when you have a chance, please set up the gnu mailman translation group
[15:30] <danilos> barry: done, https://translations.edge.launchpad.net/+groups/mailman-translators
[15:31] <danilos> barry: I've made you the owner (you can reassign to a team or whatever) so you can assign each per-language team
[15:31] <sinzui> barry: bac: You can see the UI 3.0 update bugs at https://edge.launchpad.net/launchpad-registry/+milestone/3.0
[15:31] <danilos> barry: we usually have people register teams like mailman-l10n-XX
[15:31] <danilos> (XX is the language code)
[15:31] <bac>  sinzui: great, thanks!
[15:31] <barry> danilos: fantastic, thanks
[15:32] <barry> sinzui: looking
[15:32] <barry> sinzui: so i will just claim some bugs and start working on them
[15:33] <sinzui> barry: yep. I think the forms are just change the layout and add the page_title to the view.
[15:35] <barry> +1
[15:49] <flacoste> abentley: say i use bzr co -r '2009-07-27' to create a working tree at a particular point in the past, how do I update the working tree to say its state one week later?
[15:49] <flacoste> bzr co - r '2009-08-03' fails with .bzr already exists
[15:49] <maxb> I want to give ownership of some branches to ~launchpad. If I post to launchpad-dev@, I guess there are some people on the launchpad dev team with the relevant super admin powers to take the branches?
[15:50] <flacoste> maxb: yep, you can't give it away yourself?
[15:50] <maxb> You can't give to a team you're not a member of
[15:50] <maxb> Which is fair enough, if inconvenient in this instance
[15:50] <flacoste> maxb: ok, we need to ask a LOSA to do it then, what branches?
[15:51] <maxb> I was thinking that perhaps being a ~bazaar-expert would be enough
[15:51] <maxb> abentley could tell us :-)
[15:52] <abentley> flacoste: there isn't a way to do that.  update -r is a missing feature.
[15:52] <flacoste> great
[15:52] <wgrant> abentley: revert -r?
[15:52] <maxb> not quite the same
[15:52] <maxb> that would change the file text, but not what revision the tree thought it was related to
[15:52] <sinzui> bac: I see you changes a bug to Medium. What does that mean?
[15:52] <wgrant> True.
[15:53] <flacoste> revert -r seems to work
[15:53] <maxb> flacoste: but now try bzr status
[15:53] <flacoste> well, for my purpose, i simply care about the content of the tree
[15:53] <bac> sinzui: that it's higher than a low.  sorry, i forgot our ban on mediums
[15:54] <maxb> I recall having a long discussion on #bzr about why update -r was missing, and it being something to do with the confusion about what it should mean for bound branches
[15:54] <sinzui> bac: you you are committing us to fixing the bug by a certain time, it is High. otherwise it is low
[15:54] <bac> sinzui: i can change it to high if you want, but it's in review now and will be fix committed soon
[15:54] <bac> high it is
[15:54] <flacoste> revert will work fine for my purpose here
[15:55] <maxb> abentley: does being a ~bazaar-expert give you the powers to reassign some branches away from me to ~launchpad?
[15:55] <sinzui> bac: Bugs uses Medium to mean we want to fix it bug we wont commit to it. I think that stinks because it implies Low is "Someone wants my to fix their bug but I do not wan to."
[15:56] <gary_poster> cprov: hey.  is poppy soyuz-related?  If so, am I right in assuming we still use it?
[15:56] <maxb> gary_poster: I thought it was the upload ftp server?
[15:56] <cprov> gary_poster: yes, it is.
[15:56] <wgrant> Yes, it's... rather critical.
[15:56] <gary_poster> :-) ok
[15:56] <gary_poster> ok thanks all
[15:57] <abentley> maxb: I am not sure.
[15:57] <wgrant> gary_poster: Porting it off ThreadedAsync?
[15:57] <gary_poster> yeah
[15:57] <gary_poster> in spare cycles ;-)
[16:23] <henninge> What's wrong with buildbot? The page won't load ...
[16:43] <deryck> danilos, ping.
[16:43] <danilos> deryck: hi
[16:56] <bac> sinzui: on the product index page, the in-line programming languages picker is broken.
[16:56] <sinzui> bac: I saw
[16:56] <bac> ok
[16:57] <barry> danilos: ping
[16:58] <danilos> barry: pong
[16:58] <barry> bac: there's a bug open on lazr-js about that
[16:58] <barry> it's a lazr-js bug
[16:58] <bac> barry: ok.
[16:58] <barry> danilos: hi.  will you be around for a little while to talk about your page titles email?  i am tasked with trying to figure it out and would like to pair with you on this
[16:59] <danilos> barry: not for a lot longer, and I believe I should have a call with flacoste in a few minutes
[17:00] <danilos> barry: let me see if flacoste is around for a call (I know he was in the UI call), and if we are not having a call, we can do it instead
[17:00] <barry> danilos: okay, it can fill you in with the basics.  i'll figure out what i can and we can chat tomorrow.
[17:00] <barry> s/it/he
[17:00] <danilos> barry: ok, cool
[17:01] <flacoste> danilos: i'm free!
[17:01] <danilos> flacoste: cool :)
[17:01] <barry> danilos: i am going to get some lunch, flacoste and you can fill me in on anything you decide and i'll read the scrollback when i return
[17:01] <danilos> barry: ok, though it'll mostly be phone call :)
[17:03] <barry> cool
[17:03] <sinzui> noodles775: ping
[17:29] <rockstar> sinzui, jtv, deryck - Could I get your 3.0 conversion progress reports by email?
[17:29] <rockstar> deryck, I picked you because intellectronica is on leave (and I'm sending the email out for him)
[17:29] <deryck> rockstar, np.
[17:29] <jtv> rockstar: mwhmyumsoonmhwmsI'mthrough<smack>dinnermyom
[17:31] <rockstar> jtv, :)
[17:42] <flacoste> abentley, rockstar: as members of ~bazaar-experts can you reassign ownership of branches to arbitrary team?
[17:42] <abentley> flacoste: I don't know.
[17:43] <flacoste> ok, i'll ask a LOSA anyway
[17:45] <maxb> flacoste: they can, I checked in a dev launchpad instance
[17:54] <jtv> rockstar: yhm
[18:16] <rockstar> abentley, hey - does hitchhiker have a way of killing and recreating the .bzr directory of a branch?
[18:16] <rockstar> abentley, I need to restart an import branch, but the user has made it a development focus, so I can't delete and try again.  I was thinking maybe I'd use hitchhiker to be clever.
[18:18] <abentley> rockstar: It can delete the .bzr directory, it can't create a new one.
[18:18] <abentley> rockstar: but bzr can.
[18:21] <rockstar> abentley, hm, as a bzr-expert, can I just init the path then?
[18:21] <abentley> rockstar: Yes.
[18:22] <rockstar> abentley, hm, when I try to get into the branch, it tells me the dir doesn't exist...  wtf?
[18:23] <rockstar> Oh wait, I think it's trying to get into the mirrored area.
[18:23] <rockstar> Nope that wasn't it.
[18:24] <abentley> rockstar: This is an import branch?  I don't think you have access to those.
[18:24] <rockstar> abentley, yeah, that might be it.
[18:25] <rockstar> abentley, although that seems kinda odd.  I can mess with people's owned branches, but I can't mess with the ones that are owned by a team I'm a member of.  :)
[18:26] <rockstar> Anyway, I'll just have the user remove the series link, and then do the change through the UI.
[18:40] <salgado> sinzui, I'm thinking of doing the person-edit* pages now.  is that ok or has someone already taken them?
[18:40] <sinzui> salgado: take them all
[18:41] <sinzui> salgado: I broke it into smaller bugs: bug 421975, bug 421976
[18:41] <mup> Bug #421975: Update identity/location pages to UI 3.0 <story-ui-3> <Launchpad Registry:Triaged> <https://launchpad.net/bugs/421975>
[18:41] <mup> Bug #421976: Update keys/wikiname pages to UI 3.0 <story-ui-3> <Launchpad Registry:Triaged> <https://launchpad.net/bugs/421976>
[18:41] <salgado> sinzui, cool, I'll assign them to me
[18:42] <sinzui> salgado: we can avoid creating links between the edit pages if we add the edit icon to the information on the +index page.
[18:43] <sinzui> salgado: beuno really wants us to do that. It might be awkward if we cannot add it to the 2.0 +index page
[18:44] <salgado> sinzui, ok, I'll give that a try, but '2.0'?
[18:44] <sinzui> salgado: the user page is still 2.0
[18:45] <sinzui> salgado: I see we have links to the edit pages in now...maybe we should keep them. When we update the +index to 3.0, we can remove them from the edit pages.
[18:45]  * sinzui thinks that is a fastest way to update the pages
[18:47] <salgado> that sounds like a plan
[18:50]  * barry is doing the /people/+new{person,team} pages
[18:51] <salgado> sinzui, currently it's only the +edit page that has links to other pages. should I add them to +edit[irc/jabber/etc]?
[18:53] <sinzui> salgado: we could create a menu, but I think that is work we should avoid. We use a related pages menu on an edit page if it is not possible to get to the form from the +index page
[18:53] <sinzui> salgado: branding is only form that we cannot make a link to from an +index page.
[18:54] <sinzui> salgado: that is why is suggested that we may want to update the 2.0 +index page
[18:54] <sinzui> salgado: You could pick something else from https://edge.launchpad.net/launchpad-registry/+milestone/3.0 and we take take up the person edit pages /after/ the user page is 3.0
[18:55] <salgado> that might be a better idea
[18:56] <salgado> barry, I think you'll want to assign bug 421972 for you, then ;)
[18:56] <mup> Bug #421972: Update merge pages to UI 3.0 <story-ui-3> <Launchpad Registry:Triaged> <https://launchpad.net/bugs/421972>
[18:57] <salgado> sinzui, I'll take bug 421966, then
[18:57] <mup> Bug #421966: Update contact, annoucement, driver pages to UI 3.0 <story-ui-3> <Launchpad Registry:Triaged> <https://launchpad.net/bugs/421966>
[18:57] <sinzui> fab, you'll be done is 2 hours
[18:57] <sinzui> maybe less
[18:58] <barry> salgado: i grabbed bug 421974
[18:58] <mup> Bug #421974: Update new person/team pages to UI 3.0 <story-ui-3> <Launchpad Registry:In Progress by barry> <https://launchpad.net/bugs/421974>
[18:59] <salgado> barry, duh. I misunderstood you and were thinking you'd be doing the /people/+*merge pages. nevermind me
[19:01] <barry> :)
[19:08] <salgado> sinzui, are all form pages supposed to have the <h2 content="context/title"> before the page's main heading, like in http://people.canonical.com/~salgado/double-heading.png ?
[19:09] <sinzui> salgado: That is a header issue that barry is going to work on, and it related to bug 417089
[19:09] <mup> Bug #417089: the base-layout heading-slot should not render any heading for IPrimaryContext <story-ui-3> <Launchpad Foundations:Triaged by sinzui> <https://launchpad.net/bugs/417089>
[19:10] <sinzui> salgado: ignore it since we have more than 50 pages that do exactly what you are seeing
[19:11] <salgado> ok, cool
[19:11] <barry> right.  i'm going to work on that as soon as i get this other bug into review (should be within the hour)
[19:11] <barry> danilos: bug 422150 describes the other problem i mentioned in our skype
[19:11] <mup> Bug #422150: Not all series are displayed when setting up translation branches <Launchpad itself:New> <https://launchpad.net/bugs/422150>
[19:11] <danilos> barry: cool, thanks!
[19:12] <danilos> barry: don't forget the "john is the uploader" bug as well :)
[19:13] <barry> danilos: that one's in the email i just sent, following up to that thread
[19:13] <barry> hey is anybody having trouble resolving the dns for launchpad.net?
[19:14] <danilos> barry: excellent, always a step ahead, thanks!
[19:14] <barry> :)
[19:14] <bac> hi sinzui.  can i have a mid-imp chat with you re: bug 422128?
[19:14] <mup> Bug #422128: Making a private team the owner of a project fails if the project has a ProductRelease <Launchpad Registry:Triaged by bac> <https://launchpad.net/bugs/422128>
[19:14] <barry> hmm.  it seems happy again.
[19:14] <barry> sinzui: i guess i should steal the assignment of bug 417089
[19:14] <mup> Bug #417089: the base-layout heading-slot should not render any heading for IPrimaryContext <story-ui-3> <Launchpad Foundations:Triaged by sinzui> <https://launchpad.net/bugs/417089>
[19:15] <sinzui> barry: I'll paste a conversation into the bug
[19:17] <sinzui> barry: I updated the bug
[19:17] <barry> sinzui: thanks
[19:34] <sinzui> bac:  sorry, I got distracted. Yes talk about the bug now
[19:54] <bac> hi sinzui
[19:55] <sinzui> bac: skype?
[19:55] <bac> ok
[20:13] <EdwinGrubbs> cprov: ping
[20:13] <cprov> EdwinGrubbs: pong
[20:14] <EdwinGrubbs> cprov: I'm trying to make a team the maintainer of a sourcepackagerelease, so that I can test the showing/hiding of the Maintained Packages link in the portlet. Is there a test helper function for that?
[20:16] <cprov> EdwinGrubbs: not specifically, but you can create new SPRs using SoyuzTestPublisher.getPubSource(maintainer=a_person)
[20:17] <EdwinGrubbs> thanks
[20:19] <cprov> EdwinGrubbs: np
[20:48] <beuno> EdwinGrubbs, has the team page landed yet?
[20:49] <EdwinGrubbs> beuno: no, I'm working on tests for it.
[20:49] <beuno> EdwinGrubbs, super
[20:54] <gary_poster> flacoste: someone looked at lp this weekend and was a bit horrified to discover that not only did our JS tests not pass, they didn't even run because of a trivial bug (http://python.pastebin.com/m34a9f134).  This highlighted to me that mars' absence is kind of a big deal, especially with 3.0's focus.
[20:54] <gary_poster> AFAIU, we don't have automated tests, and we don't have any chance of getting a non-red buildbot for this.  I don't think I have anybody on foundations that can work on this, but it feels a bit urgent.  Do you have any thoughts?
[20:55] <gary_poster> (we don't have automated tests that are run, I mean, apparently)
[20:55] <flacoste> gary_poster: i don't unfortunately
[20:57] <gary_poster> flacoste: ok.  are we getting further and further in debt because of that right now, or is custom JS halted ATM because of the template changes?
[20:57] <flacoste> gary_poster: kind of the latter
[20:57] <flacoste> everyone is working on template conversion
[20:58] <flacoste> so we shouldn't be adding JS much at this point
[20:59] <gary_poster> flacoste: ok.  I guess I'll bring up with team leads that problem, and ask that if any JS-aware dev starts to move from templates to new JS things, they move instead to fixing the tests.  I think that should be the next JS thing to happen, with or wothout mars
[20:59] <flacoste> i agree
[20:59] <gary_poster> ok cool
[21:06] <beuno> flacoste, what are you using to create the burndown chart for the UI conversion?  I was thinking about doing a per-week checkout and creating a report per week
[21:06] <beuno> thought about all kinds of fancy things, but considering we're 3 weeks to go...
[21:06] <flacoste> beuno: it's all taken care of
[21:06] <flacoste> beuno: i have the data
[21:06] <beuno> flacoste, super
[21:07] <flacoste> and updating the script and HTML template to show it
[21:07] <flacoste> beuno: i'll send you an email with update instructions
[21:07] <beuno> flacoste, perfect, looking forward to seeing what it looks like  :)
[21:07] <flacoste> beuno: actually, if you are not going away soon, i'll ask you for feedback on the actual charet
[21:07] <beuno> flacoste, I am not
[21:07] <beuno> have TONS of things to do
[21:07] <beuno> *TONS*
[21:07] <beuno> caps and bold
[21:08] <flacoste> which i think means you are locked to your computer for a while...
[21:27] <maxb> So, now we have branches for launchpad-dependencies, I want to submit some changes - what's the right thing to do with debian/changelog here - completely update it ready to build the new version? Leave it saying UNRELEASED?
[21:44] <mwhudson> maxb: are you asking for policy or advice?
[21:44] <mwhudson> i'm pretty sure there's no policy yet...
[21:44] <maxb> either? both?
[22:01] <thumper> beuno: I really need to talk to you about breadcrumbs soon
[22:01] <thumper> beuno: I have a call with abentley now
[22:01] <thumper> beuno: perhaps in an hour and a half maybe?
[22:01] <beuno> thumper, sure. One hour sounds better, but we can see what happens  :)
[22:03] <flacoste> beuno: http://people.canonical.com/~flacoste/conversion.html
[22:04] <thumper> flacoste: nice!
[22:04] <flacoste> thumper: well, arguably...
[22:04] <flacoste> kind of show in our face that we aren't going to make it
[22:05] <thumper> flacoste: I've submitted a CP request for the branch listing timeouts in production
[22:05] <flacoste> ok, i'll look at it in an instant
[22:05] <thumper> flacoste: ta
[22:06]  * thumper waits for abentley to call
[22:09] <flacoste> maxb: i'd vote for "ready to build"
[22:14] <flacoste> beuno: i sent you an email with the update instructions
[22:14] <maxb> flacoste: ok, and "bzr tag" the new revision too?
[22:16] <maxb> I guess I could even put the package to my PPA, but then if the changes are not accepted as-is, I have a version in my PPA which I can't delete and revise
[22:16] <rockstar> flacoste, your page is great.  I fear we have too many people setting up this graph.  It might be nice to have one canonical page (no pun intended)
[22:18] <flacoste> rockstar: beuno is the canonical source now
[22:19] <rockstar> flacoste, he doesn't have your super sexy graph.
[22:19] <flacoste> rockstar: he will, my copy is just a demo, it's not updated
[22:20] <flacoste> maxb: about bzr tag, i have no idea how this works, so whatever you feel makes sense
[22:20] <flacoste> maxb: regarding you publishing some version, i don't think it's a big deal. if changes are not accepted, we'll see them in the changelog
[22:20] <rockstar> flacoste, okay.  We should maybe think about putting it somewhere official looking.
[22:20] <flacoste> maxb: or we can use UNRELEASED until it's merged approved
[22:23] <barry> jml: please make --headless go faster :(
[22:23] <maxb> That might be best ... I put the branch up as UNRELEASED, file a merge proposal, wait for approval, then do one more commit changing UNRELEASED->karmic, do the bzr tag, upload the source package to my PPA, and then a ~launchpad member just has to pull/push the changes and copy the packages between PPAs
[22:24] <beuno> flacoste, cool, thanks
[22:25] <beuno> I will update now
[22:25] <flacoste> maxb: that sounds good
[22:25] <barry> sinzui: ec2 --headless is too slow so i'm crossing my fingers and jfdi
[22:26] <rockstar> barry, I think you meant to direct your statement about --headless to mwhudson
[22:26] <lifeless> mwhudson is not headless!
[22:27] <sinzui> barry: your changes should have only affected the doc/browser/stories tests. if something fails, I think you have justification to remove the offender
[22:28] <barry> i thought i saw a bug from jml on --headless, but maybe it was mwhudson (or maybe it's assigned to him)
[22:28] <barry> sinzui: yep.  worst case, backing out the button change is easy
[22:28] <mwhudson> yes, --headless should go faster
[22:28] <mwhudson> unfucking buildbot seems higher priority right now though
[22:32] <beuno> flacoste, looks like we're doing a great job at deleting templates
[22:33] <flacoste> beuno: well, not enough i think, we still have more than 60% to go and 3 weeks left
[22:33] <flacoste> we need to make a serious dent in that curve this week
[22:34] <mars> :)
[22:35] <mars> nice burndown chart.  it really helps visualize the progress.
[22:40] <gary_poster> mars: whoa! hey man!  how goes it?
[22:40] <mars> gary_poster, busy :)
[22:40] <gary_poster> heh, I bet
[22:41] <mars> nothing much else to say, really.  Just normal newborn stuff, but going through 30 nappy changes a day, instead of the usual 12.
[22:41] <gary_poster> lol
[22:42] <gary_poster> cool, well, congratulations.  hope you send some pics to warthogs eventually
[22:42] <mars> names first, then pictures :)
[22:42] <gary_poster> heh, ok, I'll agree to that ordering
[22:42] <beuno> flacoste, http://people.canonical.com/~beuno/conversions.html
[22:42] <mars> everyone is happy and healthy, btw.
[22:42] <gary_poster> excellent
[22:47] <jml> :(
[22:47] <jml> my network connection went down while running tests on an instance.
[22:48] <gary_poster> maxb: btw, I have a branch that cleans out the last traces of the old zope branch, ~gary/launchpad/poppyasync.  We've had more than the usual share of spurious failures today, so I'm retrying an ec2test run.  Should be in either within the next few hours, or the next ~16 or so.  I tried to make some progress on the karmic/buildout problem but getting things running on karmic is still not done, and I couldn't focus on it exclusively.
[22:48] <gary_poster> But anyway, I'm working on these things.
[22:49] <gary_poster> bye all
[22:52] <rockstar> beuno, WOOT!
[23:01] <thumper> rockstar: skype?
[23:01] <rockstar> thumper, here
[23:01] <thumper> rockstar: skype doesn't think so
[23:02] <rockstar> Skype == retarded
[23:03] <Ursinha> lol
[23:07] <barry> looks like we're in testfix
[23:07] <mwhudson> barry: shouldn't be
[23:07] <rockstar> We never SHOULD be in testfix
[23:07] <barry> mwhudson: hmm. i just had a branch fail because it didn't match the testfix regexp
[23:11] <mwhudson> barry: hmm
[23:12] <jml> hello
[23:12] <barry> mwhudson: otoh, r9280 seems happy
[23:12] <barry> (in buildbot)
[23:12] <mwhudson> barry: jtv's branch seems to be being processed
[23:13] <mwhudson> barry: regexps are a notoriously wonderful user interface component, are you sure pqm is telling you it's in testfix?
[23:14] <barry> mwhudson: i just deleted the email :(  but i resubmitted :/  the regexp had no ui= or r= match that i could tell
[23:14] <barry> mwhudson: let's see what happens with jtv's and my branches
[23:15] <mwhudson> The size of the diff (15093 lines) is larger than your specified limit of 1000 lines
[23:15] <mwhudson> oof
[23:20] <mwhudson> barry: can you say [ui=edwin, sinzui] yet?
[23:20] <sinzui> I do not think you can
[23:20] <sinzui> ui=<beuno|none|rs>
[23:21] <barry> really?  istr doing that in a previous branch
[23:21] <barry> it would be crazy if we can't since we have ui mentats
[23:22] <sinzui> barry: without a request to a losa to update the *provided* RE, it wont happen
[23:22] <barry> are there any losas around right now?
[23:22] <spm> barry: no we're all hiding. sorry. :-P
[23:22] <sinzui> barry: first we need to get the current RE
[23:22] <mbarnett> barry: none, none whatsoever!
[23:22] <barry> spm: can you give us the current regexp for pqm?
[23:22] <barry> you guys... :)
[23:23] <spm> arrrgghhh!!! stop typing 'bzr' when you want 'barry'
[23:23] <spm> barry: sure. db-devel? devel?
[23:23] <barry> spm: devel
[23:24] <spm> barry: commit_re=(?is)^\s*(:?\[testfix\])?\[(?:release-critical|rs?=[^\]]+)\]\[ui=(?:.+)\]
[23:25] <barry> mwhudson, sinzui ^^ see?  ui=.+
[23:25]  * jml tries running the tests for this branch again.
[23:25] <mwhudson> barry: cool
[23:25] <barry> yay!  well, let's see what happens
[23:26] <mwhudson> jtv's change landed
[23:27] <barry> cool
[23:29]  * jml files bug 422274
[23:29] <mup> Bug #422274: PQM regex rejection emails are confusing <build-infrastructure> <Launchpad Foundations:New> <https://launchpad.net/bugs/422274>
[23:29] <thumper> beuno: ping
[23:30] <beuno> thumper, pong
[23:30] <thumper> beuno: call?
[23:30] <beuno> thumper, in 10
[23:30] <thumper> ok
[23:31] <thumper> flacoste_afk: how close are we to python 2.5 now?
[23:34] <beuno> thumper, ready
[23:34] <maxb> thumper: http://dev.launchpad.net/LaunchpadOnKarmic has a list of known test failures
[23:36] <barry> success this time
[23:46] <beuno> thumper, https://wiki.canonical.com/Launchpad/UI/Navigation
[23:46] <mwhudson> barry: oh, before, it's possible that the buildbot-poller hadn't noticed that we were out of testfix yet
[23:47] <mwhudson> spm: how often does the buildbot-poll.py script run?
[23:48] <barry> mwhudson: that's what i was thinking
[23:48] <spm> mwhudson: every 5
[23:48] <mwhudson> spm: thanks
[23:48] <mwhudson> MOAR EVENTS PLS
[23:49] <lifeless> mwhudson: so
[23:49] <lifeless> mwhudson: there is a fix branch script; that I've been nagging you to run :)
[23:50] <lifeless> mwhudson: and as Andrew points out, users cannot fix their mirrored branches themselves - we overlooked that in the initial work.
[23:50] <mwhudson> lifeless: on which branches?
[23:50] <lifeless> bug 354036
[23:50] <mup> Bug #354036: ErrorFromSmartServer - AbsentContentFactory (unfixable by users) error when  pulling a branch from the mirrored area <hpss> <lp-needs> <Bazaar:Fix Released by spiv> <Bazaar 1.13:Fix Released by tanner> <Launchpad Bazaar Integration:Fix Committed> <bzr (Ubuntu):Confirmed> <https://launchpad.net/bugs/354036>
[23:50] <mwhudson> lifeless: it sounds like it's going to take a LOSA to run this script
[23:50] <mwhudson> lifeless: is there much value in going through me?
[23:51]  * mwhudson puts his build engineer hat on so hard it cover his eyes
[23:51] <lifeless> you could add the ability for people to say 'please remirror'
[23:51] <lifeless> which would be generally useful as a in-extremis knob.
[23:55] <mwhudson> yes, there's a bug about that already
[23:55] <mwhudson> which i am also not going to work on this month
[23:55] <lifeless> ok
[23:55] <lifeless> then its an rt tissue
[23:55] <mwhudson> yeah
[23:56] <beuno> barry, still around?