[12:18] <dilys> Merge to devel/launchpad/: Fix https://launchpad.net/products/launchpad/+bug/6429 (Links to consumed tokens generate 404 errors). r=jamesh (r3478: Guilherme Salgado)
[12:40] <kiko> matsubara, DUPEME: https://launchpad.net/malone/bugs/39293
[12:40] <Ubugtu> Malone bug 39293 in rosetta "No way to search for specific translated item" [Normal,Unconfirmed]  
[12:41] <matsubara> kiko: duped that one today in the morning.
[12:41] <kiko> rock and roll
[12:43] <kiko> don't you wish all our launchpad error reports were like the one on easter sunday? :)
[12:48] <sabdfl> kiko!
[12:48] <kiko> sabdfl, sabdfl, sabdfl!
[12:48] <sabdfl> happy easter, bunny
[12:49] <kiko> I refuse to be a bunny!
[12:49] <lifeless> kiko: dude, stop bouncing then :)
[12:49] <kiko> ai ai
[12:49] <sabdfl> mdz and i just toured the DC with james
[12:50] <kiko> isn't it lovely?
[12:50] <sabdfl> great work he and Znarl have been up to
[12:50] <kiko> yeah, they are busy bodies
[12:50] <kiko> okay, let me move out of the airport into the house
[12:51] <sabdfl> kiko: did stub decide if he was going to power ahead with zope3.2 tomorrow, in production?
[12:51] <lifeless> sabdfl: for your stuff I think he was going to cherry pick it
[12:52] <sabdfl> not likely
[12:52] <sabdfl> pretty big patch landed there, with lots of rf merges along the way
[12:52] <kiko> mmmm not sure
[12:52] <lifeless> oh? touches too much ?
[12:54] <sabdfl> mpt_ did a great job on the menu
[12:54] <sabdfl> looks much better
[12:54] <sabdfl> need to put proper links there though
[12:56] <erdalronahi> Hi all, hi doko
[12:56] <erdalronahi> I just tried to export some po-templates of OpenOffice2 in Breezy,
[12:56] <erdalronahi> but Rosetta "encountered" problems.
[12:57] <sabdfl> night all
[12:57] <erdalronahi> Unfortunately these templates are vital for us, since we (the Kurdish team) produce our GSI for upstream from them, 
[12:58] <erdalronahi> and the deadline for OOo 2.0.3 is in two days.
[12:58] <erdalronahi> Can anybody help with that? Maybe doko?
[01:04] <radix> Hi!
[01:05] <radix> I'm having trouble creating a branch for a team for a product, or something
[01:05] <lifeless> yup
[01:05] <lifeless> just waiting for ddaa to resume
[01:05] <radix> Branch URL is required (I've had other problems with this before), but lifeless is telling me I should be able to create a branch without specifying it
[01:06] <radix> ok
[01:06] <lifeless> historically we had that form set so you could create it with NULL
[01:07] <lifeless> which creates a team branch.
[01:08] <lifeless> ddaa: hi
[01:08] <ddaa> just for a moment ;)
[01:08] <lifeless> 09:04 < radix> Hi!
[01:08] <lifeless> 09:05 < radix> I'm having trouble creating a branch for a team for a product, or something
[01:08] <lifeless> 09:05 < radix> Branch URL is required (I've had other problems with this before), but lifeless is telling me I should be able to create a branch without specifying it
[01:09] <ddaa> Well, no, you should not.
[01:09] <lifeless> ddaa: I knew you'd know this
[01:09] <lifeless> ddaa: how do we do hosted branches now ?
[01:09] <ddaa> just push to sftp
[01:09] <radix> aha
[01:09] <radix> so, what's the format for pushing to a team SFTP URL, then?
[01:09] <lifeless> ddaa: oh. Can we -please- get a web ui for it back.
[01:09] <lifeless> ddaa: discoverability!
[01:09] <lifeless> radix: I'll show you in a sec
[01:10] <ddaa> sftp://bazaar.launcphad.net/~team/product/branch
[01:10] <radix> cool
[01:10] <ddaa> assuming you are a member of team
[01:10] <radix> yeah, I should be now
[01:10] <radix> hrm
[01:10] <ddaa> lifeless: I think I have work in the pipe that includes some text which explains that hosted branches are created by pushing.
[01:10] <radix> can a team create a branch for any product? cause I don't think I've done any explicit association between my team and my product yet
[01:11] <lifeless> ddaa: it forces people to use an awkward workflow.
[01:11] <lifeless> #1 go to the web
[01:11] <lifeless> #2 go to bzr, init, push
[01:11] <radix> oh right, --create-prefix.
[01:11] <lifeless> #3 back to the web to set the rest of the metadata
[01:11] <radix> ddaa: awesome
[01:11] <radix> ddaa: I'd be happy to review ;-)
[01:12] <ddaa> lifeless: the #1 is one-off, it's not part of the workflow
[01:12] <ddaa> and it's much less error-prone
[01:12] <ddaa> since once the branch has been set with a NULL url, you cannot edit it.
[01:12] <lifeless> ddaa: well, thats a different issue.
[01:12] <ddaa> are we talking about UI?
[01:12] <lifeless> ddaa: I think you should be able to unhost a branch - not delete, just move it to a new home.
[01:13] <lifeless> ddaa: and if you can do that, the branch url starting NULL is not a problem.
[01:13] <ddaa> yes, but it's not trivial, and IMO it's not worth the trouble right now
[01:13] <lifeless> that said, I think there should be a toggle for having a NULL branch - rather than just enter nothing, have a group, with a tick box for 'hosted' and a text field for 'mirrored'
[01:14] <ddaa> I thought about that at first, but writing a custom widget was too much trouble at the time
[01:14] <ddaa> lifeless: I think your point has merit, so please file bugs if you do not want to to be forgotten
[01:15] <ddaa> But the current UI is the best compromise I (in concertation with spiv, salgado, etc.) could come up with given the current constraints.
[01:16] <ddaa> for example, switching branches to/from hosted would require expensive, launchpad-driven, operations on the branch warehouse.
[01:17] <lifeless> nup
[01:17] <lifeless> it doesn't
[01:17] <ddaa> I knew you would disagree :)
[01:17] <lifeless> it *could*
[01:18] <cprov> good night, guys
[01:20] <ddaa> cprov: good night
[01:20] <ddaa> lifeless: at the very least, it would require implementing a garbage collector for the sftp area.
[01:20] <ddaa> could be a simple cron script
[01:20] <ddaa> hey mpt_
[01:20] <radix> mpt_: "damnitwhyamIupsoearlybuggrit"?
[01:20] <mpt_> comportment (k?m-p?rt'm?nt, -p?rt'-) n. Bearing; deportment.
[01:21] <mpt_> but I'm guessing it means something wildly different in French
[01:21] <ddaa> in french it means "behaviour" or "attitude"
[01:21] <mpt_> bug 39312 seems to be using it synonymously with "problem"
[01:21] <Ubugtu> Malone bug 39312 in konqueror "BAD tab comportements in Launchpad (and others)" [Normal,Rejected]  http://launchpad.net/bugs/39312
[01:22] <mpt_> Seveas, that's a slight bug in Ubugtu
[01:22] <ddaa> lifeless: essentially I agree with you on the desired functionality.
[01:23] <Seveas> mpt_, it currently sorts on severity first and status second
[01:23] <Seveas> I'm planning to make it a bit more intelligent
[01:23] <ddaa> lifeless: what I'm arguing is that the present UI is a reasonable way to present the _existing_ functionality.
[01:24] <ddaa> I'll be happy to discuss it when I come back from vacation, thursday.
[01:29] <lifeless> ddaa: thanks
[01:32] <mpt_> Seveas, cool
[01:37] <Seveas> turned out not to be a lack of intelligence but a bug, fixed
[01:37] <Seveas> it still is somewhat unintelligent, but I'm not too much in a hurry to fix it 
[04:34] <stub> Do we have a magic method to flush the SQLObject cache in tests that need to do so?
[04:35] <stub> nm... found it
[05:13] <dilys> Merge to devel/launchpad/: [trivial]  Person.is_valid_person should be false for teams (Bug 39241) (r3479: Stuart Bishop)
[05:49] <dilys> Merge to devel/launchpad/: [trivial]  Add explicit 'return None' to assignKarma (r3480: Stuart Bishop)
[06:51] <doko> erdalronahi: I currently can't do anything about the rosetta export problem, waiting we'll have to wait until the removal of the wrong message strings is finished. carlos and stub are working on it
[07:39] <mpt> Gooooooooooooooooood evening Launchpadders!
[08:46] <carlos> morning
[09:00] <SteveA> morning
[09:09] <stub> yo
[09:11] <carlos> stub: hi, sorry for not answering your email, I got the branch review and did all fixes I was asked for, but I'm getting weird test errors (looks like a bad conflict resolution with sample data) and my girlfriend was not happy with the idea of me working on holidays...
[09:12] <carlos> stub: I'm fixing the problem now and will ping you to execute it on production (after testing it on staging again)
[09:12] <stub> ok. So the only holdup is sample data? That shouldn't affect me running it for OOo
[09:13] <carlos> stub: that's what I think, but I want to be 100% sure
[09:13] <carlos> that script destroys data
[09:13] <stub> ok.
[09:14] <stub> Email me when you are done - hopefully I can run it tomorrow morning my time.
[09:14] <SteveA> mpt_: ping
[09:17] <SteveA> stub: voice call in a bit?
[09:18] <stub> SteveA: Sure.
[09:19] <carlos> stub: ok, thanks
[09:20] <stub> carlos: Or tonight if it doesn't take 7 hours to run on staging this time ;)
[09:20] <carlos> stub: well, I'm not sure it will be faster, but I'm not going to remove all templates we need to remove on production, I will test it only with a couple of POTemplates
[09:21] <carlos> if it works there, it should work for 10-13
[10:04] <erdalronahi> doko: good morning
[10:05] <doko> erdalronahi: good morning
[10:08] <mpt_> SteveA, pong
[10:08] <erdalronahi> doko: Maybe you have read my mail, we had serious problems with your script
[10:10] <doko> erdalronahi: I didn't claim it would be perfect, didn't see the failures you experience
[10:11] <erdalronahi> :) I'm sure you didn't
[10:11] <erdalronahi> Unfortunately I did. Now we are stuck up a bit,
[10:12] <erdalronahi> because the deadline of OOo 2.0.3 is tomorrow and I can't
[10:12] <erdalronahi> produce a GSI, let alone an up-to-date GSI
[10:13] <erdalronahi> I could not figure out what the script is supposed to do, else I would have done it "by hand" myself
[10:15] <doko> you can find the updated GSI here: http://people.ubuntu.com/~doko/GSI_ku_20060418.sdf
[10:17] <erdalronahi> doko: I am very grateful
[10:17] <doko> we currently cannot import the 2.0.3 templates into rosetta (not before dapper release), when the first OOo 2.0.3 is uploaded. but maybe carlos knows that better
[10:19] <carlos> doko: right, Ubuntu should not have .pot files that doesn't match what we have in Ubuntu
[10:20] <carlos> doko: I guess we don't have 2.0.3 in dapper, right?
[10:21] <erdalronahi> doko: the last time the GSI was 12,1 megabyte, now it is 4,4
[10:21] <erdalronahi> there seem to be some things missing
[10:21] <erdalronahi> it's not the en-US originals that are missing
[10:22] <doko> I check, that about 7800 translations in the po files are present in the GSI as well
[10:23] <doko> s /check/checked/
[10:24] <doko> carlos: right, but I'm talking about GSI files ;-P it should be safe to import these once the project is in string freeze
[10:24] <carlos> doko: Import the GSI files?
[10:24] <carlos> doko: we don't have a way to import them, It's a completely new feature we need to implement
[10:26] <carlos> doko: about your mail to upload a new OO file, we will execute it later today. I think you will be able to do the upload tomorrow morning (your morning)
[10:29] <erdalronahi> doko: 7800 may be correct, but why was the GSI so much bigger last time?
[10:29] <erdalronahi> And not only yours, the one Rail Aliev from OOo produced was even bigger, 14,4 MB
[10:31] <doko> it has only the en-US strings, for which you have translated strings
[10:31] <erdalronahi> ok, that's a sound explanation
[10:32] <erdalronahi> but it means you have used a different script now?
[10:34] <doko> no, apparently po2oo wants to have the template files saved with an .oo extension
[10:37] <erdalronahi> that is a good explanation why I got those "no template present" errors
[10:44] <SteveA> mpt_: skype call?
[10:48] <erdalronahi> doko: the translate-toolkit in Dapper (0.8rel) is newer than 0.8rc6? Does "rel" stand for release?
[10:50] <doko> erdalronahi: yes
[10:51] <erdalronahi> doko: so to use your script I have to rename all "pot" to "oo"?
[10:52] <mpt_> SteveA, sure
[10:53] <doko> erdalronahi: no, the sdf files
[10:54] <erdalronahi> well, I didn't come that fare, before I get there, the directory with the script and all subdirs are wiped out completely
[10:54] <erdalronahi> I reproduced that on two different computers
[11:16] <carlos> stub: hi, do you have 5 minutes to help me with a test that is failing with the new testing infrastructure? (it was working before)
[11:22] <SteveA> BjornT: voice call later (phone perhaps) ?
[11:25] <BjornT> SteveA: sure, either phone or skype.
[11:26] <stub> carlos: sure
[11:27] <stub> carlos: I probably need to see the test output and the setup and teardown methods being used.
[11:29] <carlos> stub: this is the test: https://chinstrap.ubuntu.com/~dsilvers/paste/filePN146I.html
[11:29] <carlos> stub: I think the problem is that I'm doing the SetUp and TearDown twice
[11:30] <carlos> stub: the problem is that the second SetUp is not restoring the database, and the test after "Or even a concrete language."
[11:30] <stub> I need the test output
[11:30] <carlos> is getting the database modifications done before
[11:30] <carlos> ok, let me run it again...
[11:31] <stub> Don't worry - I think I know what is going wrong
[11:31] <carlos> stub: https://chinstrap.ubuntu.com/~dsilvers/paste/file86S8sg.html
[11:34] <carlos> stub: what should I fix?
[11:34] <stub> from canonical.ftests.pgsql import PgTestSetup
[11:34] <stub> PgTestSetup._reset_db = True
[11:35] <stub> What is happening is that database changes are not being noticed, as they are being made by a subprocess, so the database is not being reset.
[11:35] <carlos> oh
[11:35] <stub> carlos: Put those lines before the tearDown
[11:36] <carlos> Ok
[11:36] <carlos> thanks
[11:36] <stub> I think I have worked out how to fix this ad hope to sort this when improving the test fixtures.
[11:37] <carlos> ok, thanks
[11:40] <carlos> stub: in fact... it was breaking the next test
[11:41] <carlos> I guess we should add it always before the tearDown if we test a script, even if we execute the setUp and tearDown just once, right?
[12:14] <stub> So what happens when I push a --lightweight checkout to rocketfuel?
[12:14] <stub> c/rocketfuel/chinstrap
[12:19] <BjornT> stub: don't know, i would suggest pushing the whole repo instead
[12:20] <stub> So commits to the lightweight branch are actually committed to the repo, and then you push the repo as a whole. I see.
[12:20] <BjornT> yeah
[12:36] <lifeless> stub: right
[12:39] <sabdf1> stub: are you planning a rollout today?
[12:40] <sabdf1> i'm keen to send off a note w.r.t. dapper+1 specs that depends on the rollout
[12:40] <stub> sabdf1: Yes. Just deciding on what revision. Thinking about r3473
[12:41] <carlos> jamesh: hi, around?
[12:41] <jamesh> carlos: yeah
[12:42] <carlos> jamesh: Seems like I did a small mistake this weekend and merged from rocketfuel in the middle of fixing a branch you reviewed
[12:42] <carlos> jamesh: I was planning to send you a diff with the changes I did after the review
[12:43] <carlos> but I don't see a way to do it... Do you mind if I send you a diff against rocketfuel?
[12:43] <jamesh> carlos: that's fine.  Alternatively if you've pushed to chinstrap I should be able to see that diff on the pending reviews page
[12:44] <carlos> jamesh: you have there partial changes, I just did the final ones and I guess it would take some time to get the pending reviews page updated, but whatever you prefer
[12:44] <jamesh> carlos: in that case, send me the diff
[12:45] <carlos> ok
[12:51] <sabdf1> stub: does that include mpt's nice menu improvement, and my milestone landing?
[12:56] <stub> sabdfl: That would be r3473 and r3474. They can go in too if you are confident they are solid.
[12:56] <stub> Most developers will not have tested it though as yesterday was a holiday for most
[12:57] <sabdf1> stub: yes, they are solid
[12:57] <stub> (But then again, same goes for the Sunday code I was considering...)
[12:57] <stub> ok.
[12:57] <sabdf1> ok, thanks!
[12:57] <sabdf1> pls ping me when it's out so i can send that mail
[01:10] <carlos> stub, anyone else: Is there any problem if I turn off staging for 10 - 15 minutes to merge one of my branches and test a script there?
[01:10] <stub> No problem here
[01:23] <SteveA> Seveas: around?
[01:24] <Seveas> yes
[01:31] <lifeless> BjornT: could you do me a favour ?
[01:32] <BjornT> lifeless: maybe :) what do you want me to do?
[01:32] <lifeless> allocate the current pending reviews to folk
[01:33] <BjornT> sure
[01:33] <lifeless> thanks - I owe you one
[01:33] <lifeless> tchau eveyone
[01:38] <carlos> hmm, seems like staging will take a bit more to be back
[01:38] <carlos> the bzr merge says that it would take 45 minutes....
[01:39] <stub> BjornT: My branch in unassigned is a fix for the topcrasher and small
[01:41] <BjornT> stub: ok, i can review it today then if you send me a diff. it shows up as already merged, though, can you check out why?
[01:42] <lifeless> BjornT: you haven't pushed it ;0
[01:44] <stub> My bad
[01:45] <cprov> morning, hackers
[01:45] <mpt> hi cprov, there's an urgent bug for you
[01:46] <cprov> mpt: tell me which one
[01:47] <mpt> "Can I please have a fix for this available somewhere on drescher by the end of Tuesday? We *need* to have this fixed for beta." -- bug 37156
[01:47] <Ubugtu> Malone bug 37156 in qprocd "can't change sections or priorities with change-override.py" [Major,In progress]  http://launchpad.net/bugs/37156
[01:48] <cprov> mpt: I've sorted this with Kamion yesterday, landed a workarrounded script in drescher for him, I'm reimplementing new version right now
[01:49] <cprov> mpt: my fault, must update the bug info :(
[01:51] <mpt> ok, no worries, just saw it hanging there :-)
[01:52] <carlos> lifeless: https://chinstrap.ubuntu.com/~dsilvers/paste/filewRqTXf.html
[01:52] <carlos> lifeless: any idea about that one?
[01:52] <lifeless> carlos: looks like a corrupt branch
[01:52] <lifeless> are you using a shared repository ?
[01:52] <carlos> not yet
[01:53] <cprov> mpt: bug info up to date, thank you for the heads up 
[01:54] <carlos> lifeless: what could I do to fix it (and help you to debug the problem that caused it)?
[01:55] <lifeless> carlos: report it on #bzr
[01:55] <lifeless> carlos: file a bug
[01:56] <lifeless> what it indicates is that a revision referenced in that branch is not in the storage for the branch.
[01:56] <carlos> lifeless: and is there a fast solution to be able to merge that on staging?
[01:57] <lifeless> carlos: your branch is corrupt
[01:57] <lifeless> carlos: you need to fix that, which probably involves remirroring it
[01:57] <carlos> I guess I would need to get a diff and create a new one...
[01:57] <carlos> oh, so it's a problem with the mirror?
[01:57] <dilys> Merge to devel/launchpad/: [trivial]  expose destroySelf() through the IRevisionNumber interface (r3481: James Henstridge)
[01:57] <carlos> I mean, it would be a problem with the mirror?
[01:58] <lifeless> its a problem with sftp://carlos@chinstrap.ubuntu.com/home/warthogs/archives/carlos/launchpad/bug-32610/
[01:58] <lifeless> probably
[01:58] <carlos> lifeless: I had a network problem pushing that branch, but I thought that a new push would fix anything broken ...
[01:59] <lifeless> carlos: how do you push? rsync or sftp ?
[01:59] <carlos> rsync
[01:59] <lifeless> it should yes
[02:01] <carlos> is there any way to test my local branch to know if it's a problem with my branch instead of the mirror?
[02:02] <lifeless> bzr check
[02:17] <carlos> lifeless: it ends killed
[02:18] <carlos> that smells like somethig is wrong with my branch :-(
[02:20] <lifeless> probably out of memory
[02:20] <lifeless> weave check can do that I hear
[02:21] <lifeless> its late here and I'm really beat
[02:21] <lifeless> can you please seek help on #bzr?
[02:22] <lifeless> night all
[02:29] <carlos> sure
[02:29] <carlos> lifeless: thanks
[02:29] <carlos> lifeless: and night
[02:47] <stub> Kinnison, cprov: I'm disabling the ftpmaster stuff on drescher in preparation for an update.
[02:47] <cprov> stub: okay
[02:47] <stub> cprov: Do you want the code updated too? Or should we keep running the existing code
[02:47] <cprov> stub: we need code update 
[02:52] <stub> Launchpad will be going down in 15 minutes for a regular code update. Estimated downtime is 10 minutes. Wikis will be in read only mode during this period.
[03:20] <stub> Kinnison, cprov: Soyuz stuff should all be online again
[03:20] <cprov> stub: thank you 
[03:34] <jamesh> cprov: are you still involved with the CoC code?
[03:34] <cprov> jamesh: UI code, when I have time
[03:34] <cprov> jamesh: I've seen bug 39547
[03:34] <Ubugtu> Malone bug 39547 in launchpad "Code of Conduct 1.0.1 signatures not accepted" [Normal,Confirmed]  http://launchpad.net/bugs/39547
[03:35] <cprov> jamesh: not sure if I'll have time for it today
[03:35] <jamesh> It looks like changing CodeOfConductConf.currentrelease to '1.0.1' would make 1.0.1 signatures work (and stop 1.0 signatures from being accepted)
[03:36] <cprov> jamesh: yes
[03:37] <jamesh> but it seems a bit weird that https://launchpad.net/codeofconduct/1.0.1/+sign expects a signed 1.0 CoC
[03:37] <cprov> jamesh: I wonder if we can make this system better, maybe replace this code by a config section
[03:37] <jamesh> and after updating current version to 1.0.1, https://launchpad.net/codeofconduct/1.0/+sign would expect a 1.0.1 signature
[03:38] <cprov> jamesh: yes, it's wrong, old CoC version should not traverse to +sign
[03:39] <cprov> jamesh: what do you think ?
[03:40] <jamesh> cprov: ideally the 1.0 CoC should point people at the 1.0.1 CoC for signing
[03:41] <jamesh> cprov: if we only have a single CoC, I'd expect to have https://launchpad/codeofconduct/+sign (no version number)
[03:42] <jamesh> or if we have multiple CoC series, https://launchpad/codeofconduct/$cocseries/+sign
[03:42] <elmo> stuuuuuuuuuuuub
[03:42] <cprov> jamesh: makes sense, "Sign the current version", maybe "Read the old versions"
[03:42] <stub> elmoooo!
[03:42] <jamesh> cprov: to top it off, mpt would like to see this stuff under /people/$user/...
[03:43] <jamesh> (at least the signing UI)
[03:43] <elmo> stub: never mind
[03:43] <mpt> your signatures in /people/you/+signatures, and the Ubuntu CoC in /distros/ubuntu/+coc/1.0.1
[03:44] <cprov> jamesh: feasible, summarizing CoC system needs some hours of love
[03:44] <cprov> mpt: so you mean CoC you be oriented by distribution ?
[03:45] <mpt> cprov, or product or project
[03:46] <cprov> mpt: uhm, that's a nice decision, we missed it from the original implementation 
[03:46] <zul> ./whois kiko
[03:46] <zul> oops...
[03:46] <mpt> cprov, either that, or we say "right, CoC's an Ubuntu-only thing", and put it at conduct.ubuntu.com similar to ShipIt
[03:47] <cprov> mpt: the last should make people less scared for now
[03:48] <cprov> mpt: not sure if project/product admins will fill comfortable to manage CoC things at all (yet)
[03:49] <jamesh> mpt/cprov: it is something that needs some specing (plus decisions on what is worth spending time on to support).
[03:49] <mpt> yeah
[03:50] <cprov> jamesh/mpt: what about have a meeting with SteveA/kiko about the conduct.ubuntu.com idea ?
[03:50] <mpt> yes, or maybe bring it up at the LP meeting
[03:51] <mpt> We probably need whatever evidence there is of the CoC working for Ubuntu
[03:51] <mpt> (has it been enforced? Is it a good persuasive tool? etc)
[03:51] <mpt> to know whether it's worth letting everyone else have one
[03:51] <jamesh> cprov: moving it to a separate site sounds like it would be a similar amount of work to allowing multiple CoCs (especially if you include the work the admins would need to do to get the separate site up and running with SSL, etc)
[03:51] <stub> elmo: If I'm supposed to be able to log in to carbon, I can't; it doesn't seem to have my key.
[03:52] <elmo> stub: yeah, it won't yet - I've "borrowed" it for preview on thursday
[03:52] <stub> elmo: No probs
[03:53] <jamesh> elmo: a few months ago you reported https://launchpad.net/products/launchpad/+bug/30276.  Do you remember enough about what you did to answer the question I asked in a comment?
[03:53] <Ubugtu> Malone bug 30276 in launchpad "launchpad claims a key is expired when it's not" [Major,Needs info]  
[03:54] <elmo> jamesh: I suspect it was after - I didn't notice the key had expired until the (old dak-based) archive broke
[03:54] <elmo> gar, why can't you reply to specific comments through the web-ui
[03:54] <cprov> jamesh: maybe, sounds like we are swapping coding time by DC-admin time; don't know need focused discussion.
[03:55] <jamesh> elmo: okay.  I'll dupe it then.
[04:00] <zul> is there any launchpad admin's around that can merge 2 accounts for me?
[04:02] <Kinnison> Is there a reason why you cannot merge them yourself?
[04:02] <zul> yeah i dont have access to one of the email addressess anymore
[04:03] <Kinnison> aah, yes
[04:03] <zul> zul is the old one and i want it to be merged with zulcss
[04:03] <Kinnison> zul: you probably need one of lifeless or stevea
[04:04] <Kinnison> kiko may also know how to do it
[04:04] <Kinnison> s/admit/admin/
[04:04] <zul> ok...ill just wait around for kiko then
[04:04] <tseng> steve did it for me
[04:05] <tseng> send him a gpg signed request with both account names
[04:05] <tseng> is the key on both of them?
[04:05] <zul> just one of them
[04:06] <tseng> the lost one, or the good one?
[04:07] <zul> the good one
[04:07] <tseng> cool
[04:08] <zul> tseng: the bad one has my gentoo account and im pretty sure it has been retired
[04:26] <carlos> stub: still around?
[04:26] <stub> carlos: yes
[04:26] <carlos> stub: could you take a look to pqm?
[04:27] <carlos> seems like it's stalled, we got a confirmation of current task about 2 hours and a half
[04:27] <carlos> ago
[04:27] <mpt> so, that's pretty cool
[04:27] <mpt> Launchpad is censoring the FAQ
[04:28] <carlos> mpt: I see it...
[04:28] <mpt> by not linking to it on half the pages in Launchpad
[04:28] <stub> carlos: it is busy doing stuff - I think the 'push to chinstrap' stage. You sure about that  2 hours?
[04:29] <carlos> mpt: oh
[04:29] <carlos> stub: that or we got the same merge request twice
[04:30] <carlos> stub: I got the email from arch-commits mailing list two hours and a half ago
[04:31] <stub> Hmm... not pushing to chinstrap - no activity on that box...
[04:37] <stub> ok. Can't see anything to do except kill it :-(
[04:38] <carlos> stub: Can you do the push manually? or next merge will do that push?
[04:38] <carlos> or will be that merge lost?
[04:40] <stub> carlos: The merge never completed - it didn't get to the push stage. So there is nothing new to push.
[04:40] <stub> pqm is retrying the job now.
[04:41] <carlos> ok
[04:41] <carlos> stub: thanks for looking at it
[04:48] <SteveA> zul: hello
[04:49] <zul> hi SteveA 
[04:50] <SteveA> let's talk in private about your account merging issues
[04:50] <zul> sure..
[04:50] <mpt> SteveA, bug 40014 is very strange, I think it might be Zope
[04:50] <Ubugtu> Malone bug 40014 in launchpad "Variable chunks (e.g. FAQ link) missing from pages' footer" [Normal,Unconfirmed]  http://launchpad.net/bugs/40014
[05:07] <BjornT> mpt, SteveA: yes, it is zope, it happens every time zope inserts a <base> tag. it doesn't update the content-length header after doing so.
[05:11] <SteveA> aw crap
[05:11] <SteveA> BjornT: any idea if this is fixed with zope3.2
[05:11] <SteveA> ?
[05:14] <BjornT> SteveA: it doesn't seem to be fixed, but i'll write a test just to make sure.
[05:14] <SteveA> ok
[05:14] <SteveA> this can go straight upstream, of course
[05:21] <SteveA> as a workaround, add whitespace crap at the end of the main template ;-)
[05:29] <BjornT> SteveA: i have a test now that confirms that it's not fixed. do you want me to fix it?
[05:35] <SteveA> please
[05:35] <SteveA> if you fix it upstream, then we can also apply the diff to our Zope
[05:36] <SteveA> or do it the other way around, if you prefer
[05:37] <BjornT> i'll fix it upstream first since i have zope3 trees already set up.
[05:38] <SteveA> ok
[05:40] <stub> quick fix is to trash the content-length header
[06:30] <BjornT> stub: can you please pull r67079 from upstream zope3? it fixes bug 40014, and the diff is at https://chinstrap.ubuntu.com/~dsilvers/paste/fileo1sNuL.html
[06:30] <Ubugtu> Malone bug 40014 in launchpad "Variable chunks (e.g. FAQ link) missing from pages' footer" [Normal,In progress]  http://launchpad.net/bugs/40014
[06:36] <SteveA> BjornT: looks good to me.  r=me
[06:40] <BjornT> cool
[06:41] <BjornT> SteveA, stub: btw, did you see my patch i sent to launchpad-reviews? it gets rid of the annoying warnings produced when running page tests?
[06:46] <SteveA> what kind of warnings?
[06:46] <SteveA> i saw that it was a very minimal patch
[06:48] <BjornT> SteveA: bug 39426
[06:48] <Ubugtu> Malone bug 39426 in launchpad "Running page tests produces lots of warnings" [Normal,Unconfirmed]  http://launchpad.net/bugs/39426
[06:49] <SteveA> is this since zope3.2 ?
[06:50] <SteveA> your fix looks okay, if you add a comment saying something like "tell our custom database adapter that the request has started"
[06:52] <SteveA> do we get the same warnings on staging, i wonder
[06:52] <BjornT> SteveA: yeah, i think so. i would guess that the set_request_started() call was removed by accident or something like that. i couldn't find any other place where that method was called.
[06:53] <SteveA> it could mean that the request timeout stuff hasn't been working properly
[06:53] <SteveA> and isn't working properly in production right now
[06:54] <SteveA> in which case this should get cherry-picked
[06:56] <BjornT> yeah could be, i'm not sure how to test if the timeout stuff is working properly, though.
[07:04] <SteveA> see if we get tons of warnings in the production logs
[07:04] <SteveA> see if we've had any timeout oopses
[07:05] <jordi> I generated a few the other day
[07:06] <jordi> https://launchpad.net/people/jordi/+translations does it
[07:06] <jordi> but this is known
[07:09] <BjornT> the timeout stuff probably is broken then, https://launchpad.net/people/jordi/+translations takes around 25 seconds to render, but it doesn't time out.
[07:10] <jordi> it did the other day
[07:10] <jordi> it worked for me now as well
[07:11] <jordi> kiko is working on a new page for that
[07:29] <carlos> jordi: it depends on the load of the server
[07:31] <jordi> I figured
[07:31] <jordi> ok, time to leave office
[07:31] <jordi> laters
[07:31] <carlos> see you later
[08:26] <Seveas> SteveA, ping
[08:27] <SteveA> Seveas: pong
[09:55] <dguido> The page on the wiki is not complete, does anyone know where i can get an architecture overview of Malone?
[10:00] <dguido> I'd like to specifically know how the branching of new distributions works and how new distros stay maintained with continually updated sources from upstream.
[10:18] <kiko> e-hello
[10:24] <Seveas> jamesh, ping
[10:24] <kiko> SteveA, ping
[10:32] <dilys> Merge to devel/launchpad/: [trivial]  expose destroySelf() through the IRevisionNumber interface (r3481: James Henstridge)
[10:32] <kiko> yay
[10:32] <kiko> oh that's weird
[10:32] <kiko> two commits
[10:32] <kiko> but same number
[10:33] <kiko> did pqm drop the first?
[10:39] <BjornT> kiko: yes, something went wrong with the first merge request
[10:39] <kiko> I see
[10:49] <kiko> cprov, "qprocd"? not "launchpad-qprocd"?
[10:50] <cprov> kiko: duderino, don't blame me ;)
[10:51] <kiko> matsubara, ping?
[10:52] <kiko> matsubara, can you verify bug 6010 is actually fixed-in-production?
[10:52] <cprov> kiko: I preffer launchpad prefix too, but I'd really like another fancy name like 'librarian' or 'supermirror' 
[10:52] <Ubugtu> Malone bug 6010 in malone "error when putting non-number into bug number field: OOPS-B192" [Major,Fix committed]  http://launchpad.net/bugs/6010
[10:52] <kiko> I don't dislike qprocd
[10:52] <kiko> just..find it odd that it doesn't refer to lp
[10:52] <kiko> maybe you're right
[10:57] <cprov> kiko: but I won't fight against this new name/standard. It's weird, but harmless  
[10:57] <matsubara> kiko: it's working and I changed the bug status to Fix Released
[10:58] <kiko> matsubara, I just tested in production following the steps reported and got the same 404
[11:02] <matsubara> kiko: hmm, we don't have a custom bug not found page. The fix for that bug was to make the bug field accept bug nicknames too.
[11:03] <kiko> that's not the entire bug, though
[11:03] <kiko> read the description
[11:04] <matsubara> I see. Should I re-open it or open a new one requesting a custom bug not found page?
[11:05] <kiko> I'd reopen it
[11:10] <matsubara> kiko: it doesn't belong to the oops milestone anymore, right? What about the severity?
[11:10] <kiko> matsubara, you are somewhat right (though it causes 404s) -- severity Normal.
[11:12] <matsubara> kiko: what milestone do you suggest? 1.0?
[11:13] <kiko> matsubara, later or none
[11:14] <kiko> does anyone know if today's the first day we're running on the new zope?
[11:26] <mdke> carlos, jordi, around?
[11:27] <jordi> yes
[11:27] <carlos> mdke: hi
[11:27] <carlos> kiko: no idea, sorry
[11:27] <mdke> wow, 2 for the price of one
[11:27] <carlos> :-P
[11:27] <carlos> mdke: sorry, you have only half of me...
[11:27] <mdke> if I upload an updated pot template, with lots of changes to line numbers, but very few changes to strings, do the strings get merged automatically, or do translators have to redo them?
[11:27] <mdke> carlos, half is enough
[11:28] <carlos> mdke: what do you mean by line numbers?
[11:28] <mdke> carlos, :
[11:28] <mdke> -#: C/config-system.xml:1069(para) 
[11:28] <mdke> +#: C/config-system.xml:1084(para) 
[11:28] <carlos> that will not affect translations at all
[11:28] <mdke> same msgid
[11:29] <carlos> only the msgid changes are 'bad' for translators
[11:29] <mdke> good, thanks v much, as usual
[11:31] <carlos> mdke: you are welcome
[11:32] <carlos> mdke: btw, I owe you an email answer... I will try to send it tomorrow, now that I'm done with the OO fixing
[11:32] <carlos> sorry for the delay...
[11:32] <mdke> carlos, no problema
[11:33] <mdke> carlos, who can upload pot templates to distros/ubuntu/+source/kubuntu-docs/+translations?
[11:34] <jordi> the owner of the template, usually
[11:34] <jordi> who is it?
[11:34] <mdke> lemme see
[11:35] <BjornT> kiko: yes, today is the first day we're running on zope 3.2
[11:35] <mdke> jordi, rosetta administrators
[11:35] <kiko> how does it feel? any major differences?
[11:36] <jordi> mdke: hmm, why is it rosetta admins?
[11:36] <carlos> mdke: I think we talked about give you the ownership until I add rights to all Ubuntu uploaders 
[11:36] <carlos> jordi: automatic imports
[11:36] <carlos> jordi: by default we use that owner
[11:37] <mdke> carlos, yes, did that happen?
[11:37] <jordi> oh, I thought it had been transfered to them
[11:37] <carlos> mdke: no, doing it atm...
[11:37] <tortho> A question about Rosetta... I have translated a lot of the Schoolbell package for dapper, but when i go to the main rosetta page and navigate to schoolbell, and then norwegian, i can se that it is not translated at all, is it possible to transfer in some way?
[11:37] <mdke> actually np, Riddell is going to upload a new package with the pot
[11:38] <carlos> mdke: we prefer the package path, but is ok to do the manual upload
[11:38] <carlos> mdke: could you remind me the owner we should set there?
[11:38] <BjornT> kiko: so far i haven't seen much difference. one or two bugs have been found related to it, though.
[11:38] <kiko> I haven't seen much difference either
[11:39] <mdke> carlos, let's just leave it, the package path is better, as you say
[11:39] <carlos> mdke: is better but it's slow and I understand that it would be a problem for you
[11:39] <carlos> mdke: it will not cause any problem
[11:40] <mdke> ubuntu-doc?
[11:49] <carlos> there are two teams related to ubuntu-doc...
[11:49] <carlos> ubuntu-doc
[11:49] <carlos>     Ubuntu Documentation Project
[11:49] <carlos> ubuntu-doc@lists.ubuntu.com
[11:49] <carlos>     Ubuntu Documentation Team 
[11:49] <carlos> that's weird...
[11:50] <kiko> should be merged
[11:50] <carlos> you should have just one team...
[11:51] <mdke> carlos, kiko, there's a bug about it
[11:51] <kiko> yeah
[11:51] <mdke> kiko, if you wanna do your bug magic on it, it's been open a while
[11:51] <mdke> ;)
[11:51] <kiko> remind me what bug number it is, mdke?
[11:52] <mdke> https://launchpad.net/malone/bugs/29177
[11:52] <Ubugtu> Malone bug 29177 in launchpad "Allow merging of teams (and specifically merge ubuntu-doc and ubuntu-doc-lists)" [Normal,Confirmed]  
[11:52] <mdke> carlos, the first one is right
[11:52] <kiko> thank you
[11:52] <mdke> i think ;)
[11:52] <carlos> ok
[11:53] <carlos> mdke: kubuntu ownership changed
[11:53] <mdke> merci
[11:55] <Seveas> kiko! You broke more of my account 
[11:55] <kiko> Seveas, I didn't do anything else, but I did notice your calendar was bustificated!
[11:55] <Seveas> kiko, the wiki thinks I no longer have an e-mailaddress
[11:55] <Seveas> I can login though
[11:55] <kiko> wow, that's weird
[11:55] <kiko> really?
[11:56] <Seveas> but subscribe won't work
[11:56] <Seveas> well, I was still logged in
[11:56] <Seveas> will try logout+login
[11:57] <carlos> mdke: and ubuntu-doc should be fixed tooo
[11:57] <Seveas> kiko, yes I can login with it
[11:57] <mdke> carlos, merci BEAUCOUP
[11:58] <kiko> Seveas, I can't see how it can't find your email address
[11:59] <Seveas> kiko, hmm, now it CAN find it but my list of subscriptions is missing...
[11:59] <Seveas> seems to be a session/cookie issue
[11:59] <kiko> odd
[11:59] <Seveas> anyway: it got busted but is now fixable by myself
[11:59] <kiko> sorry bout that once more
[11:59] <Seveas> kiko, AH! wait
[12:00] <Seveas> when I edit my profile it complains again
[12:00] <kiko> complains?
[12:00] <Seveas> This list does not work, unless you have entered a valid email address!
[12:01] <kiko> where is that?
[12:01] <Seveas> on the UserPreferences page
[12:01] <kiko> that's very very odd
[12:01] <Seveas> kiko, can you please edit wiki.ubuntu.com/FreeNX, just add a few letters
[12:01] <Seveas> let's see if it mails anyway
[12:02] <kiko> changed... DanielHolbach2, Vorik, OttoKeklinen, JunKobayashi, MarcAbramowitz, AndrewMitchell: Mail sent OK
[12:02] <kiko> mmmm
[12:02] <kiko> what's your wikiname?
[12:02] <Seveas> DennisKaarsemaker
[12:05] <kiko> Seveas, seems like you've run into an odd bug.. I don't quite understand how this could happen because the authserver can't lie about it, but if you could file a bug explaining the problem we'll have spiv look into it.
[12:05] <tortho> Is it possible to download a po file for a Dapper package, and upload it to the main package to transfer the translation?
[12:05] <Seveas> kiko, will do
[12:06] <mdke> tortho, it's done automatically