User1: hi I signed up for launchpad to get cd's from shipit but I'm not really sure what launchpad is... anyone wan't to give me a short description?
User2: jamesh: ping
User3: are there any launchpad developers in here from the phoenix area?
User2: I don't think so
User2: you want to meet up with one ?
User3: kind of
User2: ...
User3: i need a zope3 developer
User4: Your closes Launchpad Z3 developer would be in Montreal, followed by Sao Paolo
User4: User2 Can you please mirror alicia03@example.net/launchpad--production--1.34 across
User2: User4 they are not that few ;0
User4: Launchpad Z3 developer, not Z3 developer
User2: done
User2: User4 he just wants z3 ;0
User3: yeah, but i'd at least know i was getting a guy with experience if he was launchpad z3
User3: :)
User5: I somewhat doubt an LP developer would have time to take on a second job
User6: Merge to alicia03@example.net/dists--devel--0: [trivial]  production-1.34 config (patch-117: alicia03@example.net)
User3: true
User6: Merge to alicia03@example.net/launchpad--production--1.34: Cherry pick alicia03@example.net/launchpad--CherrypickNoKarmaForRosettaImports--0--patch-1 into production 1.34 (patch-1: alicia03@example.net)
User6: Merge to alicia03@example.net/launchpad--production--1.34: Merge production 1.34 up to patch-2480 (patch-2: alicia03@example.net, alicia03@example.net, alicia03@example.net ...)
User2: jamesh: ping
User6: Merge to alicia03@example.net/launchpad--production--1.34: Cherry pick patch-2486 into production 1.34 (patch-3: alicia03@example.net, alicia03@example.net)
User6: Merge to alicia03@example.net/launchpad--production--1.34: Cherry pick patch-2487 into production 1.34 (patch-4: alicia03@example.net, alicia03@example.net)
User7: hey all
User8: good morning
User8: spiv: ping?
User8: User4 morning
User8: jamesh: hi.  any progress on the warning spew from subprocesses?
User4: Morning
User8: User4 what's the news on request timeouts?
User4: No news (is good news)
User8: so, the timeout is currently waaaaay to high compared to where we want it to ideally be
User8: the rosetta cron scripts are fit to run, and should be running
User8: but kiko called me at the weekend to check if they're actually enabled in the crontab
User8: i have a mail waiting from jordi about that
User4: They are enabled (I responded to that email)
User8: you're doing some remedial work on the statistician, right?
User8: okay, great
User4: statistician changes are with pqm
User8: nice
User8: so, that will be back with the next roll-out
User4: Yes - I'll be cherry picking it as soon as I get a patch number
User6: Merge to alicia03@example.net/launchpad--devel--0: [r=spiv]  Make update-stats.py play nicer with the other kids (patch-2488: alicia03@example.net)
User4: There we go
User8: BjornT, jamesh or spiv: i've got a menus review that needs someone's help.  i want it to hit PQM soon, so that i don't have to deal with huge amounts of conflicts.
User8: User4 read your reply to jordi.  does the bug still need fixing?
User4: Yes. The gajim import won't run until it is fixed. It is currently spamming us every 10 minutes.
User4: Carlos or kiko won't have had a chance to look at it yet
User9: User8 i can do it, send me the diff
User8: thanks BjornT
User8: User4 i'll alicia03@example.net.  it looks trivial.
User4: User8 Do you happen to know what this unhelpful exception means? https://chinstrap.ubuntu.com/~dsilvers/paste/fileaiazws.html
User9: User4 i think i had a similar error before, the reason was that iface was security proxied.
User8: so, is 'isOrExtends' missing from the security on an interface?
User4: There is no security on the interface
User9: do interfaces even have security declarations?
User4: This is just me trying to register an adapter:
User4: <adapter
User4: for="canonical.launchpad.webapp.LaunchpadBrowserRequest"
User4: provides="canonical.launchpad.webapp.interfaces.INotificationResponse"
User4: factory="canonical.launchpad.webapp.adaptRequestToResponse"
User4: />
User8: sure there's a security declaration for interfaces
User8: User4 the factory
User8: what is it?
User4: hmm... working now. might have just failed to save an editor window or something
User4: nope.... but I've worked out the issue
User8: yeah, isOrExtends is allowed for interfaces
User4: LaunchpadBrowserRequest did not implement any interfaces.
User4: If I create a marker interface, and make LaunchpadBrowserRequest implement it, it works just fine.
User4: z3 bug
User8: User4 it looks like there's something claiming to be an interface implements declaration on a class, but it isn't really one
User8: User4 can you file a malone bug on me about this, so i can look into it?
User4: Possibly because LaunchpadBrowserRequest is a subclass of (BrowserRequest, NotificationRequest)
User4: I'll stick some XXX's in indicating how to trigger the bug in this branch, and file a bug.
User8: ta
User6: Merge to alicia03@example.net/launchpad--production--1.34: Cherry pick patch-2482 into production 1.34 (patch-5: alicia03@example.net, alicia03@example.net)
* SteveA prepares a fresh diff for bjorn
User8: User9 mailed you a diff
User9: cool
User6: Merge to alicia03@example.net/launchpad--production--1.34: Cherry pick patch-2488 into production 1.34 (patch-6: alicia03@example.net, alicia03@example.net)
User4: Bah. Our page tests don't support sessions :-(
* stub needs to manually extract and send the cookies
User8: yeah
User8: what do you want to test with sessions?
User4: User8 browser notifications, where the messages are stored server side in the session
User4: Got it working
User9: User8 review sent
User8: thanks
User8: reply sent
* Kinnison catches up with enough to say good morning
User8: hello daniel
User10: hi steve
User11: morning
User12: your favourite silver.supporter is BACK
User8: good morning
User8: although, today you're alicia03@example.net
User8: a
User12: User8 hmm.. no bling no longer. ah well, was fun while it lasted
User7: hey sabdfl !
* BjornT -> lunch
User7: Hey Kinnison
User12: hiya sivang
User12: User10 so, how was TheTestWeek?
User10: User12 Well, my laptop is running breezy as installed from http://dogfood.ubuntu.com/ubuntu/
User12: nice
User12: well done!
User10: User12 We have uncovered some issues with depfailure in the builder. cprov is working on 'em
User12: ok, cool
User10: User12 and I got gina down from a large number of failed imports to nearly zero
User12: that's to be expected
User12: well done again
User10: I know how to get that to almost exactly zero in fact
* Kinnison just has to get rid of the version checking in the DB and add a protective wrapper in the dominator
User7: User10 whee cool, so the amazing new infrastrucutre for pkg building through launchpad work :)
User10: yep
User10: https://dogfood.ubuntu.com/+builds/dogfood
User7: ouch, EFORBIDDEN
User10: oh yeah, you need an SSL cert for that
User10: sorry
User10: http://users.pepperfish.net/dsilvers/foody.png
User5: pimp
User10: pardon?
User7: User10 so every spect of building a source/derivation repo is controlled from thoise consoles? impressive
User10: Well, it will be :-)
* sivang is astonished
User10: User12 https://chinstrap.ubuntu.com/~dsilvers/paste/fileAA19tL.html
User10: User12 those are the current gina failures
* Kinnison has a plan for each of the three failure modes
User10: just gotta implement
* Kinnison writes a script as that's the third time in a week he forgot --no-cacherev when branching launchpad
User8: does that make branching less heavyweight?
User10: well it stops the base-0 being cached
User10: which saves a 17 meg push across my adsl
User10: and since baz is supposedly caching every 50 revs on rocketfuel I figure it's fairly safe
User10: also it makes the branch operation itself finish in about a twentieth the time
User6: Merge to alicia03@example.net/launchpad--devel--0: r=BjornT, more actions portlets converted to menus, introduction of LaunchpadView. (patch-2489: alicia03@example.net)
User8: User11 did you see the mail from stu about why the rosetta back-end scripts aren't running right now?
User8: there's a bug in them that stops them running, so probably a test missing there?
User11: no, I didn't
User11: it sounds like that
* carlos goes for it...
User11: SteveA, oh
User11: it's not that the scripts are not running
User11: it's just that some real data is breaking our parser
User11: SteveA, we have some of them. Kiko filed bugs about that, not sure if that concrete problem is filed. Anyway, fixing those bugs is my current tasks
User8: from the error stu showed, the code should be using .startswith() rather than [0]
User11: SteveA, that parser should be killed, anyway I will fix it that way. thanks
User11: When I say 'killing it' I don't say forget it, just that it sucks.
* Kinnison keeps getting check failures due to baz
User10: is this a known thing?
User8: User10 what kind of errors?
User10: User8 argv: 'archive-mirror', '/home/dsilvers/dev-canonical/launchpad/launchpad-gina-remove-version/,,temp-archive1', '/home/dsilvers/dev-canonical/launchpad/launchpad-gina-remove-version/,,temp-archive2', 'foo-bar--HEAD--0--patch-1'
User10: * error report
User10: could not connect to archive '/home/dsilvers/dev-canonical/launchpad/launchpad-gina-remove-version'
User10: that sort
User8: no, i have never seen such an error
User8: User13 ?
User10: Anyone mind if I stop dogfood to upgrade it?
User10: I'll take that as "no" and go ahead
User13: User10 bug in COTM breaking pybaz
User13: use baz 1.4.2
User10: Oh
User13: Yes it sucks.
User10: Yes, it does
User10: fix it
User10: damnit
User10: :-)
* ddaa thinks he's the one person to have found the most bugs in arch and baz
User13: I grew tired of isolating and filing bugs for baz regressions, but apparently lifeless won't fix them before making a x.0 unless I do.
User10: I guess we're concentrating hard on bzr
User13: I guess so. This sort of things staying unfxed (and baz 1.5.0 not seeming any closer to a release than it was several weeks ago) is probably an unpleasant side effect of the pie-in-the-face bzr sprint.
* SteveA --> lunch
User13: But that's little pain I'm willing to endure if that means we'll be using bzr for rocketfuel in one month.
User10: Aye
User10: apparently weave is pretty much done now
User13: The fundamentals are done, my uninformed guesstimate is there's ~ one week of work to get support propagated thorough the code base.
User10: right
* carlos -> lunch
User11: ddaa, thanks for helping with my branch, I will try your instructions after lunch and will try to do the things better.
User13: User11 it assumes you have not made further commits since you reported the problem
User11: ddaa, no commits done, don't worry
User13: hey spiv
User13: how would you feel about some cscvs reviews today? ;)
User10: Do we automatically run the doctests in canonical.launchpad.validators ?
User10: if so, how can I ask the test suite to run just those?
User9: User10 python test.py canonical.launchpad.validators
User10: User9 ta
User10: okay that tells me that the doctest isn't run
* Kinnison updates it anyway
User9: it should be run, i think. which doctest is it?
User10: the one for valid_debian_version in launchpad/validators/version.py
User9: it is being run for me
User10: with that commandline you said?
User9: yeah
User10: 'cos I just added a must-fail test I.E. I changed a True to 'Cheese' and it didn't fail
User10: in version.pyu
User10: s/u$//
* Kinnison lunches, brb
User9: sure you didn't forget to save the file? :) i also change a True to False, and it failed
User14: maybe cheese is true
User10: maybe it is
* Kinnison tries again
User10: nope, it's as though it's not running the docstring at all
* Kinnison prods gently at his mind
User10: clearly I'm too hungry to work
User10: TTOTD: When changing tests, run the test runner ON THE SAME COMPUTER
User10: sorry bjorn
* Kinnison lunches for real this time
User10: bbl
User15: yay for mondays
User14: User9 Am I right in thinking that product-bugs.pt isn't used any more?
User15: mpt, wasn't that replaced by bugs-for-context?
User14: it looks like it, yes
User14: same for distribution-bugs.pt
User14: and distrorelease-bugs.pt
User9: User14 yes you're right
User14: but distrosourcepackage-bugs.pt is still used
User14: cower before the power of baz rm!
User9: yeah, sourcepackage-bugs.pt is also used
User15: these are new pages
User14: and packages-bugs.pt
User9: User15 do you want to take a look at the branch lifeless reviewed for me?
User15: BjornT, hmmm how big is it?
User9: 750 lines
User15: sure
User9: User15 thanks. and if you feel like reviewing some more, a have a patch for fixing email wrapping problems up for review, only 400 lines (mostly doctests).
User15: sure
User15: I can do both, this morning
User9: cool, that'd be great
User14: User8 ping
User15: ddaa, do you know if it's safe to nuke anything under ~/.arch-cache/ ?
User13: User15 it's entirely safe
User13: though it might hurt your performance, it caches the ancestry information that it takes so long to retrieve when doing some merges.
User15: ddaa, will it be regenerated automatically?
User13: yup
User15: ours are like 800mb
User13: just go ahead and remove if you want. It will hurt nowhere as much as removing the revlib.
User15: okay, cool
User15: ddaa, and revlib directories with names starting with ,,?
User13: that's entirely safe and desirable to delete _unless_ there's a baz running on the system (in which case that might be a perfectly legitimate and useful temporary directory)
User13: Typically those are left around when operations like get, merge or switch are interrupted.
User15: yeah
User8: User14 hi
User9: User8 when you converted the action portlets to menus, you removed "Report a Bug" from distribution and distrorelease bug listings
User8: User9 I guess that means there's no test that someone can report a bug using a menu ;-)
User8: i've been putting the old portlets and new menus on the same page, to check the look/work the same
User8: but, i guess i made a mistake there
User9: yeah, it'd be nice with a test framework that allowed you to say "click the Report a Bug link" ;) (or maybe we should start checking that some page contains the url that is being page tested)
User8: i'll be alicia03@example.net shortly
User8: got a few launchpad infrastructure things to finish first
User8: and zope3.1 has that kind of thing available.
User9: yeah i know, haven't tested it yet, though, but it seems to be quite nice.
User14: User8 I just worked out how to get the context+application menus to appear (a) in the right place and (b) only once in non-three-column layouts
User8: User14 so, the way i was going to do this is by using a slot for other RHS boxes for 2-col layouts.
User8: what's your way?
User4: User8 alicia03@example.net/launchpad--zope31--0 , sqlos--zope31--0 and zope--test--3.1  was where I got to with alicia03@example.net
User8: cool
User4: (that zope branch is rc2 I believe)
User14: User8 <metal:nomenu fill-slot="column_two"></metal:nomenu>
User14: and <tal:menu replace="structure CONTEXTS/@@+menubox" />
User8: ok
User14: so I can now register DistributionBugsMenu...
User8: you can register it anyway
User14: (which I'd created, but not registered because it was in the wrong place)
User8: we mustn't let UI polish get in the way of these things
User8: do you have any unmirrored changes on your menus branch?
User14: ... and hey presto, BjornT, the distribution bugs page has "Report a Bug" again :-)
User16: User18 hi. can you please reject the "upstream ubuntu" tasks on bug #2382 and #2384?
User16: "Ubuntu is a desktop Linux that you can give your girlfriend to install." -- ??
User16: Is every distribution meant to have a corresponding upstream product then?
User13: ripping off of viril attributes
User14: My girlfriend keeps whining to me about problems with Ubuntu
User14: Yesterday she was complaining that there's no simple way of upgrading from 5.04 to 5.10 without using a CD
User17: User14 mine did to, so I fixed them for her :-).
User13: User14 your girlfriend is too geeky, no girfriend in his own right would try to upgrade her OS :)
User13: * in her own right
User14: User13 Yeah, she's going to stick to Gentoo for the time being
User17: baah, just teach her sed :-P. I did ;-).
User16: My gf got pretty annoyed the other night at trying to do her homework on my Powerbook keyboard AND OOo AND in English. This had bad consequences for me.
User16: (If you know what I mean.)
User13: "Not tonight honey, I have tendinitis"?
User16: heh
User7: User13 lol
User16: User4 The BNM stuff looks cool. Any ETA on when we might be able to start using it?
User4: User16 As soon as it gets through review. mpt might want to redo my css that that is trivial and doesn't block people using the API
User16: cool. looking forward to it.
User8: User14 other than the main template change, is there any other menus work from you i need to merge?
User15: brb, rebooting
User14: User8 I've just made a bunch of tweaks to to distribution, product, and source package menus
User14: and fixed some strangeness in the Rosetta legend
User14: https://staging.ubuntu.com/distros/ubuntu/hoary/+sources/pmount/+translations
User14: "Summary of what the branch does Newly translated in Rosetta"
User14: User8 Why did you use "THIS FILE IS DEAD." rather than baz rm?
User8: two reasons
User8: 1. to better catch conflicts
User8: 2. so that all the files can be removed at once in a separate sweep
User8: User14 i don't want our work to conflict.  i shall do the rest of the actions menus now.
User14: User8 My next problem is, how to get menus appearing for (for example) people-index and not person-index
User8: User14 write a description in the wiki page so i can see what you see, and understand why
User14: is that just a matter of saying they're for IFooSet rather than IFoo?
User8: probably yes
User8: but stop
User8: i have already done these, on my branch
User14: In the past three hours?
User8: YES
User14: ok :-)
User8: i have been saying this
User8: we need to co-ordinate
User8: i'll do the rest of the actions menus, right now
User14: ok, shall I work backwards from z then?
User14: ok
User8: no, i'll do the rest
User8: i want you to check i haven't made any more mistakes
User8: PQM merged a bunch of them this morning
User8: (that is, menus, not mistakes, hopefully)
User18: User16 hmm, can I really do that?
User8: and let me know about any odd problems you find that need solving.
User8: like, things aren't displaying properly, or whatever
User8: User14 is there stuff i should merge into my branch?
User14: User8 My distribution menus changes are committing now
User14: +product+sourcepackage
User8: ok
User14: and deletion of no-longer-used templates (that do not include actions portlets)
User8: ok
User8: that's good
User8: hmm, i should be able to make the test suite detect unused templates
User10: User8 it's easy if you mandate that the FS the tests are run on is not mounted -o noatime
User10: or does zope load them all anyway?
User8: well
User16: User18 yes, you should be able to (did you try?)
User8: there are templates that are on the FS but aren't referenced in page templates or zcml
User8: that's a category of template that would be found like that
User8: then, there's pages that aren't actually used as part of the test suite
User8: that's another set of pages
User15: carlos, ping?
User10: right
User18: User16 yes, but I don't find an obvious link
User16: User18 yeah, we know :/
User16: User18 you have to click on the (completely non-obvious) "upstream ubuntu" link in the task listing on the bug page
User8: User10 and the pages that aren't tested are actually worse than the "decoys"
User8: because those are a liability
User16: User18 eventually, i'll hopefully be able to put back my "Edit Assignee/Status Details" link into the actions portlet
User8: User14 have you looked at the maintenance message UI ?
User18: User16 ok, so inside here, what do I do?
User16: User18 are you logged in?
User14: User8 mirror finished
User8: thanks
User18: User16 if you can also give me more info about why the change is necessary, etc, better for the next time
User18: User16 yup
User16: User18 ok, does it look like an edit form?
User14: User8 I'm not sure what you mean by "maintenance message UI", so, probably not
User14: User8 do you mean offline.html?
User18: yes
User16: User18 ok, so, just change the "Status" value in the dropdown to "Rejected", and save changes
User18: and I see a few links that take me to the same page I'm seeing now: "Edit Task Status" and "also reported in:"
User8: pagetests/standalone/xx-maintenance-message.txt
User18: oh
User8: User14 see that pagetest
User18: I thought I had to get rid of the "upstream ubuntu property" or something.
User6: Merge to alicia03@example.net/launchpad--devel--0: [trivial]  Fix for bug 2527: Trac ticket URL wrong. May contain traces of nuts. Contains gluten. No lint. (patch-2490: alicia03@example.net)
User18: User16 any comment for rejection?
User16: User18 comment unnecessary, probably
User16: User18 the reason for rejecting it is that people should never be filing bugs against the ubuntu upstream product, only against the ubuntu distribution
User18: nod
User18: done for both
User16: thanks
User14: Why is there an Ubuntu upstream product?
User16: dunno, but I sincerely hope it's unnecessary
User16: nobody answered my question from earlier though: is it necessary for every distro to have a product registered for it?
User16: more specifically, would anybody object to the Ubuntu upstream product being removed? silence, consent, etc.
User16: User15 would you object to us removing the Ubuntu upstream product?
User12: User14 that's an aberration
User12: User16 i had thought to rename it to something else, just never got around to it
User12: there should not be an ubuntu upstream project
User12: product, that is
User16: ok
User7: who entered the text describing the UBZ on the sprint tracker?
User14: oy
User15: me? I'm not opposed to anything that involves "removing"
User14: User15 First we need to move the bugs, no?
User4: I've just set active=false on the ubuntu product
User19: User8 ping
User8: User19 hello
User8: User19 i've just added canonical urls for various CoC things.
User8: (with tests)
User14: gneuman/matsubara: I just tried to request bug 1 to be fixed in the Ubuntu distribution (no source package specified), and got a system error
User19: User8  do you have time for a quick review in buildd stuff (100 lines, most comments) ?
User16: User4 I didn't that too, but it doesn't help much.
User8: User19 i'm reviewing some stuff for Kinnison right now
User19: User8  thank you I'have a look later today, if it's not too late for you
User8: i can review your stuff too, i guess
User19: User8 you rock ! https://chinstrap.ubuntu.com/~dsilvers/paste/fileMj2wOa.html
User16: s/didn't that/did that/
User19: User8 I'm going to lunch now, back in 45 min
User8: k
User14: bah, I can't move any of the Ubuntu product bugs
User16: User14 indeed. reassignment across upstream/distribution is just begging for screwups. this is an unusual situation, i think.
User15: mpt, bradb, maybe stub can do it though magic? :-)
User4: maybe tomorrow
User14: I don't mean reassignment, I mean rejecting the old request and making a new one
User16: User14 ah.
User14: bradb, you still can't reassign even from one product to another, can you?
User16: User15 i'm wondering, should we make upstream tasks wiki-mode as well?
User16: User14 no, that's a bug that has some workflow issues along with it.
User15: bradb, I don't see why not -- have we gotten any bug defacement?
User8: User10 review in the mail
User16: User15 not that I've seen or heard reported
User15: right
User14: User16 I already commented in the bug to say that no, it didn't have some workflow issues along with it
User14: unless there's something I'm missing
User14: it's just an extra field in the form
User15: I tend to agree with mpt
User13: User15 feel up to a quick review (or to point me to somebody who has the time for that)?
User16: under the new URL scheme, the workflow issues may no longer really be present
User16: User14 what bug are you talking about? https://launchpad.net/malone/bugs/2030 is the only one i find when searching Malone bugs for "reassign"
* SteveA workraves to let baz do its stuff
User16: User14 I don't think a simple field in the form will work for various reasons: 1. it doesn't really clearly communicate "hey, edit this field to reassign the product to a different place". an LP developer might think that would be obvious, but it seems to be less obvious to users. 2. at least previously, we had no notion of a "null bug task", which would mean that changing that product field jumps you into an entirely different conte
User14: entirely different conte... ?
User15: bradb, to be honest, I think we should worry about that if it becomes a problem
User16: User15 it did. when we used to allow reassignment, people asked how to reassign the bug to a different upstream.
User16: User14 yeah, if you reported a bug on /products/foo, the URL was /products/foo/+bugs/1/+edit. if you change the product field to "bar", you have to redirect to /products/bar/+bugs/1/+edit, because /products/foo/+bugs/1/+edit would no longer work.
User14: User16 Even if it's not perfectly obvious, 3 clicks + 2 page loads is vastly better than 5 clicks + 4 page loads.
User16: at least, that was the context in which #2030 was reported. like i say, under the new scheme, we have the notion of a null bugtask, and can better deal with that problem
User14: I don't see what the problem with redirection is
User14: but then, I don't know what a null bugtask is either :-)
User16: we can always try it again and see what happens again. i'm not too bothered either way, tbh.
User16: so, wiki-mode and allow the product field to be changed?
User14: User16 oh, by "null bugtask" do you mean you go through the Back menu to get to the task that no longer exists at that context, and get the message "Bug X is not recorded as needing a fix in Y"?
User16: User14 yeah. null bugtask, e.g. being able to present a page for a task, even if that task doesn't exist yet.
User16: s/e.g./i.e./
User13: User8 when you are back, are you willing to review a quasi-trivial patch? https://chinstrap.ubuntu.com/~dsilvers/paste/filemaD45h.html
User13: (removal of inspect dependency from Launchpad test suite)
User14: User16 You are returning a 404 header on such a page, right?
User8: for the case outlined here, i think redirection is more appropriate
User8: User13 i'll look when i'm next waiting for baz to process.  should be within the next 30 mins.  is that okay?
User14: oh, sure, when you move a task, you should end up in the next context
User13: User8 that's okay
* ddaa goes for a snack
User14: but if you (for example) use the Back button, you get the null task with the 404 header
User16: User14 404 at what URL?
User14: User16 E.g. /distros/redhat/+bugs/1
User14: because it's an Ubuntu bug, not a Red Hat one
User16: it's +bug, but why would it be a 404?
User14: because that task doesn't exist in that context
User16: it's a valid page to display. that's the page with the "This bug has not yet been reported in Redhat, etc."
User8: i think such a page should set the status to 404
User14: Sure it's a valid page to display, but it's still representing something that doesn't exist yet
User8: you don't want that page in your browser "locations" history
User8: we must work with HTTP
User8: not against it
User8: it needn't be a NotFound error to set the response status to 404
User14: There are a whole bunch of cases where we should be doing special-case 404s, null bugtasks are just one of them
* bradb reads that part of the HTTP spec before saying much more
User8: not really necessary
User14: e.g. https://launchpad.net/products/fqwhgads should show me a list of products with names similar to fqwhgads, and also give me the chance to register the fqwhgads product
User8: although, no harm in reading it
User8: User14 fqwhgads?  isn't that the bad guy from Shrek ?
User14: User16 https://launchpad.net/malone/bugs/1073
User14: User8 No, fqwhgads is a mythical character from the Strong Bad E-mails
User14: the Shrek guy was F*ck-wad
User14: though I think it was spelled differently
User14: because he was modelled after some Disney executive who the Shrek creator detested
User14: User16 https://launchpad.net/malone/bugs/1073
User14: User8 Just mirrored fixes to the distrorelease menus: you can now report a bug on a distrorelease, and also see its spec roadmap
User14: (among other things)
User8: okay, i'll merge it into my work next time i commit
User16: User14 yeah, i see that :)
User8: User16 want to try this?  http://gintas.pov.lt/darcs/z3reload/README.txt
User14: User16 Sorry for pasting twice, I got an itchy trigger finger
User16: User8 yeah, i saw that package before. wondered if it was worth the effort though.
User16: it seems like it requires a fairly careful understanding of the nature of Python reloads, and of the structure of one's view classes. so much so, that my brain is happier to say "mm, just restart zope already."
User8: User16 i think one member of the lp team should do a bit of reconnaisance and see if it helps for launchpad
User8: we could set it up for just view classes, for example
User8: maybe spiv can take a look...
User16: i can take a look and see if it helps, day-to-day
User8: User16 actually, reading it, i think i'd need to do some work on it to make it work with launchpad
User8: it makes various assumptions that aren't really true
User16: ah, ok
User8: like, it uses the DatabaseOpenedEvent to tell that zcml has been loaded
User16: right
User8: which isn't how it works in launchpad, and just a coincidence about how it works in zope3 most of the time
User8: still, i reckon i can use parts of it
User20: kiko, why do you marked 2553 as a dupe of 2369?
User15: salgado, because it's a dupe, I saw the traceback
User20: kiko, but that's not about a traceback. the user is complaining he can't see a link to where he can edit the team's wikiname. and in fact, there isn't one for teams
User15: I think I mixed something up
User21: heh
User15: sorry
User21: np at all
User21: i don't get this wikiname business
User15: it was 2551, of course
User21: what determines whether a user has one?
User21: why does my user not have one for example
User15: every user gets one for the ubuntu wiki
User15: except for users where salgado's code broke :-)
User21: ok so why the system error?
User21: ah
User21: and which users are they?
User15: some 20 users IIRC, right salgado
User21: grr
User20: I guess something like that
User21: why does LP use this "wikiname" concept, instead of just a wiki page?
User15: mdke, because of how moin integrates with launchpad, we need it
User21: kiko, how does it work?
User15: every launchpad account allows for log in to different services, mdke -- shipit, the ubuntu wiki, etc.
User21: you mean for authentication?
User15: right
User21: yeah ok
User15: the issue is that because LP accounts are email addresses, we need a way to give a user a wikiname so moin works
User15: that's roughly the issue
User21: but wikinames were introduced into LP way after it was being used to authenticate the moin wiki, right?
User15: I'm not privvy to the protons of it, but that's the idea.
User15: mdke, it used to be a bit different, but they have always existed
User21: ah okay i see
User6: Merge to alicia03@example.net/launchpad--devel--0: Allow non-policy-compliant version numbers into the db and make sure our validators and dominator cope. r=stevea (patch-2491: alicia03@example.net)
User21: moin uses the wikiname to login of course
User15: j^, you can just file on the distribution and set the package name there
User21: i thought you'd hacked all the way around that ;)
User15: mdke, our hacked moin is a bit different
User15: yeah, we did
User15: it still needs the wikiname to function properly IIRC
User21: kiko, ok, thanks for taking the time to explain that!
User5: j^: https://launchpad.net/products/bazaar/+filebug
User15: mdke, think nothing of it, enjoy
User15: j^, User5 that's upstream. he's talking about a source package
User5: ah
User15: j^, I think I understand your use case now. bradb, User9 there's no way to create a link to report a bug on a specific SP, is there? craaack
User16: SteveA, User14 does that mean that all the names hanging off a null bugtask (+addwatch, +addurl, +addattachment, etc.) should also return 404?
User15: null bugtask?
User15: aieee
User15: does anyone know how to slack in gtimelog?
User8: User16 is there a use-case for the null bugtask other than when you change the product etc. ?
User8: User15 ** i slacked
User16: User15 to report a bug on a sourcepackage, you just use the "Report a Bug" link from the sourcepackage's bug listing. the URL changes haven't been rolled out yet though.
User16: User8 yeah, there are tons of use cases for it. any time you want to view a bug report that hasn't yet been reported in your context.
User8: User16 we must seek an opinion from lifeless
User16: User8 so, when might you want to do this? 1. when you're searching to see if your bug has already been reported. 2. when you click on a bug that is a dup of this bug, and for whatever reason, it hasn't yet been reported in your context, etc.
User15: bradb, j^: if you can wait till tomorrow, you will have a stable one -- can you?
User15: j^, /distros/ubuntu/hoary/+sources/firefox/+bugs
User16: j^: gotta wait until my monster URL changes patch gets rolled out
User16: yeah, that can be used too, but it's less than ideal
User16: yup. when the URL changes land, you can chop out the "hoary" part of that URL
User16: yeah
User8: User14 can you alicia03@example.net ?  it has special styling
User8: can i rename it then?
User8: as it isn't really an "actions portlet" in launchpad
User8: can you suggest a new name?
User16: hey, who snuck that "Edit Status" link back into the actions portlet, and why didn't you sneak in "Edit Assignee/Status Details" instead! :)
User16: User8 are you interested in drive-by'ing a small patch to return 404s for the view/edit status page of null bugtasks (instead of 500's, like it will currently)?
User16: i have the diff ready
User16: it's like 40 lines
User16: or BjornT?
User9: User16 sure, send it to me
User16: User9 sent
User13: User9 I just used SteveA, I got another small patch (~10 lines) to get through quickly. Feeling up to it?
User9: User13 sure
User13: will tell you nopaste url once I have it :)
User13: User9 https://chinstrap.ubuntu.com/~dsilvers/paste/fileyvlyjz.html
User9: cool, i'll look at it soon
User13: User9 please do not mention the pep8 violations in surrounding code, I have a really HUGE patch in the pipe for importd, so I want to keep incidental disruption to a minimum.
User9: ok
User6: Merge to alicia03@example.net/launchpad--devel--0: [trivial]  Adding bug titles to dupe links (patch-2492: alicia03@example.net)
User9: User16 reply sent
User8: User11 sent you a script
User11: SteveA, thank you
User11: I will resend it to pitti
User8: i cced him
User11: ok, thanks!
User8: try it, and let me know how it can be improved
User8: or just hack it yourself
User8: i didn't include the option to filter out additions
User8: nor ignoring metadata
User9: User13 r=bjornt
User22: is it possible to set the hackergotchi on your homepage?
User13: User22 naaaaaaah, this link does nothing yet and should have been removed already :)
User8: User22 it's being fixed
User8: User22 you'll be able to soon
User11: SteveA, ok
User22: SteveA, cool :)
User22: ofcourse i want to utilize every cool feature of launchpad ;)
User8: User11 i should have left some comments in the code or something
User11: SteveA, it does not look like a too complex script, don't worry
User8: ok
User8: i was surprised how quick it was
User8: when grep took ages on the same file
User8: User11 some of the problem seems to be related to encodings
User8: msgid "Edit"
User8: -msgstr "Dzelt"
User8: +msgstr "Dzelt"
User8:
User8: like that
User11: that's a fix
User11: the main problem is with removals more than changes
User8: well, it is easy to exclude these from output of the script
User8: 53322 lines
User8: if you take out "changes" and "additions" leaving just "removals"
User11: ok
User8: fewer still if you remove metadata too
User19: User8 do you have time for a quick meeting about test-suit supporting binary content, with me and matsubara ?
User18: User11 any progress on the gajim thing?
User15: jordi, I checked in a fix for it, it can be cherry-picked if carlos/stub wants
User18: nod
User18: my vote for that
User18: :)
User11: jordi, anyway, If you review the file you would fix anything that is unusual
User11: jordi, that's the faster way to fix it
User11: jordi, kiko thinks it's near the obsolete entries
User15: jordi, look for lines containing "#~" and nothing else
User11: jordi, if you could send me that file that would be helpful to improve our tests
User18: I'm searching for it.
User11: kiko, did you added a test?
User18: #~ msgid "_About"
User18: #~
User18: #~ msgstr "_About"
User18: that's it
User18: :q
User18: User11 want a full file, or is that enough?
User15: <jordi> #~
User15: that's foobs
User15: I fixed it in our codebase, anyway
User15: but it's foobs
User18: yeah.
User18: apparently gettext doesn't care at all though
User11: jordi, welcome to real data world...
User18: heh
User16: User14 was it you that readded the "Edit Status" link or kiko? :)
User15: not me!
User15: bradb, https://launchpad.net/malone/bugs/1443 is yours and fixed.
User14: User16 Yes, I'd be tempted to say that +addwatch, +addurl and co. for a null bugtask should be returning NotFound even -- adding stuff to a fix request that doesn't exist makes no sense
User16: User15 In-Reply-To ain't me. I only did Reply-To. BjornT perhaps this is yours to close?
User15: ah
User15: I missed the In-Reply
User6: Merge to alicia03@example.net/launchpad--devel--0: [r=carlos]  Fixing problem with gajim pofile import by working around lines that contain only #~, minor reformatting (patch-2493: alicia03@example.net)
User16: User14 hm, that doesn't feel right
User9: bradb, User15 thanks, closed.
User16: User14 wouldn't it be more surprising if all those pages 404'd than if they Just Worked? afterall, they're all bug specific, not depedant on context.
User14: oh, true
User16: User14 from the user perspective, even though this might be covering edge cases more than anything, it seems to me that having all the bug pages continue to work as normal would be more practical than having them suddenly 404.
User14: hmmmm
User14: possibly they should 404 *and* Just Work
User16: User14 that was a question SteveA wanted to pose to lifeless
User16: (i.e. specifically about what status code should be returned)
User14: User16 I don't remember altering "Edit Status" at all, but menus stuff has been going from SteveA -> rocketfuel and from me -> SteveA -> rocketfuel, so it might have been a bad merge somewhere
User16: User14 is that link meant to remain? given that sabdfl strongly disliked the "Edit Assignee/Status Details", i have to wonder. :) (even though i agree that it's an insult to the user not to have an "Edit Assignee/Status Details" link, but...)
User16: it matters to the extent that i'm thinking about what the link should do/look like when viewing a null bugtask.
User14: User16 If Google finds a mailing list message (or a bug report) that points to +addwatch or whatever for a context to which the URL doesn't belong, something at that URL should say "don't index me"
User14: to which the bug doesn't belong, I mean
User23: Hey, I notice that LP has https://launchpad.net/tickets now.  Should I be using that for Canonical Employees now?
User23: err.
User14: User16 Personally, I think all the "Edit *" links currently in Launchpad are crack, but we're some way off from fixing that
User23: Canonical customers.
User16: User14 yeah, i agree.
User16: it'd be nicer if they were in a place that people expect them to be, like near the thing they want to edit
User14: User23 You do tech support for Canonical?
User23: User14 Half-time, theoretically. =)
User16: User14 i'm curious though, should an "Edit Status" link be disabled for a null bugtask?
User23: Right now I've got all the support@ emails going into an RT system.
User23: User14 If you're interested in purchasing a support contract...
User16: User14 and, if so, how do you disable it nicely?
User14: User23 You might find that it's somewhat (or much) less featureful than RT, but I guess it's probably intended that you be using it eventually
User14: try it out and see :-)
User11: kiko, I have a diff for you
User11: kiko, waiting for bazaar to give you a branch
User23: User14 Well, the basic things I'd need for it to be usable right now are that support requests from these users should be 1) Private. 2) Assigned to me automatically.
User23: Aside from that, it's on par with how I use RT at the moment.
User15: ddaa, ping?
User15: carlos, rock
User15: this is a weird one
User14: User23 report those as bugs :-)
User23: User14 a'ight. =)
User23: User14 Against what product? =)
User14: launchpad
User14: There is malone, there is rosetta, and then there is ... launchpad
User15: there's also launchpad-cal I just discovered
User23: 'kay, I wasn't sure if there would be one for 'tickets'
* jbailey tries to figure out where to file this anyway. =)
User16: I think I'll remove Edit Status for now
User11: kiko-afk, added to the pending review page
User11: kiko-afk, I will leave now to have dinner
User11: kiko-afk, will answer your questions when I'm back. The karma related changes is already reviewed by Steve and cherrypicked into production (lacks a small change that I will do before the final merge)
User11: see you later
* carlos -> dinner
User6: Merge to alicia03@example.net/launchpad--devel--0: [trivial]  Add karma column name to people listing, fixing issue stub pointed out. Redo the way the batching header is displayed, strangle me if wrong (patch-2494: alicia03@example.net)
User14: ok, traceback time
User14: I just tried to open https://launchpad.net/malone/bugs/2106 and got a system error
User14: then I reloaded and it opened fine
User16: User9 I replied to your reply. In summary: I removed the "Edit Status" link entirely (because the sab hates it) and added INullBugTask. Can I merge the patch?
User14: User16 so how do you edit a fix request now?
User16: User14 it's very tricky.
User16: User14 you have to know that clicking on "ubuntu mozilla-firefox" takes you to the edit assignee/status details screen
User16: in reality, a lot of people don't (nor should be expected to) know that
User14: Oh, I haven't seen this new URL scheme yet
User14: before, clicking on "ubuntu mozilla-firefox" would take you to a non-editable page
User14: now it takes you to an editable page?
User16: it takes you to edit if you have the perms to edit, otherwise the view page
* mpt waits for refuel
User16: but i'm going to make upstream tasks wiki-mode today
User14: oh, good
User14: like Bugzilla pre-2000?
User16: heh
* bradb pings BjornT
User23: User14 Okay, I have to ask.  Where do I find 'launchpad' for filing a bug?  It seems to be neither a product nor a distribution?
User14: User23 It's a product
User14: https://launchpad.net/products/launchpad
User14: How did you not find it?
User23: User14 I don't see it under https://launchpad.net/malone/products
User16: i was going to add a "Place in Which You've Recently Reported a Bug" section to the front page
User23: When I go to Malone and click on "Locate Product and View Bugs"
User16: Places, that is
User16: the malone front page is just too much
User14: User23 Not meaning to be rude, but if you couldn't find it that's probably a bug
User20: SteveA, ping?
* mpt worded the question poorly
User23: User14 Oh, I don't take that as rude.
User6: Merge to alicia03@example.net/launchpad--devel--0: [r=stevea]  remove uses of pybaz OrderedTestLoader (patch-2495: alicia03@example.net)
User14: launchpad is listed under https://launchpad.net/products/+all
User23: User14 If could even be a bug on me.  And you're welcome to file it as such. =)
User16: User23 no, it's our fault
User9: User16 yeah, you can merge.
User16: User9 thanks
User10: Is there a time_in_the_past formatter?
User23: The link you gave me worked, should I file a bug as well saying that Launchpad doesn't show up in that product list?
User10: I.E. I have a field which is a datetime and I want it rendered as "forty minutes ago" or the like
User16: User10 use fmt:approximateduration
User16: User10 for an example of how i used it with IBugTask, check out BugTask.age
User10: page template?
User16: i've also suggested a fmt:age formatter, but nobody's wanted it enough yet to implement it
User23: Oh, hmm..
User23: It says "Most Recently Registered"
User23: So it does look like the bug should be assigned to me: "RTFWebPage, Jeff"
User16: User10 bugtask-macros-listview.pt:23:        tal:content="string:(${task/age/fmt:approximateduration} old)"
User10: righty, coolio
User10: thanks
User16: np
User16: User10 btw, you seem like the right guy to ask about sourcepackagey things. do you know if we have an FTI to search all sp's by name? e.g. i want to search for "firefox" and get "ubuntu mozilla-firefox", "debian mozilla-firefox", etc.
User23: User14 Do you want my tickets wishlists to be filed individually, or in one big  page?
User10: User16 We don't currently have FTIs on sourcepackagerelease or sourcepackagename
User10: If you want 'em, feel free to add 'em
User10: you just add entries to fti.py
User16: User10 any idea how far off we are from being able to provide some search terms, and get a list of distro SPs back that make sense?
User10: you know how?
User10: We have binary package FTI, I know that much
User14: User23 One bug per bug report please
User16: hm, FTI'ing ISPR would get us about 40% of the way there
User10: Feel free to do it
User10: Nothing I use (currently) would be affected if you did
User10: Other than slowing inserts of SPRs slightly (imperceptibly)
User16: hm, not really what i'm looking for though :/ (40% == not enough to Actually Work, i don't think, because we would have to post-process the result list to transform it into a list of distro sp's, as best i can tell.)
User10: How do you mean?
User10: you might want to check how soyuz's sourcepackage search works
User16: last time i checked, it didn't
User16: it never returned any results, even for things that i thought existed, but i'm trying it again now
User16: User10 basically, in an ideal world, when the user visits the malone front page, it would be nice to give them a box in which they can type some keywords to find the thing on which they want to report a bug. each row in the results returned would be either 1. an upstream or 2. a distro sourcepackage
User10: what is a "distro sourcepackage"
User16: User10 an object that has at least two pieces of information: a distribution (e.g. an IDistribution) and a sourcepackagename (e.g. an ISourcePackageName)
User10: Right
User10: You've got one interesting option
User10: Add FTI on sourcepackagename
User10: create a view which joins distribution to sourcepackagename through distrorelease, sourcepackagepublishing and sourcepackagerelease
User10: include the FTI on the view
User10: use that view for getting what you want
User6: Merge to alicia03@example.net/launchpad--devel--0: [trivial]  builder page missed bits (patch-2496: alicia03@example.net)
User16: hm, that might work
User10: Soyuz is the heaviest user of views
User10: and it seriously improves performance
User16: User14 What do you think about that? e.g. a Malone front page that has at least two ways of searching: 1. for bugs (including jumping directly to a bug report by id) and 2. searching for a thing on which to view or report bugs? (e.g. a text search box where you just type "firefox", click "Search", and it returns results like "Mozilla-Firefox (upstream)", "debian mozilla-firefox", "ubuntu mozilla-firefox", etc. then you click on one a
User16: the front page could also list things on which you've recently reported bugs (say, in the last month), which would be a list of upstreams and/or distro sps
User10: is there an easy way to run a specific pagetest?
User15: hey ddaa?
User10: lib/canonical/launchpad/pagetests/standalone/xx-builder-index.txt
User10: in particular
User15: Kinnison, yes. python test.py -f . pagetext
User15: so
User15: python test.py -f . xx-builder-index
User10: rocktastic
User10: thanks dude
User15: enjoy
* Kinnison is trying his hand (slowly) at bits of UI
* Kinnison is learning ZPT/TAL/TALES/METAL etc
User14: User16 You seem to be describing MaloneFrontPages
User14: From /malone, the search form should both return products/packages/etc containing your terms, and bug reports containing your terms
User16: User14 not really describing MFP, at least not by looking at the prototype screen, which says "Search all bug reports"
* mpt realizes he's been waiting an hour for baz merge
* Kinnison ponders some food before continuing with this UI tweak
User16: User14 also, i don't see anything in the prototype screens for MFP that try to help the user tumble into the right place with the "Places in Which You've Recently Reported a Bug" type thing
User16: tumble, stumble, whatever
User16: bumble, etc
User10: User15 btw, have you been watching https://dogfood.ubuntu.com/+builds/dogfood-builder-1 ?
User14: grumble
User6: Merge to alicia03@example.net/launchpad--devel--0: [r=BjornT]  make +{view,edit}status pages return 404 for null bugtasks. (patch-2497: alicia03@example.net)
User10: Anyone available for a v. quick review?
User10: User15 ?
* Kinnison is just merging the change onto dogfood for added testing
User15: not me, sorry, need to run out for a bit
User10: okay
User10: thanks anyway
User13: User15 I'm back, but I'm going off for the night soon.
User15: ddaa, was going to ask you if you know what happened to the ProductSeries.needsSyncReview method?
User15: i.e.
User15: see bug 750
User13: hu...
User13: kiko-afk: I do not know what +syncreview is, I can guess it would have had something to do with reviewing nicole data, and would therefore be obsolete, but that's only a guess.
User13: since AIUI nicole was deemed unsufficiently reliable
User13: kiko-afk: I think celso (he worked on nicole I think) would know
User10: mmmm
User16: 16:55 < tseng> User16 clicking "Ubuntu Tomboy" to edit the status of the big is still silly
User17: s/big/big\ bug/
User17: :-)
User14: User16 Wake me up when I'm allowed to touch the bug page :-)
User16: heh
* Kinnison prods review team
User10: anyone awake
User10: ?
* Kinnison has another not-quite trivial
User16: User9 around? i have another simple patch that i'm hoping to get reviewed. wiki-mode upstream tasks.
User16: or salgado?
User10: BjornT, User20 Any chance of an eye-over a not-quite-trivial UI fix?
User10: It's really simple
User20: Kinnison, sure. it's more than two weeks since my last code review. give it to me!
User10: User20 https://chinstrap.ubuntu.com/~dsilvers/paste/fileLKANCa.html
User20: Kinnison, out of curiosity, why is there a lot of "zsh: exit 1     baz file-diff lib/canonical/launchpad/database/builder.py" inside the diff?
User10: because if I gave you the diff, it'd contain the base-0 changelog
User10: which sux
User10: so I did a bunch of file-diff commands
User10: and they exit non-zero when there are changes
User10: so zsh tells me they exited non-zero
* Kinnison goes to grab his pizza, brb
User20: I see
User16: User20 Any chance of you taking a quick look at my small patch after Kinnison's?
User20: bradb, how many lines?
User16: User20 6 files changed, 22 insertions(+), 462 deletions(-)
User10: heyheyhey sabdude
User10: woah, go go gadget deletion
User16: User20 it's simple: making upstream tasks "wiki-mode", so that any logged-in user can edit them. this means removing a bunch of code that was handling a more complex permission scheme.
User16: ("them", i.e. the public ones, of course)
User20: bradb, okay. send me the diff
* salgado goes grab an apple to eat while reading bradb's diff. there shouldn't be a lot to comment on code that's being removed, I hope
User16: User20 sent!
User16: User20 the biggest blob of removed code was a removed file, which is a test that no longer makes sense, because it was testing "team awareness" of editing an upstream bugtask. this is no longer applicable given that, if you're logged in, you can edit an upstream task.
User16: User10 home-made pizza?
User10: User16 well, oven-bake
User10: Kinni|Lazy today
User16: ah
* Kinnison cooked himself a curry for lunch though
User10: with loadsa shrooms
User24: hi
User16: mmm, curry. england taught me curry.
User24: what are number of plural forms and pluralform expression?
User12: night guys
User24: night sabdfl
User20: bradb, is there a spec for this 'making upstream tasks "wiki-mode"' somewhere?
User16: User20 nope
User16: there's a BugTaskManagement spec that i could update though
User12: User16 could you put bug/bugtask permissions on the agenda for ubz please?
User20: I guess this was discussed before?
User16: User12 sure
User12: kiko-afk: any progress on registering LP specs in LP?
User16: User20 yes. making it wiki-mode now for two reasons: 1. users keep getting annoyed that they can't edit tasks when they need to, 2. we haven't seen or heard of any vandalism distro-side (where it's already wiki-mode).
User12: User14 nice bold-on-facet tabs
User6: Merge to alicia03@example.net/launchpad--devel--0: [r=bjornt]  perform an update for svn trees before syncing (patch-2498: alicia03@example.net, alicia03@example.net)
User12: User16 good job, i see you've registered a bunch of malone specs
User16: yes, all the 1.0 specs (that i know of) are in there :)
User12: cool. is there a milestone?
User12: also, you can add a spec to the UBZ agenda now
User12: on the spec page, bottom of the actions portlet, "Add to Meeting Agenda"
User12: i've put BjornT's email-for-ticket-system spec in there
User12: when you register a spec, if it's for UBZ, add it to that agenda too
User12: so jamesh can start playing with his Schedul-O-Matic
User16: User12 eh, right, re: the milestone, i was wondering if there was a way to target a bunch of specs at once to a milestone? if not, i'm more inclined to write that UI than spend the time driving the UI the distance required to do that "by hand" for all of them
* bradb looks
User12: User16 please just do it the boring way for the moment
User12: multiple-selector-interfaces are not well defined in LP, i don't want any more added
User16: ok
User12: but i don't mind if you put a placeholder spec in the system for that :-)
User12: and assign it to UBZ
User12: with me as approver, mpt as drafter, and yourself as assignee if you want it
User16: right, i'll add that
User10: ciao all
User11: kiko-afk, hi, around?
User11: kiko-afk, I'm back from dinner and will be go to sleep really soon
User11: kiko-afk, will you have the review any time soon or should I wait until tomorrow?
User15: carlos, I can do it tonight, but it might be too late for you, right?
User11: kiko, yeah
launchpad
Ubuntu IRC