[12:26] <sabdfl> has anyone else seen test failures doubled up with make check>
[12:26] <sabdfl> ?
[12:31] <kiko> sabdfl, not me
[12:31] <kiko> sabdfl, what I have seen are librarian failures
[12:31] <kiko> but they don't occur reliably
[12:31] <sabdfl> i see the same set of failures, twice
[12:31] <sabdfl> am refueling now to see if that's fixed
[12:32] <kiko> odd.
[12:32] <sabdfl> it was almost as if the test suite was being run twice
[12:33] <sabdfl> kiko: we should figure out a way to produce an RF repo that has been beaten up to represent three years of dev
[12:33] <sabdfl> i.t.o. commits, branches etc
[12:33] <sabdfl> and see what the performance is like
[12:33] <sabdfl> i fear a baz-like implosion once we cross certain mem thresholds 
[12:33] <kiko> you mean making random commits?
[12:33] <sabdfl> something like that
[12:33] <sabdfl> simulate 20 developers over a few years
[12:34] <sabdfl> merge is definitely slowin
[12:34] <kiko> make that an mpool problem :-)
[12:34] <sabdfl> sure, i do think they are working on it, knits are supposed to solve a lot of that
[12:43] <sabdfl> hi lifeless
[12:45] <lifeless> morning sabdfl
[12:45] <kiko> yawn
[12:45] <kiko> okay, rolling my bones home
[12:45] <sabdfl> how's life in oz?
[12:45] <sabdfl> night kiko, and thanks
[12:45] <kiko> night, thanks to you
[12:45] <kiko> I'm very tired today. wonder why
[12:45] <sabdfl> am working on those tests, hope to submit before crashing
[12:45] <sabdfl> :-)
[12:45] <mdz> I would like to be a bug contact for a product
[12:46] <mdz> but it looks like there can only be one?
[12:46] <kiko> that is true, you'd need to use a team.
[12:46] <lifeless> pretty good. This is the best time of year here - the HEAT is gone, but the chill hasn't set in.
[12:46] <sabdfl> that's what i was saying about the bug subscription model being unsatisfactory right now
[12:46] <sabdfl> think of it as a more general bug subscription framework
[12:46] <kiko> it's simple but does 90% of the job :)
[12:46] <sabdfl> then also think that we want subscriptions for other "facets" too
[12:47] <sabdfl> like - subscribe me to info about bounties on a product
[12:47] <mdz> kiko: it should work like packages
[12:47] <mdz> where anyone can register themselves as a contact
[12:47] <sabdfl> agreed
[12:47] <kiko> I am wary of creating a massive system for managing subscriptions to anything
[12:47] <sabdfl> the current approach does have the nice "this is the person responsible for foo" angle
[12:47] <sabdfl> which we should preserve
[12:47] <mdz> speaking of which, I inadvertently prevented some bugs from going to Launchpad Developers because of this
[12:47] <kiko> but sure, we could offer N-1 mapping of subscriptions.
[12:47] <mdz> there was no bug contact set, and I didn't realize that the registrant was copied if there was no contact
[12:47] <sabdfl> but we will definitely need a more general subscription framework
[12:48] <sabdfl> mdz: the idea is that someone who is flying solo should not have to go and set themselves as the foo-role everywhere
[12:48] <sabdfl> it should jsut work
[12:48] <kiko> yeah
[12:48] <sabdfl> but they can delegate responsibility just by putting someone else's name in the slot
[12:49] <kiko> maybe we could make that clearer in the UI
[12:51] <sabdfl> lifeless: any reason a merge should have blown out to 25 mins for me?
[12:52] <lifeless> sabdfl: what phase is it on ?
[12:52] <sabdfl> 0/5
[12:52] <lifeless> check ~/.bzr.log
[12:52] <lifeless> its probably got a message there saying either garbage inventories or incorrect history
[12:52] <sabdfl> bunch of ghosts, no current activity
[12:53] <sabdfl> found ghost Arch-1:brad.bollenbach@canonical.com%launchpad--devel--0--patch-271
[12:53] <sabdfl> Garbage inventory {mark@canonical.com-20060411224150-f0388fd5dbf64c95} found.
[12:53] <lifeless> right
[12:53] <sabdfl> ?
[12:53] <lifeless> its triggered a reconcile
[12:53] <lifeless> on weaves thats very very slow
[12:53] <sabdfl> of the order of... hours?
[12:53] <lifeless> yes
[12:53] <sabdfl> should i go to sleep?
[12:53] <lifeless> you can defer it
[12:53] <lifeless> hit ctrlC
[12:53] <lifeless> do the merge again
[12:53] <lifeless> keep working
[12:54] <raphink> hi there
[12:54] <lifeless> but it will need to happen at some point. so when you are ready to sleep, just type in 'bzr reconcile' and walk away.
[12:54] <sabdfl> if i do the merge again, won't it just trigger the reconcile?
[12:54] <lifeless> only if there is more data in the source branch
[12:54] <raphink> I have translated the ubuntu packaging guide into french this week, but it was modified since. Is it possible to import the translations I did previously since the changes are minimal ?
[12:55] <lifeless> if you already have all the data, the code path to check is not triggered.
[12:55] <sabdfl> lifeless: that's too much for my brain i am just going to crash and deal in the morning
[12:55] <sabdfl> with knits... ?
[12:55] <mdke_> raphink, it is done automatically. Are you saying it has gone back to 0?
[12:55] <lifeless> sabdfl: ok. Let it run then, it will be ready for you when you get up
[12:55] <raphink> mdke: many strings are erased yes
[12:55] <lifeless> sabdfl: with knits it happens much more rarely, but is still slower than I'd like
[12:56] <raphink> I had translated much more than what is left
[12:56] <mdke> raphink, show me, please
[12:56] <lifeless> (with weaves, -normal operation- can cause it)
[12:56] <raphink> https://launchpad.net/distros/ubuntu/dapper/+source/ubuntu-docs/+pots/packagingguide/fr/+translate?offset=10&show=untranslated
[12:56] <raphink> all the things that show here were translated
[12:56] <raphink> and only few changes have been made to them
[12:57] <mdke> raphink, you had translated it 100%?
[12:57] <sabdfl> night all
[12:57] <raphink> not 100% mdke
[12:57] <lifeless> gnight, sleep well
[12:57] <raphink> but much more than what is left
[12:57] <mdke> raphink, how much?
[12:57] <raphink> night sabdfl
[12:58] <raphink> mdke: I'd say I had about 500 strings left
[12:58] <raphink> instead of 530
[12:58] <raphink> or so
[12:58] <mdke> raphink, ah. PHEW. 30 strings could easily have changed in the update
[12:58] <raphink> sure, but they're huge strings
[12:59] <raphink> it's not a program, it's doc
[12:59] <raphink> and strings are often entire paragraphs
[12:59] <raphink> so 30 strings is a lot of work to translate
[12:59] <mdke> yes. If part of a long string changes, I'm afraid there is nothing we can do about that
[12:59] <raphink> ah ...
[12:59] <mdke> the whole string has to be retranslated
[12:59] <raphink> the previous translation can't be taken back
[12:59] <raphink> so I can modify it
[01:00] <raphink> there's not even a place where I can get it to copy and paste?
[01:00] <mdke> the previous translation is somewhere in rosetta yeah, but I don't think there is a way for you to download it
[01:00] <raphink> hmpf
[01:00] <mdke> sorry about that
[01:01] <raphink> that is very bad news
[01:01] <raphink> I really want to get this guide translated 
[01:01] <raphink> and I've got other things to focus on
[01:01] <raphink> :s
[01:01] <mdke> I hope it doesn't put you off. If you email the mailing list, maybe the rosetta developers can dig around for you.
[01:02] <raphink> that'll be fine
[01:02] <mdke> sorry about that
[01:02] <raphink> np
[01:02] <mdke> I'm afraid that guide was rushed through quite late, hence the changes
[01:03] <raphink> yes I know
[01:03] <raphink> I'm part of the contributors
[01:03] <raphink> and latest contributors actually ;)
[01:04] <raphink> I believe it's even my fault if I have to retranslate everything, cause I reported some errors
[01:04] <raphink> but I didn't think I would have to rewrite everything
[01:04] <raphink> hence my deception
[01:04] <raphink> but I'll deal with it ;)
[01:07] <mdke_> grr
[01:07] <raphink> connexion issue ?
[01:07] <mdke_> yeah
[01:07] <mdke> yes I know
[01:07] <mdke> :p
[01:07] <mdke_> whoa
[01:08] <raphink> lol
[01:08] <mdke_> that's crazy shit
[01:08] <mdke_> anyhow, sorry about those problems you've had
[01:08] <mdke_> thanks for translating that guide
[01:09] <raphink> oh well I'd feel bad helping to write a guide and not translating it in my own language
[01:09] <raphink> ;)
[01:17] <Seveas> damn kiko is asleep
[01:17] <Seveas> he completely broke my launchpad account and I'm locked out now 
[01:18] <Seveas> any other launcpad admin around? I can't even send bugmail
[01:21] <Seveas> argh
[01:21] <Seveas> I won't get bugmail either
[01:21] <Seveas> this is pretty serious
[01:22] <Seveas> lifeless, you still here?
[01:22] <lifeless> yup
[01:22] <lifeless> whats up ?
[01:22] <Seveas> kiko destroyed my account
[01:22] <Seveas> he merged dennis into dennis-mirage, should have been done the other way around
[01:22] <Seveas> he tried to correct it
[01:23] <Seveas> but my mailaddresses and karma are missing
[01:23] <Seveas> and this I can't login
[01:23] <Seveas> s/this/thus/
[01:23] <lifeless> so you want to be dennis-mirage ?
[01:23] <Seveas> and my karma was nice and high and is now 0 :'(
[01:23] <Seveas> no, I want to be dennis
[01:23] <lifeless> https://launchpad.net/people/dennis
[01:23] <Seveas> and it is dennis now, but the account misses karma and mailaddresses
[01:24] <Seveas> the former is not too serious, but the latter makes it impossible for me to use lp
[01:24] <lifeless> that should not have happened
[01:24] <lifeless> merging is symmetrical
[01:24] <Seveas> well, it did happen
[01:24] <Seveas> look at /people/dennis
[01:25] <lifeless> can you paste a log of your discussion with kiko ?
[01:25] <Seveas> no karma, no mailaddresses
[01:25] <Seveas> was via mail
[01:25] <lifeless> yes, I see it. I need information
[01:25] <Seveas> sec
[01:25] <lifeless> otherwise I'll just make it worse
[01:25] <lifeless> cc to stub too please
[01:25] <lifeless> I may bounce this to him, as he wrote the merge magic in the first place
[01:26] <Seveas> http://paste.ubuntu-nl.org/12134
[01:26] <Seveas> can't you at least add my e-mailaddress again (with password) so I can at least use launchpad?
[01:27] <lifeless> Seveas: I'm going to see what I can see. But its not like edit /etc/passwd, its much more complex.
[01:27] <lifeless> email addresses are in a separate table from password
[01:27] <lifeless> passwords are restricted access
[01:28] <lifeless> I realise the impact this is having on you
[01:28] <Seveas> people should not go to sleep after messing with accounts ;)
[01:30] <Seveas> urgh - can't even use the wiki of course :/
[01:30] <Seveas> I should just go to sleep too and hope it's resolved by the time I wake up 
[01:32] <mdke_> probably not a bad idea
[01:53] <ddaa> lifeless: help!
[01:53] <ddaa> Trying to merge baz2bzr, and I get this failure (multiple times)
[01:54] <ddaa> ValueError: time data did not match format:  data=2006-02-21 17:21:18 CET  fmt=%Y-%m-%d %H:%M:%S %Z
[01:54] <ddaa> obviously, it _does_ match
[01:54] <ddaa> and I cannot reproduce it locally
[01:54] <ddaa> can forward you the pqm message if you think that would help
[01:59] <lifeless> weird
[01:59] <lifeless> the whole message wont help much. But a traceback might
[01:59] <lifeless> what are you merging in ?
[01:59] <lifeless> spiv has a patch in that area too
[01:59] <ddaa> david/launchpad/baz2bzr
[01:59] <ddaa> I also merged the bzrtools bugfix that blocked spiv
[01:59] <lifeless> was bzrtools broken ?
[02:00] <lifeless> details, gimme details.
[02:00] <ddaa> the test case tested for the presence of 'nick': 'rd'
[02:00] <ddaa> 'branch-nick': 'rd', I mean
[02:00] <lifeless> absence surely ?
[02:00] <ddaa> tested for presence
[02:00] <ddaa> that was the bug
[02:00] <lifeless> !
[02:01] <ddaa> so, fixed that, and the merge went in
[02:01] <lifeless> who wouldda thought
[02:01] <ddaa> apparently, I was the last one to touch this line
[02:01] <ddaa> back then when I adjusted the logs produced by baz-import...
[02:02] <spiv> lifeless: current bzr.dev and bzrtools did fix my problem too, although I haven't checked if it woud break anything in launchpad yet.  The rest of sourcecode/ seemed happy enough with it.
[02:02] <ddaa> lifeless: so I guess it must have gone through review unnoticed :)
[02:03] <ddaa> lifeless: I'll forward you chosen pieces from the pqm message
[02:03] <lifeless> ddaa: pastebin
[02:03] <lifeless> I'd like spiv to look at it too
[02:04] <lifeless> score
[02:04] <lifeless> samba-the-segfaulting-daemon. 
[02:06] <ddaa> https://chinstrap.ubuntu.com/~dsilvers/paste/fileVrQJzd.html
[02:06] <ddaa> stripped all the boring stuff at the beginning
[02:09] <spiv> ddaa: "strptime('2006-02-21 17:21:18 CET', '%Y-%m-%d %H:%M:%S %Z')" fails on my local python too, fwiw
[02:09] <ddaa> spiv: fails with the same error?
[02:10] <spiv> ddaa: Yep.  Try it yourself: python -c "from time import strptime; strptime('2006-02-21 17:21:18 CET', '%Y-%m-%d %H:%M:%S %Z')"
[02:11] <ddaa> spiv: worksforme
[02:11] <ddaa> Python 2.4.3
[02:12] <spiv> ddaa: Interesting.  It doesn't for me, dapper's python 2.4.3... it may be a locale issue?
[02:12] <spiv> If I s/CET/EST/, it works.
[02:12] <ddaa> blah
[02:13] <ddaa> dapper python here too
[02:14] <ddaa> infrastructure problem
[02:16] <lifeless> pqm is not running dapper yet FWIW
[02:17] <spiv> >>> _strptime._TimeRE_cache.locale_time.timezone
[02:17] <spiv> (frozenset(['utc', 'est', 'gmt'] ), frozenset(['est'] ))
[02:17] <spiv> python's strptime only knows about utc, gmt and your current timezone by default, it seems.
[02:18] <ddaa> mh
[02:18] <ddaa> okay, it blows because that test is running with a bzr branch extracted from a tarball, that I created on my local system
[02:18] <ddaa> spiv: congrats
[02:18] <ddaa> that's still a bug in bzr
[02:18] <lifeless> ddaa: whats the branch ?
[02:18] <ddaa> david/launchpad/baz
[02:19] <ddaa> david/launchpad/baz2bzr
[02:19] <lifeless> ddaa: dude, no. META
[02:19] <lifeless> ddaa: I want to know what you are testing there that requires a tarball.
[02:19] <lifeless> tarballs are IMO a really bad way to manage fixtures
[02:19] <spiv> Yep, that's the issue, if I set TZ=Europe/Paris it knows about CET.
[02:19] <lifeless> spiv: wow, nice regression
[02:20] <ddaa> lifeless: that's simple, I'm happy with it, and the branch scanner should be able to deal with 0.7 branches for a while.
[02:20] <ddaa> besides, it exposes some fun bzr bugs.
[02:20] <lifeless> ddaa: meh. Could you -please- answer the question ?
[02:21] <ddaa> I think I did.
[02:21] <ddaa> The branch has nothing special.
[02:21] <lifeless> I want to know what you are testing there that requires a tarball.
[02:21] <spiv> ddaa: In fact, the documentation for time.strptime explicitly says "Support for the %Z directive is based on the values contained in tzname and whether daylight is true. Because of this, it is platform-specific except for recognizing UTC and GMT which are always known (and are considered to be non-daylight savings timezones)."  I should have checked there first...
[02:21] <ddaa> I think I answered. What I am testing is baz2bzr
[02:22] <ddaa> and nothing _requires_ a tarball, except it's simple, good enough, and it should work
[02:22] <lifeless> ddaa: I get the feeling you are being deliberately opaque here.
[02:22] <ddaa> s/baz2bzr/baz-import/
[02:22] <ddaa> mh
[02:22] <ddaa> I'm not opaque
[02:22] <lifeless> and its not simple. It has the following deficiencies at minimum.
[02:22] <ddaa> I'm tired and confused.
[02:22] <lifeless> its hard to see what the fixture represents - 
[02:23] <lifeless> you need to unpack a tarball, play with the data, /understand/ why its the way it is.
[02:23] <lifeless> its hard to modify by two people at once - 
[02:23] <ddaa> and TBH quite pissed after spending all the day doing review fixes and trying to stuff down PQM's throat
[02:23] <lifeless> you need to merge the contents of the tarball.
[02:24] <lifeless> let me put it another way then.
[02:24] <lifeless> GO TO SLEEP.
[02:24] <lifeless> this is an important discussion, and not one that carrying on while you are tired and grumpy will be conducive too
[04:07] <lisi> hello all
[04:08] <lisi> I have some problem wih my .po file
[04:08] <lisi> I remember someone here some time ago had solved this problem with a Perl script
[04:08] <lisi> that cleans the file
[06:37] <robotgeek> hmm, any konqueror users in here? need help confirming a konqueror/lp bug
[07:13] <robotgeek> Bug #39396
[07:13] <Ubugtu> Malone bug 39396 in launchpad "javascript focuses new tab automatically in Konqueror" [Normal,Unconfirmed]  http://launchpad.net/bugs/39396
[07:38] <spiv> jamesh: do you know why this pygpgme test is failing? https://chinstrap.ubuntu.com/~dsilvers/paste/file7A2Fca.html
[07:50] <jamesh> spiv: looks like a default value has changed between gpgme releases
[07:51] <jamesh> between 1.0.x and 1.1.x
[07:54] <spiv> jamesh: That test failure appears to be blocking me from merging my buildbot branch -- if you can fix it, that would be appreciated :)
[07:58] <jamesh> spiv: just pushing the change to chinstrap
[07:59] <spiv> Excellent :)
[08:38] <jamesh> spiv: http://pqm.launchpad.net/ <- pqm doesn't look like it is happy with the merge request
[08:44] <jamesh> spiv: seems that I'm not authorised to update the copy in rocketfuel
[08:44] <spiv> jamesh: Ah.
[08:45] <jamesh> lifeless: ^^^ I guess this needs some manual intervention?
[08:54] <jamesh> merge sftp://chinstrap.ubuntu.com/home/warthogs/archives/jamesh/pygpgme/devel/ sftp://chinstrap.ubuntu.com/home/warthogs/archives/rocketfuel/pygpgme/devel
[08:54] <jamesh> Command failed!
[08:54] <jamesh> All lines of log output:
[08:54] <jamesh> Sender not authorised to commit to branch sftp://chinstrap.ubuntu.com/home/warthogs/archives/rocketfuel/pygpgme/devel
[08:54] <jamesh> ^^^ that's what pqm sent back to me
[09:52] <BjornT> mpt: ping
[10:26] <Seveas> hmm, my account problem seems partially solved. It's the less serious part that's solved though :( 
[10:28] <BjornT> Seveas: what is it that's not working?
[10:29] <jamesh> raphink: your OOPS from yesterday was caused because you didn't fill in the URL in the add branch form (the fact that you got an oops is a bug though)
[10:32] <Seveas> BjornT, something went wrong in an account merge yesterday
[10:32] <Seveas> my e-mailaddresses are missing, so I can't login
[10:32] <Seveas> the minor thing was that the karma was reset - that seems to have been solved with the daily karma sweep
[10:35] <lifeless> jamesh: we had not setup the autotesting foo policy for it
[10:36] <BjornT> Seveas: oh, that seems bad, i can't help you with that.
[10:36] <Seveas> lifeless, didn't you sleep at all? ;)
[10:36] <jamesh> lifeless: would it be possible to pull the new revision from my branch manually?  One of the tests is failing with the newer libgpgme (it was testing the default value of a gpgme context variable)
[10:38] <lifeless> jamesh: I'm doing that
[10:38] <lifeless> jamesh: the altered test reads 'foo = 2; assert foo == 2' (paraphrasing ) ;)
[10:39] <lifeless> done
[10:39] <jamesh> the failing test was "self.assertEqual(ctx.include_certs, 1)" on a new context
[10:40] <jamesh> with 1.1.0, the default is -256
[10:41] <jamesh> the second bit of the test was there before (testing that setting the value works)
[10:42] <lifeless> jamesh: I realise that ;)
[10:43] <lifeless> its just amusing
[10:45] <jamesh> lifeless: an unrelated question: if I'm doing a local bzr import of a CVS branch, and merge the changes I made in bzr into CVS, would it break anything if I manually edited the revision-store file for the merge to add the extra parent?
[10:50] <raphink> jamesh: I was trying to find out how to open a bzr branch on LP
[10:50] <raphink> if there's a way
[10:51] <jamesh> raphink: hosted in the supermirror?
[10:51] <lifeless> jamesh: what do you mean ? 
[10:51] <raphink> jamesh: well is there an official bazaar server for ubuntu?
[10:52] <jamesh> lifeless: I'm running tailor to create a bzr import of a CVS branch.  I make some changes in a local bzr branch that diverges from the import and I want to commit them to CVS
[10:53] <lifeless> when you use tailor to bring that revision across to bzr, edit .bzr/checkout/pending-merges and add the revision id
[10:53] <jamesh> lifeless: if I do so and then import that merge revision into bzr, would editing the parents list so that bzr knows that a merge occurred break anything?
[10:53] <lifeless> if you get it right it wont break anything, but the data is very redundant
[10:53] <lifeless> you need to edit:
[10:53] <dilys> Merge to devel/launchpad/: [trivial]  make some tests, which test code used by send-bug-notifications.py, connect as the bugnotification user, to catch permissions problems. (r3470: Bjorn Tillenius)
[10:53] <lifeless> the revision xml
[10:53] <lifeless> the revision knit index
[10:53] <lifeless> the inventory knit index
[10:54] <lifeless> the index of each file that merged *and assign new revision ids to that* 
[10:54] <lifeless> and update the inventory content to reflect that
[10:54] <lifeless> ...
[10:54] <lifeless> the official way to record a merge is to have it in pending-merges when commit happens.
[10:54] <jamesh> raphink: if you have uploaded an ssh key in Launchpad, you can log into sftp://bazaar.launchpad.net, and create branches of with names like /~myusername/product/branchname
[10:55] <jamesh> lifeless: is all that necessary with a 0.7 branch?
[10:55] <raphink> jamesh: ty
[10:55] <lifeless> jamesh: all but one.
[10:55] <jamesh> raphink: so "bzr push sftp://bazaar.launchpad.net/~raphink/productname/branchname" should work, iirc
[10:58] <jamesh> lifeless: okay.  I guess I'll look at the .bzr/pending-merges option then (maybe kill(getpid(), SIGSTOP) at the right place)
[10:58] <lifeless> jamesh: put the bzr revision id in the commit log
[10:58] <lifeless> teach tailor to turn that into a pending merge
[10:59] <jamesh> lifeless: that sounds like a good long term option
[11:00] <lifeless> Seveas: sorry, I made no progress
[11:00] <raphink> jamesh: when registering the branch, it says "Leave that empty if the branch is hosted on bazaar.launchpad.net."
[11:01] <Seveas> lifeless, it's ok - I'll wait for kiko to wake up
[11:01] <raphink> so I can leave it empty, but only if I have a sftp://bazaar.launchpad.net/~raphink/productname/branchname already created ?
[11:01] <jamesh> raphink: yeah.  I'm not disputing that you ran into a bug.
[11:01] <raphink> ah ok
[11:01] <raphink> so I should put the branch url even if on launchpad 
[11:01] <lifeless> raphink: if you have create sftp://bazaar.launchpad.net/~raphink/productname/branchname then the branch is created already
[11:01] <jamesh> raphink: when you create a branch by pushing to bazaar.launchpad.net, the branch should show up on https://launchpad.net automatically
[11:02] <lifeless> raphink: that field MUST be blank if you want SFTP access to the branch at bazaar.launchpad.net
[11:02] <raphink> ah
[11:02] <lifeless> its a confusing UI right now. The way it works is:
[11:02] <raphink> I logged to launchpad via sft and created the dirs
[11:02] <lifeless> BLANK URL == we host the branch on SFTP
[11:02] <raphink> will that work?
[11:02] <raphink> s/sft/sftp/
[11:02] <lifeless> NON-BLANK URL == we monitor the branch that you are hosting somewhere else
[11:03] <raphink> ah yes it seems to work :)
[11:03] <lifeless> yes, if you login via sftp and push the branch - i.e. 'bzr push --create-prefix sftp:.....' then it will just work
[11:03] <raphink> lifeless: no i mean if I mkdir it
[11:04] <lifeless> raphink: it wont work if you mkdir it because you will confuse bzr
[11:04] <raphink> hmmm ok
[11:04] <lifeless> bzr will think (correctly) that you have an empty directory there.
[11:05] <lifeless> and currently that means it will complain at you so it doesn't do the wrong thing by mistake
[11:06] <lifeless> if you have done a 'mkdir' using sftp, I can talk you through getting bzr to push there.
[11:10] <raphink> lifeless: I'd like that
[11:10] <raphink> cause I'm a bit fighting with it right now
[11:10] <lifeless> python
[11:10] <lifeless> import bzrlib.bzrdir
[11:11] <raphink> ok
[11:11] <lifeless> bzrlib.bzrdir.BzrDir.create('sftp://...')
[11:11] <lifeless> (this assumes you have a normal branch, not a knit branch or metadir branch)
[11:12] <raphink> >>> bzrlib.bzrdir.BzrDir.create('sftp://bazaar.launchpad.net/~raphink/klik/main')
[11:12] <raphink> <bzrlib.bzrdir.BzrDir6 object at 0x303c6e10>
[11:12] <lifeless> ok
[11:12] <lifeless> quit python and now you can push to there
[11:12] <raphink>  $ bzr push sftp://bazaar.launchpad.net/~raphink/klik/main
[11:12] <raphink> bzr: ERROR: Not a branch: /home/raphink/klik/main/
[11:13] <raphink> :s
[11:13] <lifeless> thats your local path ;)
[11:13] <raphink> sorry to be so bzr-illiterate
[11:13] <raphink> yes I know it's my local path
[11:13] <lifeless> make sure you are in your local tree first
[11:13] <raphink> how do you mean in my local tree ?
[11:14] <lifeless> have you used bzr before ?
[11:14] <raphink> nope
[11:14] <raphink> only svn
[11:14] <lifeless> ok
[11:14] <lifeless> join #bzr
[11:14] <raphink> ok
[11:14] <lifeless> you need to walk before you run
[11:14] <raphink> indeed
[01:42] <salgado> jamesh, around?
[01:42] <jamesh> salgado: yeah
[01:43] <salgado> hey! did you see my reply to your review?
[01:44] <jamesh> yeah.  I've just been going through carlos's review.  I'll send a reply soon
[01:45] <salgado> great. thank you
[01:59] <mpt_> kiko-zzz, wake up
[02:00] <ddaa> mpt_: do you really think he sleeps with his lappy under his pillow?
[02:00] <mdke> mpt_, if that works, I'll be very impressed
[02:01] <mpt_> ddaa, he lives dangerously, but not *that* dangerously
[02:05] <spiv> cprov: Any sign of kiko?
[02:06] <ddaa> intermittent snoring
[02:06] <stub> Ok. We can start the meeting without kiko.
[02:06] <stub> Who is here?
[02:06] <mpt_> ok, MEETING TIME
[02:06] <ddaa> jamesh: do you have a brazilian on your shoulder?
[02:06] <spiv> I am.
[02:06] <mpt_> me
[02:06] <BjornT> i'm here
[02:06] <matsubara> i'm here
[02:06] <bradb> mo
[02:07] <salgado> here
[02:07] <ddaa> prsent
[02:07] <stub> jamesh: ?
[02:07] <mpt_> matsubara or salgado, can you call kiko?
[02:07] <jamesh> here
[02:07] <stub> cprov: ?
[02:07] <cprov> here
[02:07] <salgado> calling
[02:07] <mpt_> lifeless here?
[02:08] <mpt_> meanwhile, agenda:
[02:08] <mpt_> * Roll call
[02:08] <mpt_> * Agenda
[02:08] <mpt_> * Next meeting
[02:08] <mpt_> * Activity reports
[02:08] <mpt_> * Items from last meeting
[02:08] <mpt_> * Launchpad oops milestone report
[02:08] <mpt_> * Production / staging (stub)
[02:08] <mpt_> * ...
[02:08] <mpt_> * Keep, Bag, Change
[02:08] <mpt_> * Three sentences
[02:08] <matsubara> kiko is coming.
[02:09] <mitsuhiko> argh. rosetta is damaging my eyes...
[02:09] <lifeless> mpt_: sortof
[02:09] <mitsuhiko> whom do I have to contact for bigger fonts?
[02:09] <mpt_> * Next meeting
[02:09] <lifeless> mpt_: you pseudo steve ?
[02:09] <stub> So should we have a meeting next week? How many people are on leave?
[02:09] <lifeless> not on leave.
[02:09] <mpt_> lifeless, whoever wants to pitch in :-)
[02:09] <stub> (it is easter elsewhere this weekend isn't it?)
[02:10] <mpt_> I'm technically on holiday right now
[02:10] <stub> As I am
[02:10] <spiv> And me... but Steve's back next week I think.
[02:10] <lifeless> stub: and I
[02:11] <mpt_> Anyone who can't attend 1200 UTC next Thursday?
[02:11] <kiko> grumble
[02:11] <kiko> I can
[02:12] <mpt_> ok, someone using a better IRC client than I am can change the topic
[02:12] <ddaa> duh
[02:12] <mpt_> * Activity reports
[02:12] <mpt_> kiko, properly awake yet? :-)
[02:12] <kiko> yes!
[02:13] <kiko> but go on, I like to watch
[02:13] <lifeless> up to date
[02:13] <stub> kiko: https://chinstrap.ubuntu.com/~dsilvers/paste/fileJpY4Zv.html
[02:13] <kiko> up to date
[02:13] <mpt_> I'm two days behind
[02:13] <stub> up to date
[02:13] <BjornT> i'm up to date
[02:13] <cprov> up to date
[02:13] <bradb> up to date
[02:13] <ddaa> up to snuff
[02:13] <matsubara> I'm up to date
[02:13] <spiv> up to date
[02:13] <salgado> up to date
[02:14] <jamesh> not up to date
[02:14] <mpt_> jamesh and mpt_, get organized
[02:14] <mpt_> especially you, mpt_
[02:14] <mpt_> well done everyone else
[02:15] <mpt_> * Items from last meeting
[02:15] <mpt_> We don't seem to have minutes from the last meeting on the wiki.
[02:15] <mpt_> Is that because Daf usually compiled them?
[02:15] <kiko> yes. we don't, that's right. but there were no meetingactions presented.
[02:15] <mpt_> ok
[02:16] <mpt_> * Launchpad oops milestone report
[02:16] <matsubara> Yesterday I restarted to send the Bug report reports.
[02:16] <matsubara> I fixed the person widget validation in advanced bug search, I'll merge it today.
[02:16] <matsubara> Apart from that we have a new TypeError in a +translate page: OOPS-102C417. Some Retry exceptions and 'sessiondata_key' violating unique constraint. The ascii encoding password which is bug 2496. Yes, I suck. Some other exceptions that I'll take a look today and report.
[02:16] <Ubugtu> Malone bug 2496 in launchpad "Launchpad blows up if you try to use non-ascii characters in your password" [Normal,In progress]  http://launchpad.net/bugs/2496
[02:16] <Ubugtu> https://chinstrap.ubuntu.com/~jamesh/oops.cgi/102C417
[02:16] <matsubara> The most critical Time Outs are happening in +translation pages and this page https://launchpad.net/malone/bugtrackers/ubuntu-bugzilla when you click Show all bug watches option
[02:17] <mpt_> because it's not batched?
[02:17] <kiko> matsubara, the latter I fixed yesterday
[02:17] <kiko> the former, well, I added a comment to the relevant bug (is it bug 2497?)
[02:17] <kiko> yes
[02:17] <kiko> and forwarded it to launchpad
[02:17] <kiko> it will require some database caching or rethinking
[02:17] <kiko> jordi, are you around?
[02:18] <kiko> stub, about the retry and session data oopses -- do you have a handle on them?
[02:19] <kiko> they are happenning very rarely, but still
[02:19] <stub> I haven't increased the # of retries attempted yet. I'll open a bug on that.
[02:19] <mpt_> mitsuhiko, report a bug <https://launchpad.net/products/rosetta/+bugs>, ideally including a screenshot
[02:19] <mitsuhiko> mpt_: i will do
[02:19] <mpt_> thanks
[02:19] <stub> There is a bug on making retry exceptions more informative, which may be more important than I originally though
[02:19] <kiko> stub, can you explain what the Retry and sessionkey exceptions are?
[02:20] <stub> Session data oopses I'm not sure of. My testing shows the approach I'm using should work just fine, but it isn't.
[02:20] <kiko> are the tracebacks in the oops helpful?
[02:20] <stub> I need to discuss the approach on the PostgreSQL mailing lists.
[02:21] <mitsuhiko> https://launchpad.net/products/rosetta/+bug/39439
[02:21] <Ubugtu> Malone bug 39439 in rosetta "Font Sizes" [Normal,Unconfirmed]  
[02:21] <mpt_> anything else on oopses?
[02:21] <mitsuhiko> hope that's enough
[02:21] <mpt_> Are we still doing better this week than last week?
[02:21] <kiko> I'll follow up with stub in private
[02:21] <mpt_> ok
[02:21] <kiko> we don't know yet mpt
[02:21] <stub> But what is happening (unless I've just screwed up the SQL) is that there is a race condition in the query, affected by updates committed during the query execution. But I didn't think that was possible.
[02:22] <mpt_> * Production / staging (stub)
[02:22] <jamesh> stub: do you think it would be useful to get the error reporting code to record any extra info for Retry exceptions?
[02:22] <stub> I don't want to rollout production next week to give Zope 3.2 extra time to have the bugs shaken out.
[02:23] <stub> jamesh: The retry exception is a wrapper for another exception. We need to display that wrapped exception.
[02:23] <kiko> stub, is reasonable. will you take some cherry pick requests?
[02:23] <stub> Yes - cherry picks are fine and expected.  I'll probably batch them and apply them on Tuesday.
[02:24] <stub> Staging is running Z3.2 of course.
[02:24] <mpt_> stub, have there been many 3.2-related bugs reported so far?
[02:24] <jamesh> stub: do you think it'd be worth special casing Retry, or is there some pattern to zope exceptions wrapping other exceptions?
[02:24] <mpt_> or is it far too soon to tell
[02:24] <stub> mpt_: One, and fixed by Bjorn
[02:25] <kiko> stub, there seem to be some odd regressions related to resources.
[02:25] <stub> jamesh: Either special casing retry, or improving its __repr__ method to be more informative. The latter is probably more generally useful, but I'm not sure how to actually make it readable.
[02:25] <kiko> at least that is what I /think/
[02:25] <stub> kiko: I'm not aware of them, and the tests pass. 
[02:26] <kiko> stub, some of the images seem to be missing
[02:26] <stub> Ok - please file a bug report with details.
[02:26] <kiko> hmmm, maybe it's not 3.2 then
[02:26] <kiko> I'll look into it this morning
[02:26] <stub> The resources stuff was a bit of a pain porting across, so it may well be a 3.2 issue
[02:27] <mpt_> ok
[02:27] <stub> It is quite likely that missing resources aren't noticed by our page tests.
[02:27] <stub> But we need details of what works and what doesn't - might just be not all the old URL syntaxes still work (++resource++foo vs /@@/foo
[02:27] <stub> )
[02:28] <kiko> ok
[02:28] <mpt_> we should have special tests for them and probably don't, I guess
[02:28] <mpt_> anything else for production/staging?
[02:28] <mpt_> that's the phrase I was trying to think of :-)
[02:28] <stub> Nothing more from me
[02:28] <mpt_> I knew it had "traverse" in it somewhere
[02:28] <mpt_> ok
[02:28] <mpt_> * User support requests (kiko)
[02:28] <kiko> so
[02:28] <kiko> we've been getting some pretty outrageous support requests
[02:28] <kiko> as in, 
[02:29] <mpt_> "asdfdfdfs"
[02:29] <ddaa> mh, do not remember receiving any lately...
[02:29] <kiko> New support request #714 on Launchpad:
[02:29] <kiko> https://launchpad.net/products/launchpad/+ticket/714
[02:29] <kiko> loco por linux
[02:29] <matsubara> hehe
[02:29] <kiko> now, while I understand this /would/ happen anyway
[02:29] <ddaa> hahaha
[02:29] <kiko> the rate is pretty high
[02:29] <mpt_> "want bunto cds"
[02:29] <kiko> as in, 5-1 noise
[02:30] <kiko> does anyone -- mpt_ perhaps -- have suggestions?
[02:30] <matsubara> I've been rejecting those. There's some guy from the community that's also trying to help there.
[02:30] <kiko> yeah, I saw that
[02:30] <mpt_> So one big idea of the support tracker was that it would reduce noise in the bug tracker
[02:30] <kiko> matsubara, have you considered inviting him to be a launchpad-support team member?
[02:30] <mpt_> but we never got bug reports like those
[02:31] <stub> Barrier to entry is much lower
[02:31] <mpt_> yes
[02:31] <mpt_> we could:
[02:31] <mpt_> * remove the link to the support tracker from the error page (leaving the e-mail instructions there)
[02:31] <mpt_> * make support requests harder to create
[02:32] <kiko> I am somewhat for the latter
[02:32] <ddaa> put a link to shipit in the support request form?
[02:32] <stub> * consider dud support requests a good thing, as it shows what some users are trying and failing to do
[02:32] <ddaa> "If you want ubuntu CDs, go there!"
[02:32] <jamesh> reject support requests with more than a certain threshold of spelling mistakes?
[02:32] <mpt_> * encourage volunteers to help out in closnig rubbish requests
[02:32] <matsubara> kiko: I could do that, but he seems to use a default answer: "Launchpad is in maintenance..."
[02:33] <matsubara> mpt_: to do that we first need to fix it
[02:33] <matsubara> mpt_: because only the requester can close support request or an admin
[02:33] <mpt_> For the ShipIt-related requests, a big problem is that once you've signed up to Launchpad for ShipIt, Launchpad doesn't redirect you back to ShipIt
[02:33] <salgado> mpt_, yes, it does
[02:34] <ddaa> I think we should not encourage people to post support request from the oops page
[02:34] <kiko> it does mpt_ 
[02:34] <mpt_> it does?
[02:34] <mpt_> hmmm
[02:34] <ddaa> the problems they are reporting are already tracked, it's wasting their times and ours
[02:34] <stub> If it doesn't, it is a regression and needs a bug report
[02:34] <mpt_> ok, who can fix the "let anyone close a request" bug
[02:35] <BjornT> do we really want anyone to close a request, though?
[02:35] <mpt_> We let anyone close a bug report
[02:35] <mpt_> Do we have loose cannons going through /products/launchpad/+tickets at the moment?
[02:36] <kiko> filing reports? yes
[02:36] <kiko> commenting on them? no
[02:36] <mpt_> I mean, adding comments
[02:36] <BjornT> yes, but a support request is not a bug report. it can be hard for the one who answer a request to know that the answer is clear enough for the submitter to understand
[02:36] <kiko> BjornT, can the submitter easily reopen? if so..
[02:37] <mpt_> ok, let's try making it possible for everyone to clsoe
[02:37] <mpt_> close
[02:37] <salgado> mpt_, I've just created a new account and it did redirect me back to shipit.
[02:37] <mpt_> and if it's troublesome, we'll probably need to use the same kind of permissions model for support requests and bug reports
[02:38] <mpt_> salgado, apologies for the false accusation then
[02:38] <BjornT> kiko: i wouldn't say really easily. i think we'll end up with cases where someone provides an answer and closes the request. then the submitter simply says that he doesn't understand the anser, but leaves the request as closed.
[02:39] <kiko> BjornT, matsubara and I can take care of reopening if that is the case. to be honest I haven't seen any really valid uses of the support tracker yet.
[02:39] <ddaa> hehehe https://launchpad.net/products/launchpad/+ticket/670
[02:39] <kiko> most are just to report OOPSes which we already know about
[02:39] <ddaa> matsubara: I think that guy wants edubuntu cds
[02:39] <mpt_> and I'll remove the link from the error page
[02:39] <kiko> I thought it was good that it motivated salgado to fix the OOPS bug he's been sitting on though
[02:39] <kiko> but in the long run..
[02:40] <mpt_> ok
[02:40] <mpt_> * Keep, Bag, Change
[02:40] <ddaa> https://launchpad.net/products/launchpad/+ticket/660 Can we reassign support requests?
[02:40] <ddaa> BAG: scary zope warnings when running "./test.py canonical pagetests.branches"
[02:40] <ddaa> CHANGE: bzr too slow, test runner too slow
[02:41] <matsubara> ddaa: you mean re-target to another product?
[02:41] <ddaa> matsubara: yes, make the problem of the ubuntu folks
[02:41] <matsubara> ddaa: that's bug 34050
[02:41] <Ubugtu> Malone bug 34050 in launchpad "Unable to retarget support request" [Normal,Confirmed]  http://launchpad.net/bugs/34050
[02:41] <kiko> sharp matsubara 
[02:42] <kiko> stub, are you going to look into reducing z3.2 warnings/verbosity?
[02:42] <stub> The bag? No - there are other issues affecting users I need to look at first. We can put up with aesthetic issues only affecting us for a while
[02:42] <stub> (unless someone else wants to give it a go)
[02:43] <kiko> okay.
[02:43] <ddaa> A couple screenful of warnings is hardly cosmetic IMO...
[02:44] <kiko> ddaa, it'll get fixed, just perhaps not this week.
[02:44] <ddaa> great
[02:45] <mpt> is that it for KBC?
[02:45] <kiko> yes
[02:45] <mpt> ok
[02:45] <mpt> * three sentences
[02:45] <mpt> Fire when ready
[02:45] <matsubara> DONE: fixed bug in validation of person widgets in advanced search form, some other validations bugs, bug report report, support requests.
[02:45] <matsubara> TODO: fix ascii encoding bug, more oops bugs, bug triage
[02:45] <matsubara> BLOCKED: No
[02:45] <lifeless> DONE: BZR stuff
[02:45] <mpt> DONE: bug page tweaks, bugfixes, LaunchpadLoginService braindump
[02:45] <mpt> TODO: more MaloneSimplifications, bugfixes
[02:45] <mpt> BLOCKED: no
[02:45] <BjornT> DONE: reviews. various malone bug fixes. zope3 widget bug. work and discussions about deleting bug watches.
[02:45] <lifeless> TODO: switch to qa
[02:45] <kiko> DONE: work on timeouts, fix many small and medium-sized bugs, launchpad report, manage contentious issues
[02:45] <BjornT> TODO: easter holidays. more bug watches work.
[02:45] <ddaa> DONE: gave jamesh tasks, xorg bug reports, finish bazaar-ui, address many reviews
[02:45] <ddaa> TODO: fix baz2bzr, merge branches, cscvs/bzr-native
[02:45] <ddaa> BLOCKED: spiv's buildbot merge, mpt's bazaar-ui review, jamesh giving no sign of life
[02:45] <BjornT> BLOCKED: no
[02:45] <lifeless> BLOCKED:note
[02:45] <bradb> DONE: Landed SecurityTeams. Removed binary package name, but landing blocked on consent from ubuntu-devel. A few bug fixes. A bit of work on bug dates.
[02:46] <bradb> TODO: Propose a solution for landing BPN removal and land it. Land bug dates changes. Other stuff.
[02:46] <spiv> DONE: reviews, making sourcecode/ pass make check.
[02:46] <spiv> TODO: holiday, returning Wednesday 26th.
[02:46] <spiv> BLOCKED: jamesh has pygpgme branch that needs to land to allow a buildbot branch to land -- just needs attention from lifeless.
[02:46] <bradb> BLOCKED: No.
[02:46] <cprov> DONE: catch up after hollidays, queue-ui mark's request, dak-tools bug fixes
[02:46] <cprov> TODO: work out SQL patch for soyuz duplicated uploaded files and PPA-NG
[02:46] <cprov> BLOCKED: None
[02:46] <kiko> TODO: work on 404s and timeouts, reporting, working out more contentious issues and solving them
[02:46] <kiko> BLOCKED: none
[02:46] <stub> DONE: Landed Z3.2
[02:46] <stub> TODO: Retry exceptions, Session race condition, popup performance.
[02:46] <stub> BLOCKED: Nope
[02:47] <mpt> ddaa, if I haven't done that review by Tuesday your time, yell and scream at me
[02:47] <mpt> ddaa, what do you need from jamesh?
[02:47] <salgado> DONE: Fixed #28679, #38256, #30143, #6429, #33995 and some work on ShipItForDapper
[02:47] <salgado> TODO: ShipItForDapper
[02:47] <salgado> BLOCKED: No
[02:47] <mpt> jamesh, when do you expect the pygpgme branch to land?
[02:48] <ddaa> feedback on how he's doing with: RevisionNumber.destroySelf, importd error reporting, transactional fix to branch-scanner code. Activity reports.
[02:49] <stub> Oh - 360 degree reviews. The clock is ticking.
[02:49] <jamesh> mpt: pqm isn't set up to accept merges, so it needs to be done manually.
[02:49] <kiko> stub, they are due, what, this week?
[02:49] <lifeless> which branch ?
[02:49] <stub> I can't remember - I seem to recall 28th?
[02:50] <stub> This week would be silly with Easter.
[02:50] <jamesh> lifeless: the pygpgme one
[02:50] <lifeless> jamesh: which pygpgme one ?
[02:50] <stub> I expect bottlenecks will be kiko, steve and me so earlier the better.
[02:50] <lifeless> that you need to land I mean
[02:50] <spiv> Yeah, 28th according to the email.
[02:51] <mpt> Any volunteers with uncrashed IRC logs to summarize this meeting on the wiki?
[02:51] <stub> So I think everyone should have done their self assesment and sent first round of review requests by next meeting?
[02:51] <lifeless> jamesh: the one you gave me to land earlier is landed
[02:51] <kiko> mpt, why don't you do it? I'll send you a log
[02:51] <jamesh> lifeless: okay.  Then spiv's landing shouldn't be blocked
[02:51] <mpt> kiko, good plan
[02:52] <kiko> thank you!
[02:52] <mpt> all right, we started 7 minutes late and we'll finish 8 minutes late, not too shabby
[02:52] <spiv> jamesh, lifeless: thanks!
[02:52] <mpt> next week we will be in the far more capable and knowledgable hands of SteveA
[02:52] <Seveas> kiko, I got your mail trying to activate my e-mailaddress - launchpad won't eat my password though
[02:52] <mpt> 5
[02:52] <kiko> Seveas, ping?
[02:52] <mpt> 4
[02:52] <mpt> 3
[02:52] <mpt> 2.5
[02:52] <mpt> 2
[02:52] <mpt> 1
[02:53] <mpt> MEETING ENDS
[02:53] <kiko> Seveas, -> privmsg
[02:53] <ddaa> jamesh: would you like a phone call about our tasks?
[02:53] <mpt> thanks everyone
[02:55] <stub> Bug 39426
[02:55] <Ubugtu> Malone bug 39426 in launchpad "Running page tests produces lots of warnings" [Normal,Unconfirmed]  http://launchpad.net/bugs/39426
[02:57] <mpt> mitsuhiko, are you able to attach a screenshot to bug 39439?
[02:57] <Ubugtu> Malone bug 39439 in rosetta "Font Sizes" [Normal,Unconfirmed]  http://launchpad.net/bugs/39439
[02:57] <jamesh> ddaa: okay.  Could we do it a little later? (need to get some food)
[02:57] <mitsuhiko> mpt: sure i would be able :)
[02:58] <mpt> thanks mitsuhiko
[02:58] <ddaa> jamesh: sure, need to do some things here too. When would that be convenient for you?
[02:58] <jamesh> ddaa: maybe an hour or so?
[02:59] <mitsuhiko> mpt: is there an attachment functionalitiy in malone?
[02:59] <ddaa> jamesh: okay see you here at 1400 UTC to arrange call
[02:59] <mpt> mitsuhiko, I KNEW you were going to ask that question
[02:59] <mitsuhiko> :)
[02:59] <mitsuhiko> ok. i'll scp it :)
[02:59] <kiko> mitsuhiko, there is!
[03:00] <mitsuhiko> kiko: where?
[03:00] <mpt> mitsuhiko, in the box on the left side, "Add Attachment" is under "Subscribe Someone Else"
[03:00] <kiko> mpt, shall we move the link to under/near the comment link?
[03:00] <ddaa> mitsuhiko: the answer to that sort of question is invariably "in the portlet"
[03:00] <kiko> lol
[03:00] <mitsuhiko> urks
[03:00] <mitsuhiko> i will file a second bug :)
[03:01] <mitsuhiko> usability problem :)
[03:01] <mpt> indeed
[03:01] <stub> ddaa: A quick workaround for bug 39426 is to edit test.py in the top level directory and filter that warning (there is a section in there already where we switch of other warnings)
[03:01] <Ubugtu> Malone bug 39426 in launchpad "Running page tests produces lots of warnings" [Normal,Unconfirmed]  http://launchpad.net/bugs/39426
[03:01] <cprov> BjornT: are you happy with dak-tools last review comments (just sent) ? may I merge ?
[03:01] <mpt> kiko, I wish
[03:01] <kiko> mpt, okay, I can add it.
[03:02] <stub> ddaa: I'm off now, but feel free to give it a go and land it [trivial]  if it works.
[03:02] <mitsuhiko> mpt: done
[03:02] <mpt> kiko, http://usabilitynews.com/news/article1528.asp
[03:03] <ddaa> stub: okay, I'll keep that in a note
[03:03] <bradb> BjornT: do you have time to review the patch I sent you the URL for yesterday? I just merged from rf, no conflicts.
[03:05] <stub> ddaa: there is already a filter for it in fact - just needs changing from 'always' to 'ignore' (it is set to 'always' so it doesn't get raised as an error, which I have set as the default behavior for warnings under the new test runner)
[03:05] <BjornT> cprov: well, i'm still not clear on the os.access(uploader_log, os.F_OK) check. when will that fail, and what will happen? won't if work without that check?
[03:06] <ddaa> stub: ack
[03:06] <BjornT> bradb: seems like matsubara hasn't merged his branch yet. matsubara what's holding the merge up (the branch i reviewed for you)?
[03:06] <mitsuhiko> ah. and who is responsable for the "start bar" on the top of the page?
[03:07] <mitsuhiko> looks misplaced :)
[03:07] <kiko> mitsuhiko, shift-reload?
[03:07] <cprov> BjornT: really ? it's a not created tempfile at the first upload run
[03:07] <mitsuhiko> kiko: ney. looks like a start bar. but very small fonts and looks like macos :)
[03:07] <cprov> BjornT: in this case I don't need to 'reset' it 
[03:08] <mpt> mitsuhiko, sabdfl for the design, SteveA and myself for the implementation
[03:08] <kiko> paper bags for all
[03:08] <mitsuhiko> urks
[03:08] <mpt> yeah
[03:08] <mpt> but I'm going to nuke the stripes
[03:08] <mitsuhiko> please :)
[03:08] <mpt> mitsuhiko, Mac OS X 10.2, to be precise
[03:08] <matsubara> BjornT: i'm conflicting in that bugtask-macro-buglisting.pt
[03:08] <kiko> mpt, will you fix the missing images as well?
[03:09] <mpt> kiko, I don't see any missing images, what's the bug #?
[03:09] <kiko> I just discovered them in today's oops report, mpt
[03:09] <matsubara> BjornT: I resolved the conflict, commit it, but when I submit it to pqm it conflicts again
[03:09] <mpt> ok, I'll look on Saturday
[03:09] <ddaa> mpt: emailed you log of the meeting
[03:09] <kiko> mpt, sent you via privmsg, seen?
[03:09] <bradb> matsubara: did you push your changes up?
[03:10] <matsubara> bradb: yes, sure
[03:10] <mpt> thanks ddaa
[03:14] <Seveas> kiko, can you please look at my new homepage on https://launchpad.net/people/dennis ;)
[03:14] <kiko> I am honored
[03:15] <BjornT> cprov: in that case, 'os.path.exists(uploader_log)' is clearer.
[03:16] <kiko> BjornT, ok
[03:16] <kiko> (on cprov's behalf)
[03:17] <jordi> kiko: hey
[03:25] <salgado> ddaa, do you know in which version of bzr shared repositories were introduced?
[03:26] <salgado> (the one on chinstrap doesn't seem to have it)
[03:47] <kiko> salgado, can you take a look at database/poll.py:getWinners() for me?
[03:48] <salgado> kiko, looking
[03:48] <kiko> salgado, do you know what queryAll() returns?
[03:48] <kiko> you're getting some NULLs back in that query
[03:51] <kiko> salgado, note that that method is not doctested
[03:53] <ddaa> salgado: 0.8
[03:54] <salgado> kiko, is that the newmember poll of the ubuntu-l10n-hi team?
[03:55] <kiko> yes
[03:55] <salgado> I'm not sure the problem is on that method
[03:56] <salgado> https://chinstrap.ubuntu.com/~dsilvers/paste/fileOe3k0P.html
[03:58] <salgado> there's a bug somewhere, though. I'm going to investigate and file it
[03:59] <kiko> yeah, I thought it was some sort of dud option
[03:59] <kiko> oh kay
[04:00] <salgado> okay, I think I found it
[04:01] <salgado> kiko, do you have an oops for that?
[04:02] <kiko> yes
[04:02] <kiko> https://chinstrap.ubuntu.com/~jamesh/oops.cgi/2006-04-12/C183
[04:03] <salgado> ddaa, do you know why we're running "bzr (bazaar-ng) 0.8pre bzr checkout, revision 1455 nick: bzr.integration" on chinstrap?
[04:03] <ddaa> because the bzr release process is broken and 0.7 is hopelessly outdated?
[04:08] <LarstiQ> hmm
[04:08] <LarstiQ> perhaps time to do third party rcs
[04:09] <kiko> ddaa, that sounds like an exaggeration
[04:09] <ddaa> kiko: it is
[04:09] <kiko> good
[04:10] <ddaa> I know why 0.8 is not released. Nevertheless 0.7 is quite seriously outdated, and I consider it a bug that some intermediate point release was not done since then.
[04:20] <bradb> matsubara: do you think you'll have a chance to merge that branch soon? I've got a merge of my own blocked by it, because BjornT says it'll cause conflicts in my branch
[04:20] <matsubara> bradb: it's on pqm now. let's see if it'll not cause a conflict again.
[04:22] <bradb> ok
[04:22] <salgado> kiko, filed bug 39463
[04:22] <Ubugtu> Malone bug 39463 in launchpad "Display of poll results will break if everybody spoilt their votes" [Normal,Confirmed]  http://launchpad.net/bugs/39463
[04:22] <kiko> thanks salgado 
[04:44] <lisi> hello people, can someone help me with my freshtranslated libgnomeui.po ?
[04:45] <lisi> when I controll validity I get       msgfmt -cv libgnomeui.po -o /dev/null
[04:45] <lisi> libgnomeui.po:17:7: parse error
[04:45] <lisi> msgfmt: found 1 fatal error
[04:45] <lisi> but with this line everything is ok.
[04:59] <bradb> matsubara: no luck with the merge, it looks like :/
[05:00] <matsubara> bradb: nope. I'm talking in #bzr to solve it. I might end up replaying the patch in another branch
[05:02] <AlinuxOS> hello boys
[05:02] <AlinuxOS> can gently someone test my fresh translated libgnomeui.po file and tell me where the problem is ?
[05:02] <AlinuxOS> I get libgnomeui.po:17:7: parse error
[05:03] <AlinuxOS> but this line seems ok 
[05:03] <AlinuxOS> and I don't know what to do :/
[05:06] <AlinuxOS> I've put my libgnomegui in rosetta too.
[05:06] <doko> carlos: would it possible to make an OOo upload now, and import the language data, when the removal run is done? i.e. blacklist the import?
[05:07] <AlinuxOS> https://launchpad.net/distros/ubuntu/dapper/+source/libgnomeui/+translations 
[05:07] <AlinuxOS> I have 3 collors there
[05:07] <AlinuxOS> I what means blue color in the middle ?
[05:08] <AlinuxOS> I know only meaning of green and pink colors.
[05:20] <seb128> hi
[05:21] <seb128> https://launchpad.net/distros/ubuntu/+source/gdm/+bug/11595 has a comment from "ivanii'
[05:21] <Ubugtu> Malone bug 11595 in gdm "GDM won't change resolution back, after loggin out from Gnome session" [Normal,Confirmed]  
[05:22] <seb128> when trying to subscribe that guy to the bug launchpad page displays a "Constraint not satisfied"
[05:25] <salgado> seb128, that's because this account was created during the bugzilla import and it has no password
[05:25] <kiko> right.
[05:25] <seb128> ok, fine
[05:25] <salgado> as a consequence of that, it's not considered a "valid" account, and then can't be subscribed to bugs
[05:25] <kiko> what's the right solution to that problem?
[05:25] <seb128> it was just to get a reply from the guy
[05:25] <andrewski> is there any way to 'import' a bug into launchpad that was reported upstream?
[05:25] <salgado> seb128, we've discussed that on the mailing list, but didn't fix it yet
[05:25] <seb128> but I'm happy to ignore it, that's not a frequent case
[05:25] <kiko> andrewski, not currently -- does it affect ubuntu?
[05:26] <andrewski> kiko: yes, a program in ubuntu.
[05:26] <kiko> I see
[05:26] <kiko> you need to manually file the bug and link an upstream status in
[05:26] <andrewski> ok, i'll just copy and paste and then add the bugwatch.  more tedious, but whatev. ^_^
[05:26] <andrewski> thanks kiko
[05:26] <salgado> seb128, it is a problem and we're aware of it. we just need to decide what would be the less painful way to solve it.
[05:26] <andrewski> btw, all you launchpad devs, the recent changes look very nice!
[05:27] <kiko> hey thanks!
[05:27] <seb128> k
[05:28] <seb128> some fonts were nicer and easier to read before though
[05:28] <andrewski> kiko: :)  to link it upstream, do i choose "link to other bug tracker" or "affects upstream"?
[05:28] <kiko> affects upstream
[05:28] <kiko> actually
[05:28] <kiko> yes
[05:28] <kiko> it will allow you to link to the other bug tracker as part of that step
[05:29] <kiko> BjornT, see above.
[05:29] <andrewski> cool.  done.  cheers.
[05:30] <kiko> thanks!
[05:59] <seb128> hum, launchpad broken?
[05:59] <mdke> yes, here too
[05:59] <Kinnison> DC appears to have dropped off the 'net
[05:59] <Kinnison> I imagine elmo or znarl is already on it
[06:01] <AlinuxOS> #, c-format - what means this line in a .po file source ?
[06:03] <mdke> AlinuxOS, you need a translation channel
[06:05] <jamesh> AlinuxOS: that the translation is used as a C format string (e.g. first argument to printf())
[06:05] <jamesh> AlinuxOS: so all the "%s"'s and "%d"'s should occur in the translated string, and in the right order
[06:06] <AlinuxOS> ah
[06:06] <AlinuxOS> jamesh, thank you :)
[06:07] <jamesh> AlinuxOS: Rosetta does special checks for format string translations to catch common errors though
[06:11] <matsubara> launchpad front page is oopsing
[06:12] <matsubara> not anymore. :)
[06:12] <mdke> it's oopsing here too
[06:12] <mdke> maybe because it just came back up?
[06:13] <matsubara> most likely
[06:18] <mitsuhiko> launchpad isn't that stable. isn't it?
[06:18] <mitsuhiko> i'm currently getting many "OperationalErrors"
[06:18] <Seveas> hmm, many pages oops the first tim you visit them
[06:19] <Seveas> and the CSS switches a lot with F5
[06:20] <mdke> Seveas, it's just coming back up, it's a bit cranky
[06:20] <Seveas> yeah
[06:20] <Seveas> looks funny 
[06:21] <mitsuhiko> i think it's because of me :)
[06:21] <mitsuhiko> i don't like ZOPE ^^
[06:21] <mitsuhiko> and ZOPE doesn't like me
[06:37] <uws> pfff
[06:37] <uws> LP is pretty b0rked :)
[06:39] <dilys> Merge to devel/launchpad/: Fix https://launchpad.net/products/malone/+bug/33978 (Advanced search page doesn't do any input validation) r=BjornT (r3471: Diogo Matsubara)
[06:39] <matsubara> yes!!!
[06:40] <matsubara> finally!
[06:49] <Bluekuja> hi all
[06:49] <Bluekuja> im having from two hours this error OperationalError
[06:49] <Bluekuja> A server error occurred.
[06:50] <Bluekuja> maintenance?
[06:52] <salgado> Bluekuja, I don't think so. the DC's connection to the internet went down 1h ago or so and we noticed these problems since it came back
[06:52] <salgado> you said you experienced it two hours ago?
[06:53] <Bluekuja> two hours ago the problem started
[06:53] <Bluekuja> and i couldnt connect to lp
[06:53] <Bluekuja> now i get that error
[06:53] <salgado> and is it always the same OperationalError?
[06:54] <Bluekuja> i get that error and this one 
[06:54] <Bluekuja> Oops!
[06:54] <Bluekuja> Sorry, something just went wrong in Launchpad. Weve recorded what happened, and well fix it as soon as possible. Apologies for the inconvenience.
[06:54] <Bluekuja> If this is blocking your work, you can make a support request so we can help you out. Include the error ID OOPS-103C2300 in your request.
[06:54] <Ubugtu> https://chinstrap.ubuntu.com/~jamesh/oops.cgi/103C2300
[06:54] <Bluekuja> If you cant make a support request, e-mail system-error@launchpad.net with the error ID, including bug in the Subject line.
[06:54] <matsubara> https://chinstrap.ubuntu.com/~jamesh/oops.cgi/2006-04-13/D653
[06:56] <Bluekuja> if i refresh all works good again
[06:57] <jamesh> is anyone getting an OOPS with an A or B in it?
[06:57] <jamesh> (as opposed to a C or D)
[06:57] <jamesh> if not, then it means the first app server is fine and the second app server is having trouble
[06:59] <Bluekuja> yeah right
[06:59] <Bluekuja> i get only c and d
[07:07] <doko> does launchpad has hickups?
[07:08] <doko> "Operational error"
[07:08] <uws> it does :)
[07:24] <jordi> oops
[07:55] <kiko> bradb, hey
[07:55] <kiko> jamesh, one of the app servers is bongo'd yes
[07:55] <kiko> bradb, https://launchpad.net/distros/ubuntu/dapper/+source/aqsis/+bug/1/+index
[07:55] <Ubugtu> Malone bug 1 in Baltix "Microsoft has a majority market share" [Major,Confirmed]  
[07:55] <kiko> bradb, the "Also Needs Fixing Here" shouldn't show up and raises an AssertionError :)
[07:57] <kiko> congratulations matsubara 
[07:58] <bradb> OperationalError
[07:58] <kiko> bradb, reload
[07:59] <bradb> yeah, hm
[08:00] <kiko> not the biggest deal (how did the guy get to that page anyway)
[08:00] <kiko> but..
[08:01] <kiko> bradb, just keep a diff of your branch and reapply 
[08:01] <bradb> heh, if only :)
[08:01] <bradb> most of the templates it changed don't exist anymore
[08:02] <kiko> wow
[08:02] <bradb> but, the fix might not be so bad, just taking a look at the new UI in another branch first
[08:24] <mdke> ctrl clicking links in launchpad open the link in a new tab, and in the active tab
[08:24] <mdke> that's pretty weird
[08:25] <robotgeek> mdke: turn off javascript
[08:26] <mdke> robotgeek, should I have to do that?
[08:26] <mdke> I have not seen that on any other websites
[08:26] <robotgeek> mdke: me too, i experienced that behaviour in lp (maybe similiar behaviour) 
[08:26] <mdke> hmm, only happens on some pages, too
[08:40] <bradb> BjornT: I fixed my branch after matsubara's landing. Do you have time to review the (small) patch?
[09:01] <sebpayne> i'm trying to set an account up and  get an OperationalError
[09:01] <sebpayne> when i followed the link in my email
[09:02] <salgado> sebpayne, we're experiencing some problems in one (or maybe two) of our app servers
[09:02] <sebpayne> it's just worked now, thanks though
[09:03] <dsas> sebpayne: (hi again), it seems if you just refresh a page it'll work.
[09:03] <salgado> yeah, I was going to suggest that you try again, in the hope that you get served by a different app server
[09:05] <sebpayne> out of interest, how many servers are there behind launchpad?
[09:07] <sebpayne> also, is it possible to shut down an old launchpad account?
[09:08] <salgado> sebpayne, you can't shut it down, but you can merge it into another one
[09:08] <sebpayne> cool - how cna i do that?
[09:09] <salgado> there's a link for doing that at https://launchpad.net/people
[09:09] <sebpayne> thanks
[09:09] <salgado> you're welcome
[09:50] <sabdfl> bradb: ping
[09:51] <bradb> sabdfl: pong
[09:51] <sabdfl> hiya
[09:51] <bradb> hey
[09:51] <sabdfl> bugtarget-filebug.pt
[09:51] <sabdfl> was looking a little bare
[09:51] <sabdfl> can you guess what I added?
[09:52] <bradb> most commonly reported bugs?
[09:52] <sabdfl> and?
[09:52] <sabdfl> well, that would be nice, but i added latest bugs and...
[09:52] <bradb> a details portlet? :)
[09:52] <sabdfl> ed zachary
[09:53] <sabdfl> would you make sure all your 3col pages are suitably decorated please?
[09:53] <bradb> i intentionally left that out, since we tend to abuse that portlet, IMHO
[09:53] <sabdfl> and do we have a most-dup'd portlet for an IBugTarget?
[09:53] <bradb> sabdfl: not yet
[09:53] <sabdfl> bradb: can you imagine what launchpad would look like if everybody made up their own UI rules?
[09:54] <sabdfl> for example, on that portlet, you can see the security contact, in context...
[09:54] <bradb> sabdfl: pretty weird. what's the rationale for having the details portlet on every page though?
[09:54] <sabdfl> bradb: only on pages where it contains information that is basically relevant to that page
[09:54] <sabdfl> when we move to a more facet-oriented view, AND I GIVE THE SIGNAL, we can break the details portlets down into sub portlets
[09:54] <sabdfl> so, for example, the rosetta-details would go in a portlet
[09:55] <sabdfl> on a translation page, you should quickly be able to see all the translation group info for whatever you are translating
[09:55] <sabdfl> on a bug page, security contacts, bug contacts etc
[09:55] <sabdfl> as well as high level info
[09:55] <bradb> right, that'd be helpful
[09:55] <sabdfl> at the moment, thats all aggregated in details portlet
[09:55] <sabdfl> so please just put it in
[09:55] <bradb> ok
[09:55] <sabdfl> thanks
[09:55] <sabdfl> on this page, i put the latest-bugs portlet at the top
[09:56] <sabdfl> on the right
[09:56] <sabdfl> in general, given the current menu position, the top right portlet is the first you should fill
[09:56] <sabdfl> generally, with the relevant details portlet
[09:56] <sabdfl> but in this case i put the latestbugs portlet there
[09:56] <sabdfl> because its RIGHT NEXT TO the place you put in the bug title
[09:56] <sabdfl> which maximises the chance a guy looks over and sees... someone else just filed that bug
[09:57] <bradb> indeed
[09:57] <sabdfl> so one question
[09:57] <sabdfl> in the latestbugs portlet for a distro
[09:57] <sabdfl> or a distrorelease
[09:57] <sabdfl> do we show bugs that include a spn?
[09:57] <sabdfl> i.o.w. is that latest bugs for the distro, period, or is it latest bugs just for the distro-without-spn
[09:58] <sabdfl> on the sourcepackage page, the latestbugs portlet should of course jsut show latest bugs for the sp
[09:58] <sabdfl> but on distro, i could think its relevant either way
[09:58] <bradb> yeah, we make no exception, it's just the most recent five, AFAIK
[09:58] <sabdfl> i'm inclined to think that's the right approach
[09:58] <sabdfl> because spn just denotes a smarter bug filer
[09:58] <sabdfl> who may have got it wrong
[09:58] <sabdfl> so good work there
[09:58] <sabdfl> otherwise, i see malone coming along nicely - thank you
[09:59] <bradb> glad you like, thanks
[09:59] <sebpayne> hi sabdfl - i will be talking at LugRadio Live so should see you there :-)
[10:00] <sabdfl> sebpayne: coolio
[10:00] <sebpayne> sabdfl, i will be talking about iFolder with some demos on Ubuntu
[10:00] <sabdfl> nice! i haven't seen that yet
[10:01] <sebpayne> i'm just wrting some new documentation on the Wiki
[10:01] <sabdfl> think that's a dapper+1 feature?
[10:01] <sebpayne> it is yes, but whiprush and mez have done some nice Dapper packages
[10:01] <sebpayne> which work very very well
[10:02] <sebpayne> so i'm writing up how to use those
[10:15] <sabdfl> BjornT: on the manage-supportcontacts page
[10:15] <sabdfl> what is the rationale for the list of teams?
[11:03] <BjornT> sabdfl: it was mainly to be consistent with how bug contacts (for source packages) work
[11:05] <sabdfl> BjornT: what logic generates the list?
[11:07] <BjornT> sabdfl: it list all the team that you are an active member of, using IPerson.myactivememberships
[11:12] <sabdfl> night BjornT, and thanks