[12:19] <TLE> ok thanks lifeless
[01:25] <saua> I've got a conceptual question about launchpad: who's supposed to register a project? only the party responsible for it?
[01:31] <poolie> saua, no, anyone can
[01:42] <saua> hm ... that's what I've thought initially as well. That's the reason why I registered the eclipse project so that I could to "Also affects upstream" on a bug I triaged. (I'm not related to the Eclipse project, I'm only a user). Now I wonder if I should have done that ... 
[02:02] <poolie> hello jml
[02:03] <poolie> saua, is there a problem?
[02:08] <saua> poolie: i don't know, that's what I'm trying to find out ;-) I don't want to take any big responsibility with having registered this project (I don't have the time to invest a lot, I'm just here to help with some bugs, triag and maybe send a patch or two)
[02:09] <poolie> saua, as long as the registration is correct and doesn't duplicate an existing registration then you're fine
[02:10] <jml> poolie: hi
[02:10] <saua> ok, I've checked before that there isn't any other project for it already and I double checked all info, so that should be ok, thanks
[02:10] <jml> ah, it did time out.
[02:11] <poolie> saua: then cool, thanks for adding it!
[03:30] <mpt> Gooooooooooooood afternoon Launchpadders!
[03:30] <ajmitch> hi mpt 
[03:33] <mpt> Theuni, you could make a "Future" milestone for bugs you want to defer
[03:34] <mpt> The drawback would be that it's rather difficult at the moment to search for bugs that aren't in a particular milestone
[03:34] <mpt> (You need to select every milestone except that one)
[03:38] <mpt> TLE, you should ask carlos or danilos when they are here
[03:39] <mpt> Theuni, the original idea behind Fix Committed vs. Fix Released was that:
[03:39] <mpt> - a bug would be marked as Fix Committed when a fix was incorporated into the mainline
[03:40] <mpt> - Fix Committed bugs would still appear by default in search results, so that people who were using the latest stable release wouldn't report (quite so many) duplicates
[03:40] <ubotu> New bug: #109113 in malone "please indicate closed bugs in the recently filed/touched lists" [Undecided,Unconfirmed]  https://launchpad.net/bugs/109113
[03:40] <mpt> - when a new stable version was released, the bugs that were fixed in that version could be mass-changed from Fix Committed to Fix Released.
[03:41] <mpt> Unfortunately, that hasn't worked. We don't have that mass-change function, and it's too much work to change them individually.
[03:41] <mpt> So Ubuntu developers (for example) have been marking bugs as Fix Released for Ubuntu versions that haven't been released yet.
[03:43] <mpt> The Launchpad team uses Fix Committed and Fix Released the way we intended, but we're speshul :-)
[03:44] <mpt> So we're pondering what to do about those statuses.
[03:46] <poolie> good morning mpt!
[03:47] <mpt> hello poolie 
[03:47] <lifeless> mpt: bzr uses the differently ;)
[03:47] <mpt> Ooh, do tell
[03:48] <mpt> (by "the" I assume you mean "the bug statuses"...)
[03:48] <lifeless> http://bazaar-vcs.org/BugGuidelines
[03:50] <mpt> a-ha
[03:50] <mpt> "I have a truly marvellous fix, which this mainline is too narrow to contain"
[03:51] <Lumiere> mpt: one it gets nominated for a release
[03:51] <Lumiere> it should get closed
[03:52] <Lumiere> and there should be a way to post that a release occured (outside ubuntu)
[03:52] <Lumiere> as there are packages in launchpad that aren't currently in ubuntu
[04:02] <poolie> mpt, i assume the 25th is a holiday for you too?
[04:03] <lifeless> mpt: the reason we do fix released when it hits bzr.dev is so the bug doesn't show open anymore
[04:03] <lifeless> mpt: which at root is us optimising for developers not users.
[04:03] <mpt> poolie, yes
[04:04] <mpt> So one possibility I've been kicking around
[04:04] <lifeless> mpt: e.g. users want to see 'bugs which I may be seeing including those fixed in the next release', but devs want 'show me bugs to work on'
[04:04] <lifeless> where work includes 'review' and 'code' and 'design'
[04:04] <mpt> is to have a single "Done" status, and for project maintainers to be able to configure how long "Done" bugs should appear in the open bugs list
[04:05] <mpt> depending on their user base's typical upgrade cycle, bug-reporting savviness, and so on
[04:05] <poolie> mpt, that might be nice
[04:05] <lifeless> what I'd like as a user
[04:05] <lifeless> is to be able to tell launchpad what I'm using.
[04:05] <lifeless> e.g. I'm using 'feisty'
[04:06] <lifeless> I want to see all bugs that are relevant to me. I dont want to see bugs that were 'done' before feisty released.
[04:06] <lifeless> or things introduced after feisty
[04:06] <mpt> We also probably need a field for "This bug is fixed in versions: __________"
[04:06] <lifeless> lp is designed to be able to do this
[04:07] <lifeless> but the first implementation of it was horrendous and was pulled out. (well, it wasn't designed to know what *I* am interested in, but the rest it was)
[04:07] <mpt> Infestations, you mean?
[04:07] <lifeless> I think that was the code name given to them.
[04:08] <mpt> yeah, not sure we want to go down there again
[04:08] <mpt> but
[04:09] <mpt> Nor would just "omit bugs that were Done before release N" work, if we start having overlapping release cycles (people start hacking N+1 before N is released)
[04:10] <lifeless> right
[04:10] <mpt> I don't know how many Free Software projects do that currently
[04:10] <lifeless> which bzr does
[04:10] <lifeless> squid does
[04:10] <mpt> ah
[04:10] <lifeless> ubuntu doesn't
[04:18] <lifeless> poolie: spiv: you have approved and unmerged changes
[04:37] <TLE> mpt: thanks
[04:48] <mpt> whoa, deja vu
[04:49] <mpt> Two bugs with (almost) exactly the same summary, reported by the same person, three months apart
[04:50] <lifeless> you can test that
[04:50] <lifeless> file a bug
[04:50] <lifeless> with the summary
[04:50] <lifeless> but dont complete the process
[04:51] <mpt> ah, true
[04:53] <mpt> yep, they both show up
[04:54] <mpt> but at the time the second was reported on "launchpad", I think the first was filed under "malone"
[04:54] <mpt> Our use of separate projects bites again
[04:59] <lifeless> I'd argue that the partitioning between projects is biting
[04:59] <lifeless> ;)
[05:16] <ubotu> New bug: #109131 in malone "When you are an idiot you can't remove a bug" [Undecided,Unconfirmed]  https://launchpad.net/bugs/109131
[05:18] <jml> strong words
[05:31] <lifeless> well they can't fix them either
[05:36] <mpt> heh
[05:36] <mpt> That bug is a duplicate of a bug with "retarget" in its summary, but all that mention of idiots made my fingers type "retarded" instead
[05:43] <Lumiere> I always thought that malone should be a subproject of launchpad <_<
[05:44] <lifeless> Lumiere: it is
[05:44] <Lumiere> lifeless: and accessed from launchpad's project (instead of malone as a project)
[05:45] <lifeless> https://launchpad.net/launchpad-project/
[05:46] <Lumiere> but see
[05:46] <Lumiere> when you search for 'launchpad'
[05:46] <Lumiere> you don't get that
[05:46] <Lumiere> it's option 3
[05:46] <Lumiere> and not option 1
[05:47] <mpt> And that arrangement means Launchpad is a subproject of Launchpad
[05:47] <Lumiere> mpt: which makes sense
[05:47] <Lumiere> but a super project is usually higher priority then a sub project
[06:42] <lifeless> mpt: ping
[06:42] <mpt> (lifeless: In case I'm not here right now, tell me about what you want, and I'll reply when I'm available.)
[06:43] <lifeless> mpt: is there somewhere I can click from a product home page to go straight to a bug listing?
[06:52] <mpt> lifeless, not in Launchpad's interface
[06:52] <lifeless> :(
[06:52] <lifeless> thanks
[06:53] <mpt> You can click in your browser's URL field and type "/+bugs" at the end, that's what I do :-] 
[06:53] <lifeless> surely thats a bug?
[06:53] <mpt> yes, and it's reported
[06:53] <lifeless> I'll me-too.
[06:53] <lifeless> got the number or a search for google?
[06:53] <Hobbsee> hi mpt, lifeless 
[06:54] <lifeless> hi
[06:58] <mpt> lifeless, not handy, but I'll find it
[06:58] <lifeless> thanks
[07:01] <lifeless> mpt: another question
[07:01] <lifeless> mpt: is there any chance of the bug list being made cachable? its really annoying that lp takes 10 seconds to bring up the list everytime I hit back.
[07:03] <mpt> lifeless, bug 94458
[07:03] <ubotu> Malone bug 94458 in malone "bugs.launchpad.net/project and bugs.launchpad.net/project/+bugs are different and not obviously linked" [Medium,Confirmed]  https://launchpad.net/bugs/94458
[07:04] <mpt> lifeless, nag SteveA and kiko to get launchpad-mostly-over-http implemented :-)
[07:10] <lifeless> mpt: do you think that the pick-user dialogs (e.g. assign driver) could/should have a shortcut to say 'me' ?
[07:13] <lifeless> mpt: one more thing, where does one go now to configure project-wide bug trackers? Its not on the project admin page.
[07:15] <mpt> lifeless, I think there should be a "Me" radiobutton under each person field (with another next to the field itself)
[07:15] <mpt> like we do currently for bugs
[07:16] <mpt> lifeless, from the project's Overview page, choose "Define Launchpad usage"
[07:16] <lifeless> re bugtracker for project, I found it, but theres no way to say 'uses malone'
[07:17] <lifeless> mpt: no, thats the per-product level.
[07:17] <mpt> oh, you mean per-project-group
[07:17] <lifeless> i'm looking for a way to define launchpad usage for the project group.
[07:17] <lifeless> (sorry, spent what, nearly 3 years doing 'project', project-group is coming hard)
[07:18] <mpt> yeah
[07:18] <lifeless> so yeah, I'm looking for (doesn't exist) https://launchpad.net/bazaar/+launchpad
[07:18] <lifeless> should I file a bug?
[07:18] <mpt> yes
[07:19] <mpt> actually
[07:19] <mpt> I think it might be reported already
[07:20] <mpt> lifeless, bug 87228
[07:20] <ubotu> Malone bug 87228 in malone "No option to say a project uses Malone!" [Medium,Confirmed]  https://launchpad.net/bugs/87228
[07:20] <mpt> Hooray for Google's "inurl:" advanced operator
[07:21] <lifeless> heh too late, I already fired off a bug via email
[07:21] <lifeless> I may have made my point more generally though. dunno.
[07:23] <lifeless> man evo is crack
[07:30] <ubotu> New bug: #109150 in launchpad "no +launchpad for project groups" [Undecided,Unconfirmed]  https://launchpad.net/bugs/109150
[07:50] <ubotu> New bug: #109153 in launchpad "Rename project->projectgroup and product->project" [Undecided,Unconfirmed]  https://launchpad.net/bugs/109153
[07:55] <lifeless> review meeting in 5 minutes
[07:59] <lifeless> mpt: 109150 is the new one I filed that may be a dupe. 
[08:01] <lifeless> reviewer meeting time
[08:01] <lifeless> BjornT: 
[08:01] <lifeless> spiv: 
[08:01] <lifeless> jamesh: 
[08:01] <jamesh> hi
[08:01] <spiv> Hello
[08:01] <BjornT> hi
[08:02] <lifeless>  * Roll call
[08:02] <lifeless>  * Next meeting
[08:02] <lifeless>  * Queue status.
[08:02] <lifeless>  * How are post-merge reviews of rs/trivial commits going?  (BjornT for .eu)
[08:02] <lifeless>  * [fasttrack]  (BjornT for .eu)
[08:02] <lifeless>  * Urgent review requests (lifeless for .au)
[08:02] <lifeless>  * New reviewers (lifeless for .au)
[08:02] <lifeless> BjornT: I think you forgot to link in your minutes. Can you do so after the meeting (I'm editing the page at the moment)
[08:02] <lifeless> next meeting on the 30th, same time ?
[08:03] <BjornT> lifeless: sure, i'll take a look at it. (i was sick, so i wasn't chairing the meeting)
[08:03] <lifeless> BjornT: ah! forgot that.
[08:03] <lifeless> BjornT: are you better now ?
[08:03] <BjornT> yes, much better, thanks.
[08:06] <lifeless> ok
[08:06] <lifeless> queue status.
[08:07] <lifeless> 15 branches
[08:07] <lifeless> 8 over target
[08:07] <lifeless> (I'm not counting the merged branch)
[08:08] <lifeless> spiv: I imagine you have the same excuse as last week ?
[08:08] <spiv> lifeless: basically, although I'm over half-way through the big one (Carlos').
[08:08] <lifeless> ok. 
[08:08] <spiv> So I am less behind than last week.
[08:08] <spiv> I expect I'll be caught up today.
[08:08] <lifeless> BjornT: looks like the bulk of the overdue ones should be caught up with by the .eu meeting - can you particularly nag then ?
[08:09] <lifeless> kiko and salgado together are half the overdues
[08:09] <BjornT> lifeless: yeah, i'll nag.
[08:11] <lifeless>  jamesh ?
[08:11] <lifeless> jamesh: how about your branch?
[08:11] <lifeless> BjornT: were you still ill on friday ?
[08:11] <jamesh> lifeless: just sent the review.
[08:11] <lifeless> jamesh: hah!. deadlines :)
[08:12] <jamesh> lifeless: I think salgado has been lax in updating the status of some of his
[08:12] <lifeless> hmm. BjornT - please be sure to find out if that is the case.
[08:12] <lifeless> ok
[08:12] <lifeless> urgent reviews
[08:13] <jamesh> lifeless: he sent me a review of jamesh/launchpad/storm-initialise-zstorm
[08:13] <BjornT> lifeless: no, i was back to work on friday
[08:13] <lifeless> That went to the list, but hasn't been really resolved one way or another. The big thing that has come out of it is that urgent != cherrypick.
[08:14] <lifeless> ok. Well I'm not particularly stressed, as the bulk of them are only just over when you count the weekend. and with jamesh' not the overdue count is lower.
[08:14] <lifeless> that said, we are aiming for 0 right?!
[08:14] <BjornT> i still think that cherrypick -> urgent, so it makes sense to document urgent fixes and have cherrypicks be a special case of an urgent fix.
[08:14] <spiv> I am, believe it or not! :)
[08:15] <lifeless> BjornT: did you read stubs explanation ?
[08:15] <BjornT> let me take a quick look at that explanation
[08:16] <lifeless>  Also critical fixes may not be critical
[08:16] <lifeless> enough to roll out if the affected users are happy using fixes on the edge
[08:16] <lifeless> or beta systems and there is nothing stopping the automatic updates of these
[08:16] <lifeless> systems.
[08:16] <lifeless> thats the bit I agree with
[08:17] <BjornT> yes, that's why i think we should talk mainly about urgent/critical fixes, and have cherrypicks be a special case of them.
[08:17] <BjornT> if the fix needs to be rolled out, put it on LaunchpadProductionStatus page.
[08:17] <lifeless> ok
[08:17] <lifeless> well I suggest that you continue the thread on the list.
[08:17] <BjornT> sure
[08:18] <lifeless> from a review perspective the important thing is documentation for developers
[08:18] <lifeless> how they should interact with the review process.
[08:18] <lifeless>  * New reviewers (lifeless for .au)
[08:19] <lifeless> - Barry Warsaw (barry) that I (flacoste) will coach;
[08:19] <lifeless> - Brad Crittenden (bac) that kiko will coach;
[08:19] <lifeless> - Elliot Murphy (statik) that salgado will coach;
[08:19] <lifeless> - Tim Penhey (thumper) that should be coached by an .au reviewer.
[08:19] <lifeless> This should allow everyone to drop back to one review a day I think, once they are up to speed.
[08:20] <lifeless> as we previously discussed we will have their first 1/2 weeks worth of reviews be sent to another coach for double-checking.
[08:20] <lifeless> I'm going to send a welcome-and-heres-how-coaching should work mail to them, but first we need a 'volunteer' to coach thumper.
[08:20] <spiv> I'm happy to coach Tim; I assume that means being available to review his reviews and perhaps chat with him about them?
[08:21] <lifeless> indeed. I'd suggest it means doing the same review and comparing his and your results.
[08:21] <spiv> Ok.
[08:21] <lifeless> ok. spiv to tutor thumper.
[08:22] <lifeless> jamesh: can I ask you to update the PendingReviews page? 
[08:22] <jamesh> just a sec.
[08:23] <lifeless> jamesh: if that means 'sure thing I'm doing it now', lets move on :)
[08:23] <jamesh> it does.  I'll let you know when it completed
[08:24] <jamesh> completes, even
[08:24] <lifeless>  * other business
[08:24] <lifeless> none from me
[08:24] <lifeless> type now or hold your keyboard forever
[08:24] <lifeless> 5
[08:24] <lifeless> 3
[08:24] <lifeless> 2
[08:24] <lifeless> 1
[08:25] <lifeless> Meeting over! thanks for coming.
[08:25] <spiv> 4 is such an overrated number.
[08:25] <lifeless> its not prime
[08:25] <jml> neither is 1
[08:25] <spiv> No wonder you skipped it :)
[08:25] <lifeless> jml: termination point, special cased.
[08:25] <jml> heh
[08:26] <jamesh> lifeless: it has updated
[08:26] <lifeless> thanks!
[08:27] <jamesh> lifeless: what do you think of winding the "stale branch" age in a bit?
[08:27] <jamesh> it is currently set at 50 days
[08:27] <lifeless> shit all over the place, you mean ?;)
[08:28] <jamesh> I was thinking 31 days might be a good number (one month without activity)
[08:28] <jml> also prime
[08:28] <jamesh> we could consider all branches with a prime age to be stale
[08:28] <jml> heh heh
[08:29] <jamesh> to make things interesting
[08:31] <jml> now I'm wondering how many prime numbers are also fibonacci numbers.
[08:32] <lifeless> jamesh: Uhm. I'd prefer the email notifications and the 'about to go red' features; if you are changing things ;)
[08:33] <lifeless> I dont think that the brown threshold matters very much. Now it exists there is psycological pressure.
[08:50] <carlos> morning
[08:51] <spiv> carlos: good morning
[08:51] <spiv> carlos: I just sent you a review :)
[08:51] <carlos> spiv: cool, thanks!
[08:51] <spiv> carlos: sorry about the delay, I haven't been juggling my tasks very well.
[08:52] <spiv> carlos: I hope it was worth the wait ;)
[08:52] <carlos> spiv: don't worry, as long as it's done... :-P
[08:52] <spiv> carlos: I would have less to say if you'd been using make lint ;)
[08:54] <carlos> spiv: yeah, it stopped working at some point and I forgot to use it again once it was fixed...
[08:56] <spiv> jml: oh the bzr upgrade finally worked?
[08:56] <jml> spiv: yeah, it's landed in RF already
[08:57] <jml> waiting for deployment.
[08:58] <jml> does bzr.dev not work with the smart server on devpad?
[08:58] <spiv> jml: woo!
[08:58] <spiv> jml: Right
[08:58] <jml> spiv: yeah, very woo.
[08:58] <spiv> jml: you can use BZR_REMOTE_PATH, though
[08:59] <jml> spiv: or one of the twelve older versions of bzr I have lying about
[08:59] <spiv> jml: e.g. BZR_REMOTE_PATH=/home/andrew/bzr.dev/bzr bzr push bzr+ssh://devpad/...
[08:59] <spiv> jml: I'd prefer it if you'd dogfood my new code, so you can report bugs :)
[09:00] <jml> spiv: I will do that for future pushes.
[09:01] <jamesh> spiv: it'd be cool if I could use a locations.conf setting for that
[09:01] <jamesh> spiv: e.g. [bzr+ssh://hostname] \nbzr_remote_path = /path/to/bzr
[09:03] <lifeless> jamesh: ptc.
[09:04] <spiv> jml: (and so you can enjoy the modest speed improvements)
[09:16] <jml> what's the tag for unit test related bugs?
[09:21] <mpt> jml, test-system iirc
[09:22] <jml> mpt: thanks
[09:23] <schwuk> lo mrevell :)
[09:24] <mrevell> schwuk: welcome!
[10:31] <bostik> hi all 
[10:31] <bostik> anybody from lauchpad ?? 
[10:34] <poolie> hi bostk
[10:36] <carlos> bostik: hi
[10:36] <bostik> hi 
[10:36] <carlos> usually there is always one of us here, just go ahead and ask whatever you need ;-)
[10:37] <popey> http://www.ubuntu.com/getubuntu/upgrading has links at the top which send you to the wiki which redirects you back to http://www.ubuntu.com/getubuntu/upgrading again
[10:37] <popey> https://help.ubuntu.com/community/FeistyUpgrades#head-902d9d56fb765ea581cc6859e0eb1ccd47dba831 for example
[10:37] <bostik> carlos: i have  an ubuntu mirror recorded in lauchpad and it seems it's not updated since friday
[10:38] <bostik> no more probe 
[10:38] <bostik> here is the link 
[10:38] <bostik> https://launchpad.net/ubuntu/+mirror/ubuntu.fastbull.org-release
[10:41] <TLE> Hello carlos and danilos. I was here last night with a couple of questions about how the LP upload of translations work, and I was told to ask one of you guys when you were her :)
[10:42] <carlos> TLE: please, go ahead and ask
[10:43] <TLE> First of all. Regarding the difference between the two use upload methods. I found info in a thread somewhere that suggested that the difference between "user upload" and "published upload" is that in "published upload" the uploaded translations overwrite the ones already in LP, in "user upload" they do not. Is that correct?
[10:47] <carlos> TLE: the oposite
[10:48] <TLE> carlos: the opposite, so "user uploads" overwrites LP
[10:48] <carlos> 'published upload' means that is something you didn't do on Launchpad but that comes from the source tree directly and done outside Launchpad as part of GNOME development or KDE one
[10:48] <carlos> user upload is just like doing translations on the Launchpad web interface
[10:50] <carlos> the 'published upload', sometimes, will change translaitons in Launchpad, for instance, when it matches previous published one
[10:51] <carlos> so we don't fork in Launchpad when someone fixes a translation outside Launchpad
[10:52] <carlos> bostik: the scripts to handle mirrors are working correctly
[10:52] <carlos> bostik: so I suppose your mirror is already up to date
[10:53] <bostik> carlos: i get this: This mirror was last verified 2007-04-21
[10:53] <carlos> bostik: anyway, if you want to be 100% sure, check it with salgado. He's in charge of that script. He should be available in 2-3 hours
[10:53] <bostik> carlos: is this the date of last probe ?
[10:54] <bostik> carlos: ok, thanx a lot i'll contact him
[10:54] <carlos> bostik: well, I guess (just a guess) we only check if there are updates to check for
[10:54] <TLE> carlos ok, what I need to do is to upload translations that come from the upstream Gnome cvs tree, and I want them to overwrite the ones already in LP. So how would I go about doing that. Could I then do something like intltool-update the po-file from upstream Gnome against the pertaining Ubuntu sourcepackage and then make it a userupload to ensure that this happens ?
[10:54] <bostik> carlos: ok but our mirror is not listed here https://launchpad.net/ubuntu/+cdmirrors
[10:55] <lifeless> bostik: please open an answer request
[10:55] <lifeless> https://answers.launchpad.net/soyuz/ should be the right place.
[10:55] <carlos> TLE: is that a way to revert translation changes on Launchpad? or are those files more up to date than the ones with latest GNOME version in Ubuntu?
[10:56] <carlos> bostik: it's at https://launchpad.net/ubuntu/+archivemirrors
[10:56] <Znarl> bostik : Your mirror is not listed because it failed a probe on Friday.  It should have been tested again over the weekend but was not.
[10:56] <carlos> and it's set as up to date, so you will need salgado for that. Please, file a ticket as lifeless suggested
[10:56] <carlos> Znarl: thanks for handling this
[10:59] <bostik> carlos: thanx and sorry for my bad english 
[10:59] <carlos> bostik: no problem at all
[11:03] <TLE> carlos: Sort of. Actually the reason I want to do it to corrects some errors in the Ubuntu versions of the translations (in 2 pakcages, errors in one of them also present upstream the ones in the other aren't). And then because we do all our Gnome translation upstream and because our LP team wasn't "closed" and managed untill resently, I in general, would like to make the sure that as many upstream translations go in and replace the LP ones, since I'm doin
[11:04] <carlos> TLE: then, my advice is to upload them twice, once as published and once as user upload
[11:05] <carlos> TLE: if it's for the whole GNOMe nad you do it by hand, do it as published and once everything is imported (when you get the confirmation emails) open a ticket on answers.launchpad.net/rosetta and request to revert to upstream/published translations and we will do it in our side
[11:09] <TLE> carlos: I was planning to do it over a period whenever I could see the need to upload a po-file anyway. So but uploading then upstream file as "user upload" I don't need to worry about potential po file differences?
[11:10] <TLE> carlos: I mean when uploading twice as you suggested earlier
[11:11] <carlos> TLE: if you upload both, next update will do less forks, yes
[11:11] <TLE> carlos: I don't understand
[11:13] <carlos> TLE: when Gutsy is open
[11:13] <carlos> we will copy Feisty translations
[11:13] <carlos> if you only do the user upload
[11:13] <carlos> we will detect it as you wanting to fork from what GNOME has
[11:14] <carlos> and will not apply some updates on Gutsy's version of GNOME
[11:14] <carlos> if you upload it as user and published ones
[11:14] <carlos> both will be the same
[11:14] <carlos> and thus, Gutsy will update both too when the new GNOME is imported in Ubuntu
[11:15] <Nafallo> kewl. didn't know about that feature :-)
[11:18] <carlos> Nafallo: well, except for some bugs in that code, we designed Launchpad to work that way since the beginning 
[11:21] <TLE> carlos: ok so in short. wanting to upload upstream po-files and have them overwite LP-ones I can't just do it as "user upl" because then I am not sure that they will overwrite the one LP when transl. are taken out for faisty Therefore I have two options. Upload twice, one in each mode. Or upload a large quantity as "published" and when uploaded ask you guys to revert to published manually, correct ?
[11:23] <carlos> right
[11:24] <TLE> carlos: *phew* does the order of upload when doing them twice matter is it purely a matter of both of actually doing both of them ?
[11:24] <carlos> the order doesn't matter at all
[11:27] <TLE> carlos: ok great, many thanks for all your help. One last thing I was wondering. Is this functionality documented somewhere because I actually did look, but I could not seem to find it?
[11:29] <carlos> well... it's just the way  the system works, and we (ab)use it as a workaround until we add some UI pages to do it explicity
[11:31] <TLE> ok ;) well thanks
[12:16] <ubotu> New bug: #109214 in launchpad-bazaar "Use TestCaseWithMemoryTransport instead of TestCaseWithTransport" [Undecided,Unconfirmed]  https://launchpad.net/bugs/109214
[12:45] <ubotu> New bug: #109223 in launchpad "Mirror-prober hanging on UnknownURLScheme error" [Undecided,Unconfirmed]  https://launchpad.net/bugs/109223
[01:06] <cprov> good morning !
[03:00] <ubotu> New bug: #109259 in launchpad "typo on cc2007-dholbach" [High,Confirmed]  https://launchpad.net/bugs/109259
[03:08] <marga> Hi! I just realized that I appear 4 times in launchpad: twice for my debian packages (automatic accounts), once for the account I used to order CDs and once for the account I had created to try out Rosetta.  Is there a way of unifying those 4 accounts?
[03:09] <salgado> marga, yep, there's a link to merge the accounts at https://launchpad.net/people/ 
[03:20] <marga> salgado: thanks.
[06:05] <ubotu> New bug: #109310 in malone "upstream task opened on a product not using malone as bug tracker" [Undecided,Unconfirmed]  https://launchpad.net/bugs/109310
[06:26] <ubotu> New bug: #109318 in launchpad "unequal " on "Define Launchpad usage" page" [Undecided,Unconfirmed]  https://launchpad.net/bugs/109318
[06:49] <ubotu> New bug: #109326 in malone "mouse crazy in ubuntu 7.04" [Undecided,Unconfirmed]  https://launchpad.net/bugs/109326
[08:27] <Seveas> I need to change the txt in a poll that has been started already for the ubuntu members (typo in a url). Can someone help me with that?).
[08:38] <Phineas> Hey folks, so I'm trying to get my PGP key on to Launchpad but I seem to be having some troubles getting it onto the Ubuntu key server. I typed 'gpg --keyserver keyserver.ubuntu.com --send-keys' and it ran with no errors reported but the key is not showing up on the server. Is there some delay that I should expect?
[08:40] <Phineas> Anone?
[08:41] <Phineas> anyone even
[08:41] <habeeb> I bet that everyone here is too busy with ubuntu-classroom :/
[08:41] <salgado> Seveas, a poll can't be changed after it has started... if that's really a problem I can try to get our DBA to change it manually, though
[08:41] <salgado> Phineas, yeah, there usually is some delay, although not very long
[08:42] <Phineas> I'm coming up on 10 minutes and it still is not registering
[08:42] <Seveas> salgado, it's a highly visible poll for ubuntumembers and there is now a broken link in it. It's important to me and looks stupid. Whether that's important nough for you I don't know, but I'd be very thankful if it can be changed
[08:43] <kiko> Phineas, is your key available on other keyservers?
[08:43] <Phineas> I don't think so, I'm just figuring out the pgp stuff now.
[08:44] <Phineas> and of course it comes up now
[08:44] <Phineas> thanks guys
[09:15] <ubotu> New bug: #109390 in launchpad-answers "Rename alias and host for incoming/outgoing notifications" [High,Confirmed]  https://launchpad.net/bugs/109390
[09:31] <ubotu> New bug: #109393 in rosetta "When msgstr_plural changes we should accept it and set the string as needing review" [Undecided,Unconfirmed]  https://launchpad.net/bugs/109393
[10:42] <salgado> Seveas, please subscribe to bug 109259. I asked one of our DBAs to fix it
[10:42] <ubotu> Malone bug 109259 in launchpad "typo on cc2007-dholbach" [High,Confirmed]  https://launchpad.net/bugs/109259 - Assigned to Tom Haddon (mthaddon)
[10:44] <harrisony> salgado: you can subscribe him
[10:44] <harrisony> https://bugs.launchpad.net/launchpad/+bug/109259/+addsubscriber
[11:00] <apokryphos> kiko: hey, did you receive the email?
[11:11] <kiko> apokryphos, I did, yeah
[11:11] <apokryphos> kiko: cool, anything else to do?
[11:12] <kiko> remind me of his name?
[11:12] <kiko> found it.
[11:13] <kiko> apokryphos, done.
[11:13] <kiko> https://launchpad.net/~francis
[11:14] <apokryphos> kiko: thanks a lot :)
[11:14] <kiko> most welcome
[11:14] <kiko> where was I..
[11:19] <bdmurray> The bugsquad mailing list just started getting support question e-mails
[11:19] <bdmurray> and Ubuntu BugSquad somehow seems to be subscribed to a few questions
[11:26] <ubotu> New bug: #109431 in malone "Kubuntu 7.04 Feisty Does Not Install On IBM r40e From Using The Live Desktop Installer." [Undecided,Unconfirmed]  https://launchpad.net/bugs/109431
[11:28] <Kmos> OOPS-478D1969
[11:28] <ubotu> https://devpad.canonical.com/~jamesh/oops.cgi/478D1969
[11:40] <ubotu> New bug: #109435 in launchpad-answers "OOPS-478D1969 on answers edit languages..." [Undecided,Confirmed]  https://launchpad.net/bugs/109435
[11:43] <tomtom> hi