[12:31] <mpt> Gooooooooooooooooooood morning Launchpadders!
[01:40] <Ubugtu> New bug: #58408 in blueprint "Can't associate a branch with a specification" [Untriaged,Unconfirmed]  http://launchpad.net/bugs/58408
[03:20] <Ubugtu> New bug: #58410 in malone ""Subscribe Someone Else" should be restricted to drivers of relevant software" [Untriaged,Unconfirmed]  http://launchpad.net/bugs/58410
[03:22] <lifeless> err
[03:22] <lifeless> that seems excessively restrictived
[03:23] <mpt> Well, it wasn't my first choice
[03:25] <mpt> and it probably would be worse than the status quo, actually
[03:59] <somerville32> What is the date format for Launchpad?
[03:59] <somerville32> ie: What is 2006-06-07?
[04:02] <crimsun> ISO date
[04:02] <crimsun> year month day
[04:06] <mpool> hello
[04:06] <mpool> is staging down at the moment?
[04:19] <jamesh> mpool: it seems to be down at the moment, lifeless can probably kick it
[04:19] <mpool> i don't really care
[04:19] <mpool> i just wasn't clear if it was generally expected to be up or not?
[04:20] <jamesh> it is supposed to come up automatically again, but often it doesn't (which is a problem)
[04:28] <somerville32> I made a mistake in a bugreport. 
[04:28] <somerville32> https://launchpad.net/products/xfdesktop/+bug/48924
[04:28] <Ubugtu> Malone bug 48924 in xfwm4 "Icons on desktop (single click and resizing)" [Unknown,Unknown]  
[04:29] <somerville32> I added a package from upstream to the effected list thinger but made a mistake and picked the wrong one for one of them
[04:29] <somerville32> I'd like to change xfwm4 (upstream) to xfdesktop (upstream).
[04:30] <jamesh> click on "xfwm4 (upstream)" and change the package name
[04:30] <somerville32> We can't
[04:30] <somerville32> And there isn't a package name, just a product name :P
[04:30] <jamesh> ah.
[04:31] <jamesh> you won't be able to change it to xfdesktop anyway, since you've already got an xfdesktop task
[04:31] <somerville32> Ok
[04:31] <somerville32> What should I do then?
[04:31] <jamesh> I'd probably leave it as is
[04:31] <somerville32> The bug report has a wishlist item AND an actual bug report in one and hence there is two corresponding bug reports upstream for the same product.
[04:32] <somerville32> Ok
[04:32] <jamesh> probably would've been better to split it out into a separate bug report
[04:34] <somerville32> Can you remove the xfwm4 task and I'll remove the wishlist item since that task is for the wishlist upstream?
[04:34] <somerville32> Then I'll file the wishlist item as another bug report.
[04:36] <jamesh> I can't remove it, but if you remove the bug watch from the task, you can reject it
[04:36] <jamesh> or you could just leave it as is
[04:37] <somerville32> Do I just change the remote watch to none?
[04:37] <jamesh> yep
[06:11] <Burgundavia> jamesh: are you looking at allowing multiple files to be attached to a bug report in a single click? If so, please look at how gmail does it.
[06:36] <jamesh> Burgundavia: I agree that it's nice.  Not sure exactly how we'd implement it.
[06:37] <Burgundavia> yep, is trick
[06:37] <Burgundavia> tricky, rather
[06:37] <jamesh> mpt: I added SMTP auth properly to my branch of pqm-submit
[06:41] <mpt> jamesh, I saw that, thank you
[07:02] <jamesh> mpt: would you be able to sort out the bug page issue with kiko?
[07:02] <mpt> jamesh, I hope so
[07:03] <mpt> It's not often the problem is too much action, not enough talk, but this might be such an occasion
[08:08] <lifeless> jamesh: is staging ok ?
[08:08] <lifeless> jamesh: do you need me to bounce it ?
[08:12] <jamesh> lifeless: seems to be okay now.  mpool was asking about it earlier
[08:12] <lifeless> mpool: staging looks ok to me
[08:26] <jamesh> lifeless: I've put together a branch to remove the cache code from product-release-finder.  Do you think it's worth waiting til we do another run before looking at merging this?
[08:27] <lifeless> yeah
[08:27] <lifeless> or rather, I dont think its related
[08:27] <lifeless> functional vs quality changes
[08:29] <jamesh> diffstat says 12 files changed, 17 insertions(+), 194 deletions(-)
[08:53] <carlos> morning
[08:54] <mpt> hi carlos 
[09:33] <carlos> jamesh: hi, around?
[09:34] <jamesh> carlos: yeah
[09:34] <carlos> jamesh: did you started with my branch review?
[09:34] <jamesh> carlos: nope.  Didn't notice that it was in my queue
[09:35] <jamesh> (looks like it was added about an hour ago)
[09:35] <carlos> ok, perfect, I just added some extra code there and wanted to be sure that you don't miss it
[09:35] <jamesh> I'll wait til the next pending-reviews run completes then
[09:35] <carlos> I'm pushing my changes atm
[09:35] <carlos> ok
[09:35] <carlos> thanks
[09:36] <ddaa> mpool: ping
[10:50] <Ubugtu> New bug: #58447 in launchpad "There's no field in the bug report page to enter distribution release or arch." [Untriaged,Unconfirmed]  http://launchpad.net/bugs/58447
[11:17] <ddaa> bug 58369
[11:17] <Ubugtu> Malone bug 58369 in launchpad "ContextWidget should return the actual context object, not its id." [Untriaged,Confirmed]  http://launchpad.net/bugs/58369
[11:27] <sivang> morning
[11:30] <malcc> spiv: Ping
[11:31] <spiv> malcc: pong!
[11:31] <malcc> spiv: Do you remember, way back in the mists of time, offering to discuss Soyuz testing with me?
[11:32] <spiv> Yes :)
[11:33] <malcc> When's good for you?
[11:33] <spiv> Probably about 20-25 minutes time, I have some food about to pop out of the oven.
[11:33] <spiv> How's that suit you?
[11:34] <malcc> That's ideal
[11:34] <spiv> Excellent.
[11:54] <lifeless> mmm, soyuz testing
[12:02] <spiv> malcc: so, I've eaten.
[12:02] <malcc> spiv: Cool. My only VOIP at the mo is skype, where I'm malcolmcleaton
[12:03] <malcc> spiv: Ekiga remains a mystery
[12:03] <spiv> Ok, I'll fire up skype.
[12:04] <lifeless> malcc: I thought you got good ekiga once ?
[12:05] <malcc> lifeless: Yes, from the hotel at the sprint last week
[12:05] <malcc> lifeless: Now it's moved on to a whole different set of errors
[12:05] <spiv> malcc: skype is giving me "Reason unknown"
[12:06] <spiv> Hmm, apparently the problem is on my end.
[12:07] <malcc> Well if it helps, I just tried ekiga again, and today it works
[12:08] <spiv> Heh, ok.
[12:10] <spiv> Ah, killing esd was the trick.
[12:12] <jamesh> USB headsets avoid this problem entirely ...
[12:50] <sladen> Malone doesn't allow a bug to link to two upstream bugs...
[12:51] <jamesh> sure it does.  But you can only have one bug watch associated with a task
[12:51] <jamesh> you can have bug watches not associated with any task too, if you want
[12:51] <sladen> I faked it by setting one to be 'gnomemeeting' and one to 'ekiga'
[12:52] <sladen> otherwise it says "A fix for this bug has already been requested for ekiga"
[01:12] <BjornT> sladen: which bug is this? it sounds like the two upstream bugs should really be duplicates, so it'd be interesting to see what the malone bug looks like.
[01:19] <sladen> BjornT: was bug #21711 but I think I'm inclined to agree now that I think about it
[01:19] <Ubugtu> Malone bug 21711 in ekiga "[enhancement]  Gnomemeeting Real name should use GECOS data" [Unknown,Unknown]  http://launchpad.net/bugs/21711
[01:19] <sladen> two similar bugs should be broken out in our report to keep them separate
[01:20] <sladen> what would be really useful is an upstream bug filing wizard
[01:51] <Ubugtu> New bug: #58462 in malone "Rejecting an upstream task still causes the bug to show when searching with "show only bugs that have to be forwarded upstream"" [Untriaged,Unconfirmed]  http://launchpad.net/bugs/58462
[02:30] <spiv> jamesh: btw, I was using a USB headset.
[02:45] <Ubugtu> New bug: #58466 in rosetta "better listing of Ubuntu on landing page" [Untriaged,Unconfirmed]  http://launchpad.net/bugs/58466
[03:05] <kiko> ah, morning
[03:42] <kiko> hey fjlacoste, got a new middle name there?
[03:43] <fjlacoste> kiko: actually, i always had it
[03:43] <kiko> the j is kinda cool
[03:43] <flacoste> i use it as a fallback when flacoste is already registered
[03:43] <flacoste> kiko: it stands for Julien
[03:44] <kiko> flacoste, I gave you some email yesterday
[03:44] <flacoste> kiko: i know :-) i'm about to read them, I'm all excited!
[03:44] <flacoste> kiko: thanks a lot
[03:45] <kiko> sorry for taking so long, I have been amazingly busy context-switching
[03:45] <flacoste> kiko: do you know what revision will be roll out next week?
[03:45] <kiko> jeez, I don't -- I can only imagine something between yesterday and today
[03:45] <flacoste> kiko: that's fine, the timing is kind of fine, all my pending branches landed yesterday
[03:45] <kiko> because.. well, stub's on holiday. I expect some email on monday to sort it out
[03:45] <flacoste> tt-search landed in 4001, i'm not sure I would like seeing that in production next tuesday
[03:46] <flacoste> i might want to test it a little on staging beforehand
[03:46] <kiko> flacoste, yeah. maybe email stub so he knows?
[03:46] <flacoste> actually, i *want* to test it on staging beforehand
[03:46] <flacoste> kiko: will do
[03:46] <kiko> flacoste, you have today and monday though
[03:46] <flacoste> kiko: Monday is Labour day :-)
[03:47] <kiko> oh is it! every day appears to be a labout day for me :-(
[03:47] <kiko> hey carlos 
[03:47] <kiko> did you get my comments yesterday? do they make sense?
[03:47] <carlos> kiko: hi
[03:47] <carlos> kiko: yes I got them
[03:47] <flacoste> kiko: actually, the invented labour day in north america as an alternative to the May 1st Workers day which is a holyday mostly everywhere else
[03:47] <kiko> carlos, were they things you agree with or are they way off the bat?
[03:48] <carlos> and I think that they make more or less sense, I need to start with it to be completely sure. What I don't see is why you prefer to not use inheritance...
[03:48] <flacoste> kiko: i also planned to try to contact the people who are support contact on ubuntu to try them to take a look at staging and get some feedback. do you think it's a good idea?
[03:48] <kiko> carlos, well.. inheritance is an option, but it can lead to confusing code if the classes don't match well. maybe they will though.
[03:49] <carlos> kiko: I see
[03:49] <kiko> carlos, there is another option, you know, that I just thought of
[03:49] <kiko> which is to make POMsgSetPageView go away completely
[03:49] <kiko> and instead 
[03:50] <kiko> when rendering a POMsgSet page you would use POFileTranslationView with a count of 1.
[03:50] <kiko> naaah
[03:50] <kiko> that would be a hack
[03:50] <kiko> never mind what I just said. :)
[03:50] <carlos> kiko: that sucks ;-)
[03:52] <carlos> kiko: anyway, your suggestion of three classes is also a good solution
[03:52] <kiko> sure
[03:52] <kiko> what it does which is good is separates presentation of the page from presentation of the translation
[03:52] <carlos> yeah
[03:52] <kiko> and then the two pages have a lot of similarities at that point
[03:52] <kiko> so you end up with two page classes and one "slave" view for just the individual translation
[03:53] <kiko> the slave view would have a "zoomed_in" attribute that you'd set in the right situation
[03:53] <kiko> hopefully that will work!
[03:54] <carlos> What I don't know how to do it is to move from  a POST to GET for the alternative language. We use a widget to generate that selector so I'm not sure if is possible to use a custom argument name instead of the long and ugly default one 
[03:55] <carlos> I mean, I know how to change the form, but I'm not quite sure how to change that name so we don't use argument names that suck
[03:55] <carlos> but there should be a way to do it
[03:58] <LarstiQ> 15:38:54 < GyrosGeier> "when I need to delete 150153 files, I'm happy that I'm using ext3"
[03:58] <LarstiQ> 15:39:13  * GyrosGeier attempts recreational trolling
[03:58] <LarstiQ> 15:38:54 < GyrosGeier> "when I need to delete 150153 files, I'm happy that I'm using ext3"
[03:59] <LarstiQ> 15:39:13  * GyrosGeier attempts recreational trolling
[03:59] <LarstiQ> aargh
[03:59] <LarstiQ> sorry about that
[04:00] <salgado> is he getting rid of tla/baz?
[04:00] <LarstiQ> salgado: GyrosGeier? No, entries in a spam folder
[04:01] <salgado> it sounded like he was deleting a tla archive or revision libraries
[04:05] <malcc> kiko: Ping
[04:05] <kiko> malcc, pong!
[04:05] <kr> Hi, i have a problem, i don't remember which e-mail address i passed on registration to launchpad. I only know a name. Who can I ask for the e-mail address to this account?
[04:06] <malcc> kiko: Just to let you know, I've run into some problems with the testing on mawson, will be a little longer
[04:06] <kiko> malcc, talk to me. send email to launchpad when this sort of thing happens -- you guys need to use email to status update everybody
[04:06] <malcc> kiko: Just found out my earlier-in-the-week attempts to rsync things from drescher didn't give me a usable set of files, something went wrong with symlink loops
[04:06] <kiko> argh
[04:06] <kiko> malcc, the archive rsync?
[04:07] <malcc> kiko: Yes
[04:07] <kiko> darn
[04:07] <malcc> Exactly.
[04:07] <kiko> can you email so that we can pick it up there?
[04:08] <malcc> Sure
[04:08] <kiko> malcc, thanks. one question
[04:09] <kiko> malcc, should I file a bug to drop running deathrow all the time?
[04:10] <malcc> kiko: Hmm. I just checked and, if I'm not mistaken, the current rocketfuel wouldn't run it at all :)
[04:10] <kiko> heh
[04:10] <kiko> okay, I'll file a bug, Hi-pri?
[04:10] <malcc> kiko: But yes, a bug would be good. Initially we should switch it on for every run, then once we've seen some of the new metrics we can make a decision
[04:10] <malcc> Yes, high will be fine, thanks
[04:10] <kiko> sure.
[04:12] <salgado> kiko, on bug 57507, which approach do you prefer?
[04:12] <Ubugtu> Malone bug 57507 in soyuz "Mirror listings for distro should be a single table having a country column instead of one table per country" [High,In progress]  http://launchpad.net/bugs/57507
[04:13] <kiko> let's see
[04:16] <kr> Ok, i did it myself, i find e-mail address using search option in merging accounts page. Bye.
[04:19] <flacoste> kiko: i think i like your idea of two steps confirmation
[04:19] <flacoste> kiko: and the guided ticket is implemented and can be tested on staging, you can try out to see how my filtering out of non-keywords work
[04:20] <kiko> flacoste, you are da man
[04:21] <flacoste> kiko: what do you think of contacting the ubuntu support contacts for testing?
[04:21] <kiko> sounds like a good idea
[04:40] <flacoste> kiko: i already found a problem with guided file ticket submission
[04:40] <flacoste> i have no limit on the number of similar tickets i show
[04:41] <flacoste> i should probably limit it somewhat or use batching
[04:43] <kiko> flacoste, limit it to ~ 10?
[04:44] <carlos> doko: http://people.ubuntu.com/~carlos/ooo-dapper-2006-08-30.tar.gz
[04:44] <carlos> doko: sorry, I forgot it...
[04:44] <flacoste> kiko: yeah 10-15 is probably a good number
[04:44] <doko> carlos: thanks, will update the package tomorrow
[04:44] <carlos> doko: I did a md5 checksum and it's the same in my laptop and at people.ubuntu.com
[04:45] <flacoste> kiko: another issue, i currently only look for OPEN or ANSWERED similar tickets (I excluded REJECTED ones) what do you think of that?
[04:46] <kiko> flacoste, hmmm. if you order in a reasonable order and limit, I think including REJECTED is okay, but... your call.
[04:46] <salgado> flacoste, it seems like after entering the summary and submitting, the focus on the next page will go to the summary field again, causing the page to scroll to that point when we get a list of possibly similar tickets
[04:47] <flacoste> kiko: i think i excluded REJECTED ones because I thought that this status is for silly support requests (SPAM or shipit question)
[04:47] <salgado> that's not good when we get more than a few similar tickets because then I only see the last ones and I don't see the header, explaining that these are similar tickets
[04:48] <flacoste> salgado: indeed that's a problem, it's caused by the automatic focusing code
[04:49] <flacoste> jamesh: anyway to turn off the automatic JS focusing?
[04:49] <flacoste> jamesh: (in LaunchpadFormView)
[04:49] <jamesh> flacoste: initial_focus_widget = None
[04:49] <flacoste> jamesh: ok, that's with the new code
[04:50] <salgado> hey kiko, did you look at bug 57507?
[04:50] <Ubugtu> Malone bug 57507 in soyuz "Mirror listings for distro should be a single table having a country column instead of one table per country" [High,In progress]  http://launchpad.net/bugs/57507
[04:50] <jamesh> flacoste: with the old code, it would have been focused_element_id = None
[04:50] <kiko> salgado, getting there.
[04:50] <jamesh> it's basically the same
[04:50] <flacoste> jamesh: wasn't that the default value?
[04:51] <jamesh> flacoste: a special marker object that causes the first widget to get focused.
[04:51] <flacoste> jamesh: ok, that explains it then
[04:52] <flacoste> jamesh: if I set focused_widget_id = None, will the focus still be set in the case the user submit the form and there is a validation error?
[04:53] <jamesh> flacoste: yep
[04:53] <flacoste> jamesh: awesome!
[04:54] <tuplanolla> 1/disconnect
[04:55] <kiko> salgado, will comment.
[05:06] <Kamion> I don't seem to be able to file a bug on the kmformat package in Ubuntu (using https://launchpad.net/distros/ubuntu/+source/kmformat/+filebug), even though I know it exists
[05:06] <Kamion> It tells me: "kmformat" does not exist in Ubuntu. Please choose a different package. If you're unsure, please select "I don't know"
[05:06] <Kamion> but it definitely does exist, see https://launchpad.net/distros/ubuntu/+source/kmformat
[05:07] <salgado> Kamion, there's a bug filed for it, IIRC
[05:08] <salgado> Kamion, bug 58000, maybe?
[05:08] <Ubugtu> Malone bug 58000 in malone "Not possible to file a bug on xmame directly" [Medium,Confirmed]  http://launchpad.net/bugs/58000
[05:09] <Kamion> ok, I only just NEWed kmformat, so that's possible
[05:09] <Kamion> its binaries I mean
[05:10] <Kamion> that workaround works. Thanks!
[05:11] <Kamion> Screwily, I picked the "I don't know" radio button, and it filed it on kmformat anyway. Go figure.
[05:22] <salgado> Kamion, I just noticed that the .manifest file on releases.ubuntu.com now includes the 6.06.1 instead of the 6.06 ones.  are all mirrors supposed to be mirroring the 6.06 or the 6.06.1 ones?
[05:23] <salgado> (or both?)
[05:23] <Kamion> salgado: 6.06.1 only
[05:23] <Kamion> releases.u.c doesn't have space for both
[05:23] <kiko> Kamion, did the filenames change?
[05:24] <Kamion> kiko: yes
[05:24] <kiko> Kamion, hmm. some mirrors are missing the new files then.
[05:24] <kiko> anyway, out for the afternoon
[05:24] <salgado> only one actually
[05:24] <salgado> Znarl, around?
[05:24] <Kamion> sounds possible; if they don't have temporary space for both 6.06 and 6.06.1, and they're using rsync --delete-after, then they might not be able to get 6.06.1
[05:25] <elmo> or possibly they're just not rsyncing anymore
[05:25] <salgado> :q
[05:25] <elmo> we have people who don't cron syncing of releases
[05:29] <Znarl> Hello salgado.
[05:30] <salgado> aparently it's only https://launchpad.net/distros/ubuntu/+mirror/edugraf-ubuntu-cds which doesn't have 6.06.1
[05:30] <salgado> Znarl, ^
[05:30] <Znarl> Ah right, that's a supprise.  I'll send an email to the admin.
[05:31] <salgado> I think it should have been marked disabled when that was detected
[05:31] <salgado> Znarl, what do you think?
[05:31] <salgado> (I mean, marked as disable by the prober)
[05:32] <Znarl> salgado : Yes, I agree.  We shouldn't be sending users to it.
[05:32] <salgado> yeah, I think it was supposed to work this way.  just spotted the bug
[05:41] <flacoste> salgado: can you take a look at https://devpad.canonical.com/~andrew/paste/file8EmuIW.html
[05:41] <flacoste> salgado: it's an email I'm about to send to the ubuntu support contacts to request feedback on the new stuff
[05:41] <salgado> ah, cool. :)
[05:41] <flacoste> salgado: let me know what you think of it
[05:44] <salgado> flacoste, it looks great!
[05:44] <salgado> flacoste, just one typo, I think: s/know/known/ on "Here are some know issues..."?
[05:44] <flacoste> salgado: thx! should I send a similar one to launchpad-users?
[05:44] <flacoste> salgado: ok, i'll fix the typo
[05:45] <flacoste> salgado: and should I CC launchpad lists (or somebody else) on that mail?
[05:45] <salgado> flacoste, yes, I think the launchpad list should be CCed
[05:46] <salgado> hmm. one thing I just noticed...
[05:47] <salgado> may be good to state clearly that all data on the staging server is thrown away every day
[05:47] <flacoste> salgado: right!
[05:47] <flacoste> salgado: and that their login will work like on production
[05:47] <salgado> yeah
[05:48] <matsubara> flacoste: the new +tickets listing is very nice! thank you. :)
[05:48] <salgado> in the case of launchpad user, another possibility would be to only mail the list when this is actually deployed and these small issues fixed
[05:49] <salgado> but I'm not sure.  I think it'd be better to check with SteveA
[05:49] <flacoste> salgado: ok, i'll ask SteveA
[05:49] <flacoste> SteveA: ping
[05:50] <SteveA> hi flacoste 
[05:51] <flacoste> salgado: I added the following paragraph after the staging URL:
[05:51] <flacoste> This server runs the latest Launchpad code on a copy of our production database. Any data changes you make on that server will be thrown away the next day. Your regular Launchpad account will work like on the production server. Not also that no email notifications are sent from the server. Basically, you can fool around there to your heart's content :-)
[05:51] <salgado> s/Not also/Note also/
[05:51] <flacoste> SteveA: I'm about to send an email to ubuntu support contacts asking for feedback on the new support tracker features
[05:51] <salgado> otherwise, looks good to me.  although I'm not a native english speaker
[05:52] <flacoste> SteveA: I'm wondering if it was pertinent to send a similar email to launchpad-users?
[05:52] <SteveA> 16:51 < flacoste> SteveA: I'm about to send an email to ubuntu support contacts asking for feedback on the new support tracker features
[05:52] <SteveA> oops
[05:52] <SteveA> 16:51 < salgado> otherwise, looks good to me.  although I'm not a native english speaker
[05:52] <SteveA> 16:52 < flacoste> SteveA: I'm wondering if it was pertinent to send a similar email to launchpad-users?
[05:52] <SteveA> that was a trackpad-fart
[05:53] <SteveA> sorry about that
[05:53] <flacoste> SteveA: you might also want to check https://devpad.canonical.com/~andrew/paste/filesPsGY8.html
[05:53] <SteveA> flacoste: I think it will be good to ask for input from launchpad-users
[05:53] <flacoste> SteveA: that's the email to the support contacts
[05:54] <flacoste> SteveA: ok, i will send a similar email (without the explanation about how I got their email addresses)
[05:55] <flacoste> SteveA: I'd CC launchpad list for the first email, what do you think of that?
[05:55] <SteveA> I like the email a lot.  It's very easy to read, and respectful.
[05:56] <SteveA> flacoste: sure
[05:57] <flacoste> SteveA: thanks!
[05:59] <carlos> danilos: around?
[06:03] <jordi> carlos: ready to send email?
[06:03] <jordi> carlos: if so, translators and rosetta-users, or more?
[06:03] <jordi> SteveA: ^
[06:03] <jordi> SteveA: last time it was sent to u-announce, but I guess we can skip that one this time?
[06:07] <carlos> jordi: let me read it again...
[06:08] <SteveA> jordi: did you ask a distro person, like colin, where it should go?
[06:08] <carlos> jordi: export/import native GSI files
[06:08] <jordi> no.
[06:09] <SteveA> I think that would be good, to get an opinion from the distro team
[06:09] <jordi> just asked
[06:09] <SteveA> cool
[06:09] <carlos> jordi: other than that, green light from me
[06:09] <jordi> ok
[06:10] <jordi> 18:10 < Kamion> jordi: if Ubuntu maintainers should know about it too, then ubuntu-devel-announce would be appropriate
[06:10] <jordi> SteveA: ^ I don't think it fits in u-d-a at all right?
[06:11] <carlos> No, I don't think so
[06:16] <WebMaven> SteveA: AYT?
[06:17] <ddaa> SteveA: hey, what are the rollout plans? Is there one planned next week?
[06:18] <SteveA> ddaa: we should have on next week.  we'll talk with stu on monday
[06:19] <ddaa> Okay, will post to the mailing list about rolling out up to 4004 to get the branch ui fixes.
[06:20] <ddaa> Sorry, still have not caught up with the launchpad mailing list...
[06:21] <flacoste> ddaa: we have conflict :-) i just post asking not to roll out 4002
[06:21] <ddaa> gah
[06:22] <flacoste> ddaa: maybe it will be possible to cherrypick your changes
[06:22] <ddaa> Mh, maybe it does not depend on 4003... need to check
[06:22] <LaserJock> any helpful LP admins around that could help me with an LP calendar subscription problem?
[06:24] <flacoste> ddaa: 4003 is about the focused_widget_id change to LaunchpadFormView
[06:25] <ddaa> my patch has a hunk that relates initial widget selection
[06:31] <ddaa> duh, conflict...
[06:32] <ddaa> flacoste: would taking 4004 and reversing 4002 work for you?
[06:33] <flacoste> ddaa: probably
[06:33] <flacoste> ddaa: the only thing is that I want it on staging for testing before it rolls out
[06:33] <flacoste> ddaa: anyway that will work, i'll be fine :-)
[06:34] <ddaa> grah... that conflicts too :(
[06:35] <flacoste> hmm, staging seems out
[06:36] <flacoste> i got a timeout request after making an error and asking for https://staging.launchpad.net/distros/launchpad/+tickets
[06:36] <flacoste> now nothing seems to respond even https://staging.launchpad.net/ does not respond
[06:36] <flacoste> salgado: who should I nag when staging goes out?
[06:38] <salgado> flacoste, the ones who usually check for problems or restart staging are carlos, stub, lifeless or one of the admins, I think
[06:39] <carlos> flacoste:  let me see
[06:40] <carlos> flacoste: it's not your fault... It's "mine"
[06:40] <carlos> flacoste: language packs generation, the load is too high there, but should finish quite soon
[06:40] <flacoste> carlos: actually, i'm kind of disappointed, I would have hoped that my request for feedback would have drawn too many users to staging...
[06:41] <carlos> flacoste: the process is finishing right now
[06:41] <flacoste> carlos: ok, thanks!
[06:41] <carlos> flacoste: Should I disable the export this weekend?
[06:42] <flacoste> carlos: i don't know, do you think it will prevent any use of staging by external users?
[06:42] <LaserJock> is there an LP admin in particular that handles calendar? my calendar seems a bit hosed, I think it might just need some reseting or something.
[06:42] <carlos> well, it depend on the time of the day
[06:42] <carlos> flacoste: atm we are generating a big tarball with translations for Edgy
[06:42] <carlos> and seems like it increases a lot the server load
[06:43] <flacoste> carlos: most of the people i contacted seemed to be on the Europe time zone (except one which is in .ar)
[06:43] <carlos> then I'm going to disable it until Monday
[06:43] <carlos> because it's when the script is really active
[06:43] <flacoste> carlos: maybe nice it?
[06:43] <carlos> flacoste: hmmm, we could try
[06:43] <carlos> but I will not be around this weekend
[06:44] <carlos> so I prefer to try that option on Monday
[06:44] <flacoste> carlos: your call
[06:44] <salgado> LaserJock, what's the exact problem with your calendar?
[06:44] <LaserJock> salgado: I can't get to it
[06:44] <flacoste> flacoste: i wouldn't want to delay edgy translations because some users /might/ come and try the features
[06:45] <flacoste> carlos: ^^^
[06:45] <salgado> LaserJock, what's your launchpad name?
[06:45] <flacoste> carlos: i don't know yet what the response will be
[06:45] <LaserJock> salgado: and when I view other calendars, I get a line of probably close to 1000 listings of "Ubuntu Documentation Project" under subscriptions
[06:45] <LaserJock> salgado: mantha
[06:45] <carlos> flacoste: in fact... I cannot do that, because the load is with the DB server, the process is executed on mawson...
[06:45] <LaserJock> salgado: so now when I try to do pretty much anything with calendar stuff it timesout
[06:46] <carlos> flacoste: you don't delay it
[06:46] <carlos> flacoste: we are doing daily exports
[06:46] <carlos> as a plus
[06:46] <carlos> and In fact, I think we should change it to be every two or three days because the task starts to be quite heavy
[06:47] <salgado> LaserJock, it sounds like a known bug which we didn't get to fix yet. :/
[06:47] <salgado> LaserJock, matsubara is going to find it out for us. :)
[06:47] <LaserJock> salgado: but it doesn't effect all people? I had a couple other people try and it worked fine for them
[06:47] <LaserJock> salgado: thanks, btw
[06:50] <matsubara-lunch> LaserJock: bug 57762
[06:50] <Ubugtu> Malone bug 57762 in launchpad-cal "Repetitive SQL query while generating a calendar." [Medium,Confirmed]  http://launchpad.net/bugs/57762
[06:52] <LaserJock> matsubara-lunch: interesting, I wonder why some people have problems and others don't, does it only happen when creating a calendar
[06:54] <matsubara-lunch> LaserJock: no, it actually happens after the calendar creation. I just updated the bug summary
[06:55] <LaserJock> matsubara-lunch: ok, well I'll leave you guys alone and wait for a fix :-)
[07:06] <carlos> danilos: ping
[07:10] <LaserJock> hmm, can a person email a LP team?
[07:16] <salgado> LaserJock, only if the team has a contact address set in launchpad
[07:16] <Ubugtu> New bug: #58491 in launchpad-support-tracker "Allow sorting by source package" [Low,Confirmed]  http://launchpad.net/bugs/58491
[07:16] <flacoste> salgado: do you have a working pqm-submit for the new bzr
[07:16] <flacoste> i used bzr branch  http://bazaar.launchpad.net/~jamesh/bzr-pqm/devel
[07:16] <salgado> flacoste, I don't know. didn't try to submit any merge after the update to the new bzr
[07:16] <LaserJock> salgado: thanks
[07:17] <flacoste> salgado: ok
[07:17] <flacoste> i get the following error:
[07:17] <flacoste> devpad.ubuntu.com: forward host lookup failed: Unknown host
[07:17] <flacoste> ssh_exchange_identification: Connection closed by remote host
[07:17] <flacoste> bzr: ERROR: Connection error: Unable to connect to SSH host devpad.ubuntu.com:None:
[07:17] <salgado> flacoste, but matsubara-lunch's been fighting with it today
[07:17] <salgado> maybe he can help
[07:17] <salgado> that's weird
[07:18] <flacoste> i don' t see why it tries devpad.ubuntu.com
[07:20] <salgado> flacoste, I guess you've tried a grep -r on your .bazaar/ directory?
[07:20] <salgado> (for devpad.u.c, that is)
[07:27] <flacoste> salgado: seems like that my locations.conf was full of crap, it worked with the old one but not with the new one, it is fixed now
[07:32] <jordi> carlos: sent
[07:36] <carlos> jordi: cool, thanks
[07:50] <ddaa> flacoste-lunch: please put a brown paper bag on the launchpad list email I just sent :)
[08:00] <Ubugtu> New bug: #58495 in malone "no way to track dapper-commerical bugs/packages in LP" [Untriaged,Unconfirmed]  http://launchpad.net/bugs/58495
[09:33] <Kuhrscher> Hello, the import of katapult's translation to edgy has failed...
[09:34] <Kuhrscher> Is it necessary to post a bug?
[09:40] <Kuhrscher> https://launchpad.net/products/rosetta/+bug/58504
[09:40] <Ubugtu> Malone bug 58504 in rosetta "Import of katapult's translation to edgy failed" [Untriaged,Unconfirmed]  
[09:40] <Kuhrscher> jap
[09:41] <Kuhrscher> mine ;-)
[09:48] <matsubara> jordi: could you take a look? ^^
[09:50] <Ubugtu> New bug: #58504 in rosetta "Import of katapult's translation to edgy failed" [Untriaged,Unconfirmed]  http://launchpad.net/bugs/58504
[09:51] <lucasvo> ubugtu is kinda slow :)
[09:52] <jordi> let me have a look
[09:54] <salgado> lucasvo, I think it's because the email notifications are not sent at the same time the bug is filed
[09:55] <mdke> yep, there is like a 5 minute delay from the launchpad side
[09:56] <salgado> but it may be that it takes longer to reach ubugtu than it takes to reach normal users.  can't tell for sure
[09:57] <salgado> I mean, ubugtu could process them every five minutes or so
[10:42] <nixternal> i tell ya, irc rocks ;)
[10:43] <nixternal> flacoste: so i take it "staging" is just that...the testing site right now...this will get moved over soon?
[10:44] <flacoste> nixternal: yes it is a testing site
[10:44] <flacoste> nixternal: it is not determined yet what revision will be rolled out next week
[10:44] <nixternal> man that is awesome...i just got so used to the old setup, that i never thought about modeling it after malone
[10:44] <nixternal> awesome job
[10:44] <flacoste> nixternal: but if it is not next week, it will be in two probably
[10:44] <flacoste> nixternal: there was actually a bug opened with that suggestion
[10:45] <nixternal> heh, and obviously my small and unimaginative mind didn't pick it up ;)
[10:46] <nixternal> so, if i want to provide support, i can use the staging right now, and it will work?  to help out with testing and what not?
[10:46] <flacoste> nixternal: do you usually use the email interface or the web interface for the support tracker?
[10:51] <bradb> I suggested renaming staging to try.launchpad.net, which might make things clearer.
[10:51] <flacoste> bradb: yeah, cool name
[10:52] <flacoste> nixternal: no, the support you do there will be thrown away the next day
[10:52] <flacoste> nixternal: it works on a copy of the database and it doesn't send out any email
[10:52] <flacoste> nixternal: it's really for testing purpose not production use :-)
[10:57] <nixternal> ahhh...ok..got it
[10:59] <Ubugtu> Malone bug 58514 in launchpad "staging.launchpad.net should be renamed to try.launchpad.net" [Untriaged,Unconfirmed]  http://launchpad.net/bugs/58514
[11:00] <nixternal> heh
[11:05] <Ubugtu> New bug: #58514 in launchpad "staging.launchpad.net should be renamed to try.launchpad.net" [Untriaged,Unconfirmed]  http://launchpad.net/bugs/58514