[12:20] <ubotu> New bug: #126877 in soyuz "Package archive listing doesn't link to the packages" [Undecided,New]  https://launchpad.net/bugs/126877
[12:32] <Amaranth> how do i link https://bugs.launchpad.net/ubuntu/+bug/126876 to http://bugzilla.gnome.org/show_bug.cgi?id=458110 ?
[12:33] <ubotu> Launchpad bug 126876 in Ubuntu "Ubuntu should have Mind Mapping software" [Undecided,New]  
[12:51] <ubotu> New bug: #126879 in soyuz "Person's archive page lacks instructions on how to add it as a repository" [Undecided,New]  https://launchpad.net/bugs/126879
[12:51] <ubotu> New bug: #126880 in soyuz ""When" column in PPA table is ambiguous" [Undecided,New]  https://launchpad.net/bugs/126880
[01:41] <bmm> How do I mark a bug as a duplicate of another bug?
[01:42] <mpt> bmm, in the pink box near the top left
[01:42] <bmm> Ah, found the button, sorry!
[01:42] <bmm> oh, just to late, but thanks mpt !
[01:42] <mpt> No apology needed, it's our fault
[01:43] <mpt> too many links in that box :-)
[01:46] <bmm> Well, thanks anyway and I'll be back another day!
[01:47] <mantiena-baltix> cprov-afk: sleeping ?
[02:01] <cprov-afk> mantiena-baltix: not yet 
[02:06] <mantiena-baltix> cprov-afk: ppa doesn't work, problem is not in signing - I'm trying upload signed sources and changes file but orig.tar.gz gets time-out
[02:08] <cprov-afk> mantiena-baltix: is you connection working correctly ?  how big is the orig ?
[02:08] <mantiena-baltix> 700 kb, internet connection is ok, I'm uploading 100x bigger files
[02:10] <mantiena-baltix> cprov-afk: I can upload signed .dsc, .changes, .diff.gz  and orig.tar.gz files to public ftp and you can try to upload with my ~/.dput.cf
[02:14] <mantiena-baltix> cprov-afk: what you think ?
[02:15] <cprov-afk> mantiena-baltix: not sure what is happening, other users, including me are able to use it
[02:19] <mantiena-baltix> cprov-afk: I've uploaded signed .dsc, .changes, .diff.gz  and orig.tar.gz files to  ftp://ftp.akl.lt/Linux/Baltix/Baltix-Ubuntu-packages/feisty/gparted - please, try to upload to ppa as user mantas
[02:20] <cprov-afk> mantiena-baltix: I've just upload a 1.4Mb orig it worked ... Can you try again, please ?
[02:21] <mantiena-baltix> cprov-afk: I'm trying for about 10 times...
[02:21] <cprov-afk> mantiena-baltix: okay
[02:21] <mantiena-baltix> same error - 'Connection timed out'
[02:26] <cprov-afk> mantiena-baltix: 00:21:02 DEBUG   Session from 84.55.4.28:40629
[02:26] <cprov-afk> mantiena-baltix: and the session never ends 
[02:27] <cprov-afk> mantiena-baltix: On normal uploads I have;
[02:27] <cprov-afk> 00:16:29 DEBUG   Session from 201.72.172.10:36311
[02:27] <cprov-afk> 00:19:21 DEBUG   Processing session complete in /tmp/tmpJXHw7H-poppy
[02:28] <mantiena-baltix> cprov-afk: so, where is the problem ?
[02:29] <cprov-afk> mantiena-baltix: sorry, but apart of any weirdness in our DC, it can only be in your side.
[02:30] <mantiena-baltix> cprov-afk: so, you uploaded my signed gparted sources without problems ?
[02:31] <cprov-afk> mantiena-baltix: no I didn't. I can do it now
[02:31] <mantiena-baltix> cprov-afk: wait a minute, I try to upload from different server
[02:34] <cprov-afk> mantiena-baltix: check the dput output -> Checksum doesn't match for (...)gparted_0.3.3.orig.tar.gz
[02:35] <mantiena-baltix> cprov-afk: where I can see this ?
[02:36] <cprov-afk> mantiena-baltix: in dput output, after issuing 'dput mantas gparted_0.3.3-2feisty3_source.changes'
[02:40] <mantiena-baltix> cprov-afk: I don't get such errors - I've uploaded successfully from another machine (from different internet provider), it seems my internet provider forbids ftp :(
[02:41] <cprov-afk> mantiena-baltix: the files I downloaded from the ftp address you gave were corrupted (or get corrupted in my machine), anyway I rebuilt it and upload w/o problems to my PPA
[02:42] <mantiena-baltix> cprov-afk: I've pasted log to you privatelly
[02:44] <mantiena-baltix> cprov-afk: it seems my uploads were rejected :( I just got email from launchpad with error:
[02:44] <mantiena-baltix> could not find PPA for 'mantas' :(
[02:45] <cprov-afk> mantiena-baltix: you have to 'Activate' you PPA in https://dogfood.launchpad.net/~mantas
[02:49] <mantiena-baltix> cprov-afk: hehe, PPA contents description was empty :)
[02:49] <cprov-afk> mantiena-baltix: sorry ?
[02:50] <ubotu> New bug: #126896 in soyuz "don't list PPAs with zero packages" [Undecided,New]  https://launchpad.net/bugs/126896
[02:52] <mantiena-baltix> cprov-afk: when I activated PPA I got some page with empty ' PPA contents description' ;)
[02:53] <cprov-afk> mantiena-baltix: you are supposed to fill it. Isn't it clear enough ?
[02:53] <mantiena-baltix> No, I thought that there was a bug :)
[02:54] <cprov-afk> mantiena-baltix: I'm not following you ... should we guess a description suitable for your PPA ? 
[02:56] <mantiena-baltix> Sorry, I don't understand you. My local time is 4 hours after midnight, I should sleep for about 4 hours .. :)
[02:57] <mantiena-baltix> maybe I'm sleeping and dreaming now ? ;)
[03:03] <cprov-afk> mantiena-baltix: maybe ...
[03:03] <mantiena-baltix> cprov-afk: in any case I already got email from launchpad with word "Accepted" in subject ;)
[03:04] <cprov-afk> mantiena-baltix: great
[03:04] <mantiena-baltix> so, thank you very much - I'm trying to disconnect from internet in my dream ...
[03:07] <mantiena-baltix> cprov-afk: How long I should wait for binaries in http://ppa.dogfood.launchpad.net/mantas/ubuntu/pool/main/g/gparted/ ?
[03:09] <cprov-afk> mantiena-baltix: check https://dogfood.launchpad.net/~mantas/+archive/+builds
[03:19] <mantiena-baltix> cprov-afk: build was successfull on amd64, I hope there will be no problems on i386 too, thank you very much and good bye :)
[03:20] <cprov-afk> mantiena-baltix: bye
[03:56] <ubotu> New bug: #72083 in launchpad "Confirmed email addresses portlet overlaps over the arrow that expands the portlet" [Low,Confirmed]  https://launchpad.net/bugs/72083
[04:15] <ubotu> New bug: #126907 in launchpad "Need a less ambiguous "Private" icon" [Undecided,New]  https://launchpad.net/bugs/126907
[06:53] <Hobbsee> spiv: ping
[06:53] <Hobbsee> lifeless: ping
[06:57] <lifeless> pong
[06:57] <Hobbsee> lifeless: @ -motu :)
[06:58] <lifeless> ;0
[07:14] <desertc> Hello - referring to https://launchpad.net/ubuntu/+source/gnome-screensaver/+bug/59688 - what does it mean when someone says the bug is "fixed upstream", as is said in the last comment?
[07:14] <ubotu> Launchpad bug 59688 in totem "screensaver starts when movie plays" [Undecided,Invalid]   - Assigned to Ubuntu Desktop Bugs (desktop-bugs)
[07:17] <ScottK> It means Gnome has already fixed the bug and the fix will be in Gutsy.
[07:17] <desertc> yay!  thanks - I will inform this blogger: http://kyliewillison.blogspot.com/2007/06/totem-screensaver.html
[07:20] <mpt> see also https://launchpad.net/launchpad/+spec/upstream-terminology
[07:22] <mthaddon> Launchpad is going down in 15 mins for a code update. Estimated downtime is approx 45mins.
[07:51] <desertc> Thanks for your help.
[08:21] <mthaddon> Rollout Complete, Launchpad back up
[08:40] <ubotu> New bug: #126924 in malone "second-stage guided filebug form needs UI improvement" [Undecided,New]  https://launchpad.net/bugs/126924
[09:07] <stub> The whitespace between the whats new message and the trailing full stop is a bug or a feature?
[09:08] <siretart> can launchpad merge teams yet?
[09:08] <stub> siretart: no
[09:09] <siretart> stub: can you perhaps make https://launchpad.net/~ubuntu-motu less confusing?
[09:09] <stub> Nope
[09:09] <stub> That  looks all autogenerated
[09:10] <siretart> stub: I just got an email from a confused ubuntu user asking me as a MOTUMedia member about a package maintained by ubuntu-motu
[09:10] <stub> And changing the data to change the rendering would break stuff I suspect
[09:10] <siretart> I'm not exactly sure what the bug here is, though
[09:11] <siretart> it seems to me that a launchpad user called 'ubuntu-motu' was created
[09:11] <siretart> which doesn't make sense. there is a team https://launchpad.net/~motu, which should be the maintainer of all the packages
[09:16] <Fujitsu> The problem is that LP needs a team with ubuntu-motu@lists.ubuntu.com as an email address.
[09:16] <Fujitsu> Setting that as the motu contact address would mean the ML got a lot of bugmail, which is a Bad Thing.
[09:16] <siretart> right
[09:16] <Fujitsu> It would be nice to change the name of that user, though.
[09:17] <Fujitsu> It has been like that since DebianMaintainerField came into effect :(
[09:20] <ubotu> New bug: #126926 in launchpad "what's new message has spurious whitespace" [Undecided,New]  https://launchpad.net/bugs/126926
[10:00] <mpt> Gooooooooooooooood evening Launchpadders!
[10:43] <bmm> I was here like 14 hours ago asking about uscan https support. The next version of uscan (release but not in ubuntu yet: version 2.10.6) has support for https in uscan. So launchpad can keep hosting files under https as they should (IMHO).
[11:12] <mpt> ugh
[11:13] <mpt> Just went to report a bug, and discovered that a bug with exactly the same title had been reported two days ago by Matthew Paul Thomas
[11:13] <mpt> He always beats me to it
[11:13] <mwhudson> :)
[11:18] <soren> How often does malone process e-mail (incoming ones)?
[11:18] <BjornT> soren: every 5 minutes
[11:19] <soren> BjornT: So.. If it's been 15 mintues now and nothing has happened, then what?
[11:19] <BjornT> soren: i'll check the error logs to see i can find something
[11:19] <soren> BjornT: Bug #126845 if it helps at all
[11:19] <ubotu> Launchpad bug 126845 in iptables "TARPIT extension broken" [Undecided,New]  https://launchpad.net/bugs/126845
[11:19] <soren> BjornT: Sender address: soren@ubuntu.com
[11:20] <soren> BjornT: Will the message-id do you any good?
[11:21] <BjornT> soren: no, i've found the message, let me just check what went wrong...
[11:21] <soren> BjornT: Cool.
[11:25] <ubotu> New bug: #126941 in soyuz "Source package page title doesn't mention the package" [Undecided,New]  https://launchpad.net/bugs/126941
[11:25] <BjornT> soren: found the bug; it breaks if you say that it affects another source package, while assigning it to a team with no contact address. i'll file a bug about it.
[11:35] <ubotu> New bug: #126943 in malone "OOPS when assigning a bug to a team with not contact address at the same time a new bugtask is created" [Undecided,New]  https://launchpad.net/bugs/126943
[11:36] <soren> BjornT: Should I do the stuff manually then or will you reprocess it?
[11:40] <BjornT> soren: sorry, please do it manually, i can't fix the bug and push the fix to production that fast, so i can't reprocess it.
[11:41] <soren> BjornT: Quite alright.
[11:41] <soren> BjornT: Thanks!
[11:42] <mpt> BjornT, I think bug 103137 was just fixed without being tracked
[11:42] <ubotu> Launchpad bug 103137 in malone "What then if the bug has already been reported?" [Medium,Confirmed]  https://launchpad.net/bugs/103137
[11:43] <mpt> crap
[11:43] <mpt> I just clicked "Subscribe To This Bug" by mistake instead of "Submit Bug Report"
[11:44] <mpt> and subscribed myself to a Fix Released bug, of all things
[11:46] <BjornT> mpt: yes, i think so too. i've marked it as fix released.
[11:48] <mpt> thanks Bjrn
[11:48] <mpt> bonus fixes are always good :-)
[11:50] <ubotu> New bug: #126946 in malone ""No, I'd like to report a new bug" doesn't immediately let me do so" [Undecided,New]  https://launchpad.net/bugs/126946
[11:55] <ubotu> New bug: #126948 in malone ""Subscribe To This Bug" is incorrect capitalization" [Undecided,New]  https://launchpad.net/bugs/126948
[12:05] <ubotu> New bug: #126949 in malone "Users don't get notified about unhandled exceptions in the incoming e-mail interface" [Medium,Confirmed]  https://launchpad.net/bugs/126949
[12:25] <ubotu> New bug: #126953 in malone "Sync importance for bug watches" [Undecided,New]  https://launchpad.net/bugs/126953
[12:36] <ubotu> New bug: #126956 in soyuz "E-mail addresses in changelogs don't link anywhere" [Undecided,New]  https://launchpad.net/bugs/126956
[12:50] <ubotu> New bug: #126957 in malone "Bug status form is mushed together, especially in Helvetica" [Undecided,New]  https://launchpad.net/bugs/126957
[01:26] <ubotu> New bug: #126959 in soyuz ""Changeslist" on distribution series administration page is unhelpful" [Undecided,New]  https://launchpad.net/bugs/126959
[01:35] <ubotu> New bug: #126960 in soyuz "Changing the "Name" of a distribution series returns to the wrong page" [Undecided,New]  https://launchpad.net/bugs/126960
[01:40] <ubotu> New bug: #126961 in soyuz "Distribution series administration page has no title or heading" [Undecided,New]  https://launchpad.net/bugs/126961
[02:22] <tokj> damn..
[03:05] <ubotu> New bug: #126969 in launchpad "In sortable lists the user's selection isn't persistent" [Undecided,New]  https://launchpad.net/bugs/126969
[03:10] <ubotu> New bug: #126970 in launchpad "obfuscate_email causes the server to hang" [Critical,In progress]  https://launchpad.net/bugs/126970
[03:35] <ubotu> New bug: #126976 in launchpad-bazaar "Automatic discovery of new branches" [Undecided,New]  https://launchpad.net/bugs/126976
[03:40] <ubotu> New bug: #126975 in rosetta "TraversalError in translation page" [Critical,New]  https://launchpad.net/bugs/126975
[04:00] <bigjools> me
[04:00] <mrevell> no me
[04:00] <bigjools> :)
[04:01] <jsk_> me 2
[04:01] <flacoste> me 3
[04:01] <salgado> stub, you going to chair the meeting today?
[04:01] <mpt> SteveA, here?
[04:01] <salgado> I guess SteveA won't be around for the meeting, but I may be wrong
[04:01] <stub> me? If I have too, but I was hoping to be eating this first bit...
[04:01] <Rinchen> mpt,  I appoint you :-)
[04:01] <mpt> kiko said he'd try to be here
[04:03] <Rinchen> It's 7am for them currently.
[04:03] <mthaddon> yeah, me too :)
[04:03] <Rinchen> :-)
[04:03] <Rinchen> ah great, was just going to ask
[04:03] <Rinchen> thanks mpt
[04:04] <RainCT> hi
[04:04] <mpt> ok, MEETING TIME
[04:04] <barry> me
[04:04] <sinzu1> me
[04:04] <mpt> For the next half an hour or so, we'll be discussing Launchpad development
[04:04] <mpt> Who's here today?
[04:04] <bigjools> me
[04:04] <Rinchen> me
[04:04] <jtv> me
[04:04] <allenap> me
[04:04] <statik> me
[04:04] <gmb> me
[04:04] <BjornT> me
[04:04] <matsubara> me
[04:04] <mwhudson> me
[04:04] <stub> me
[04:04] <sinzui> me
[04:04] <bac> me
[04:04] <mrevell> me
[04:04] <adeuring> me
[04:04] <salgado> me
[04:04] <schwuk> me
[04:04] <mthaddon> me
[04:05] <cprov> me
[04:05] <flacoste> me
[04:05] <intellectronica> me
[04:05] <mpt> Team leads, please check that your co-conspirators are here
[04:05] <mpt> ddaa?
[04:05] <jtv> Translations: carlos & danilo not present.
[04:06] <jamesh> me
[04:06] <jsk_> me
[04:06] <mpt> ok
[04:06] <mpt> == Agenda ==
[04:06] <mpt>  * Next meeting
[04:06] <mpt>  * Actions from last meeting
[04:06] <mpt>  * Oops report (Matsubara)
[04:06] <mpt>  * Critical Bugs (Rinchen)
[04:06] <mpt>  * Bug tags
[04:06] <mpt>  * Operations report (mthaddon)
[04:06] <mpt>  * DBA report (stub)
[04:07] <mpt>  * Sysadmin requests (Rinchen
[04:07] <mpt>  * A top user-affecting issue (mrevell)
[04:07] <mpt>  * kiko - proper use of release-critical
[04:07] <mpt>  * kiko - Pre-release QA testing feeback
[04:07] <mpt>  * Blockers
[04:07] <mpt> == Apologies ==
[04:07] <mpt>  * carlos and danilos are at GUADEC
[04:07] <mpt> Any others?
[04:08] <mpt> SteveA and kiko are busy at Ubuntu Live I assume
[04:08] <mpt> == Next meeting ==
[04:08] <mpt> Anyone unable to be here same time next week?
[04:08] <bac> apologies: UL
[04:08] <mpt> hi cprov 
[04:08] <allenap> I'll be away
[04:09] <statik> EdwinGrubbs is here today also, a brand new launchpadder
[04:09] <bac> bac: wait, i'll be back on wednesday, so nm
[04:09] <mpt> flacoste will be parenting
[04:09] <flacoste> welcome EdwinGrubbs!
[04:09] <mpt> Welcome EdwinGrubbs
[04:09] <cprov> mpt: hi (my 'me' was already posted, no ?)
[04:09] <bac> hello EdwinGrubbs 
[04:09] <matsubara> welcome EdwinGrubbs 
[04:09] <Rinchen> Welcome EdwinGrubbs!
[04:09] <mpt> cprov, yes
[04:09] <jsk_> welcome EdwinGrubbs!
[04:09] <schwuk> lo EdwinGrubbs
[04:09] <mwhudson> hi EdwinGrubbs
[04:09] <EdwinGrubbs> thanks, glad to be here
[04:09] <gmb> greetings, EdwinGrubbs 
[04:09] <mrevell> hi EdwinGrubbs
[04:09] <mpt> Edwin is working with statik, correct?
[04:10] <adeuring> hi EdwinGrubbs
[04:10] <statik> yes
[04:10] <intellectronica> howdy EdwinGrubbs, welcome!
[04:10] <mpt> cool
[04:10] <mpt> == Actions from last meeting ==
[04:10] <mpt>  * jamesh to follow up on bug 58220
[04:10] <ubotu> Launchpad bug 58220 in launchpad "When an error occurs processing a request another oops is recorded because there's no interaction set up." [High,Confirmed]  https://launchpad.net/bugs/58220 - Assigned to James Henstridge (jamesh)
[04:10] <ddaa> me
[04:10] <mpt>  * mpt to mail Rinchen about the future of the Bug report
[04:10] <mpt> I did that
[04:10] <mpt>  * statik to record security.cfg change process on "the reviewers page" and DatabaseSchemaChanges
[04:10] <jamesh> I did follow up on bug 58220
[04:10] <statik> done
[04:10] <mpt> thanks jamesh 
[04:10] <mpt> and thanks statik 
[04:11] <mpt> == Oops report ==
[04:11] <matsubara> First, congrats on the release and a very well done job on the pre-release QA
[04:11] <matsubara> Today's oops report is about bugs 126975, OOPS-565D2528
[04:11] <ubotu> Launchpad bug 126975 in rosetta "TraversalError in translation page" [Critical,New]  https://launchpad.net/bugs/126975
[04:11] <ubotu> https://devpad.canonical.com/~jamesh/oops.cgi/565D2528
[04:11] <matsubara> Bug 126975 is the top OOPSer since the rollout. I've already asked jtv to take it
[04:11] <matsubara> OOPS-565D2528 has been taken care of by mwhudson
[04:11] <ubotu> https://devpad.canonical.com/~jamesh/oops.cgi/565D2528
[04:11] <matsubara> For those who care: https://devpad.canonical.com/~andrew/paste/file3D7k2v.html has a partial OOPS report from today.
[04:11] <ddaa> and me, good teamwork
[04:12] <matsubara> sorry ddaa, forgot about you. thanks!
[04:12] <matsubara> that's it from me mpt. back to you
[04:12] <jtv> matsubara: sorry, was off working on that very bug.
[04:12] <mpt> Thank you matsubara 
[04:12] <jtv> fix is written, reviewed & on the way.
[04:12] <mpt> == Critical bugs ==
[04:12] <matsubara> no problem jtv. thanks a lot for handling it!
[04:13] <Rinchen> I'm going to echo this too:  <matsubara> First, congrats on the release and a very well done job on the pre-release QA
[04:13] <Rinchen> I'd like to ask for the status on two bugs
[04:13] <Rinchen> Bug #126768
[04:13] <ubotu> Launchpad bug 126768 in blueprint "OOPS when subscribing a team to a blueprint." [Critical,In progress]  https://launchpad.net/bugs/126768 - Assigned to Tom Berger (intellectronica)
[04:13] <Rinchen> Bug #126970
[04:13] <ubotu> Launchpad bug 126970 in launchpad "obfuscate_email causes the server to hang" [Critical,In progress]  https://launchpad.net/bugs/126970 - Assigned to Curtis Hovey (sinzui-is)
[04:13] <Rinchen> I believe they are both underway.
[04:14] <matsubara> Rinchen: I think the first one was RCFIXED
[04:14] <matsubara> isn't it?
[04:14] <sinzui> Rinchen: fix is approved by barry. I await rc approval.
[04:14] <intellectronica> intellectronica: Rinchen - that bug is fixed and was landed rc
[04:14] <Rinchen> excellent. Thanks. Please update the bug reports today.
[04:14] <Rinchen> mpt, back to you
[04:14] <mpt> thanks Rinchen 
[04:15] <mpt> == Bug tags ==
[04:15] <mpt> There are no tags proposed
[04:15] <mpt> == Operations report ==
[04:15] <mpt> kiko-zzz, hi
[04:16] <mpt> mthaddon, go ahead
[04:16] <mthaddon> 1.1.7 Rolled out, with the exception of Importd, which will be done after this meeting with ddaa
[04:16] <mthaddon> other than that, I'm done
[04:16] <kiko-zzz> me
[04:16] <kiko-zzz> gar
[04:16] <stub> Appservers where crashing due to a regexp that behaved suboptimally for some input. As a result, email addresses in bug comments are no longer being obfuscated with the emergancy fix I put in place. This shouldn't be a problem as this was a new feature this cycle, and I believe a real fix is in the pipeline and being landed as we speak.
[04:16] <stub> The update blew up some monitoring, where a script was installed in an area of the tree that the rollout tools expect to control and thus removed it. Tom is fixing this.
[04:16] <mpt> Thank you mthaddon 
[04:17] <stub> erm... not crashing. Spinning.
[04:17] <stub> crashing would have been better since the load balancer handles that better
[04:17] <stub> all from me
[04:17] <mwhudson> suboptimally == "probably taking thousands of years to complete"
[04:17] <jamesh> a regexp only anchored in the middle?
[04:18] <sinzui> obsucate_email was released in 1.1.6
[04:18] <jtv> mwhudson: buy better hardware.
[04:18] <stub> details on the mailing list for the geeks
[04:18] <mwhudson> i or someone should post to the mailing list about it
[04:18] <mpt> stub, do you have anything DB-related as well?
[04:19] <mthaddon> jtv: any hardware that can run for thousands of years must be pretty good
[04:19] <schwuk> mthaddon: deep thought
[04:19] <stub> I did but gedit just crashed taking my buffer with it. 
[04:19] <stub> Come back to me
[04:19] <mpt> stub, matsubara, do you know that the regexp/e-mail problem is actually reported as a bug?
[04:19] <matsubara> yes it is mpt
[04:20] <mpt> ok, just checking :-)
[04:20] <matsubara> it's the second item in Rinchen's report
[04:20] <matsubara> bug 126970
[04:20] <ubotu> Launchpad bug 126970 in launchpad "obfuscate_email causes the server to hang" [Critical,In progress]  https://launchpad.net/bugs/126970 - Assigned to Curtis Hovey (sinzui-is)
[04:20] <mpt> thanks
[04:20] <mpt> stub, retrievable or no?
[04:21] <stub> Dunno. Anyone know where gedit keeps its temp files?
[04:21] <mpt> ok, if you find it before the end of the meeting, let me know
[04:21] <sinzui> I have not submitted it to pqm yet. I await approval. barry passed the branch.
[04:21] <mpt> meanwhile
[04:21] <mpt> == Sysadmin requests ==
[04:21] <matsubara> kiko-zzz: can you approve sinzui's patch?
[04:21] <flacoste> kiko-zzz: sinzui needs your release-critical=kiko for bug 126970
[04:22] <Rinchen> There was one urgent one for kiko and mrevell which has been completed 10 minutes ago.
[04:22] <Rinchen> Anyone blocked or otherwise waiting on RT requests?
[04:22] <kiko-zzz> thanks Rinchen 
[04:22] <allenap> kiko-zzz: I would like a release-critical on bug 126947
[04:22] <ubotu> Bug 126947 on http://launchpad.net/bugs/126947 is private
[04:22] <allenap> kiko: if that's okay :)
[04:22] <Rinchen> If anyone things of any after the meeting, please ping me.  mpt, back to you
[04:23] <mpt> thank you
[04:23] <mpt> == No top user-affecting issue ==
[04:23] <ddaa> does that mean all issues are affecting users equally?
[04:24] <mpt> Yes, we're equal-opportunity offenders
[04:24] <mrevell> ddaa: No, unfortunately it means that I haven't prepared one this week yet. :(
[04:24] <mpt> mrevell has been busy with release notes and other things
[04:25] <mpt> anyway
[04:25] <mpt> == Proper use of release-critical ==
[04:25] <kiko> it'll be interesting to figure out what problems are affecting users now :)
[04:25] <kiko> I suspect the three oopsers!
[04:25] <kiko> aha, proper release-critical use.
[04:25] <mpt> kiko, we'd need to do testing to find that out ;-)
[04:25] <kiko> I've noticed that people have actually not paid attention to the fact that not anyone can sign off on release-critical landings.
[04:26] <kiko> so for now, I want to underline that only Steve and I, with Joey as a backup, are allowed to give you release-critical for a branch
[04:26] <kiko> for next release we'll change this to allow for better timezone coverage
[04:26] <kiko> and have a release-critical hotline so you always have a number to call for one if you need it.
[04:27] <kiko> I'd like to close by thanking profusely everybody that tested and landed fixes through today, though
[04:27] <kiko> it's the first time we've done this and I think we've done well to find lots of problems
[04:27] <kiko> and fix them before the rollout
[04:28] <kiko> that's all on this topic.
[04:28] <mpt> which segues us nicely into the next topic
[04:28] <stub> So you really want to be woken up, even if it is blindingly obvious that a patch needs to land?
[04:28] <mpt> == Pre-release QA testing feedback ==
[04:28] <kiko> my impression is that this worked very well
[04:28] <kiko> and that we had a number of showstoppers fixed, and tests added.
[04:29] <kiko> I want to really underline that a release-critical does /not/ mean you can land without a test
[04:29] <kiko> it actually means the opposite -- release-critical means that you /can/ reproduce the problem
[04:29] <kiko> and you've got a fix written to that effect.
[04:30] <kiko> hopefully that's clear by now
[04:30] <kiko> anyway, I wanted to ask people how they felt the QA and fix period went. 
[04:30] <kiko> any comments? 
[04:30] <mpt> I've found quite a few UI glitches in the new features
[04:30] <kiko> worth doing, waste of time, change something?
[04:30] <bigjools> we should do it every time
[04:30] <mpt> Not sure what to do about that
[04:30] <jtv> The signoff format needs work.
[04:31] <mwhudson> it was good
[04:31] <Rinchen> I also think the pre-release QA worked out well. I can think of some tweaks to make it better that I'll discuss with kiko. The assembled report by Diogo was very helpful, at least to me. All in all, I think it's a good addition.
[04:31] <kiko> one question is why didn't we catch the problems we saw today?
[04:31] <kiko> matsubara, why didn't linkchecker tickle the rosetta oops?
[04:32] <matsubara> kiko: good question. I've yet to check if the oops affects staging
[04:32] <ddaa> our oops was a fault in the database schema that allowed out of date importd code to stick stuff in the db it should not be allowed.
[04:32] <matsubara> kiko: or if linkechecker is crawling those pages
[04:32] <stub> So we want to err on the side of keeping code quality rather than keep uptime and provide a good user experience?
[04:33] <ddaa> I could have been allowed if reviewer had noticed that the db patch used a default for a column that should not have a default.
[04:33] <ddaa> s/allowed/avoided/
[04:33] <kiko> ddaa, that's not the reviewer's fault.
[04:33] <kiko> review doesn't catch errors unless the reviewer is very alert and very lucky.
[04:33] <ddaa> or the branch authors
[04:33] <ddaa> not a fault in the process IMO
[04:33] <kiko> stub, we want to strike a balance.
[04:33] <kiko> right
[04:33] <mwhudson> the regexp one was a 'new code'-'real data' collision
[04:34] <kiko> mwhudson, ddaa: so was the blueprint problem that intellectronica and stub fixed
[04:35] <kiko> it's something to look out for
[04:35] <intellectronica> looks like we're having quite a few cases where the sample data doesn't serve us good enough and we get errors when trying the code with more data. could it be that our sample data is not good enough?
[04:35] <kiko> intellectronica, our sample data is not good enough, but it's hard to systematically improve it, I think
[04:35] <kiko> mark has many times complained about this, tbh
[04:35] <kiko> but I haven't yet found a practical way to manage it
[04:35] <flacoste> we have a script that reports on the breadth of sample data
[04:35] <intellectronica> there are 2 things that can be done:
[04:35] <flacoste> we have lots of empty tables
[04:36] <kiko> one crazy idea is to not edit the sampledata file directly, but update it through "patches" too
[04:36] <mwhudson> i guess we could have a poll along the lines of "how many people knew that regular expressions can match in time exponential in the length of input?"
[04:36] <intellectronica> 1) treat sample data like we do tests - for every change in code you must have sample data that exercises it
[04:36] <jamesh> "make schema" doesn't give a good workout to the database patches
[04:36] <bac> the regex problem was triggered by a long string of '.' characters.  that would've been hard for anyone to anticipate.
[04:36] <jamesh> I am not sure how to handle that better
[04:36] <mpt> intellectronica, many tests create their own data
[04:37] <stub> jamesh: One of stagings functions is to excercise that.
[04:37] <intellectronica> mpt: so why not keep this data in the sample set?
[04:37] <jsk_> intellectronica: +1. Having case-specific sample data is useful for when you're testing through the UI.
[04:37] <kiko> mpt, intellectronica: again, one idea is to update sampledata via patches
[04:37] <mwhudson> i'm a little surprised the regexp problem didn't show up on staging, given how many times it happened this morning
[04:37] <kiko> that would avoid conflicts
[04:37] <stub> jamesh: It is just more noticable now that we are landing all the patches in a couple of days that where previously landed over a month.
[04:37] <kiko> mwhudson, me too
[04:38] <sinzui> mwhudson: That was not new code. That re was released in 1.1.6 I'm looking at the diff.
[04:38] <flacoste> mwhudson: LP devs are not interested in the same bugs than the general LP crowd
[04:38] <kiko> stub, to be honest, we have had /less/ problems this rollout than ever before, though :)
[04:38] <BjornT> intellectronica: updating sampledata is hard; it's also often more readable to create the data you need in the test, rather then relying on sampledata.
[04:38] <mwhudson> sinzui: surprising!
[04:38] <ddaa> BjornT++
[04:38] <kiko> mwhudson, sinzui: I thought that too when I was reading backlog
[04:38] <BjornT> intellectronica: in fact, relying on sampledata in tests is what makes it hard to update :)
[04:38] <intellectronica> BjornT: true, but it means that you don't accumulate useful data
[04:38] <kiko> BjornT, what about updating sampledata in patches?
[04:39] <mwhudson> was the bug that flattened us only filed today then?
[04:39] <ddaa> sampledata is painful, and more of it would likely not have detected the regex problem.
[04:39] <intellectronica> BjornT: I don't think that we should rely on it in tests, just that it should be there
[04:39] <kiko> I agree with ddaa there.
[04:39] <mpt> intellectronica, I think that's begging the question in the original sense (what do you mean by "useful")
[04:39] <kiko> ddaa, mwhudson: would having the staging hpss server solve this problem?
[04:39] <flacoste> intellectronica: what was your 2) idea?
[04:40] <kiko> ddaa, mwhudson: I mean, would it allow the branch type problem to be detected earlier?
[04:40] <ddaa> you mean our bazaar problem? It was not the regexp, another one. And no, it would not have been detected.
[04:40] <mwhudson> kiko: no, because (a) it's to do with the code import system and (b) because it was to do with different versions of the code on different systems
[04:40] <ddaa> it was caused by a version mismatch between importd and the rest of launchpad.
[04:40] <kiko> mwhudson, ddaa: I see
[04:41] <kiko> mwhudson, ddaa: so next cycle when tom updates everything in sync this will not happen?
[04:41] <barry> i think updating sampledata in patches is a good idea, /but/ i really dislike sampledata for the test suite.  it's okay for demo u/i's (in fact, quite nice), but i really don't like it for tests.
[04:41] <ddaa> actually, triggered by the mismatch
[04:41] <ddaa> kiko: that would avoid detecting it, but we should not have database default that we cannot get out through sqlobject in the first place.
[04:41] <kiko> barry, agreed
[04:41] <statik> did the data center just go down?
[04:41] <intellectronica> flacoste: my 2) idea was testing the sample data itself - check that we've got good coverage for enumerations, variations, constraints, etc - it can be automated (with some work)
[04:42] <jamesh> barry: some of our APIs (e.g. LaunchpadCelebrities) expect certain data to exist
[04:42] <mthaddon> statik: I can get to launchpad
[04:42] <flacoste> intellectronica: there is a start of that in utilities/check-sampledata.py
[04:42] <jamesh> barry: so we need some sample data
[04:42] <statik> mthaddon: yeah, I can get to devpad, just lost the canonical IRC server for some reason and got worried
[04:42] <stub> (I just lost canonical IRC too)
[04:42] <BjornT> kiko: i don't see how using patches to update sampledata makes it easier. the first thing we have to do is to rewrite our tests not to rely on sampledata.
[04:42] <flacoste> barry: and I really feel that we also need sample data for page tests
[04:42] <barry> jamesh: yep.  i'm not saying we should get rid of sampledata, but new tests should not rely on it (except for very specific cases of hardcoded stuff perhaps)
[04:43] <cprov> too
[04:43] <jtv> And the mailserver.
[04:43] <mpt> We should move on
[04:43] <jamesh> barry: no complaints there.  We probably have too much sample data.
[04:43] <barry> flacoste: pagetests should be treated just like demo u/i so... agreed!
[04:43] <ddaa> kiko: so to clarify, mthaddon rolling out importd would have avoided the oopses, but the underlying problem would have likely stayed undetected.
[04:43] <mwhudson> (...hm the problem comment that hit the regexp was posted in may...)
[04:43] <kiko> ddaa, undetected until when?
[04:43] <barry> flacoste: i really like being able to look at a page test, fire up launchpad.dev and try exactly the same thing via the browser
[04:44] <flacoste> BjornT: using patch to update sample data makes it easier to avoid conflicts in the file
[04:44] <ddaa> kiko: until whenever... maybe never.
[04:44] <mpt> kiko, perhaps you could discuss this with SteveA when he has a spare moment?
[04:44] <kiko> flacoste, exactly.
[04:44] <flacoste> barry: +1
[04:44] <kiko> ddaa, so the underlying problem is not a problem? :)
[04:44] <ddaa> it's like a landmine
[04:44] <kiko> mpt, sure. I just wanted to brainstorm.
[04:44] <ddaa> it's not a problem till you walk on it.
[04:44] <mpt> understood
[04:44] <BjornT> flacoste: right. but ime, that's not the biggest problem when updating sampledata.
[04:45] <BjornT> flacoste: it's easy enough to write a patch yourself that updates sample data.
[04:45] <ddaa> kiko: I do not think hoping nobody will walk of them is a good solution to the landmine problem.
[04:45] <mpt> Ok, time to move on
[04:46] <mpt> This can be discussed further after the meeting or on the mailing list
[04:46] <mpt> but meanwhile
[04:46] <mpt> == DBA report ==
[04:46] <mwhudson> mpt: +1
[04:46] <stub> DB patches where all applied as part of the rollout.
[04:46] <stub> We are not yet in db freeze - I'll turn it back on when launchpad/devel is open for normal landings.
[04:46] <stub> There where a number of new columns that needed to be landed unpopulated this cycle in order to keep the downtime minimal.
[04:46] <stub> Person.{personal_standing, mailing_list_auto_subscribe_policy,mailinglist_receive_duplicates,account_status} are all being populated as we speak.
[04:46] <stub> update-translation-credits.sql has been translated to friendlier python and being run as we speak (POSubmission and POMsgSet updates).
[04:46] <stub> Still need to populate the POMsgSet.language and trawl the patches looking for any I missed.
[04:46] <stub> NOT NULL constraints will be added where needed after the new columns have been populated, and hopefully landed before dbfreeze is reenabled.
[04:46] <stub> A database schema modification was just made to the Branch table (removing a DEFAULT). Although this was aparently extremly urgent, we might need to revert this change in line with release landing policy as this change may well have broken tests (and no tests where added obviously). Kiko?
[04:47] <kiko> well
[04:47] <stub> We can discuss that last after the meeting perhaps
[04:47] <kiko> I think removing the default was the right thing to do
[04:47] <kiko> but david now needs to produce an RC patch to fix this.
[04:47] <kiko> and yes, it needs to pass tests (but why wouldn't it?)
[04:48] <mpt> ok, thank you stub
[04:48] <mpt> == Blockers ==
[04:48] <matsubara> TEAM: infrastructure BLOCKED: no
[04:48] <mpt> Anyone have any?
[04:48] <stub> We obviously have code that creates branches without a branch_type, and this is causing trouble. Removing the default will cause this code to crash instead of insert broken data. So I expect some tests to now be failing, unless this is untested code.
[04:48] <jsk_> TEAM: Blueprints BLOCKED: No
[04:48] <BjornT> TEAM: bug tracker BLOCKED: no
[04:48] <jtv> TEAM: Translations BLOCKED: no
[04:48] <barry> TEAM: mailing lists BLOCKED: no
[04:48] <flacoste> TEAM: answers BLOCKED: no
[04:48] <mpt> TEAM: UI BLOCKED: no
[04:48] <salgado> Team: Registry BLOCKED: No
[04:49] <bigjools> TEAM: Soyuz BLOCKED: No
[04:49] <schwuk> TEAM: hwdb BLOCKED: No, although we could do with some more feedback on our specs
[04:49] <mwhudson> stub: again, this only happened when 1.1.6 importd code ran against 1.1.7  database
[04:50] <stub> mwhudson: ok. I wasn't following the details - had enough other distractions this evening :)
[04:50] <statik>  I thought we were only saying if we were blocked
[04:50] <statik> TEAM: Commercialization BLOCKED: no
[04:51] <kiko> I'm not blocking anyone?
[04:51] <kiko> with 500 unread emails?
[04:51] <kiko> wow
[04:51] <mpt> ok, people please read schwuk's specs :-)
[04:51] <mpt> but other than that, there appear to be no blockages
[04:51] <mpt> Thank you everyone
[04:51] <mpt> and sorry this went a little long
[04:52] <mpt> MEETING ENDS
[04:52] <matsubara> thanks mpt
[04:52] <jordi> kiko: sounds like you're not too useful! :)
[04:52] <flacoste> thanks mpt!
[04:52] <Rinchen> I'm blocked on SteveA but he has that in an email
[04:52] <kiko> schwuk, stub, adeuring: I want to talk about the hwdb next monday
[04:52] <schwuk> kiko: I'm off
[04:52] <kiko> ah
[04:52] <stub> kiko: What timezone you in Monday?
[04:52] <ddaa> TEAM bazaar: BLOCKED: no
[04:53] <ddaa> sorry, was engaged in chat with kiko in another channel
[04:53] <mwhudson> kiko: 500 mails is only like half an hour for you, surely? :)
[04:53] <schwuk> kiko: I'm around tomorrow, then not until a week on moday
[04:53] <schwuk> Monday
[04:53] <adeuring> kiko, schwuk: so perhaps earlier?
[04:53] <kiko> stub, in USA central time
[04:53] <kiko> adeuring, schwuk: I'll make a big effort to do it tomorrow morning my time.
[04:54] <schwuk> kiko: ok
[04:54] <adeuring> fine for me.
[04:54] <stub> kiko: ok. Give me as much notice as you can as the call will be late here
[04:55] <kiko> stub, yeah, I'll try to do it when I wake up, and we can try doing it on IRC.
[04:55] <stub> I've discovered I get better quality out of Skype than I do the Thai telephony system.
[04:55] <kiko> jtv too I suspect :)
[04:56] <stub> If he has got the wet string replaced with ADSL
[04:56] <tck> was there an update to launchpad recently?
[04:56] <jamesh> tck: yes
[04:56] <tck> hmm thought so
[04:56] <tck> text is alot bigger
[04:57] <kiko> mrevell, has the release gone out?
[04:57] <tck> also i cant list open bugs in ubuntu-website and ubuntu-documentation
[04:57] <tck> https://bugs.launchpad.net/ubuntu-website/ for example
[04:57] <kiko> tck, what happens?
[04:58] <tck> well theres usually an open in red, saying 'List open bugs' etc..
[04:58] <tck> now its gone
[04:58] <jamesh> tck: look to your right
[04:58] <tck> ahhh
[04:58] <kiko> tck, it moved
[04:58] <tck> its moved..
[04:58] <tck> :P
[04:58] <mrevell> kiko: Yeah, to the launchpad-users list, bcc'd to the usual places.
[04:59] <kiko> mrevell!
[04:59] <kiko> rock on
[04:59] <kiko> mrevell, did you follow that little list we have for it?
[04:59] <mrevell> kiko: Yep :)
[05:00] <kiko> rock ON!
[05:01] <mrevell> now for the blog
[05:15] <ubotu> New bug: #126991 in launchpad "Answer tracker message doesn't match the UI" [Undecided,New]  https://launchpad.net/bugs/126991
[05:19] <tck-afk> I notice that in the launchpad users page, under the confirmed email section
[05:19] <kiko> yes tck-afk?
[05:20] <tck-afk> long email address will go of the page?
[05:20] <kiko> flacoste, https://bugs.launchpad.net/launchpad/+bug/126991 
[05:20] <ubotu> Launchpad bug 126991 in launchpad "Answer tracker message doesn't match the UI" [Undecided,New]  
[05:20] <kiko> flacoste, didn't we RC a fix for that yesterday?
[05:20] <tck-afk> *off
[05:20] <flacoste> kiko: i don't remember you approving the rc... but sinzui did fixes that, so it's a dupe
[05:21] <superm1> also long source package names go off as well
[05:21] <superm1> ex: https://launchpad.net/ubuntu/+source/mythbuntu-default-settings/0.5-0ubuntu1
[05:21] <kiko> flacoste, rc=kiko for it.
[05:21] <flacoste> sinzui: ^^^
[05:21] <kiko> tck-afk, superm1: URLs?
[05:22] <superm1> kiko-afk, or https://launchpad.net/ubuntu/+source/mythbuntu-artwork-usplash
[05:24] <tck-afk> kiko-afk, this is not my page 
[05:24] <tck-afk> https://launchpad.net/~patrickcrowley
[05:24] <kiko-afk> superm1, where does that "go off the page"?
[05:24] <tck-afk> but gives an example
[05:24] <superm1> kiko-afk, the left protlet
[05:24] <tck-afk> if you go to confirmed email 
[05:24] <superm1> *portlet
[05:24] <superm1> "mythbuntu-artwork-usplash"
[05:24] <superm1> the title doesn't all fit in the greyish box
[05:24] <kiko-afk> right
[05:24] <kiko-afk> mpt, did you notice this?
[05:25] <kiko-afk>  ^^^
[05:26] <superm1> also it looks like my confirmed e-mail addresses, 2 of the 4 go off: https://launchpad.net/~superm1
[05:26] <kiko-afk> mpt, ^^^
[05:26] <kiko-afk> if mpt doesn't answer, please file bugs
[05:27] <tck-afk> kiko-afk, i have to go away now
[05:27] <tck-afk> want me to file one before i go?
[05:27] <tck-afk> or just wait
[05:28] <tck-afk> i'll file one quickly
[05:29] <superm1> mpt, bug 126997
[05:29] <ubotu> Launchpad bug 126997 in launchpad "Long source names don't fit in portlet" [Undecided,New]  https://launchpad.net/bugs/126997
[05:30] <tck-afk> shit
[05:30] <ubotu> New bug: #126993 in malone "bug body text font size recently changed to be annoyingly large" [Undecided,New]  https://launchpad.net/bugs/126993
[05:36] <ubotu> New bug: #126997 in launchpad "Long source names don't fit in portlet" [Undecided,New]  https://launchpad.net/bugs/126997
[05:36] <ubotu> New bug: #126998 in launchpad "Email addresses get truncated " [Undecided,New]  https://launchpad.net/bugs/126998
[05:44] <jkakar> Thank you thank you thank you for making the fonts bigger.  My eyes are very happy and I don't have to hit Ctrl-+ all the time anymore. :)
[05:45] <mwhudson> of course, people are complaining too, you can't win :)
[05:46] <RainCT> jkakar: well, I hate the new size :P
[05:47] <RainCT> btw, on bug reports on the left where it says "X source package in ubuntu", the text doesn't fit into the "button" with 1024x768
[05:48] <jkakar> RainCT: Oh. :(
[05:48] <jkakar> mwhudson: It needs to be a per-person configuration option!
[05:49] <RainCT> *agrees
[05:49] <mwhudson> well, it is, it just uses your browsers default sans serif font
[05:50] <RainCT> but the size doesn't change if I change it on the preferences (Firefox) :s
[05:51] <mwhudson> hm strage
[06:00] <ubotu> New bug: #127002 in launchpad "No vertical space between Add a comment/attachment and What's Next?" [Undecided,New]  https://launchpad.net/bugs/127002
[06:30] <Hobbsee> Bug 67790
[06:30] <ubotu> Launchpad bug 67790 in soyuz "non-release pockets should be available before release" [High,Fix committed]  https://launchpad.net/bugs/67790 - Assigned to Celso Providelo (cprov)
[06:34] <Hobbsee> nice lot of changes in that lot :)
[06:38] <kiko-afk> Hobbsee, :)
[06:39] <Hobbsee> kiko-afk: :)
[07:03] <ScottK> kiko-afk: Attachment added to Bug #127002
[07:03] <ubotu> Launchpad bug 127002 in launchpad "No vertical space between Add a comment/attachment and What's Next?" [Undecided,New]  https://launchpad.net/bugs/127002
[07:10] <kiko-afk> thanks ScottK 
[07:10] <ScottK> No problem.
[07:10] <kiko-afk> ScottK, can you shift-reload?
[07:11] <ScottK> I don't have that window open any more, but I can do it on another bug.
[07:11] <kiko-afk> please.
[07:11] <ScottK> Yes.  That made it look very different.
[07:11] <kiko-afk> thanks.
[07:11] <ScottK> Cached style sheet?
[07:12] <kiko-afk> it's a CSS caching problem which we will fix in about 4h in production.
[07:12] <ScottK> OK.
[07:12] <kiko-afk> thanks for filing the bug.
[07:12] <ScottK> No problem.
[07:13] <ScottK> I don't suppose (now that I've seen the new style sheet) there's any point in whining I liked the old one better?
[07:18] <kiko-afk> ScottK, give it two weeks first. :)
[07:18] <kiko-afk> changes are always annoying up-front.
[07:19] <ScottK> OK.  Well I still haven't gotten over the last big U/I change.
[07:20] <ScottK> Which broke LP on my Treo in addition to being a step back in my book.
[07:20] <ScottK> Maybe I'll feel different this time.
[07:21] <kiko-afk> give it two weeks, is all I ask for. 
[07:21] <ScottK> OK.
[08:16] <blueyed> Hi. Can someone tell me why the test cvs import failed for https://launchpad.net/b2evolution/trunk and https://launchpad.net/b2evolution/v-1-10?
[08:16] <kiko-afk> ddaa might
[08:17] <ddaa> I'll have a look.
[08:18] <blueyed> Thanks. I think it would make sense if the reason would get displayed there somehow. But you probably know that already.. ;)
[08:18] <ddaa> We totally know it and are actively reimplementing the whole code import infrastructure to fix that and other related problems.
[08:19] <kiko-afk> I believe that this requires some serious plumbing that ddaa is working on.
[08:19] <kiko-afk> right
[08:19] <ddaa> The current system was banged together using spit and duct tape in 2004...
[08:19] <blueyed> Great. Thanks a lot. You're all doing a great job on launchpad! :)
[08:20] <kiko-afk> thanks blueyed 
[08:21] <ddaa> I can find no good reason, except a typo in the cvsroot
[08:21] <ddaa> it's spelled :pserver:
[08:23] <radix> we need "Read More" to get some AJAX up ins
[08:23] <blueyed> Oh, damn. Seems you have fixed it already, ddaa and started it again. Thanks.
[08:24] <ddaa> blueyed: stay online, I'll keep you posted.
[08:24] <blueyed> kthx :)
[08:25] <ubotu> New bug: #127025 in malone "DB constraint triggered re-assigning sourcepackage bugtasks" [High,New]  https://launchpad.net/bugs/127025
[08:31] <ddaa> blueyed: https://launchpad.net/b2evolution/v-1-10 won't be imported
[08:31] <ddaa> because we only import cvs MAIN
[08:32] <blueyed> ok, ddaa. Then you can remove this series. Or should/can I?
[08:32] <ddaa> in the new system, you'll be able to record such informative cvs details in a series without requesting an import.
[08:32] <ddaa> No, I'll just mark it "do not sync"
[08:32] <blueyed> ok
[08:32] <ddaa> it's useful information to the community
[08:34] <ddaa> the main import is running, 5401 revisions to import on MAIN
[08:34] <ddaa> that will take... some time
[08:35] <ddaa> several hours
[08:35] <blueyed> No problem. I think it will work out now. Thanks again.
[08:36] <blueyed> Do I understand it correctly that I can then access this through bazaar, too?
[08:36] <blueyed> from http://bazaar-vcs.org/TrackingUpstream
[08:36] <ddaa> Yes, if the import succeeds (they do not all succeed), that will produce a bzr branch on launchpad that will be updated every 12 hours.
[08:36] <ddaa> If you want a different update frequency, you can ask us.
[08:39] <blueyed> great. 12 hours is fine for now. However, because this is readonly it might be better to use a cvs checkout in the "upstream" directory, where I can commit - if I want to commit something back to upstream, correct?
[08:39] <ddaa> yes
[08:40] <ddaa> the idea is that you can use the bzr branch to work on you own stuff more easily
[08:40] <ddaa> but to get the changes back into cvs you need to revert to the good old diff+patch method
[08:40] <ddaa> actually... not quite diff+patch
[08:41] <ddaa> "bzr merge" your feature into a pristine import branch, then "bzr diff", then "patch"
[08:41] <ddaa> so you can benefit from bzr goodness like weave-merge or extmerge to resolve conflicts.
[08:42] <blueyed> ..with the launchpad cvs branch, correct? If I have the cvs checkout in "upstream" it should be possible to commit/diff right from there, after merging from my "real" bazaar branch.. not?
[08:42] <ddaa> I am not sure what you mean.
[08:42] <ddaa> so you get an "import" bzr branch producted by launchpad.
[08:43] <ddaa> that you branch into a "feature" bzr branch, when you hack, commit, merge from "import", hack, commit, etc.
[08:43] <ddaa> Then you go into "import" and "bzr merge ../feature" and "bzr diff > ../feature.patch"
[08:44] <ddaa> Then you get a cvs checkout "upstream", and into "upstream" you can do "patch -p1 ../feature.path"
[08:44] <ddaa> then "cvs ci"
[08:45] <ddaa> if you do not commit in your bzr "feature" branch, you can just "bzr diff" without the "bzr merge" step. But then why would you use a bzr branch if not for offline commit?
[08:45] <ddaa> blueyed: hope I'm making sense to you.
[08:46] <ddaa> bzr cannot transparently interoperate with cvs the way it can do with svn (thanks to the bzr-svn plugin).
[08:47] <ddaa> And probably never will, for technical and cultural reasons.
[08:47] <blueyed> ddaa: I've meant to skip the launchpad cvs branch and just handle it like at the top of http://bazaar-vcs.org/TrackingUpstream - with a cvs checkout in "upstream" where I can commit (to cvs).
[08:48] <blueyed> I'll then merge from the "my-branch"/hack-branch to the upstream branch using bzr.
[08:49] <ddaa> I think you misread this page.
[08:50] <ddaa> One key sentence there is "In general, you should not be doing a bzr commit in upstream."
[08:50] <ddaa> If you use a launchpad import, you just "bzr pull" from launchpad to update upstream.
[08:50] <ubotu> New bug: #127027 in launchpad "The obfuscte_email method is inefficient" [High,Triaged]  https://launchpad.net/bugs/127027
[08:51] <ddaa> the "bzr merge" into upstream I mentioned is just a nice way to produce a diff you can apply into cvs.
[08:51] <ddaa> It should not be followed by a "bzr commit"
[08:55] <blueyed> ddaa: I don't want to bzr commit in "upstream", but cvs commit. Additionally, I would not pull the converted lp.net bzr branch, but creat it myself using "cvs co". I would update upstream using cvs up.
[08:55] <blueyed> I can then apply the diff to upstream using just bzr merge and cvs ci.
[08:56] <ddaa> I see.
[08:57] <ddaa> To do this, you would not use a launchpad import.
[08:57] <blueyed> yes.
[08:57] <ddaa> yes you would?
[08:57] <blueyed> No, I would not use the lp.net branch.
[08:57] <ddaa> right, the launchpad import
[08:58] <ddaa> You are reading the "Coverting and ignoring history" section right?
[08:58] <blueyed> yes.
[08:58] <blueyed> Except that I would also do cvs ci, sometimes.
[08:58] <ddaa> What is explained there is what you do when you do not have a real import system.
[08:59] <ddaa> So you get a "good enough" import by doing "cvs up; bzr commit -m 'updated from cvs'"
[08:59] <ddaa> which does not preserves the actual commits from the cvs repository.
[09:00] <ddaa> This setup is what some call a "hybrid tree", because it's both a cvs and a bzr tree.
[09:00] <ddaa> Launchpad does not produce hybrid trees.
[09:00] <ddaa> If you are using a cvs import from Launchpad, this section is not relevant.
[09:01] <blueyed> I see. I would not have the cvs history in bzr really. But not using the import system in my case seems easier, because I can commit right away. But using patches might be easy enough and it would give me the history.
[09:02] <ddaa> It's your choice, but you cannot really do both at the same time.
[09:02] <blueyed> Yes. I see. Thanks for making me understand it :)
[09:02] <blueyed> History is a good point. I've not thought about it.
[09:02] <ddaa> Because a bzr branch you created yourself with "cvs co; bzr init; bzr commit" won't bzr merge with the branch produced by launchpad.
[09:03] <ddaa> Glad to help. Sorry this all sounds so complicated.
[09:09] <blueyed> Maybe it would help to emphasize the history part on the wiki page?
[09:09] <blueyed> And display the different possibilities more distinctively.
[09:16] <a7p> hi everyone ... could anyone care for this  bug (which was posted as a question)? https://answers.launchpad.net/launchpad/+question/10042 - If no one can help - does anyone know where to go?
[09:20] <kiko-afk> let me see a7p 
[09:20] <kiko-afk> salgado, ^^^
[09:21] <Rinchen> ping beuno - lwn
[09:25] <salgado> kiko-afk, a7p, I'm afraid there's nothing we can do about that yet, although there's a bug reported already
[09:26] <a7p> salgado, okay, thanks ... just as a matter of interest - where would I have found this bug?
[09:27] <Rinchen> ping beuno - UWN that is
[09:28] <salgado> a7p, https://bugs.launchpad.net/launchpad/
[09:28] <beuno> Rinchen: pong
[09:28] <salgado> a7p, https://bugs.launchpad.net/launchpad/+bug/36966 is the actual bug. :)
[09:28] <ubotu> Launchpad bug 36966 in launchpad "When claiming a Launchpad profile it should be possible to turn it into a team" [High,Confirmed]   - Assigned to Guilherme Salgado (salgado)
[09:29] <a7p> thanks a lot .. @salgado & kiko-afk 
[09:29] <kiko-afk> most welcome
[09:29] <Rinchen> beuno, Hey Martin. Just wondering. Do you guys have a dedicated email for UWN submissions or is it still the webpage?
[09:29] <Rinchen> beuno, I know the joint fridge + marketing email address is still under discussion
[09:29] <beuno> Rinchen: I believe we are using the marketing-submission list, or maybe even (I prefer), de regular mailing list
[09:30] <ddaa> blueyed: it would certainly help to clarify any thing you found confusing.
[09:30] <ddaa> that's what wikis are for :)
[09:31] <Rinchen> beuno, ok, can you let me know the exact address please? I'd like to update my documents so you get the Launchpad release notes where you want them.
[09:31] <beuno> Rinchen: ubuntu-marketing@lists.ubuntu.com
[09:31] <Rinchen> great, thank you sir
[09:32] <beuno> Rinchen: np, and you can also add anything you like to the Launchpad section  :D
[09:33] <Rinchen> beuno, :-)  
[09:57] <doko> could somebody shed some light, why the recent finished gcj-4.1 build could not be uploaded on i386?
[09:58] <kiko-afk> cprov-out, bigjools-afk
[09:58] <kiko-afk> gar
[09:59] <kiko-afk> doko, can you call cprov please?
[09:59] <doko> kiko-afk: phone?
[09:59] <kiko-afk> yes
[09:59] <kiko-afk> doko, if it's a bug he has 1.5 hours to fix it.
[10:00] <Nafallo> kiko-afk: else? :-)
[10:00] <kiko-afk> well, else it will need to be cherrypicked which is more effort
[10:00] <kiko-afk> to fix it before we update to tip and unfreeze.
[10:01] <Nafallo> ah. I almost thought you were going medieval on his sorry ass ;-)
[10:01] <Nafallo> or what they say in pulp fiction :-)
[10:03] <kiko-afk> doko, that's a pretty mysterious email :)
[10:05] <doko> kiko-afk: cannot reach him, sent sms
[10:06] <matsubara> kiko-afk, doko: cprov-out will arrive home in a few minutes.
[10:06] <kiko-afk> thanks.
[10:09] <kiko-afk> matsubara, did you investigate the UFD issue we found there?
[10:09] <kiko-afk> in the OOPS report?
[10:10] <kiko-afk> matsubara, https://devpad.canonical.com/~jamesh/oops.cgi/2007-07-19/D1913
[10:11] <kiko-afk> matsubara, BjornT: aren't we migrating old statuses in bookmarks?
[10:14] <matsubara> kiko-afk: I checked them. they seem to be old bookmarks and bots
[10:16] <kiko-afk> matsubara, but I thought we were migrating old bookmarks.
[10:16] <kiko-afk> there is code to do that.
[10:17] <matsubara> kiko-afk: check BjornT's comment in https://bugs.launchpad.net/malone/+bug/62466
[10:17] <ubotu> Launchpad bug 62466 in malone ""Untriaged" to "Undecided" rename broke search form URLs" [Undecided,Incomplete]  
[10:18] <kiko-afk> matsubara, the OOPSes are related to the field status. now what?
[10:18] <kiko-afk> matsubara, I suspect something is not working as it should or..?
[10:20] <matsubara> kiko-afk: the link in that bug point to a URL that is broken
[10:20] <ubotu> New bug: #127055 in malone "Filtering on bug assignee A does not work in bug list of bugs related to team B" [Undecided,New]  https://launchpad.net/bugs/127055
[10:20] <matsubara> well not broken, but that will return UFD
[10:21] <beuno> is anyone aware that you get an ooops error when going into any translation page?
[10:21] <matsubara> Launchpad don't produce that URL anymore and at the time that bug was reported we didn't have the redirect old bookmarks to new one code.
[10:22] <matsubara> beuno: yes
[10:22] <kiko-afk> beuno, to distribution release translation pages, yes.
[10:23] <beuno> matsubara, kiko-afk, aaah, right, thanks  :D
[11:05] <cprov> doko: pong
[11:05] <doko> cprov: please see your email
[11:05] <cprov> doko: okay
[11:13] <kiko-afk> cprov, what do you think it looks like?
[11:14] <cprov> kiko-afk: dunno, running p-u manually to find out
[11:14] <cprov> kiko-afk: uncaught exception
[11:15] <kiko-afk> cprov, aha. what's the exception?
[11:17] <cprov> http://launchpadlibrarian.net/8528578/bGaHYteDriPOAPTAQLqCkK5lK1z.txt
[11:17] <cprov>  but it doesn't make sense
[11:19] <cprov> doko: ahh, much better now: "libgcj-doc_4.1.2-14ubuntu1_all.deb: Version older than that in the archive. 4.1.2-14ubuntu1 <= 4.2-20070719-0ubuntu1"
[11:20] <cprov> the upload command-line is insanely complicated ...
[11:20] <cprov> doko: is that true ?
[11:20] <doko> cprov: ok, thanks. yes, that makes sense
[11:21] <kiko-afk> cprov, why is that an uncaught exception?
[11:22] <doko> cprov: hmm, got the REJECTED mesage now as well
[11:22] <cprov> kiko-afk: it's not, the previous erros was a missing policy in the command-line
[11:22] <kiko-afk> cprov, is it a bug, or?
[11:22] <cprov> doko: yes, I've re-processed it manually 
[11:23] <cprov> kiko-afk: the bug only related with the fact the failure cause was not included in the notification
[11:26] <kiko-afk> cprov, ah, okay. would be nice to message that back then. is there a bug for that?
[11:26] <cprov> doko: can you please file a bug about this ?
[11:27] <cprov> kiko-afk: there will be in a second ...
[11:28] <cprov> kiko-afk: two solutions for this: 1. include a rejection note in the p-u output (which is included in the b-f-n) or 2. stopping calling p-u and deal with the NU object when upload incoming binaries.
[11:29] <kiko-afk> cprov, yeah, we starting considering 2. at some point.
[11:29] <doko> cprov: will do
[11:29] <cprov> now, I have to go again. Sorry. I'm late 
[11:29] <cprov> thank you for calling ... bye
[11:55] <ubotu> New bug: #127073 in blueprint "Retarget blueprint to non-existent crashes" [Undecided,Confirmed]  https://launchpad.net/bugs/127073