[00:05] <barry> beuno: i am
[00:07] <beuno> barry, want to have that heading call?
[00:08] <barry> beuno: sure!
[00:08] <barry> beuno: give me 2m
[00:10] <beuno> barry, give me 10   :)
[00:10] <barry> beuno: okay, but if jane gets back i'll have to make dinner :)  i'm on skype now, ring me when you're ready
[00:18] <Ursinha> hey rockstar, do you have half a minute?
[00:19] <rockstar> Ursinha, sure, what's up?
[00:21] <beuno> barry, now?
[00:21] <barry> beuno: yep
[00:24] <beuno> barry, https://code.edge.launchpad.net/~sinzui/launchpad/official-portlets/+merge/10946/+review?claim=launchpad&review_type
[00:26] <beuno> barry, https://edge.launchpad.net/bzr
[00:31] <beuno> barry, https://wiki.canonical.com/Launchpad/UI/Navigation
[00:36] <beuno> barry, https://bugs.edge.launchpad.net/bzr/+bug/165293
[00:36] <mup> Bug #165293: collisions through uploading same-named .pack files not handled correctly <packs> <Bazaar:Confirmed> <https://launchpad.net/bugs/165293>
[00:38] <lifeless> beuno: ?
[00:38] <beuno> lifeless, it's my example bug  :)
[00:38] <lifeless> oh kk
[00:42] <barry> beuno: https://launchpad.dev/people/+newteam
[00:44] <barry> beuno: http://people.canonical.com/~barry/screen.png
[00:49]  * barry -> dinner
[01:03] <flacoste> thumper: actually, we should be pretty close
[01:03] <flacoste> thumper: zope is upgraded as is all of our lazr deps
[01:03] <flacoste> thumper: gary wants to tackle the chameleon branch before finishing the 2.5 upgrade
[01:04] <flacoste> thumper: but you might try it, it might actually just work
[01:04] <flacoste> thumper: python2.5 bootstrap.py && ./bin/buildout
[01:07] <thumper> flacoste: I'm happy that we're close
[01:08] <flacoste> yeah, gary wanted to tackle the chameleon integration before it bit rots more
[01:08] <flacoste> and didn't want to risk having it break more because of other deps upgrade
[01:08] <flacoste> besides, a nice performance boost on rendering would be nice for 3.0
[01:10] <beuno> flacoste, any udeas why I'd get this in karmic?  https://pastebin.canonical.com/21664/
[01:12] <bac> salgado-afk: i submitted a patch for the typo poolie reopened as bug 156919
[01:12] <mup> Bug #156919: More information on where to download files needed <Launchpad Registry:Confirmed for salgado> <https://launchpad.net/bugs/156919>
[01:14] <bac> beuno: no python-psycopg2 installed or installed against the wrong python?
[01:15] <beuno> bac, it's ssntalled
[01:15] <beuno> installed
[01:15] <beuno> how do I know against which version of python?
[01:15] <beuno> ah, I think karmic's version is newer, so it's probably taking over the PPA one
[01:15] <bac> beuno: you can dpkg -L python-psycopg2 to see
[01:17] <bac> beuno:  i've got 2.0.8-0ubuntu3~launchpad1
[01:17] <beuno> bac, you are tight
[01:17] <beuno> 2.5 and 2.6
[01:17] <beuno> DAMN
[01:17] <beuno> you are *right*
[01:18] <bac> i *am* cheap, if that's what you meant
[01:18] <beuno> heh
[01:18] <bac> beuno:  this early adoption thing -- is it serving you well?  didn't you go through this about 6 months ago?
[01:19] <beuno> bac, it is not. But I'm 50% massochist.
[01:32] <flacoste> beuno: maxb should have this fixed soon, he's really on top of the dependencies
[01:32] <flacoste> thanks to him, we can expect the karmic updates to be a lot much smoother than Jaunty
[01:33] <flacoste> bac: what are you doing on karmic?
[01:33] <flacoste> already, i mean?
[01:33] <bac> flacoste: dude, i'd be on feisty if i could
[01:34] <bac> i'm *not* on karmic -- i'm still all jaunty
[01:34] <flacoste> ah, i see
[01:34] <flacoste> you were speculating
[01:34] <bac> i was just poking fun at beuno
[01:34] <flacoste> good guess!
[01:42] <beuno> flacoste, it's fixed
[01:42] <beuno> but something else is broken now
[02:00]  * jml frowns
[02:01] <jml> so here's the thing
[02:01] <jml> pocket-based upload permissions have nothing to do with the uploader.
[02:03] <lifeless> who do they have to do with
[02:03] <lifeless> also, you're @ café?
[02:03] <jml> I am.
[02:04] <jml> no one. they are a function of the archive and the distroseries
[02:21]  * jml grumps at soyuz and timezones
[02:24] <lifeless> jml: why is this? surely fine grained permissions will give individual users privilege via team-or-something inheritance?
[02:25] <jml> lifeless, I have no idea what you mean, I'm sorry.
[02:25] <lifeless> jml: ok
[02:25] <lifeless> well I'll be there about 10 past 12
[02:25] <jml> heh
[02:26] <lifeless> if you want to discuss in more detail before ring me
[02:28] <jml> thanks
[02:29] <wgrant> jml: Is canUploadToPocket so hard to use?
[02:29] <jml> wgrant, it's not hard to use
[02:29] <jml> wgrant, the question is whether it's relevant.
[02:31] <wgrant> jml: Not for normal permission checking. I think it's only relevant for whether the branch should be completely immutable.
[02:31] <mwhudson> time for nommage
[02:31] <wgrant> Which goes beyond 'does this user have additional privileges', as it affects even the branch owner.
[02:32] <jml> wgrant, yes, this is what I'm thinking.
[02:32] <wgrant> abentley: Can you forward me the failure email?
[02:33] <jml> wgrant, also, while james_w is still uploading branches, I can see a pocket check getting in the way
[02:33] <wgrant> jml: Crap, you are right.
[02:33] <wgrant> How awkward.
[02:34] <jml> wgrant, yes.
[02:34] <wgrant> Sounds like you need a new distroseries or even distribution column.
[02:35] <jml> well, at the least, I think I want to talk to james_w
[02:36] <wgrant> jml: Actually, maybe you don't need to.
[02:36] <wgrant> jml: Because the branches are probably only made official at the end.
[02:37] <wgrant> So it might not matter that they become immutable.
[02:37] <jml> good point.
[02:37] <jml> but even that means changing my plans a little
[02:38] <wgrant> Why?
[02:38] <jml> since I was going to change the permissions for "make official" from what they are now to "own the branch & can upload"
[02:39] <wgrant> 'own the branch' is probably wrong.
[02:39] <jml> now, it would mean "(own the branch & can upload) OR are local deity"
[02:39] <jml> wgrant, why?
[02:40] <wgrant> jml: Mmm, I guess it's a good idea to require that if it means that privileges will be revoked.
[02:40] <jml> wgrant, well, the thing is that it's unacceptable to allow random uploaders to expand branch permissions
[02:41] <wgrant> But ISTM that launchpad.Edit in general shouldn't be revoked based on IDS.canUploadToPocket. You probably want to still allow editing of the description and all that.
[02:41] <abentley> wgrant: There wasn't a failure email.  I ran it on my own box before submitting it.
[02:41] <wgrant> And I don't think the officialness setting should be forbidden based on that either.
[02:41] <wgrant> abentley: Ah. Can you then advise me which tests failed?
[02:41] <wgrant> Or shall I run it myself?
[02:42] <abentley> wgrant: I don't remember which tests failed.
[02:42] <wgrant> abentley: OK.
[02:49] <jml> wgrant, in an ideal world, I think officialness should be set through a handshake
[02:50] <wgrant> jml: Probably. But that's overcomplex.
[02:50] <jml> I agree :)
[02:50] <wgrant> jml: (owner & uploader) | ~ubuntu-branches is probably the best you can do.
[02:50] <jml> wgrant, yeah, that's what I'm leaning toward.
[02:50] <jml> (where ubuntu-branch == local deity)
[02:50] <wgrant> jml: But it would have been reallly nice to kill off ~ubuntu-branches.
[02:51] <jml> yes, it would have been nice
[02:51] <jml> maybe we still can.
[02:51] <jml> but one step at a time.
[02:53] <jml> and I think the best next step is to change the bug nomination logic to use my newly extracted permissions function
[02:53] <jml> since neither cares about pockets
[02:54] <flacoste> hey jml!
[02:54] <jml> flacoste, hello
[02:54] <jml> sorry I missed your privmsg
[02:54] <jml> xchat hates me
[02:58] <EdwinGrubbs> sinzui: ping
[02:58] <sinzui> Hi EdwinGrubbs
[03:00] <wgrant> jml: Oh! Did anything come of my branch?
[03:00] <EdwinGrubbs> sinzui: it looks like all the story-ui-3 registry bugs are triaged. Do I just steal one and hope that they haven't started on it? I was going to work on it some tonight so I can be ready for reviews in the morning.
[03:01] <sinzui> EdwinGrubbs: Triaged means it is acknowledged an waiting for someone like your self to take and mark in progress.
[03:03] <sinzui> EdwinGrubbs: All the Update...UI 3.0 that are triaged are available: https://edge.launchpad.net/launchpad-registry/+milestone/3.0
[03:14] <wgrant> jml: Was that the instance during which the network died?
[03:15] <jml> wgrant, yes. it was
[03:15] <jml> wgrant, sorry, I'm on the phone right now
[03:15] <jml> wgrant, I've fired off another ec2test instance for merging
[03:16] <wgrant> jml: Isn't that just going to die silently again?
[03:16] <jml> wgrant, who knows!
[03:16] <wgrant> We shall see. Thanks.
[04:45] <wgrant> Can somebody please ec2test lp:~wgrant/launchpad/refactor-librarian-log-parser? Apparently there are failures, but I can't run the whole test suite sufficiently reliably here at the moment.
[05:15] <jml> wgrant, hey
[05:15] <jml> wgrant, I can do that.
[05:16] <wgrant> jml: Thanks.
[05:21] <jml> wgrant, have you got any email about the structural subscription branch?
[05:22] <wgrant> jml: No :(
[05:22] <jml> ok
[05:22] <jml> the instance isn't running
[05:23] <jml> this is obviously a critical bug in the test suite
[05:23] <jml> ec2test, rather
[05:24] <wgrant> Well, ec2test is meant to terminate the instance in situations where the test suite dies.
[05:25] <wgrant> So it's doing exactly what its meant to, however useless that may be.
[05:27] <mwhudson> it's also meant to tell you what happened before that
[05:27] <wgrant> Hm, so it is.
[05:27] <wgrant> Hadn't looked at ec2test-remote in detail.
[05:27] <wgrant> So it is being bad after all.
[05:34] <jml> wgrant, any situation where you can run tests and not get results reliably is critical, imo
[05:34] <jml> wgrant, otherwise, wtf does 'test' mean?
[05:35] <wgrant> jml: 'no results' == 'uberfail'
[05:38] <wgrant> jml: Do you have any idea how far through it died?
[05:38] <jml> wgrant, no, none at all.
[05:39] <jml> wgrant, basically, I threw it over the wall, and nothing came back.
[05:39] <wgrant> jml: Right. Damn.
[05:41] <wgrant> jml: There's nothing that can really be done besides running it headless and hoping the connection survives, is there?
[05:43] <jml> wgrant, running headful, itym
[05:43] <wgrant> jml: That one.
[05:46] <thumper> For anyone who is interested: https://dev.launchpad.net/Code/Review/Plans
[05:49] <jml> thumper, thanks!
[05:51] <jml> mwhudson, how much pain would be involved in setting up a buildbot that ran with --coverage
[05:51] <wgrant> Wouldn't that take like forever to run?
[05:52] <jml> wgrant, yes.
[05:53]  * jml files some bugs
[05:54] <mwhudson> i think a rule of thumb is that --coverage takes 5x as long as normal
[05:54] <mwhudson> jml: setup, not much pain
[05:55] <spiv> Fortunately, every test that uses subprocesses will seem 5x as fast with --coverage ;)
[05:55] <mwhudson> spiv has a point
[05:56] <mwhudson> you could probably get around that by running the tests with a mangled ./bin/py
[05:56] <spiv> Or just change site.py in the ec2 image...
[05:59] <jml> well, I'm happy to have an incomplete coverage report to start with
[06:00] <jml> the report is still interesting even if it ignores coverage via subprocess execution
[06:00] <spiv> Yes.
[06:00] <spiv> Plus, it adds motivation to fix tests that use subprocesses :)
[06:01] <jml> or delete code only used in subprocesses :)
[06:25]  * mwhudson is more or less done for the day
[06:46]  * jml is off
[07:03] <lifeless> so coverage times are distorted
[07:03] <lifeless> measure time and coverage separately.  KThanks.
[07:04] <lifeless> mwhudson: you can get some rad coverage using lspro
[07:04] <lifeless> f
[07:29] <jml> mwhudson, you've probably EODd, but https://bugs.edge.launchpad.net/launchpad-foundations/+bug/5814 is interesting
[07:29] <mup> Bug #5814: want to know breakdown of test run time by area of development <build-infrastructure> <test-system> <Launchpad Foundations:Triaged by flacoste> <https://launchpad.net/bugs/5814>
[07:34] <mwhudson> jml: four figure bug!
[07:34]  * mwhudson is not here
[07:34] <jml> mwhudson, yes!
[08:28] <henninge> Hallo noodles775!
[08:29] <henninge> Moin al-maisan!
[08:29] <noodles775> Hi henninge and al-maisan :)
[08:29] <al-maisan> good morning noodles775 and henninge :)
[08:29] <henninge> noodles775: I am for the first time trying to use a sub-view. I see two different approaches.
[08:30] <henninge> noodles775: Register it as a page in zcml, including the template, and call that page from the enclosing template (@@,,,)
[08:31] <henninge> noodles775: or not register in zcml and tell the sub-view in-line about its template using ViewTemplateFile (I think it is called) and then just calling the view from TAL (structure ...).
[08:31] <henninge> noodles775: are you with me? ;_)
[08:31] <henninge> ;)
[08:31] <noodles775> yep
[08:32] <henninge> noodles775: is there any preference on one of the approaches?
[08:33] <noodles775> So, afaik, at least in soyuz code we usually go for the former (ie. keeping the configuration in the zcml - not that we like zcml, but for consistency ;) ).
[08:33] <al-maisan> hmm .. zcml .. my love ;)
[08:33] <noodles775> I'm not sure of other advantages/disadvantages, wgrant, what are your thoughts?
[08:35] <henninge> I was wondering if using the @@ approach engages more zope machinery than necessary and there might be a performance penalty.
[08:35] <henninge> I am using this in a repeat for a list of translatable strings.
[08:35] <noodles775> yeah, that would be very interesting to know.
[08:35] <noodles775> one tic
[08:36] <noodles775> henninge: why isn't a simple tal:repeat with a template-snippet/macro enough in that case?
[08:36] <wgrant> henninge: I think keeping it in ZCML is better, but I'm not thoroughly opinionated on that yet.
[08:36] <wgrant> Er, noodles775 ^^
[08:36] <noodles775> Why do you need a separate view for each repetition?
[08:36] <noodles775> wgrant: thanks.
[08:37]  * noodles775 looks for similar example for henninge 
[08:37] <wgrant> noodles775: Bug comments, maybe.
[08:37] <henninge> noodles775: well, the display is a bit more complex than just a string.
[08:37]  * wgrant looks.
[08:38] <wgrant> henninge: A tal:repeat can contain anything, though.
[08:38] <henninge> true
[08:38] <noodles775> henninge: sure, I was thinking more of printing a table row for each repetition...
[08:39] <noodles775> henninge: but if you need some complicated manipulation of the repeated item's attributes, then yeah, that's a pain in the template (and is usually where we'd use a view).
[08:40] <henninge> noodles775: yes, there is more to it.
[08:40] <adeuring> good morning
[08:40] <henninge> Hi adeuring!
[08:40] <noodles775> henninge: so in templates/archive-index.pt
[08:40] <adeuring> hi henninge!
[08:40] <noodles775> hi adeuring :)
[08:40] <adeuring> hi noodles775!
[08:40] <henninge> noodles775: I am not sure I want to put this all into the enclosing view
[08:40]  * henninge looks at that
[08:41] <noodles775> henninge: you'll see at the bottom <metal:package-list use-macro="context/@@+macros/source-package-list" />
[08:41] <wgrant> See also bugs/templates/bugtask-index.pt just after line 300.
[08:41] <wgrant> That might be more like what you want.
[08:42] <noodles775> yeah, that's a good example, so the original view is providing an enum of structured information that can be easily repeated.
[08:43] <henninge> wgrant: yes, thanks
[08:43] <wgrant> Great.
[08:44] <noodles775> s/enum/iterable
[08:47] <henninge> noodles775: thanks, too
[08:47] <noodles775> np! /me loves learning too :)
[08:48] <henninge> ;)
[08:59] <noodles775> henninge: jfyi, the reason we use a macro on that archive template is because we re-use the source-package-list in other places too.
[09:00] <noodles775> I'm not sure how expensive the context/@@+macros/macro-name is though.
[09:01] <noodles775> It's not creating a new view though - it just uses the current view (similar to the new navigation menus, afaics)
[09:02] <henninge> noodles775: yes, I was just trying to figure out how that works (from bugtask-index.pt, though).
[09:02] <henninge> noodles775: but I'll go with an extra page and view for now.
[09:02] <noodles775> yep.
[09:02] <henninge> sub-page and sub-view
[09:03]  * henninge needs to get results ... ;)
[09:03] <noodles775> Hmm... I should have said dis-similar to the new menus, they do use their own sub-views too (NavigationMenuTabs).
[09:04] <wgrant> jml: ec2test won't have submitted that branch, will it?
[09:04] <wgrant> jml: (it succeeded -- abentley must have caught devel at a bad time)
[09:05] <jml> wgrant, it doesn't say it submitted
[09:05] <jml> hmm.
[09:05] <jml> I must have forgot the -s
[09:05] <wgrant> jml: Well, I didn't ask you to submit.
[09:06] <wgrant> jml: Because I believed it would fail.
[09:06] <jml> oh right.
[09:07] <jml> wgrant, do you want me to submit?
[09:07] <wgrant> jml: So, can you submit it please? "[r=abentley][ui=none] (wgrant) Refactor the librarian apache log parser so pieces can be reused for PPA download counts."
[09:07] <jml> wgrant, can do
[09:08] <wgrant> jml: Thanks.
[09:12] <jtv> Why does our CSS make labels non-wrappable?  It wreaks total havoc with our radio buttons!
[09:16] <noodles775> jtv: I assume it makes sense in the general case - it's been in the style.css for a long time (r6771). But you can always provide a more specific rule for your exception?
[09:17] <jtv> noodles775: I'm not sure how I'd do that cleanly though, since these are LaunchpadForm-generated.
[09:17] <jml> wgrant, it's in PQM now
[09:17] <jml> statik, are you actually around?
[09:18] <wgrant> jml: Thanks.
[09:20] <noodles775> jtv: in your template, if the call to the form macro is within a div with a class of your choice, you can then style it easily. If you're using generic-edit etc., then I'm not sure :/
[09:21] <noodles775> Hrm, but even in the first case, it would apply to all labels on that form.
[09:21] <jtv> noodles775: it's in there, but CSS says "label { white-space: ... }"
[09:22] <jtv> I wouldn't even mind if I could override it for all labels on that form, except that the problem happens elsewhere as well.
[09:22] <jml> bigjools, I don't have time this evening, but I'd really appreciate the chance to chat with you or cprov about package permissions.
[09:22] <bigjools> jml: of course
[09:23] <bigjools> maybe tomorrow, I can get up early
[09:23] <jml> bigjools, that'd be great
[09:23] <jtv> noodles775: maybe the solution is to give these labels an extra class that doesn't have this setting.  Right now it's just "label," and all labels have wrapping prohibited.
[09:23] <jml> bigjools, thanks.
[09:23] <noodles775> jtv: I'm not sure I'm understanding... if your form is rendered within a <div class="foo">... then you can add a style rule div.foo label {white-space: normal} and it will override the other one (as it's more specific).
[09:25] <jtv> noodles775: oh, hadn't tried it that way...  I just tried setting it directly on the div, but that would be overridden by the label style of course.
[09:36] <jtv> noodles775: nope, that doesn't work either.  :(  I can override label locally, but that's probably not the way Mommy Would Want.
[09:36] <noodles775> jtv: push your branch and I'll try it.
[09:37] <jtv> noodles775: Thanks.  Pushing to lp:~jtv/launchpad/translations-person-3.0-mechanical
[09:38] <jtv> noodles775: will advise when it's pushed in all the way.
[09:39] <noodles775> jtv: great, thanks! And the demo url you're using.
[09:39] <jtv> noodles775: the home page for whomever you're logged in as; Translations tab.
[09:39] <noodles775> Perfect, thanks.
[09:39] <jtv> There, go to "Translations licensing."
[09:40] <jtv> Then make your window narrow enough that at least the text for the bottom radio button want to wrap.
[09:40] <jtv> *wants
[09:40] <jtv> noodles775: pushed!
[09:47] <noodles775> jtv: http://pastebin.ubuntu.com/262973/
[09:48] <noodles775> That works, but I'd not really recommend doing it...
[09:48] <jtv> *facepalm*
[09:48] <jtv> noodles775: I agree, but what's the alternative?
[09:50] <noodles775> jtv: just doing it with the current style and creating a bug explaining the problem so it can be solved generally - there might be other pages that would benefit too.
[09:50] <jtv> noodles775: can't argue with you there; I want this solved for other templates.
[09:51] <maxb> beuno: I'm a little confused by your problem earlier, since python-psycopg2 has the same version in jaunty and karmic. (And I can't see your paste)
[09:51] <noodles775> Great. The less work-arounds we have, the easier it will be for us to fix/maintain etc.
[10:12] <maxb> Whoa, new /builders page.
[10:13] <maxb> Overall, quite shiny, though I don't like the way all the builders are now squished into one table, instead of being visually demarcated by architecture and official/ppa status
[10:13] <maxb> The summary side portlet is neat, though
[10:13] <noodles775> maxb: you can click on the table headers to sort by arch/status etc.
[10:15] <maxb> that's simultaneously neat yet kinda pointless, as it disrupts the default sort that separates official/ppa, and I can't imagine any use case where you want the two mixed
[10:16] <bigjools> maxb: bug 225738 and bug 245459
[10:16] <mup> Bug #225738: new build farm page UI is a regression for buildd admins <ui> <Soyuz:Fix Committed by cprov> <https://launchpad.net/bugs/225738>
[10:16] <mup> Bug #245459: Sort the list of builders by architecture then status, not by hostname <trivial> <ui> <Soyuz:Fix Committed by cprov> <https://launchpad.net/bugs/245459>
[10:16] <noodles775> maxb: the default ordering has all the official first and then all the ppa builders (see the first column). It was a hard problem to solve - the input that cprov got was that it *needed* to be sortable.
[10:19] <maxb> hmm, why does it suddenly need to be sortable when the 2.x page is not?
[10:20] <noodles775> maxb: I think the 1.0 was, and the 2.0 was considered a regression, as per the bug above (I wasn't around, but am just guessing).
[10:22] <maxb> Hmm. I think a good start at fixing the 3.0 layout would be to put ppa and official in separate tables
[10:25] <noodles775> maxb: you can read a bit about the purpose and target audiences that cprov used for the current 3-0 design at https://dev.launchpad.net/SoyuzBuildersIndexPage
[10:25] <noodles775> and chat with him later when he's around.
[10:39] <wgrant> maxb: Also, the distinction between official and PPA, and between the architectures, is going to become much more hazy soon.
[10:40] <wgrant> maxb: This new layout makes that much easier.
[10:57] <deryck> Morning.
[10:57] <noodles775> Hi deryck :)
[10:58] <noodles775> deryck: btw, thanks for the TextAreaEditorWidget - it couldn't have been easier to integrate :)
[10:58] <deryck> noodles775, excellent!  good to hear.
[12:42] <bigjools> wgrant: around?
[13:06] <wgrant> bigjools: I am.
[13:06] <bigjools> wgrant: do you know who's the LP MOTU contact?
[13:06] <wgrant> bigjools: mok0 and myself.
[13:06] <bigjools> fabulous
[13:07] <bigjools> wgrant: I grant you three wishes for Soyuz improvements
[13:07] <noodles775> heh, and you're not allowed to choose things that you're implementing yourself ;)
[13:07]  * wgrant shall put it to the list.
[13:22] <bigjools> wgrant: https://dev.launchpad.net/VersionFourDotO/Soyuz
[13:23] <wgrant> bigjools: Thanks.
[13:23] <bigjools> wgrant: I kept the items from the 3.0 pages on there as suggestions, feel free to re-use them
[13:24] <bigjools> and now, food
[14:04] <gary_poster> maxb: ping?
[14:18] <gary_poster> abentley: btw, I talked with Francis about the approach we talked about for bug 113993.  He thought it sounded good, and had some suggested refinements.  My focus right now is on a couple of other things, but I can maybe get to it next week or the week after.  Alternatively, I can share what Francis told me with you, and you can do it.  Let me know.
[14:18] <gary_poster> uh, mup?  bug 113993 ?
[14:18] <gary_poster> https://bugs.edge.launchpad.net/launchpad-foundations/+bug/113993
[14:19] <abentley> gary_poster: Thanks for following up on that.
[14:19] <gary_poster> np
[14:20] <abentley> gary_poster: For right now, I don't think I'll tackle it, but I'll let you know.
[14:20] <gary_poster> ok cool
[14:21] <gary_poster> I'll keep it on my medium-term to do list
[14:42] <beuno> maxb, it was because I was installing the karmic version, which dos not install in python2.4
[14:58] <sinzui> salgado: Are you still working on bug 419742? Do you want to drop it for 3.0.
[14:58] <mup> Bug #419742: downloads page should include some data about the releases <Launchpad Registry:In Progress by salgado> <https://launchpad.net/bugs/419742>
[14:59] <salgado> sinzui, I've fixed that too; just need to do a couple minor tweaks that martin requested
[14:59] <sinzui> salgado: okay
[15:48] <beuno> anyone know why I could be getting this error?  http://paste.ubuntu.com/263176/
[15:50] <beuno> danilos, looks like something to do with translations  ^
[15:54] <jtv> beuno: libgettextpo isn't building...  Problem with your rf setup.
[15:55]  * jtv is not being very helpful
[15:55] <beuno> jtv, care to give me any tips?
[15:55] <beuno> :)
[15:56] <jtv> beuno: slow but easy to try: move your lp-sourcedeps/sourcecode out of the way and run rocketfuel-setup
[15:58] <beuno> jtv, I can do slow and easy (right after I finish with my skype calls)
[15:58] <beuno> thanks
[16:25] <deryck> rockstar, ping
[16:26] <rockstar> deryck, yo!
[16:26] <barry> beuno: ping
[16:26] <beuno> barry, hi
[16:27] <barry> beuno: hi!  Please verify the rules here https://dev.launchpad.net/VersionThreeDotO/UI/Conversion#Heading%20rules
[16:27] <barry> beuno: the coding guidelines haven't yet been updated, but please let me know if i got any of the ui rules wrong
[16:28]  * beuno looks
[16:28] <beuno> barry, I'm secretly on a call, but will get back to you about this
[16:29] <barry> beuno: no rush.  i have to run up to the local computer store.  my wireless ap died last night.  i'm going to combine that with lunch so will be back in 60 minutes or so
[16:29] <barry> beuno: just pvtmsg me with your feedback and we can chat when i get back
[16:29] <beuno> barry, will do. Have fun computer-shopping
[16:32] <barry> beuno: it's always fun shopping, never fun paying :)
[16:32] <beuno> barry, you can make it more exicting if you don't...
[16:34] <barry> beuno: just be sure to respond to that facebook "bail me out" app request
[16:34] <beuno> :)
[16:38] <danilos> beuno: not sure why you'd get that, it's about compiling gettext python library... is this a new system?
[16:38] <beuno> danilos, upgraded to karmic
[16:39] <danilos> beuno: hum, haven't tried that yet, perhaps I will as soon as the new laptop gets here
[16:48] <salgado> beuno, have you given any thoughts on breadcrumbs for https://code.launchpad.dev/~name12/firefox/main/+bug/5/+delete ?
[16:48] <sinzui> beuno: I think I need to design the product and distro series pages at the same time to ensure they are consistent
[16:49] <beuno> salgado, same as the bug, but an extra "Delete this bug"?
[16:49] <beuno> sinzui, I agree
[16:50] <salgado> beuno, that page is for deleting a bug-to-branch link
[16:50] <beuno> salgado, ah (I don't have a running rf)
[16:51] <beuno> salgado, than "delete link to branch"?
[16:52] <salgado> beuno, right, but the previous items should be identical to the bug's breadcrumbs?  nothing pointing to the branch(es)?
[16:52] <beuno> salgado, I don't think so, no
[16:53] <beuno> that should be an ajax action anyway
[16:53] <salgado> fair enough
[17:12] <maxb> beuno: huh. How did you end up with the karmic version, not the karmic-ppa version?
[17:12] <beuno> maxb, by being stupid  :)
[17:14] <maxb> oh, that reminds me, does a member of ~launchpad fancy copying subversion from ~maxb/+archive/launchpad to ~launchpad/+archive/ppa ?
[18:03] <maxb> gary_poster: Just noticed your ping of 4 hours ago - I'm semi-around now
[18:10] <gary_poster> maxb: np.  hey.  had two checkins of interest for you yesterday
[18:10] <gary_poster> first should get rid of zope branch completely
[18:11] <gary_poster> second switches to lazr.* distributions
[18:12] <maxb> oh that's excellent, I shall be sure to get another testrun going overnight then
[18:12] <gary_poster> that *might* fix the karmic buildout
[18:12] <gary_poster> I'd love to know if it does
[18:30] <maxb> gary_poster: hmm... no luck on the "caused the installation of lazr.uri 1.0" buildout issue.
[18:30] <gary_poster> maxb: ok, thank you very much for checking.  Will try to finish getting lp on karmic up today
[18:31] <maxb> In theory it should be just the same as getting it running on Jaunty, if you add my launchpad ppa
[18:32] <gary_poster> maxb: except the problem is lazr.uri on karmic, right?
[18:32] <maxb> ah, right, well you just temporarily uninstall all the python-lazr-* system packages to dodge around that temporarily
[18:33] <gary_poster> I already have it running on jaunty generally, of course (and squashed various similar buildout-with-system-python problems)
[18:33] <maxb> but then, if the problem you're trying to investigate *is* that problem.... :-)
[18:33] <gary_poster> righht :-)
[18:34] <gary_poster> My zc.buildout changes are about to be reviewed upstream so I'd like them to also address whatever it is you found
[18:34] <gary_poster> so we can be using an official release rather than the local dev release I made
[18:34] <maxb> That would be nice :-)
[18:34]  * maxb has to go afk now
[18:34] <gary_poster> ok thanks maxb
[19:07] <maxb> Most unhelpful test failure EVER!:
[19:07] <maxb> Failure in test testScanRescuesJobFromBrokenBuilder (lp.buildmaster.tests.test_manager.TestBuilddManagerScan)
[19:08] <maxb> that's  it. nothing more
[19:11] <barry> beuno: how'd that page look?
[19:12] <beuno> barry, I... forgot
[19:12] <beuno> looking now
[19:12] <barry> beuno: no worries
[19:13] <beuno> barry, perfect
[19:14] <barry> beuno: sweet.  now let's see if i can implement it :)
[20:31] <beuno> sinzui, "yes"
[20:31] <beuno> let me know if you need anything else from me for that bug
[20:32] <beuno> tomorrow is my last day before I start my vacations
[20:32] <sinzui> beuno: I think salgado has the talent to make that happen after he lands the person page
[20:32] <beuno> sinzui, I think salgado has the talent for everything
[20:33] <salgado> not for snowboarding
[20:45] <beuno> sinzui, who has the "stop using green titles for registry and soyuz" bit on their plate?
[20:45] <beuno> do you know?
[20:46] <beuno> or should I just file a bug?
[20:46] <sinzui> beuno: no one
[20:46] <sinzui> beuno: That is just colour
[20:46] <beuno> sinzui, so can I file a bug and assign to you?
[20:46] <beuno> so I can sleep well while on leave?   :)
[20:46] <sinzui> beuno: I can fix that at the same time I make the download links blue in the sidebar
[20:47] <beuno> sinzui, thank you
[20:47] <beuno> and, the green link is my fault
[20:47] <beuno> I let it leak through the design
[20:47] <beuno> I'm sorry about that
[20:49] <sinzui> beuno: I really think I need to move the RDF to the infomation portlet. Then it will be in the same place for all objects that have it.
[20:51] <beuno> sinzui, I'm almost certain I agree
[20:57] <barry> sinzui: it's a thought, though we do not currently use tags.  in the meantime, i want to change that to read it out of a version.txt file at the top level.  it'll still need a manual update, but it will be /much/ cleaner to change that file than to hack the base-layout.pt.  i just want to be sure i'm not messing with some existing scripts or something
[20:57] <sinzui> barry: You'll need to repeat that...I closed the tab trying to view it
 sinzui: it's a thought, though we do not currently use tags.  in the
[20:58] <barry>         meantime, i want to change that to read it out of a version.txt file
[20:58] <barry>         at the top level.  it'll still need a manual update, but it will be
[20:58] <barry>         /much/ cleaner to change that file than to hack the base-layout.pt.  i
[20:58] <barry>         just want to be sure i'm not messing with some existing scripts or
[20:58] <barry>         something  [15:57]
[20:58] <barry>  
[20:58] <barry> (oh that looks horrible)
[20:58] <sinzui> I agree
[20:58] <barry> cool.  i'll do it in this branch then, since i'm already looking at it
[21:08] <sinzui> barry: I am available now. I got distracted by a test I took a disliking to.
[21:11] <rockstar> sinzui, hi
[21:11] <sinzui> Hi rockstar
[21:12] <rockstar> sinzui, so, do we already have existing styles for 3.0 for something like the branch index pages details area (the one that shows the branch path, how to push/pull, the branch formats, etc.)
[21:12] <sinzui> rockstar: yes
[21:12] <rockstar> It's currently a table, and in 3.0 CSS its not styled at all.  I'm wondering if I should restyle it, or implement it differently.
[21:13] <rockstar> sinzui, where can I find an example?
[21:13] <sinzui> rockstar: it is the <object> Information format
[21:13] <rockstar> sinzui, I'm not sure what that means.
[21:13] <sinzui> Look at the product-index.pt
[21:14] <rockstar> sinzui, nice, thanks.
[21:14] <sinzui> rockstar: The info should follow any narrative (it if exists) and be the first left portlet,
[21:14] <rockstar> sinzui, great.  I'm glad to see we're using dl/dt/dd now too.
[21:14] <sinzui> rockstar: the magic is:
[21:14] <sinzui>             <div class="two-column-list">
[21:14] <sinzui>               <dl id="partof" tal:condition="context/project">
[21:15] <rockstar> sinzui, great, thanks.
[21:27] <rockstar> sinzui, where can I find a demo of the markup in product-index.pt on launchpad.dev?
[21:27]  * rockstar suspects CSS foolery in his implementation
[21:27] <sinzui> rockstar: firefox
[21:28] <sinzui> rockstar: or every project on edge
[21:28] <sinzui> And ever projectgroup and every distro
[21:29] <rockstar> sinzui, ah, okay.  Just as I thought - I need do a little more redesign than previously suspected.
[21:30] <kfogel> sinzui: if someone needs to merge their N launchpad accounts into one account, how do they do that?  Ask us?
[21:30] <sinzui> rockstar: if you need to add something after the <dl>s, do it after the </div> so that the content clears the floats.
[21:30] <kfogel> ~sullivan and ~latchkeyed want to merge into ~sullivan (it's Ian Sullivan, and I just talked to him in person about it)
[21:31] <sinzui> kfogel: If the user cannot do it himself, (he has not email for the old account), he asks a question for a LOSA to do it
[21:31] <kfogel> sinzui: ^^
[21:31] <kfogel> sinzui: no, he should have email.  I'll go talk to him.
[21:33] <sinzui> kfogel: https://edge.launchpad.net/people/+requestmerge will work if the user has email access to the old account.
[21:36] <kfogel> sinzui: thank you.  We just did it.  I'm filing a bug now (or finding a dup) for the fact that the way you merge two accounts is: log in under the account you want to *keep*, go to "deactivate account", then find the link about merging accounts, click on it, and follow the instructions.  Not exactly intuitive to click on deactivate in the account you don't want to deactivate :-).
[21:37] <sinzui> kfogel: This problem will never be intuitive. Having more than one account is the start of non-intuitiveness
[21:38] <kfogel> sinzui: I can think of a more intuitive interface than what we've got right now: on the same page where we offer to deactivate an account, offer right next to it to merge another account into this one.
[21:38] <mwhudson> good morning launchpad!
[21:38] <mwhudson> gary_poster: particularly you :)
[21:38] <launchpad> morning, mwhudson!
[21:39] <sinzui> kfogel: There is a bug that the deactivate the user in non-intuitive. I agree they should be in the same place though.
[21:39] <gary_poster> mwhudson: lol :-) on call; when done will ping you
[21:39] <mwhudson> gary_poster: ok :)
[21:40] <kfogel> sinzui: "let not the perfect be the enemy of the cliché", or something like that
[21:40] <sinzui> kfogel: bug 165148
[21:40] <kfogel> sinzui: thx
[21:40] <mup> Bug #165148: "Deactivate my account" link is hard to find <registry-people> <ui> <Launchpad Registry:Triaged> <https://launchpad.net/bugs/165148>
[21:42] <rockstar> beuno, I has a question for you.
[21:43] <beuno> rockstar, I can take it
[21:46] <rockstar> beuno, so, on branch merge proposals, do we really need the subscribers portlet?
[21:47] <rockstar> (I tend to think the answer is no, because you're technically not subscribed to the bmp)
[21:47] <beuno> I agree
[21:48] <beuno> what I do think we need to convey
[21:48] <beuno> is who's being notified of the MP
[21:48] <beuno> is that not the same list?
[21:48] <rockstar> Maybe.
[21:50]  * maxb wonders why bin/test --list-tests doesn't give the tests in the same order that they are actually running
[21:55] <kfogel> sinzui: filed bug #422837
[21:55] <mup> Bug #422837: UI for merging accounts is unintuitive <ui> <Ubuntu:New> <https://launchpad.net/bugs/422837>
[21:56] <sinzui> kfogel: why in ubuntu?
[21:56] <kfogel> sinzui: huh?
[21:56] <kfogel> lost sinzui
[22:01] <gary_poster> mwhudson: yo. :-)
[22:02] <mwhudson> gary_poster: actually, i didn't have anything super urgent to say over the email i just sent you
[22:02] <gary_poster> heh, oh, didn't see, will look
[22:02] <mwhudson> gary_poster: we can supply our own html for the root resource
[22:04] <mwhudson> gary_poster: so we can stick a couple of buttons on there
[22:04] <gary_poster> mwhudson: cool.  yeah.  sounds good to me. <shrug> :-)
[22:05] <gary_poster> Agree that maybe the FAQ stuff doesn't belong in glue.
[22:05] <gary_poster> at least not in that format
[22:05] <gary_poster> I can add what I wrote really quickly to /Trunk if you are +1
[22:06] <gary_poster> IRT the bzr test stuff, if you think it is working, I think it is working. ;-)
[22:06] <gary_poster> I'm happy to look at it or not, as you think is helpful.
[22:06] <mwhudson> gary_poster: +1 for a FAQ on Trunk
[22:06] <gary_poster> mwhudson: k, on it
[22:08] <mwhudson> argh
[22:08] <gary_poster> listen! the sound of someone hacking on buildbot!
[22:08] <mwhudson> it looks like the bzr builder isn't the latest one that was running on devpad.buildbot.info :(
[22:08] <gary_poster> mwhudson: oh :-(
[22:08]  * mwhudson really should pay attention to the standup call he's on...
[22:09] <gary_poster> mwhudson: (when you get a chance) do you want me to fire up the image of the old ec2 master I made before I shut it down?
[22:09] <gary_poster> and send you a copy of the master.cfg?
[22:09] <mwhudson> gary_poster: would be good, yeah
[22:10] <gary_poster> ok
[22:27] <gary_poster> mwhudson: hey.  just sent you master.cfg.  Could you verify that it is what you need so I can safely shut down the instance?
[22:30] <gary_poster> maxb: we need to tell upstream about the zope.sendmail problem.  Did you get a chance to get more details?  /me looks for bug...
[22:32] <mwhudson> gary_poster: yeah, that's more what i expected thanks
[22:32] <gary_poster> cool, ok, shutting it down
[22:34] <gary_poster> maxb: got it, you put it in the bug report thank you.  I'll follow up with upstream.
[22:42] <mwhudson> gary_poster: btw, i filed http://buildbot.net/trac/ticket/613
[22:43] <gary_poster> Cool.  I strongly suspect that the maintainers will applaud a JFDI approach.
[22:43] <gary_poster> I need to run.  Have a good day