[01:26] <lifeless> jamesh: does kiko/launchpad/rosetta-view-refactoring have the right pending-merge metadata ?
[03:00] <mpt> Goooooooooooooooooooood afternoon Launchpadders!
[03:25] <Ubugtu> New bug: #65800 in launchpad "Staging server should obviously be a demo" [Undecided,Unconfirmed]  http://launchpad.net/bugs/65800
[03:26] <Paddy_EIRE> how do I change the status of a bug to "Answered" on launchpad and Assign credit where it is due?
[03:27] <Paddy_EIRE> here is the bug https://launchpad.net/distros/ubuntu/+ticket/1719 someone posted that I should do this and I wish to
[04:17] <vezult> I would like to register a sourceforge cvs branch in launchpad. I don't really know too much about CVS, so when attempting to register the branch, and one of the required fields is the CVS "branch." As far as I know, there is only one, default branch.
[04:23] <jamesh> vezult: use MAIN
[04:23] <vezult> jamesh: thanks.
[04:25] <ajmitch> jamesh: regarding that, what do we do about failed imports?
[04:36] <jamesh> ajmitch: currently you need to ask ddaa about it.
[04:37] <ajmitch> alright
[04:37] <jamesh> ajmitch: if a CVS import previously was importing correctly but has stopped, it usually indicates that the upstream performed CVS surgery and the import needs some manual attention to get it going again
[04:38] <ajmitch> quite possibly - I went back to cutting patches out of CVS manually :)
[04:38] <jamesh> I know the rhythmbox guys were doing stupid things like moving ,v files around
[04:39] <jamesh> which is generally worse than copying them
[04:39] <jamesh> since you have no chance of recovering the history
[04:39] <jamesh> (copying just results in extra files existing in past revisions
[04:39] <ajmitch> I'll check with upstream to see if they've done anything silly
[06:15] <stub> canonical.com addresses are relaying fine...
[06:19] <stub> lifeless: Did you change PQM stuff in the last few hours?
[06:20] <lifeless> yes
[06:20] <lifeless> whats up?
[06:20] <stub> lifeless: The last patch.xxx.log contains just the line 'global name 'branch' is not defined'
[06:20] <stub> And I received no notifications of success or failure from pqm, nor has the commits mailing list
[06:22] <lifeless> let me check
[06:22] <lifeless> I've probably got a backtrace
[06:25] <lifeless> stub: merge went through at 11am
[06:26] <stub> lifeless: are you sure? bzr log on the launchpad/devel branch shows no landing
[06:26] <lifeless> stub: yes, I'm sure.
[06:27] <lifeless> stub: the dists branch is out of date, I forgot to upate it
[06:27] <stub> dists branch?
[06:27] <lifeless> stub: you need to use /code/ now for everything; if you do a commit to the dists branch replacing the sodium home/warthogs paths with /code/ it will fix it
[06:28] <lifeless> stub: yes, /code/rocketfuel/dists/...
[06:28] <lifeless> stub: where the VCS configs are stored
[06:28] <stub> I have
[06:28] <stub> Hmm
[06:28] <lifeless> let me see
[06:30] <lifeless> nope, /home/pqm/archives/rocketfuel/dists/devel/configs/canonical.com/launchad/development is still using the old paths.
[06:30] <lifeless> I'll fix it
[06:30] <lifeless> stub: try now, it should be happier
[06:30] <stub> Ahh... I understand now. I'd forgotten all about dists and config manager stuff ;)
[06:36] <jamesh> lifeless: btw, would it be possible to remove bzrtools and gnarly from rocketfuel-built?  Removed branches don't seem to disapear from it
[06:37] <lifeless> jamesh: sure
[06:37] <lifeless> stub can do that as can I
[06:37] <lifeless> I'll do it now
[06:37] <lifeless> done
[06:37] <jamesh> thank you
[08:58] <carlos> morning
[08:58] <mdke_> morning carlos 
[08:59] <carlos> SteveA: Hi, will you have time for a fast meeting with me?
[09:00] <carlos> about the Guadalinex meeting
[09:44] <SteveA> carlos: hi
[09:44] <SteveA> yes
[09:44] <SteveA> although I'll be briefly away in 10 mins
[09:44] <carlos> SteveA: hi
[09:44] <carlos> SteveA: just ping me when you have time
[09:44] <carlos> I will be around the whole morning
[09:45] <SteveA> carlos: ok
[09:45] <carlos> SteveA: thanks
[09:52] <SteveA> good morning _thumper_ 
[09:54] <SteveA> carlos: ok
[10:10] <SteveA> mpt: morning!
[10:50] <Ubugtu> New bug: #65868 in launchpad "Sprint attendance times should be considered local wallclock time" [Medium,Confirmed]  http://launchpad.net/bugs/65868
[10:56] <matthewrevell> SteveA: Hi
[11:03] <SteveA> hi matthewrevell 
[11:04] <matthewrevell> SteveA: Would you prefer to leave it until another time, as you're in the middle of a sprint?
[11:05] <SteveA> matthewrevell: let's have a quick talk now.  Can you call me?  I'll msg you a number
[11:46] <Ubugtu> New bug: #65878 in launchpad-bazaar "Cannot View Branch Online" [Undecided,Unconfirmed]  http://launchpad.net/bugs/65878
[11:47] <SteveA> jamesh: ping.  please write an email to Jean-Francois pointing him in a good direction for exporting bugs from roundup.
[12:37] <_thumper_> SteveA, ping
[01:42] <telenieko> Hi, is it possible to make the  CIA (cia.navi.cx) work with my bzr branches on launchpad ?
[02:50] <lucasvo> is there a launchpad usability team?
[03:05] <Ubugtu> New bug: #65922 in launchpad "Linking a to a bug from a spec works but not the other way around." [Undecided,Unconfirmed]  http://launchpad.net/bugs/65922
[03:20] <bradb> lucasvo: we have a usability genius in mpt, fwiw
[03:20] <bradb> mpt is the tom cruise of user experience
[03:21] <bradb> lucasvo: so feel free to talk to him to learn more about what's going on there
[03:25] <lucasvo> !seen mpt
[03:29] <cprov> carlos: ping
[03:29] <carlos> cprov: pong
[03:30] <cprov> carlos: hi, do you have any tests for copy_active_translations inside i-f-p ?
[03:31] <carlos> I think so
[03:31] <carlos> are you removing it?
[03:32] <cprov> carlos: I just can't find it
[03:32] <carlos> let me check...
[03:32] <cprov> carlos: yes, I've commented it out for now, we are going for edgy+1
[03:33] <cprov> carlos: do you see any problem ? can you run something similar later, after edgy+1 is established ?
[03:34] <carlos> yeah, I ran out of time to remove it myself
[03:35] <carlos> cprov: doc/distrorelease.txt
[03:35] <cprov> carlos: np, it's fine, I hope we can save some of the original 13 hours downtime required ;)
[03:35] <cprov> carlos: let me see
[03:36] <kiko-fud> hey there
[03:37] <cprov> carlos: what would be the best, 1. purge the function and statements or 2. comment out the statements in the test ?
[03:40] <cprov> carlos: honestly, the entire section should be in doc/initialise-from-parent.txt and the code would be moved from distrorelease.py as well, don't you think ?
[03:40] <carlos> cprov: well... comment them and file a bug assigned to me to move those test to the copy-missing-translations-from-parent tests
[03:41] <cprov> carlos: ok
[03:42] <carlos> cprov: thanks
[03:42] <carlos> kiko-fud: hi
[03:53] <cprov> carlos: well, it's more complicated then it sounded, in doc/distrorelease.txt, section "DistroRelease Translations migration", you always suppose humpy translations are in place too
[03:53] <cprov> carlos: I'd need to let copy_active_translation completly uncovered to pass the tests in PQM
[03:57] <cprov> carlos: something like this https://sodium.ubuntu.com/~andrew/paste/fileFH9PFz.html
[03:57] <cprov> carlos: which is unacceptable, IMO
[03:58] <cprov> carlos: other approach would be making initialiseFromParent(..., copy_translations=False) and make it true only inside doc/distrorelease.txt
[03:59] <cprov> carlos: what do you think about this ?
[04:07] <carlos> cprov: well, you can do the initial copy
[04:07] <carlos> like we do the incremental one
[04:08] <cprov> carlos: yes, calling humpy.copyMissingTransalationFromParent(), good idea
[04:08] <carlos> and tests should work without changes
[04:08] <lucasvo> mpt_: ping
[04:14] <cprov> carlos: just moving pieces around, translation related code is moved to the respective section. check if you like the file now, https://sodium.ubuntu.com/~andrew/paste/filexp9sjd.html (the diff is a little unreadable)
[04:15] <Ubugtu> New bug: #65932 in malone "malone changes the source package name, even if there is one in the archive" [Undecided,Unconfirmed]  http://launchpad.net/bugs/65932
[04:16] <carlos> cprov: The main one is to clone what we have in its parent distribution, like we did
[04:16] <carlos> before in this test when we created 'humpy' distribution.
[04:17] <carlos> cprov: that's wrong, isn't it? you are not doing it anymore 'before'
[04:19] <cprov> carlos: well, i-f-p runs w/o translation, it remains in the previous section, later on, in Migrating translation section, I do the initial copyMissingTranslationFrom(), the previous checks and then the original code, test works as expected, not sure it is clearer as before.
[04:21] <carlos> cprov: I know
[04:21] <carlos> what I mean is that the comment should be updated...
[04:21] <cprov> carlos: point me to it, I can't see.
[04:22] <carlos> instead of: The main one is to clone what we have in its parent distribution, like we did
[04:22] <carlos> before in this test when we created 'humpy' distribution.
[04:22] <carlos> I would just say: The main one is to clone what we have in its parent distribution.
[04:22] <cprov> carlos: I seee
[04:23] <cprov> carlos: yup, just deleted the last part of the paragraph. anything other than that ?
[04:24] <carlos> I think it's fine
[04:24] <carlos> cprov: thanks for handling it
[04:24] <cprov> carlos: very nice, thank you for reviewing it ;) (ehe rs=carlos)
[04:25] <carlos> :-P
[04:25] <carlos> see you!
[04:44] <jordi> kiko: hey, back.
[04:44] <jordi> yesterdaty was hispanic day, vacation in Spain
[05:50] <Ubugtu> New bug: #65945 in launchpad-support-tracker "Add a "Support contact of" report to the Person context " [Low,Confirmed]  http://launchpad.net/bugs/65945
[06:32] <mdz> cprov-lunch,malcc: are old .debs (no longer in the pool) kept on drescher anywhere? or only in the librarian?
[06:37] <cprov> mdz: only in librarian, you can download them via the UI
[06:39] <mdz> cprov: when I want to do something like dpkg -c on it, that is very inconvenient
[06:42] <cprov> mdz: I see, maybe we could make deathrow to move files somewhere instead of delete
[06:44] <mdz> cprov: yes, this is what katie does
[06:44] <mdz> and then they too expire after a time
[06:45] <Ubugtu> New bug: #65957 in launchpad-support-tracker "Allow subscribing to a request while giving an answer" [Undecided,Unconfirmed]  http://launchpad.net/bugs/65957
[06:46] <cprov> mdz: uhm, additional publication state may be required, anyway, it's a good idea, can you, please, file a bug ?
[06:47] <mdz> cprov: another idea would be to have a command-line tool on drescher which would fetch the files from the librarian
[06:50] <cprov> mdz: that's is possible too, if you're ok with informing name/version by hand. Is this always a very specific investigation ?
[06:50] <cprov> mdz: maybe "queue fetch" can help you immediatelly ...
[06:55] <mdz> cprov: a common use case is to fetch the past few versions of a .deb
[06:55] <mdz> or a particular old version of a source package or .deb
[06:58] <cprov> mdz: right, check if "queue fetch -Q done name/version" work for your current use cases (maybe you need some queue info before, the use the IDs for specific source or binary fetch)
[06:59] <mdz> maybe, but that isn't much better than browsing the web interface for each version
[06:59] <mdz> I just wondered if the files were already kept around so that we could do this kind of work quickly
[07:00] <mdz> it's less important than other issues
[07:02] <cprov> mdz: it wouldn't be easy to find an optimal time to keep files around and the reasonable disk-usage in drescher
[07:02] <mdz> cprov: we already did this with katie
[07:03] <cprov> mdz: deathrow removes around 1 G from the archive per day, but it would be fine to implement if distro-team can drive it.
[07:05] <kiko_> good morning vietnam
[07:05] <kiko_> SteveA, ping?
[07:06] <kiko_> matsubara, ping?
[07:07] <kiko_> the.. anyone.. anyone.. great depression
[07:07] <matsubara> kiko_: pong
[07:08] <matsubara> kiko_: did you get my message?
[07:08] <kiko_> matsubara, I didn't, no
[07:09] <kiko-afk> matsubara, try again
[07:09] <Mez> ddaa: ping
[07:16] <SteveA> kiko-afk: yo
[07:17] <kiko-afk> hey SteveA 
[07:17] <kiko-afk> SteveA, are you listening to new age?
[07:18] <SteveA> kiko-afk: a bit early for that I think
[07:18] <SteveA> clan told me 6.30, but that mark would ping
[07:18] <SteveA> I could dial in and see if we can talk before mark arrives
[07:19] <kiko-afk> SteveA, are you busy or do you want to?
[07:19] <SteveA> sure, let's DOIT
[07:19] <kiko-afk> oh good
[07:19] <kiko-afk> I am so bored 
[07:21] <SteveA> silence
[07:21] <SteveA> kiko-afk: i'm in
[07:23] <kiko-afk> oops
[07:23] <kiko-afk> hmm
[07:24] <kiko-afk> my phone is dying on me
[07:31] <SteveA> ffs
[07:31] <SteveA> stop walking around! ;-)
[08:01] <Ubugtu> New bug: #65977 in malone "Private replies to bug mail 'broken' by Reply-To misuse" [Undecided,Unconfirmed]  http://launchpad.net/bugs/65977
[08:03] <mdke_> interesting bug
[08:41] <mdz> kiko: are build failure notifications to the uploader enabled now
[08:41] <mdz> ?
[08:52] <cprov> mdz: I'm about to commit it in RF, it will be during the weekend
[08:52] <mdz> cprov: kiko told me it was only a configuration change and didn't require a code update
[08:53] <cprov> mdz: yes, but even config updates needs commit.
[09:07] <LaserJock> I've got an interesting Malone problem, the motuscience team's +subscribedbugs page doesn't seem to be getting updated
[09:07] <LaserJock> it doesn't seem to show bugs from roughly 50000 on
[09:10] <matsubara> LaserJock: I can see bug 58094 there in the first listing.
[09:10] <Ubugtu> Malone bug 58094 in arpack "Source out of date with upstream" [Undecided,Unconfirmed]  http://launchpad.net/bugs/58094
[09:11] <matsubara> LaserJock: is there any specific bug that you are sure that should be in the listing that is not listed? If yes, which one?
[09:11] <LaserJock> hmm, yeah, so it must be a bit further on
[09:11] <LaserJock> bug 65964
[09:11] <Ubugtu> Malone bug 65964 in pymol "Pymol does not start because of wrong python interpreter name in start script" [Undecided,Unconfirmed]  http://launchpad.net/bugs/65964
[09:12] <matsubara> hmm LaserJock, that's a known bug
[09:12] <matsubara> "also notified" don't show up on +subscribedbugs listing
[09:13] <LaserJock> darn
[09:13] <LaserJock> why is it in "also notified"
[09:14] <bradb> LaserJock: bug 61429 might interest you
[09:14] <Ubugtu> Malone bug 61429 in malone "Would like to see *all* assigned/subscribed bugs" [Undecided,Confirmed]  http://launchpad.net/bugs/61429
[09:14] <mpt_> bradb, I'm neither gay nor insane (as far as I know), so I'm doubtful about the Tom Cruise reference :-)
[09:14] <mpt_> lucasvo, pong
[09:14] <bradb> LaserJock: the idea, currently, is that Malone distinguishes "direct" subscriptions from "indirect" ones, so you can signal specific interest in a bug
[09:15] <bradb> mpt: you are the star of misson: impossible :P
[09:15] <lucasvo> mpt: they told me that you are the usability god of launchpad?
[09:15] <mpt> ah-har
[09:15] <matsubara> it's also notified because motu science is probably a bug contact for that package.
[09:15] <lucasvo> mpt: I got some suggestions...
[09:15] <LaserJock> bradb: but I'm looking at a teams +subscribedbugs, so they are all indirect, no?
[09:15] <bradb> LaserJock: they needn't be
[09:15] <lucasvo> mpt: and writing a hundred bug reports is kinda odd
[09:15] <mpt> lucasvo, alas that isn't true, but maybe I can help you anyway
[09:16] <LaserJock> I would assume that setting motuscience as a bug contact for that package would but it on +subscribedbugs
[09:16] <lucasvo> mpt: I just wanted to know if there are any guidelines regarding consistency of the portlets
[09:17] <LaserJock> but I need to explicitly subscribe motuscience to a bug to get it to show up there?
[09:17] <mpt> lucasvo, no.
[09:17] <mpt> lucasvo, people have just been piling stuff in there with <b> and <br> tags.
[09:18] <mpt> However, they should improve soon, as I'm reviewing them all and tidying them up.
[09:19] <bradb> LaserJock: for now, the bug contact bugs are found at https://launchpad.net/people/motuscience/+packagebugs
[09:19] <mpt> bradb, what happened to the release management stuff you were working on?
[09:19] <LaserJock> bradb: heh, fun
[09:19] <bradb> LaserJock: when the bug i mentioned earlier is fixed, this problem will go away
[09:20] <LaserJock> really?
[09:20] <bradb> mpt: conjoined bug tasks
[09:20] <mpt> oh
[09:20] <bradb> mpt: i'm working on it more with francis right now
[09:20] <LaserJock> but I don't care about seeing bugs for teams I belong to in my bug pages
[09:20] <bradb> mpt: it actually already landed, then unlanded.
[09:21] <lucasvo> mpt: and what about the position of th eboxes?
[09:21] <LaserJock> I just want to be able to go to the team's bug pages, a fix for that bug will also fix this issue?
[09:21] <mpt> lucasvo, currently they follow the Mullet Rule
[09:22] <mpt> The columns on the sides are allowed to be very long, like a mullet, as long as they're roughly symmetrical
[09:23] <bradb> LaserJock: the teams bug page is the link i gave above
[09:23] <bradb> i.e. +packagebugs
[09:23] <mpt> bradb, because my girlfriend looked at the stuff that you'd done before, and she asked me, "what if a bug gets nominated for a distribution release, and that release gets released without the bug being fixed, but the bug still exists when the next release is opened?"
[09:23] <mpt> And I didn't know the answer
[09:23] <bradb> mpt: nothing
[09:23] <bradb> mpt: it's just a nomination for a release
[09:24] <mpt> Sorry, for "nominated" in that read "accepted"
[09:24] <bradb> but i fear more deep analysis before it's been exposed to the real world, tbh
[09:24] <lucasvo> mpt: people like to have everything have it's own place. 
[09:24] <LaserJock> bradb: any timeline for fixing that? I'll write a script to process +packagebugs as a short term solution if it's going to take a while
[09:24] <lucasvo> mpt: for example the info box about of the project changes it's place various times. 
[09:25] <bradb> LaserJock: for them to be all on one page you mean?
[09:25] <mpt> bradb, for example, mdz says "yes, we'll fix this for Edgy+1", but there turns out not to be time, and then Edgy+2 opens and the bug still exists, but it's forgotten about because it was targeted to Edgy+1
[09:25] <mpt> and it's not visibly open for Ubuntu-in-general any more
[09:25] <lucasvo> mpt: this gives users a hard time trying to remember where to click on, because the location changes.
[09:25] <LaserJock> bradb: yeah, ,+packagebugs is no good to us by itself. We have ~450 packages on there
[09:26] <mpt> lucasvo, yes, it's a mess. It will improve soon, though.
[09:26] <LaserJock> bradb: I need to see the status of all the packagebugs in one place
[09:26] <lucasvo> mpt: so I should just write bug reports? or is there any pleace where these things are already written down?
[09:26] <mpt> lucasvo, normally I would say "yes, please report bugs"
[09:26] <matsubara> LaserJock: you might also be interested in bug 61024
[09:26] <Ubugtu> Malone bug 61024 in malone "+packagebugs could have better filtering." [Undecided,Confirmed]  http://launchpad.net/bugs/61024
[09:27] <lucasvo> mpt: but?
[09:27] <mpt> lucasvo, but in this case, I can tell you that it's unnecessary to report a bug about the position of boxes on the page, because that will soon be fixed anyway.
[09:28] <mdz> mpt: this is a discussion which needs to be had with input from the development team about how we actually work
[09:28] <LaserJock> matsubara: ah yes, Fujitsu seems to have beat me too it
[09:28] <mpt> Undoubtedly.
[09:28] <lucasvo> mpt: and other things?
[09:28] <mpt> lucasvo, other things, sure, please report them
[09:29] <bradb> LaserJock: not sure, but i feel your pain. it's probably between kiko and BjornT to sort out priorities for when all a team's bugs can be listed on one page.
[09:29] <mpt> bradb, we're going to miss your user-centredness :-)
[09:29] <bradb> mpt: the bug doesn't get forgotten about. there's still the open generic task.
[09:29] <mpt> (and your sense of humor)
[09:29] <bradb> heh
[09:29] <bradb> i will miss your user-centeredness!
[09:30] <mpt> bradb, so that's how ConjoinedBugTasks will work? iirc it's not how the previous system worked
[09:30] <bradb> btw, you should resurrect your old blog, you link-rotter
[09:30] <bradb> :P
[09:30] <mpt> yeah
[09:30] <LaserJock> ok, well I know you guys are really busy and all. I'll probably just create a quick script to process +packagebugs, at least until Edgy is released
[09:30] <mpt> I need to write a nice letter to the guy who runs phrasewise.com asking for redirects
[09:30] <LaserJock> I actually missed out on a few important bugs because I was looking at +subscribedbugs
[09:31] <bradb> mpt: the generic bugtask (on a distribution or product) is kept in sync with the IDistribution.currentrelease or IProduct.development_focus bugtask.
[09:31] <bradb> so, when the cur release or dev focus changes, the link is broken
[09:31] <bradb> the data flows from the generic task to the specific one
[09:31] <bradb> for milestone, assignee, sourcepackagename, importance, and status
[09:32] <mpt> Nifty.
[10:56] <ctrlsoft> Anybody here aware of a way to migrate bugs from trac to lp ?
[11:03] <matsubara> ctrlsoft: jamesh is the one who wrote the migration stuff for ubuntu's bugzilla to lp and for python's sourceforge to lp. He might be able to give you some advice there, but I don't think he's current online.
[11:14] <ctrlsoft> matsubara: ah, thanks