[06:23] <hanasaki> anyone awake?
[09:29] <SteveA> morning
[09:39] <stub> There appears to be a load of crud in /home/warthogs/archives/rocketfuel/launchpad/devel, such as .bzr.backup and repository.old. This makes it very slow to mirror it in order to prime a branch for a faster push.
[09:53] <SteveA> even if you use bzr branch ?
[09:55] <lifeless> morning SteveA 
[09:56] <lifeless> stub: indeed, both of those can be deleted.
[09:57] <lifeless> SteveA: phone call ?
[09:57] <SteveA> lifeless: can do
[09:57] <lifeless> I'm at the K+K - is it easier for you to ring me, or me you ?
[10:30] <sivang> morning
[10:42] <mdke> elmo, Znarl, do you know if admin intervention is required to effect a change in the @ubuntu.com email redirect after changing one's preferred email address in launchpad?
[10:43] <Znarl> mdke : You'll need to ask Elmo when he's around in a few hours or email RT.
[10:45] <mdke> Znarl: sure thing, thanks. Wiki magic today?
[10:46] <Znarl> mdke : Yep, should be.
[10:47] <mdke> Znarl: +D
[10:47] <mdke> or even, :D
[10:50] <mdke> Znarl: gimme a shout if you need anything
[10:51] <lifeless> jamesh: ping
[10:51] <jamesh> lifeless: pong
[10:51] <lifeless> 18  18  salgado  david/cscvs/code-cleanups
[10:51] <lifeless> that seems bong to me
[10:52] <lifeless> I'm *positive* it cannot be 18 days in that state
[10:52] <ddaa> this branch is not even a week old
[10:52] <ddaa> well...
[10:52] <ddaa> maybe I did some abusive copy-pasting though...
[10:52] <jamesh> lifeless: on PendingReviews it says 2006-05-17
[10:53] <ddaa> most probably my bad
[10:53] <mdke> btw did someone report that there are lots of dapper-upgrades uploaded which aren't coming through?
[10:54] <lifeless> jamesh: the first column is ddaa's problem
[10:54] <lifeless> jamesh: the second one though, is the 'days in state' column, and 18 is not right for that.
[10:54] <jamesh> lifeless: the penidng-reviews code believes the dates for newly added branches, which is the problem here
[10:54] <lifeless> so, ddaa - DONT DO THAT
[10:55] <lifeless> jamesh: but it would be nice to correct.
[10:55] <jamesh> yeah
[11:04] <stub> Kinnison: Your md5 column is now filled in. Are you going to need to run selects on it in the next week?
[11:05] <Kinnison> stub: No, but if you can do 'alter table libraryfilecontent alter column md5sum set not null' or similar then I'd be grateful. (Of course, only do that if you're sure it won't explode everything :-)
[11:06] <Kinnison> We'll need it when we move to trying experiments for speeding up publishing
[11:08] <lifeless> jamesh: can you poke pending reviews to have '3' for that branch ?
[11:15] <jamesh> lifeless: should be fixed on next run
[11:17] <ddaa> lifeless: sorry, no one else to blame about the tedium or registering new branches on PendingReviews
[11:17] <ddaa> lifeless: jamesh: spiv: mpool: SteveA: meeting in 43 mins
[11:35] <SteveA> hello
[11:36] <mdke> anyone?
[11:38] <Yannig> Hello everybody :)
[11:40] <Kinnison> Hi Yannig
[11:41] <SteveA> spiv, stub, jamesh: conference call tomorrow morning?
[11:41] <stub> Sure
[11:41] <jamesh> okay (I assume your morning)
[11:42] <SteveA> yes, like 0600 UTC
[11:42] <SteveA> Universal morning 
[11:44] <Kinnison> SteveA: Morning
[11:44] <Kinnison> SteveA: Can I possibly have a drive-by review of another couple of tiny bits for infinity?
[11:44] <SteveA> hello daniel!
[11:44] <Kinnison> SteveA: https://chinstrap.ubuntu.com/~dsilvers/paste/file09f7zd.html
[11:45] <SteveA> sure.  i'll get a cup of tea first, but i'll look at it shortly
[11:46] <Kinnison> Thanks
[11:49] <mdke> Kinnison: did someone ping you about dapper-updates not coming through? Not sure if you are the right person to ping, but you'll certainly know who is
[11:50] <Kinnison> mdke: Yes, that patch which you can't read should fix it
[11:50] <mdke> Kinnison: great, thanks. wanted to ask just in case
[11:59] <ddaa> lifeless: jamesh: spiv: mpool: SteveA: meeting about just now
[12:11] <lifeless> hi
[12:22] <SteveA> Kinnison: i haven't started your review yet.  no sooner had i got the tea than the bzr-launchpad meeting started
[12:22] <SteveA> i'll do it very soon
[12:23] <Kinnison> That's okay, the test suite keeps hanging
[12:23] <Kinnison> I think it's my laptop rather than the codebase
[12:25] <spiv> Kinnison: what test is it hanging on?
[12:27] <Kinnison> It fell off the top of my scrollback, sorry
[12:27] <Kinnison> If it happens again I'll let you know
[12:28] <spiv> Please do; test suite hangs are a pita that's likely to recur and affect other people or even PQM.
[12:31] <Kinnison> It's sat again
[12:32] <Kinnison> Unfortunately I think the output is being chunked instead of flushed line-by-line
[12:32] <Kinnison> so the last bit I see is the test after 15-make-team-restricted in the foaf story
[12:32] <spiv> Kinnison: ugh, yeah.  Attach gdb I guess.
[12:32] <Kinnison> Oh hang on it just moved on
[12:32] <spiv> And next time try reproducing it without the test_on_merge.py wrapper.
[12:33] <Kinnison> okay
[12:33] <spiv> (see the DebuggingWithGdb page if you're interested)
[12:33] <spiv> i.e. ./test.py -vv ...
[12:53] <lifeless> review meeting in 7 inutes
[12:55] <lifeless> review meeting in 5
[12:56] <Keybuk> hi guys
[12:56] <Keybuk> is http://bazaar.launchpad.net supposed to work inside the data centre?
[01:01] <Kinnison> spiv: read(28, "\n    test_file_construction_and_trivial_running (canonical.launchpad.ftests.test_test_pages.TestMakeStoryTest)", 4096) = 110
[01:01] <Kinnison> spiv: that was the last thing the top level test.py did before getting killed for having hung for 10 minutes
[01:03] <lifeless> reviewers meeting time.
[01:03] <spiv> Kinnison: Hmm, I doubt that's the offending test.
[01:03] <lifeless> Keybuk: dunno. If it doesn't, I think that is not so good, and it should
[01:04] <spiv> Kinnison: try test.py directly :/
[01:04] <Keybuk> lifeless: it returns 404s inside the data centre, despite appearing to be the same machine
[01:04] <lifeless>  * Roll call
[01:04] <lifeless>  * Agenda
[01:04] <lifeless>  * Next meeting
[01:04] <lifeless>  * Queue status.
[01:04] <lifeless> Keybuk: bizarre
[01:04] <lifeless> Keybuk: file a bug on launchpad-bazaar ?
[01:04] <lifeless> reviwers, please name thyself
[01:04] <SteveA> hi
[01:04] <spiv> spiv
[01:04] <Keybuk> lifeless: ok, I'm having e-mail problems at the moment, so will probably just grab people all day first :p
[01:05] <jamesh> hi] 
[01:05] <lifeless> BjornT_: ?
[01:05] <BjornT_> hi, i'm here
[01:05] <lifeless> cool
[01:05] <salgado> hey, I'm here this week!
[01:05] <lifeless> woo!
[01:05] <Kinnison> spiv: underway
[01:05] <lifeless> ok
[01:05] <lifeless> next meeting time
[01:05] <lifeless> 20060612 at 1100 UTC ?
[01:06] <spiv> Assuming that's exactly one week's time, sure ;)
[01:06] <lifeless> its 6 minutes less than one weeks time
[01:06] <spiv> I can cope with that.
[01:07] <lifeless> ok
[01:07] <lifeless> queue status
[01:07] <lifeless> ignoring ddaa's broken branch...
[01:07] <lifeless> BjornT_: jamesh - it looks like you didn't get to reviews on friday ?
[01:07] <jamesh> lifeless: yeah.  I'm just finishing off ddaa's review and will mail it shortly
[01:08] <salgado> lifeless, ddaa's broken branch is the one that's on my queue?
[01:08] <lifeless> yeah - the date is whack, but the branch is fine
[01:08] <salgado> right. I'll review it today
[01:08] <BjornT_> lifeless: right, i forgot to do it on friday. i already reviewed the branch today, though.
[01:08] <lifeless> BjornT_: thats good.
[01:09] <lifeless> so, 2 open at 4 days, is better than 3@5.
[01:09] <lifeless> but I think we can do better. Do you both check for reviews daily ?
[01:09] <lifeless> (is it on your 'I must do this once today list' ?)
[01:09] <SteveA> anyone had any pre-implementation review calls?
[01:10] <jamesh> I did one with mpt last week and mailed a summary to launchpad-reviews
[01:10] <lifeless> how did it go ?
[01:10] <SteveA> i missed seeing that.  thanks, i'll look
[01:10] <jamesh> I think it was quite useful
[01:10] <lifeless> what was your feeling about it ?
[01:11] <jamesh> we touched on a few issues that mpt hadn't thought of, which may have come up in review afterwards
[01:11] <SteveA> i see
[01:11] <jamesh> (about which cases the subjects for bug comments could be thrown away entirely)
[01:11] <SteveA> yeah, looks like mpt should request some data from stub
[01:11] <malcc> As a J. Random Launchpad developer, I found the window into what people were doing and what they were thinking about it very useful
[01:11] <SteveA> so eyeball subjects of comments
[01:12] <SteveA> hi malcolm
[01:12] <SteveA> malcc: do you have any tasks coming up that could use a pre-implementation call?
[01:13] <SteveA> perhaps some bugs to fix or tests to write or something?
[01:13] <malcc> SteveA: Nothing which really fits the bill without stretching, but if you fancy trying a call out, I could stretch some things in that direction
[01:14] <lifeless> ok
[01:14] <lifeless> back to the queue
[01:14] <SteveA> i'd much rather we err on the side of too many calls than too few
[01:14] <lifeless> I've assigned the new branches from the weekend
[01:15] <lifeless> can you please put a bit of effort in today and catch up, the needs-review queue is getting a little large
[01:15] <lifeless> there are a *lot* of branches that pending-merges thinks are merged.
[01:15] <lifeless> I'm going to send an email about that to launchpad
[01:16] <lifeless> one last thing, then any other business.
[01:16] <lifeless> Please be sure to say 'this review took X minutes' when you send a review to the list
[01:17] <lifeless> I will start nagging about this daily, as it has not been done consistently over the last week.
[01:17] <lifeless> this is important to get a feel for the time commitment being a reviewer requires.
[01:18] <lifeless> please dont worry about whether its a 'small' or 'large' amount of time - take the time you need to do the review.
[01:18] <lifeless> is that ok ?
[01:19] <salgado> sure
[01:19] <spiv> yep
[01:19] <jamesh> okay
[01:19] <BjornT_> sounds good.
[01:20] <lifeless> ok. Any new business ?
[01:20] <SteveA> spiv, stub, jamesh: conf call at 0700 tomorrow?  (one hour later than I said earlier) 
[01:20] <jamesh> SteveA: okay
[01:20] <lifeless> SteveA: thats new business ?
[01:21] <lifeless> meeting ends in 5
[01:21] <SteveA> lifeless: new business: i mailed the launchpad list asking everyone to do one pre-review call this week
[01:21] <lifeless> ah
[01:21] <SteveA> even if it is trival, i want to get everyone to experience this
[01:21] <SteveA> get the snowball rolling
[01:21] <lifeless> SteveA: thanks, I think that is a great idea.
[01:21] <SteveA> so that soon it will become a rotating ball of icy doom
[01:22] <spiv> SteveA: I'll check...
[01:22] <lifeless> meeting ends in 5
[01:22] <lifeless> 4
[01:22] <lifeless> 3
[01:23] <lifeless> 2
[01:23] <lifeless> partridge
[01:23] <lifeless> 0
[01:23] <lifeless> [01:23] <spiv> SteveA: I can do that, but not much later.
[01:23] <SteveA> spiv: okay, thanks.
[01:24] <SteveA> thanks for running the meeting lifeless 
[01:25] <lifeless> SteveA: np :)
[01:25] <lifeless> SteveA: it kinda goes with running the review process
[01:26] <SteveA> jamesh: is the pending-reviews script still running?
[01:36] <salgado> stub, around?
[01:38] <spiv> SteveA: still running -- see https://chinstrap.ubuntu.com/~jamesh/pending-reviews.new/log
[01:41] <SteveA> i didn't realize there was a log! cool
[01:44] <Znarl> stub : Ping?
[01:45] <Znarl> stub : Launchpad production logs have reached over 1gig.
[01:47] <salgado> hey spiv. have some time for some more twisted questions?
[01:49] <Kinnison> spiv: without the test_on_merge wrapper the tests run through to completion
[01:50] <Kinnison> spiv: Admittedly they take 45 minutes on this machine, but that's my own lack of RAM biting me in the arse
[01:52] <Yannig> I have another dumb question :D
[01:52] <Yannig> I see that green bars represent "Translation unchanged since last synchronized". How often is it synchronized?
[01:53] <Yannig> (just for my information :))
[01:54] <lifeless> Znarl: whats your lp account name ?
[01:54] <carlos> Yannig: hi
[01:55] <Znarl> lifeless : Karl-Tilbury
[01:55] <carlos> Yannig: it depends, for Ubuntu, I should implement something that notes when we did a new language pack export
[01:55] <carlos> for products, it means when upstream authors import a new set of .pot and .po files that include those translations done in Rosetta
[01:55] <lifeless> ahha!
[01:56] <lifeless> Znarl: thanks
[01:56] <carlos> Yannig: for ubuntu it happens with new packages uploads, but it's only valid until release time
[01:56] <Znarl> lifeless : Why do you ask? 
[01:57] <lifeless> Znarl: so I could attach you to a bug
[01:57] <lifeless> keybuk should be chatting to you now
[01:57] <lifeless> there is something that may be lp related, or may be dc-server-config related
[01:57] <Yannig> carlos> Thanks :)
[01:58] <Znarl> lifeless : Yes, trying to work out why now.
[01:58] <Yannig> Almost no green for Occitan, that's why :)
[01:58] <lifeless> cool
[01:58] <carlos> Yannig: ;-)
[01:58] <Yannig> (and still no news for ubuntu-oc-l10n@lists.ubuntu.com :-()
[01:58] <carlos> Yannig: are you sending your translations to upstream? GNOME, KDE, Debian, etc...
[01:58] <carlos> Yannig: you should do that
[01:58] <Yannig> I hope nobody will try and write it :(
[01:59] <carlos> so other distributions could reuse your translations
[01:59] <Yannig> carlos> I translate online (in Rosetta) and I sometimes upload po files
[01:59] <Yannig> Isn't it the same?
[01:59] <stub> salgado: pong
[01:59] <carlos> Yannig: upload files into Rosetta? yes, is the same for Rosetta
[02:00] <stub> Znarl: ok
[02:00] <carlos> Yannig: but you should contact GNOME, KDE and other projects that you are translating in Rosetta
[02:00] <carlos> so they get your translations 
[02:00] <Yannig> OK, I'll do it
[02:00] <carlos> and, with their next release, those translations end in Fedora, Debian, RedHat, SuSE, etc....
[02:01] <Yannig> 2,15% translated, I may wait a little while for this :)
[02:01] <LarstiQ> Yannig: you might get some help when you contact more people
[02:02] <Yannig> LarstiQ> I tried but no news for now (and as long as ubuntu-oc-l10n@lists.ubuntu.com does not exist, the contact address I used in my translations will return errors to the interested people :()
[02:03] <carlos> Yannig: if you start creating the Occitan team upstrea, you would prevent any other people start working on the same thing without reusing your work
[02:04] <Yannig> carlos> Another team than https://launchpad.net/people/ubuntu-l10n-oc ?
[02:04] <Yannig> Sorry, I don't really understand how all that works behind the scene :(
[02:04] <carlos> Yannig: I'm talking about being at: http://developer.gnome.org/projects/gtp/teams.html
[02:04] <carlos> Yannig: rosetta and launchpad are Ubuntu specific
[02:05] <carlos> so your work is used only with Ubuntu
[02:05] <carlos> perhaps in the future would be used by other projects/distributions, but it's not that way at,
[02:05] <carlos> atm
[02:05] <carlos> Yannig: in fact, I already see an Occitan team in GNOME
[02:05] <carlos> you should try to coordinate with them
[02:06] <lifeless> jamesh: might like to rerun pending-reviews now that some have been deleted
[02:06] <Yannig> Well, it's a single-translator team, just as here :(
[02:07] <carlos> Yannig: join your efforts!
[02:07] <carlos> :-D
[02:08] <Yannig> We'll try :)
[02:08] <sivang> re all, my network is back
[02:08] <stub> ddaa: How often can we expect bzrsyncd to be chewing resources like it currently is on gandwana?
[02:11] <sivang> salgado: thanks for confirming #48342 , I was afraid there is something hidden which I don't see that rationales this behavior.
[02:11] <sivang> hrm, malone #48342
[02:11] <Ubugtu> Malone bug 48342 in launchpad "Team membership should state an indirect membership instead of just "you are not a mamber of this team."" [Minor,Confirmed]  http://launchpad.net/bugs/48342
[02:12] <ddaa> stub: never
[02:12] <ddaa> there's at least two bugs at work
[02:12] <ddaa> one having to do with lockfile stuff not working
[02:13] <ddaa> the other having to do with branch-scanner getting that busy
[02:13] <stub> ddaa: Do we know what they are? I will need to shutdown the appservers on that box if it isn't fixable now, as at the moment 50% of our requests will be going really slow
[02:13] <Znarl> stub : gandwana Launchpad XMLRPC Apps Server 1/2 2/2 and Apps server 1/2 down.
[02:13] <ddaa> stub: no fucking clue what they are
[02:13] <stub> Znarl: Ta.
[02:14] <stub> Znarl, SteveA: I'm going to leave the appservers running on Gandwana down until we can resolve the bzrsyncd issue
[02:14] <ddaa> besides, I'm packing up for a suprise trip to london
[02:14] <sivang> surprise trip? :)
[02:15] <stub> Znarl, SteveA: Having them running when things go wonky will do more harm than good.
[02:24] <stub> salgado: I fixed the shipit report bug on production and reran so the reports will be there. I didn't commit the fix though because I don't have tests ;)
[02:24] <ddaa> stub: okay... found the problem...
[02:24] <ddaa> actually, known problem
[02:24] <ddaa> just did not know it was _that_ serious
[02:25] <salgado> stub, that's fine. thank you very much. I'll write a fix with a test for it today
[02:25] <stub> ddaa: Is there anything we can do to the production system to make sure it can't be triggered, or shall we just leave the appservers on gandwana off until we can deal with the issue properly?
[02:26] <ddaa> yes there is
[02:26] <salgado> stub, btw, would it be possible to give mawson a new dump of the production db?
[02:26] <ddaa> stub: we need to rm -rf away the branches on vostok that cause the CorruptRepository exception
[02:27] <ddaa> stub: if you look in the old bzrsyncd logs, I believe there was a couple of runs where bzrsyncd completed and gave us information for all those branches, there are like 2 or 3 of them.
[02:27] <stub> ddaa: Sounds like something you need to do. We can afford to leave the appservers down for a bit if you haven't time to do it now.
[02:28] <ddaa> stub: I do not quite have the time to dig into it now
[02:29] <stub> ddaa: ok. no probs. I've already sent out a  status notification.
[02:30] <stub> salgado: What is this for? If it is for examining data we might need to get you access to the staging database instead.
[02:31] <salgado> stub, no, it's for testing the mirror prober. I need recent publishing records to test it properly
[02:31] <stub> Yup
[02:32] <stub> salgado: We need to work out what to do re: Bug 5812
[02:32] <cprov> salgado: go for staging, the launchpad_dogfood DB will be compromised for a while with open edgy issues
[02:34] <salgado> cprov, well, I can't simply "go for staging"
[02:34] <cprov> salgado: carlos access staging from mawson
[02:34] <salgado> ahhhh, you mean just accessing staging's db from mawson?
[02:35] <carlos> cprov: yeah, but seems like stuart gave access only to some people 
[02:35] <cprov> salgado: yes, you have DB changes, how far are they from production ? 
[02:35] <salgado> that should be fine
[02:35] <carlos> cprov: also my access from mawson is in ro
[02:35] <cprov> carlos: he can give access to Mr. salgado as well ;)
[02:35] <carlos> cprov: I have write access from asuka
[02:35] <salgado> I'd need rw
[02:36] <stub> salgado: What PostgreSQL users do you need to connect as?
[02:36] <carlos> cprov: sure, I was just pointing that, by default, I don't think salgado has such rights
[02:36] <cprov> carlos: sure, probably not.
[02:37] <stub> salgado: The database is killed and rebuilt everyday. Will this cause a problem with testing? Otherwise you can just run another instance on mawson.
[02:37] <salgado> stub, distributionmirror
[02:37] <salgado> stub, no, the database being rebuilt every day is not a problem
[02:47] <lifeless> carlos: you should find a reviewer yourself if it is urgent
[02:47] <carlos> lifeless: ok
[02:48] <carlos> Is there anyone that has some time to do a fast review? it's not completely trivial but the amount of changes is small
[02:48] <carlos> https://chinstrap.ubuntu.com/~dsilvers/paste/file7w9yS8.html
[02:49] <carlos> the DB patch is already approved by Stuart
[03:09] <carlos> later
[03:16] <Znarl> stub : gandwana Apps servers all still down, just reminding you.
[03:16] <kiko> good morning
[03:17] <kiko> carlos, I'll take a look.
[03:21] <SteveA> Kinnison: reviewed
[03:22] <kiko> bradb, are you around already?
[03:22] <Kinnison> SteveA: thanks, the 'a' was me being crap, I'll expand it
[03:22] <bradb> kiko: hi
[03:22] <kiko> bradb, I need some help with a Snapshot change that I need to make
[03:22] <kiko> do you have some minutes to over it with me?
[03:23] <bradb> kiko: sure
[03:24] <kiko> bradb, give me 5m
[03:24] <bradb> no prob
[03:29] <salgado> hey kiko. do you have write access on staging?
[03:29] <kiko> salgado, to the instance or to the db?
[03:29] <salgado> the db
[03:29] <kiko> no!
[03:30] <salgado> :-(
[03:31] <salgado> does anybody (apart from sub, who left already) has write access to staging's db?
[03:32] <SteveA> salgado: i might do
[03:33] <salgado> SteveA, would you run a script to create some distribution mirrors there for me? I need to test it against fresh publishing records, so I can't use dogfood (which is old and can't be updated right now)
[03:33] <SteveA> salgado: i can su to launchpad.  what do i need to do?
[03:41] <stub> Znarl: Check your email. They will be down until we fix a bug in bzrsyncd or it becomes a problem and we disable bzrsyncd instead, so you will want to switch off that alert.
[03:46] <Znarl> stub : Sorry, don't have great email access in the data centre.  I'll disable these alerts.
[03:47] <stub> ok ;)
[04:19] <kiko> bradb!
[04:20] <kiko> bradb, so the problem I have is with mailnotifications.py
[04:20] <kiko> can you look at the code with me for a moment?
[04:20] <SteveA> hey bradb 
[04:20] <kiko> hey SteveA 
[04:20] <bradb> kiko: ok...
[04:20] <bradb> SteveA: hey
[04:21] <SteveA> i've asked everyone to have a voice call with a review this week
[04:21] <SteveA> doesn't matter what it is about exactly
[04:21] <SteveA> so long as it is some code you're working on
[04:22] <kiko> SteveA, bradb and I can have a call about DRM
[04:22] <SteveA> D.R.M. ?
[04:22] <SteveA> CDs that don't play?
[04:22] <bradb> heh
[04:22] <kiko> right
[04:22] <kiko> malone and multimedia
[04:31] <ploum> hey
[04:31] <ploum> is the "post-a-comment-with-same-content-when-posting-a-bug" bug already known ?
[04:32] <mdke> elmo: around?
[04:32] <salgado> kiko, https://staging.launchpad.net/distros/ubuntu/+archivemirrors
[04:34] <kiko> salgado, nice
[04:34] <kiko> any clue why -40 and -42 still have unknowns?
[04:34] <salgado> I'll check the log file in a few minutes to see what happened there
[04:36] <kiko> good work
[04:37] <carlos> kiko: ok, thanks
[04:37] <bradb> ploum: What do you mean?
[04:38] <ploum> bradb: often, when you post a new bug, a comment with the content of your bug is automatically added
[04:38] <ploum> I've seen it once for me
[04:39] <bradb> ploum: It's always added.
[04:39] <ploum> and now it seems that it happens regulary
[04:39] <cprov> sorry, my wireless connection was dropped, blame  http://www.mikrotik.com/, I wonder when we will have uBuntu (micro-Buntu) available 
[04:39] <mdke> ploum: the top one is the bug description
[04:39] <bradb> ploum: The bug description and the first bug comment are initially identical, but the description can later be edited.
[04:39] <ploum> oh 
[04:39] <ploum> so it's a "feature" !
[04:39] <bradb> If they are identical, only the description is shown.
[04:40] <bradb> ploum: Yeah. That way you can mangle the description, but you'll never lose the original bug report.
[04:40] <ploum> insightful
[04:40] <ploum> that's why I sometime see it and sometime not
[04:40] <ploum> tought it was a bug
[04:40] <ploum> sorry
[04:40] <bradb> There are perhaps better ways to deal with it, like hiding that first comment by default and allowing the user to expose it.
[04:41] <malcc> That's why some bugs have comments saying "I tried to edit this bug but I seem to have accidentally posted a duplicate comment".
[04:41] <bradb> "The description has been modified since the original report. _View the original report_."
[04:42] <kiko> stub, ping?
[04:42] <ploum> indeed, the UI is not perfect because lot of people will think that there is a bug
[04:42] <ploum> (I hope I'm not the only one ;-) )
[04:43] <bradb> others have brought this up. I'm going to email our UI guy with an idea for addressing the problem. ploum, do you an example URL, btw?
[04:43] <ploum> bradb: https://launchpad.net/distros/ubuntu/+bug/48521  this one
[04:43] <Ubugtu> Malone bug 48521 in Ubuntu "Can not activate nvidia-setings panel with nvidia-glx installed" [Normal,Unconfirmed]  
[04:44] <bradb> right, thanks
[04:44] <BjornT> bradb: i think some malone spec addresses this problem, can't remember which one, though.
[04:49] <kiko> stub, ping?
[04:53] <bradb> BjornT: Hm, I can't find one unfortunately.
[04:54] <kiko> has anyone seen test failures in sqlbase.quote?
[04:54] <kiko> and sqlvalues?
[04:54] <kiko> stub?
[04:55] <BjornT> bradb: ah, it was BugHistory which mentions it briefly.
[04:56] <jmspeex> How do I get this -- https://launchpad.net/products/speex -- fixed with vaguely correct info?
[04:56] <salgado> Znarl, around?
[04:56] <jmspeex> (I'm the maintainer)
[04:58] <kiko> jmspeex, can I reassign that product to you?
[04:58] <kiko> that way you can fix it up yourself
[04:58] <jmspeex> yes
[04:58] <kiko> if so, what is your launchpad username?
[04:58] <jmspeex> jmspeex
[04:59] <BjornT> kiko: stub did some changes regarding quoting, i think. make sure that your sqlobject branch is up to date, and that you have merged in rf recently into your branch.
[04:59] <bradb> BjornT: Ah, right. It has the same idea of showing/hiding the original comment, though integrating that idea in bug history would indeed be sweeter.
[04:59] <kiko> BjornT, ah, ok.
[04:59] <kiko> thanks.
[04:59] <kiko> jmspeex, done.
[05:02] <jmspeex> kiko: thanks. Where do I change the cvs info (Speex doesn't use a CVS anymore)
[05:04] <kiko> jmspeex, the cvs info is attached to a specific series
[05:04] <kiko> so you need to visit the "main" link
[05:05] <kiko> and then "Edit Source"
[05:09] <jmspeex> kiko: what are series?
[05:09] <stub> kiko: Wot he said
[05:10] <kiko> thanks stub 
[05:10] <kiko> jmspeex, product release series are Launchpad's name for a group or related releases
[05:10] <jmspeex> "Sorry, you don't have permission to access this page."
[05:10] <kiko> jmspeex, hmmm. that could be a bug. matsubara can you check?
[05:10] <jmspeex> kiko: You mean like a branch?
[05:10] <kiko> jmspeex, so if linux can be an example, the 2.4 series had a number of releases, including 2.4.10 and 2.4.11.
[05:11] <kiko> jmspeex, yes, that's the general idea.
[05:11] <kiko> jmspeex, I can update your details for you if you like
[05:11] <jmspeex> kiko: in the case of Linux, what would you do with 2.5.x (assuming people use it)
[05:12] <kiko> jmspeex, it would be another series.
[05:12] <kiko> for 2.6 it is more complicated
[05:12] <jmspeex> Speex has an old, stable, 1.0.x branch and a 1.1.x unstable branch. Most people actually use 1.1.x now.
[05:13] <kiko> jmspeex, was 1.0 CVS-hosted?
[05:13] <jmspeex> trunk is svn http://svn.xiph.org/trunk/speex/
[05:13] <kiko> or did you move everything over?
[05:13] <matsubara> kiko: what page is jmspeex trying to access?
[05:13] <kiko> matsubara, https://launchpad.net/products/speex/main/+source
[05:13] <jmspeex> kiko: It got converted to svn. I don't think xiph still has the cvs.
[05:13] <kiko> jmspeex, understood.
[05:14] <jmspeex> OK, off to bed. Will check that tomorrow. Email me if needed.
[05:14] <kiko> jmspeex, do you want 1.0 listed as well? there doesn't seem to be a 1.0 branch on svn.xiph.org
[05:15] <matsubara> jmspeex, kiko: bug 31294
[05:15] <Ubugtu> Malone bug 31294 in launchpad "product registrant should be able to modify product series details" [Normal,Confirmed]  http://launchpad.net/bugs/31294
[05:15] <jmspeex> kiko: http://svn.xiph.org/branches/rel-1-0-branch/speex/
[05:15] <kiko> jmspeex, thanks. will update!
[05:16] <jmspeex> kiko: You might as well list me for bugs...
[05:16] <kiko> jmspeex, you are by default the bug contact.
[05:16] <kiko> bradb, we'd do well to make that clear in the UI, btw..
[05:17] <jmspeex> Ok, bed time. g'night (or morning, or whatever!)
[05:17] <bradb> kiko: indeed
[05:17] <kiko> night
[05:17] <BjornT> SteveA: ping
[05:18] <SteveA> hi bjorn
[05:18] <BjornT> SteveA: hi. would you have time for a pre-implementation phone call re bug 32282?
[05:18] <Ubugtu> Malone bug 32282 in malone "Try to reduce of the amount of LONG comments" [Normal,In progress]  http://launchpad.net/bugs/32282
[05:19] <kiko> BjornT, I am available if you like
[05:19] <SteveA> BjornT: i do later today, but maybe kiko is a better choice
[05:21] <BjornT> kiko: ok, thanks. skype or normal phone call?
[05:21] <kiko> BjornT, either is fine if you pre-book, skype needs some lovin to actually work for me
[05:22] <jordi> hey duds
[05:22] <jordi> carlos: you marked my "further filtering" bug as In Progress. Thanks!
[05:23] <carlos> jordi: I did already the first part
[05:23] <BjornT> kiko: ok, maybe normal phone is better then. can you call me?
[05:23] <carlos> jordi: to select between distro and product entries
[05:23] <jordi> that helps a lot already
[05:23] <carlos> it should land this week, if stub does a usual production update
[05:23] <jordi> too bad the queue is emptyish now :P
[05:23] <carlos> jordi: look at staging
[05:23] <jordi> ok
[05:23] <kiko> BjornT, sure thing. 10m to read up the thread?
[05:24] <carlos> jordi: don't worry, edgy will bring us a bunch of entries....
[05:24] <carlos> jordi: ;-)
[05:24] <jordi> carlos: I had a brief look at those product lists
[05:24] <jordi> ick :)
[05:24] <BjornT> kiko: sounds good.
[05:24] <jordi> and it's not as bad as I imagined, but it made me think about the "Rosetta" and "Malone" bits.
[05:25] <carlos> jordi: well, there are a lot of products that shouldn't have a .pot file
[05:25] <jordi> carlos: with what we have in rosetta right now, probably all of the products with templatyes should be "official", right?
[05:25] <carlos> imported
[05:25] <jordi> carlos: I know, but not as many as I feared
[05:26] <carlos> jordi: yeah, I guess we could set that flag automatically
[05:26] <kiko> BjornT, can you tell me of a subject line so I can find this mail in the mailing list?
[05:26] <bradb> kiko: I updated bug 28823, admittedly first being stumped by why we don't have such a default on the distro side.
[05:26] <Ubugtu> Malone bug 28823 in malone "It's hard to figure out who the product/package/distribution bug contacts are" [Normal,Confirmed]  http://launchpad.net/bugs/28823
[05:26] <BjornT> kiko: Malone quickfixes for distro
[05:28] <jordi> carlos: I guess there'll be GNOME products with templates in the future which won't "use rosetta officially"
[05:29] <carlos> jordi: right
[05:29] <jordi> then, tere's this dude in the mailing list asking for "groups of sources" in the translation lists: ie, this is kubuntu, this is ubuntu, etc.
[05:29] <jordi> I think I'm missing that too
[05:30] <carlos> jordi: that's already planned
[05:30] <carlos> the priority thing was the first step in that direction
[05:30] <jordi> nod
[05:30] <jordi> ok, I wasn't sure.
[05:30] <jordi> I'll reply now
[05:31] <carlos> ok
[05:35] <kiko> BjornT, ready?
[05:36] <BjornT> kiko: yeah, i'm ready.
[05:36] <kiko> -> privmsg
[06:07] <Yannig> Still no news for ubuntu-oc-l10n@lists.ubuntu.com :-(
[06:07] <Yannig> Any idea if I could ask somebody else for it?
[06:13] <kiko> Yannig, hmmm. who did you make the request to?
[06:16] <mdke> Yannig: did you email mailman@lists.ubuntu.com ?
[06:31] <carlos> Yannig: I will try to contact jdub about it tonight
[06:31] <carlos> Yannig: did you manage to talk with jdub by irc ?
[06:32] <carlos> kiko: he told me that he sent the request to several admin emails and I pointed him to jdub directly
[06:32] <kiko> I see
[06:32] <kiko> hmmmm
[06:32] <carlos> kiko: seems like either jdub didn't get any email (a problem in some place...) or he's too busy to handle that request
[06:33] <kiko> I can try and help
[06:33] <carlos> kiko: I already agreed with Znarl to ask him the mailing list if I'm not able to contact with jdub this week
[06:33] <kiko> okay, cool, well handled.
[06:34] <mdke> carlos: I think the general procedure is supposed to be emailing mailman@lists.ubuntu.com, I dunno if that makes it more likely that jdub will read it though
[06:34] <kiko> BjornT, do you feel up to doing my review?
[06:34] <carlos> mdke: Yannig told me that he did it already one or two weeks ago
[06:34] <mdke> carlos: :/
[06:36] <jordi> hmm. kiko, who's CoC signing master these days?
[06:36] <jordi> is it the great Salgado?
[06:36] <kiko> jordi, matsubara might be available to help
[06:36] <salgado> jordi, no, it is the great matsubara. :)
[06:36] <jordi> CoC signing. No matter how many times I type this, it always makes me grin...
[06:37] <jordi> ooh, EL CHINO
[06:37] <jordi> matsubara: oye amigo!
[06:37] <jordi> so the XaraLX guys ask their translators to sign a document before they can translate the app.
[06:37] <BjornT> kiko: sure
[06:37] <kiko> BjornT, yes!
[06:38] <kiko> BjornT, https://chinstrap.ubuntu.com/~dsilvers/paste/file4L47Ya.html
[06:38] <jordi> Neil is asking me if Rosetta can present some kind of doc where they can say "yes, I agree to blah blah" and enter the XaraLX teams.
[06:38] <kiko> BjornT, -> privmsg
[06:38] <carlos> jordi: hi, you should CC launchpad's mailing list in your requests to update production DB
[06:38] <jordi> Is there any plan to make this kind of custom stuff available from Launchpad, or can it be related to the CoC code?
[06:39] <carlos> jordi: that would be a good thing to be more useful for upstream projects
[06:39] <carlos> not sure about its priority....
[06:39] <jordi> carlos: *nod*. I took a sample email from you which didn't have the Cc, sorry
[06:40] <cprov> mdz: ping, did you see http://dogfood.ubuntu.com/ubuntu/dists/edgy/
[06:40] <carlos> jordi: Yeah, I wasn't adding it to the CC but since last month (or two) I'm doing it so I'm sure the request is not lost
[06:40] <carlos> jordi: don't worry
[06:40] <jordi> nod
[06:40] <jordi> ok
[06:44] <matsubara> jordi: I don't know about the plans of doing the custom stuff, but I think this is something that could use the CoC code.
[06:45] <jordi> matsubara: I can file a bug
[06:47] <matsubara> jordi: please do it. I think it's possible to generalize the CodeOfConduct spec to cover this use case, but kiko probably knows better about the future plans.
[06:48] <jordi> ok
[06:48] <jordi> carlos: for another DB update request,
[06:48] <jordi> "Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2
[06:48] <jordi> && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
[06:48] <jordi> would that go verbatim in the SQL statement?
[06:48] <jordi> this expression is pretty cool
[06:49] <carlos> jordi: not sure if we should use %%
[06:49] <carlos> send the request and ask Stuart 
[06:49] <jordi> k
[06:50] <mdz> cprov: no
[06:50] <mdz> cprov: what is it based on?
[06:51] <carlos> BjornT: around ?
[06:51] <cprov> mdz: 18th May dapper was released and edgy was initialised
[06:51] <carlos> BjornT: sorry, I found the answer ;-)
[06:52] <mdz> cprov: can we do one based on current dapper?
[06:52] <mdz> cprov: does it have chroots so that we can test uploads to edgy?
[06:58] <cprov> mdz: it'd cost sometime, chroots for edgy are in place (i386 only in dogfood buildfarm)
[06:59] <cprov> read some ___ time
[07:03] <mdz> cprov: did you talk with BenC about that kernel upload?
[07:04] <mdz> that would be an excellent test
[07:04] <mdz> cprov: is there an upload queue we can use, or do we need to send the uploads to you for processing?
[07:05] <mdz> kiko-fud: you're eating AGAIN?
[07:05] <kiko-fud> I haven't eaten yet!
[07:05] <kiko-fud> I was on fake-fud earlier
[07:06] <cprov> mdz: do you have access in mawson ?  no poppy unfortunatelly
[07:06] <mdz> cprov: I have an account
[07:06] <cprov> mdz: 'launchpad' user access as well ?
[07:07] <mdz> cprov: no
[07:08] <cprov> mdz: nevermind, best solution is to store your packages somewhere in chinstrap (or even mawson itself) I can run the upload for them 
[07:08] <mdz> cprov: the easier you can make this, the more we can help you
[07:10] <cprov> mdz: request 'launchpad' in mawson access anyway, but for now, send some packages for me, we can check something you want to test
[07:10] <mdz> cprov: do you know how to do a trivial update to a package for testing?
[07:10] <mdz> apt-get source, dch, debuild -S ?
[07:12] <cprov> mdz: yes, it's already done for some "stub", do you want me to do other ones ? say which
[07:12] <mdz> cprov: stub?
[07:12] <cprov> "fake"
[07:12] <cprov> no real sourcecode 
[07:12] <mdz> cprov: you can take any package, do that, and upload it to edgy on dogfood as a test
[07:13] <mdz> cprov: you could even write a script to do them all :-)
[07:13] <mdz> there is no time to build everything now, though
[07:13] <cprov> mdz: uhm ... maybe
[07:15] <mdz> cprov: you can upload debian-installer and publish new installer builds for degy
[07:15] <mdz> edgy
[07:16] <mdz> cprov: in the Release file, the version number is '6.1' for some reason?
[07:17] <mdz> cprov: edgy has no Contents files
[07:17] <mdz> cprov: edgy has a newer version of the ntp package than dapper for some reason
[07:17] <mdz> and scrollkeeper
[07:18] <cprov> mdz: some packages were in queue when I opened edgy
[07:18] <mdz> cprov: in the queue for dapper? or for edgy?
[07:18] <cprov> mdz: no reason for '6.1'
[07:18] <cprov> mdz: dapper, edgy didn't exist at that point ;)
[07:19] <mdz> cprov: other than those changes, edgy is the same as dapper
[07:19] <mdz> cprov: I ran compare-archive on it
[07:19] <mdz> cprov: why did the dapper uploads go into edgy?
[07:21] <cprov> mdz: looks like dapper has the newer ones 
[07:22] <cprov> mdz: there was no publication for the newer package when I 'copied' edgy, later I processed the dapper queue w/o closing it 
[07:22] <mdz> cprov: which dapper do you mean? dogfood or production?
[07:22] <cprov> mdz: this process should be more coherent using initialise-from-parent script
[07:22] <cprov> dogfood
[07:23] <mdz> cprov: edgy on mawson has a version of ntp which is neither in dogfood's dapper or in production's dapper
[07:23] <cprov> mdz: weird, which one ?
[07:23] <mdz> cprov: I guess I'm not sure how you want me to judge this, since its contents are sort of arbitrary
[07:23] <mdz>        ntp | 1:4.2.0a+stable-8.1ubuntu6 | http://archive.ubuntu.com dapper/main Sources
[07:23] <mdz>        ntp | 1:4.2.0a+stable-8.1ubuntu4 | http://dogfood.ubuntu.com edgy/main Sources
[07:24] <cprov> mdz: I don't remember of doing anything for ntp, it looks like an removed package from a.u.c
[07:24] <mdz> cprov: it is most certainly not removed
[07:25] <mdz>        ntp | 1:4.2.0a+stable-8.1ubuntu3 | http://dogfood.ubuntu.com dapper/main Packages
[07:25] <mdz> cprov: it looks like dogfood/dapper and dogfood/edgy have the same source but different versions of  the binaries
[07:25] <mdz> i.e., dogfood/dapper is not up to date
[07:26] <cprov> mdz: of course, it's not it's an 18th May DB copy ;) let's investigate the NTP issue, it may be a defect in publisher or initialise-from-parent 
[07:26] <mdz> cprov: read what I wrote above
[07:27] <mdz> cprov: dogfood/dapper has ntp  1:4.2.0a+stable-8.1ubuntu4 sources but  1:4.2.0a+stable-8.1ubuntu3 binaries
[07:27] <mdz> cprov: dogfood/edgy has  1:4.2.0a+stable-8.1ubuntu4 sources and binaries
[07:27] <mdz> what does this mean? that dapper wasn't up to date when you copied it?
[07:27] <mdz> and why didn't the dapper builds take place on dogfood to bring it up to date?
[07:28] <cprov> mdz: we didn't wait build queue to quiesce, perhaps
[07:31] <cprov> mdz: uhm ..ntp-..4 take place at 18th 23:26, and queue-builder doesn't run often in mawson
[07:32] <cprov> mdz: anyway, now dapper is released and it won't be built anymore, that's why the extra checks in initialise-from-parent needs to be executed. In fact it won't happen in production.
[07:33] <mdz> cprov: can we get an archive and db snapshot immediately before we open edgy in production?
[07:35] <cprov> mdz: sure we can, exactly after waiting build/upload queue to be empty
[07:35] <cprov> mdz: uhm .. we may have space issues in drescher
[07:35] <cprov> mdz: to copy the full archive
[07:38] <mdz> cprov: a hardlink copy would be sufficient I think
[07:38] <mdz> or it could be copied over the network elsewhere, though that could take a long time
[07:39] <cprov> mdz: a hardlink is a good idea
[07:47] <ssam> i have a program that i'd like to move to a sourceforge-like system. are there any docs about how launchpad compares?
[07:57] <mdz> cprov: mawson:/tmp/dapper-edgy.diff
[07:58] <mdz> cprov: there are no differences other than what I described above, so I it should certainly work
[07:58] <mdz> cprov: is there anything in particular you would like verified?  I will be out for a couple of hours
[07:59] <cprov> mdz:  one sec
[08:00] <cprov> mdz: even the pointed diferences might be sorted, see the builds list, new (ubuntu4) ntp was built for both, dapper and edgy:
[08:00] <cprov> https://dogfood.ubuntu.com/distros/ubuntu/+builds?build_state=built&build_text=ntp
[08:01] <mdz> cprov: I suggest doing some uploads to make sure they are accepted and built
[08:01] <cprov> mdz: No specific thing to verify, IMO
[08:01] <mdz> debian-installer and the kernel
[08:02] <cprov> mdz: okay, will do and send some result summaries, thank you 
[08:26] <jordi> carlos: any news about the ooo langpacks?
[08:26] <jordi> carlos: they haven't been released yet, right?
[08:27] <carlos> jordi: right
[08:27] <carlos> I have a meeting tomorrow with doko
[08:27] <carlos> to talk about them
[08:30] <carlos> jordi: did you finish the review of the email?
[08:33] <jordi> carlos: that's why I'm ask
[08:33] <jordi> I'm rewriting
[08:33] <jordi> asking
[08:36] <carlos> jordi: don't worry about that, just finish the email
[08:37] <jordi> it's about what tense to use
[08:37] <jordi> "will be available" or "are available" :)
[09:16] <sabdfl> mdz: give me a bit of home time and then i can call to talk through blueprint
[09:30] <jordi> carlos: I'm leaving now. As soon as I get OK, I'll fire that email to the lists.
[09:30] <carlos> jordi: ok
[09:30] <carlos> jordi: you have mine
[09:30] <jordi> k
[09:31] <jordi> kiko: ^
[09:31] <jordi> gah, why is adept stuck in the import queue again?
[09:32] <jordi> whoa
[09:32] <jordi> it seems wxWidgets is moving to rosetta
[09:32] <jordi> I'll confirm this tomorrow and import
[09:36] <carlos> jordi: cool
[09:47] <jelmer> Anyone here who is attending the bzr/hg meeting?
[09:59] <kiko> jordi, something is busted with your email headers
[09:59] <kiko> at least mutt doesn't want to include you when replying to group
[10:01] <carlos> kiko: how's going that fast review?
[10:02] <Yannig> carlos> No, I wasn't able to have jdub by irc
[10:08] <Oppy> hello all
[10:08] <Oppy> i have a question if anyone's up for answering it
[10:08] <kiko> always
[10:10] <Oppy> so on the Democracy Player project, I uploaded a .po file for Romanian days and days ago
[10:10] <Oppy> it should have replaced the incomplete romanian translation
[10:10] <Oppy> I was wondering if I had to re-submit it or something
[10:11] <carlos> Oppy: is your launchpad id bog-tom ?
[10:13] <carlos> kiko: do you know why do we get this weird filenames from Windows users? -> https://staging.launchpad.net/rosetta/imports?target=products&status=NEEDS_REVIEW&type=all
[10:15] <Oppy> no, its oppy
[10:15] <kiko> carlos, heh. not really -- perhaps we are not handling the backslash correctly?
[10:16] <Oppy> bog-tom also might have uploaded it
[10:16] <carlos> kiko: well, we should not see the c:\... part of the path, I guess the browser should not send such information...
[10:18] <carlos> Oppy: I don't see any request with the failure status set. When was the last time you uploaded it?
[10:19] <Oppy> last week
[10:20] <Oppy> thursday or friday
[10:20] <Oppy> the filename was ro.po
[10:21] <carlos> did you get a confirmation email?
[10:22] <carlos> because If it failed, I should see it in the queue with the FAILED status
[10:22] <Oppy> I didn't get a confirmation e-mail.
[10:22] <Oppy> I guess I should try it again
[10:22] <carlos> yes, please, so I can trace it
[10:22] <carlos> first of all, where are you uploading it? (The url)
[10:23] <Oppy> I just uploaded it
[10:23] <Oppy> https://launchpad.net/products/democracy/trunk/+pots/democracyplayer/+upload
[10:24] <carlos> Oppy: well, that's not the right URL, or at least, you should not use it unless you are the maintainer of the application
[10:24] <carlos> Hmm, I see you as the owner of the template, that's why you are allowed to do it
[10:25] <carlos> Oppy: dude, you uploaded the .pot file
[10:26] <carlos> I see the problem
[10:26] <carlos> Oppy: you are uploading the translation as messages.pot
[10:26] <carlos> using the URL to upload templates and/or translations
[10:26] <carlos> so we take it as a translation template and discard the translations
[10:27] <carlos> (we don't have yet implemented the translation template notification)
[10:27] <Oppy> ah
[10:27] <carlos> you need to upload it using the ro.po filename you told me
[10:27] <carlos> or even better, if you are the translator, upload it to https://launchpad.net/products/democracy/trunk/+pots/democracyplayer/ro/+upload
[10:28] <Oppy> okay
[10:28] <Oppy> I can upload it there
[10:28] <Oppy> okay, I just did
[10:28] <Oppy> thank you
[10:29] <Oppy> how long should it take to be improted?
[10:29] <carlos> Oppy: 10-15 minutes
[10:30] <carlos> Oppy: btw, could you tell me the language that bog-tom translates into?
[10:30] <carlos> the file he uploaded is not associated with any language and I don't see any clue either from the content
[10:30] <carlos> http://librarian.launchpad.net/3009888/C%3A%5CDocuments%20and%20Settings%5Cbtoma%5CDesktop%5Cdefault.po
[10:31] <kiko> looks like it's romanian
[10:31] <Oppy> yeah, he does romanian
[10:32] <Oppy> I think he got a little antsy after I uploaded the file the wrong way and tried to do it himself
[10:32] <carlos> Oppy: should I link it with Romanian?
[10:33] <carlos> or just discard it if you already did the upload request?
[10:33] <Oppy> if it's the same, then you can just discard it
[10:33] <Oppy> I don't think he's made any changes since
[10:34] <Oppy> or you can discard my upload and use his instead
[10:34] <Oppy> whatever is more convenient for you
[10:36] <carlos> Oppy: I discarded yours and approved the other
[10:36] <carlos> so you will not get the confirmation email 
[10:37] <Oppy> that's fine
[10:37] <Oppy> I see the changes on the main page
[10:37] <Oppy> thank you
[10:37] <carlos> Oppy: the import is done now
[10:37] <carlos> you are welcome
[10:40] <Oppy> i have one more dumb question
[10:40] <Oppy> I'm trying to change the maintainer of the product to my team
[10:40] <Oppy> and I don't have permission for some reason
[10:40] <Oppy> despite being the admin of the product
[10:42] <carlos> Oppy: it's a know bug
[10:42] <carlos> you will need a launchpad admin that do it for you
[10:42] <Oppy> oh
[10:42] <Oppy> could you do it?
[10:42] <carlos> Oppy: like kiko, SteveA, lifeless or stub
[10:42] <carlos> Oppy: I don't have such permissions either
[10:42] <Oppy> ah
[10:42] <Oppy> kiko, you still around?
[10:43] <kiko> sure
[10:43] <kiko> what product?
[10:43] <Oppy> cemocracy
[10:43] <Oppy> *democracy
[10:43] <Oppy> change the maintainer to pcf
[10:47] <kiko> Oppy, done, I think
[10:49] <Oppy> let me check
[10:49] <Oppy> it looks good
[10:49] <Oppy> thank you
[10:57] <kiko> BjornT, my landing landed! yes!
[11:09] <Yannig> Three members in the Occitan translation team :)*
[11:10] <mdke> Yannig: you might be interested in #ubuntu-translators
[11:11] <WINBALL> :)
[11:28] <Yannig> mdke> Yes, I might :)
[11:29] <Yannig> Thannks, I didn't know about it :(
[11:51] <jordi> kiko: oh you're not the only one that tells me this
[11:51] <jordi> can you identify what it is?
[11:51] <kiko> hmmm, not sure.
[11:51] <kiko> When it's already last-minute, no need to say it's also unplanned!
[11:51] <kiko> perhaps?
[11:51] <jordi> no, the header t hing
[11:52] <kiko> jordi, let me take a look.
[11:53] <kiko> Mail-Followup-To:
[11:53] <kiko> jordi, that's the fucker
[11:53] <jordi> wtf
[11:53] <kiko> who is adding that header?
[11:53] <jordi> not sure
[11:53] <jordi> mutt I guess
[11:53] <jordi> but why?
[11:55] <jordi> yes, it's mutt
[11:55] <jordi> my sent-mail copy has it
[12:00] <jordi> I don't see anything in my muttrc
[12:04] <jordi> carlos, kiko: sent
[12:04] <kiko> jordi, set followup_to=no