[12:05] <kiko> lucasvo, welshbyte: accounts aren't deleted -- they are merged!
[12:06] <welshbyte> kiko: how does that work then?
[12:06] <kiko> welshbyte, in /people you'll see a link to merge accounts. it just steps you through the validation of the addresses and happens automatically.
[12:06] <welshbyte> ah ok :)
[12:09] <welshbyte> ooh, launchpad gave me an "Oops!"
[12:09] <kiko> that's not good
[12:09] <kiko> what's the OOPS ID?
[12:09] <welshbyte> OOPS-115A436
[12:09] <Ubugtu> https://chinstrap.ubuntu.com/~jamesh/oops.cgi/115A436
[12:10] <kiko> welshbyte, OH. that's interesting.
[12:10] <welshbyte> sounds ominous :)
[12:11] <kiko> welshbyte, it's a regression stub seems to have introduced today. but I'm not 100% sure.
[12:11] <kiko> can you file a bug? I'll email stub and ddaa about it
[12:11] <matsubara> kiko: I think ddaa has a patch for it.
[12:11] <kiko> oh he does?
[12:11] <kiko> matsubara rocks
[12:12] <matsubara> kiko: I'm not sure if it's that, but stub and ddaa were talking about the account merge function today in the morning
[12:12] <kiko> yeah, I read that too
[12:12] <kiko> but I think a bug report might be on the safe side
[12:14] <matsubara> welshbyte: are you going to report it? if not, I can do it.
[12:14] <welshbyte> i can do it if you tell me what package to report it against
[12:15] <kiko> welshbyte, /products/launchpad
[12:16] <welshbyte> okie dokie
[12:20] <welshbyte> https://launchpad.net/products/launchpad/+bug/41398
[12:20] <Ubugtu> Malone bug 41398 in launchpad "Oops On Merging Duplicate Account" [Normal,Unconfirmed]  
[12:20] <welshbyte> is that enough info?
[12:20] <matsubara> welshbyte: thanks!
[12:21] <matsubara> welshbyte: yep.
[12:21] <welshbyte> great :)
[12:22] <welshbyte> mmm karma, sweet karma
[12:59] <SteveA> matsubara: awesome!
[12:59] <matsubara> SteveA: good night. :)
[01:02] <lifeless> win 11
[01:07] <jmg> hi all
[01:08] <jmg> i wrote a draft for one of the specs calling for braindumps, but i cant link it to the wiki page as i dont have permission to edit the launchpad page
[01:09] <lifeless> jmg: there should already have been a link in the spec
[01:09] <kiko> jmg, really? what spec is that?
[01:09] <jmg> xen-enabled-kernel
[01:10] <mdke> kiko, there are loads of specs like that
[01:10] <kiko> how weird
[01:10] <kiko> jmg, can you get me a link?
[01:10] <mdke> at least, the first one I clicked on at https://launchpad.net/specs does it
[01:10] <mdke> https://launchpad.net/distros/ubuntu/+spec/ebuntu-dr17
[01:11] <jmg> kiko: https://launchpad.net/distros/ubuntu/+spec/xen-enabled-kernel
[01:11] <kiko> okay, gotcha.
[01:11] <kiko> mmmm.
[01:12] <jmg> kiko: want to link to http://wiki.ubuntu.com/XenEnabledKernelDraft
[01:12] <lifeless> SteveA: are you really gone ?
[01:12] <kiko> mdke, this is really a distro permissions problem, unless we decide to make them world-editable
[01:13] <kiko> jmg, what's your launchpad username?
[01:13] <lifeless> kiko: there is a fairly severe issue with the supermirror with bzr 0.8, I'd like to sic spiv onto that as a priority. Is that ok ?
[01:13] <jmg> kiko: cartel
[01:13] <mdke> jmg, btw, I'd drop the "Draft" in the wiki page name
[01:13] <jmg> mdke: but it hasnt been accepted yet
[01:13] <kiko> jmg, you don't need to indicate status in the wiki page
[01:13] <mdke> jmg, the status will be tracked by the spec tracker, rather than by changing the name of the spec
[01:14] <mdke> changing names of wiki pages is generally to be avoided at all costs
[01:14] <kiko> it causes LINKROTTAGE
[01:14] <jmg> i was going from the "Examples of great specs"
[01:14] <mdke> gah!
[01:15] <mdke> jmg, if you search for "Draft" on the Ubuntu wiki, there are hardly any pages with that name, and 300 specs LD
[01:15] <mdke> s/LD/:D
[01:15] <jmg> mdke: okay, ill rename it :)
[01:16] <lifeless> kiko: ?
[01:18] <mdke> lifeless, if it helps, I was told today that spiv is on vacation until the end of the week
[01:18] <kiko> yes lifeless?
[01:18] <mdke> dunno if it's right
[01:18] <lifeless> mdke: he was on leave to the 25th
[01:18] <kiko> ah
[01:18] <jmg> done :)
[01:18] <lifeless> 09:13 < lifeless> kiko: there is a fairly severe issue with the supermirror with bzr 0.8, I'd like to sic spiv onto that as a  priority. Is that ok ?
[01:18] <mdke> misinformed then, my bad
[01:18] <kiko> lifeless, email?
[01:19] <lifeless> bug 41409
[01:19] <Ubugtu> Malone bug 41409 in launchpad "initial push of a knit branch errors" [Normal,Unconfirmed]  http://launchpad.net/bugs/41409
[01:19] <lifeless> kiko: you want me to email you and spiv ?
[01:19] <kiko> lifeless, and CC: launchpad
[01:19] <lifeless> kiko: sure, I'd do that anyway
[01:19] <kiko> thanks
[01:19] <lifeless> kiko: I'm asking for the ok about asking spiv to do this as a priority so that when bzr 0.8 goes gold (this week) lp support does not lag majorly
[01:20] <jmg> thanks kiko :)
[01:21] <kiko> lifeless, yes
[01:21] <kiko> jmg, you're welcome, but if you rename, you need to reping me.
[01:21] <kiko> or well do you want to own that spec?
[01:22] <jmg> oh, i renamed. sorry
[01:22] <kiko> did you?
[01:22] <jmg> yes but it was made by Adriaan? so how does that work
[01:22] <kiko> I can still see the Draft page up
[01:23] <jmg> https://wiki.ubuntu.com/XenEnabledKernel
[01:23] <jmg> i hadnt clicked the "Rename" button
[01:24] <kiko> ah!
[01:24] <jmg> sorry >_<
[01:24] <kiko> no worries
[01:24] <sivang> night all
[01:25] <kiko> jmg, there, you should have permissions now for it
[01:26] <jmg> kiko: thanks!
[01:27] <kiko> I found my brain and turned it on just for you
[01:31] <jmg> :-)
[03:24] <mpool> can anyone help with https://launchpad.net/products/rosetta/+ticket/529 ? 
[03:24] <mpool> may require a db update
[03:26] <lifeless> heh, en-au is important dude
[03:26] <lifeless> you want us spelling ?
[03:26] <lifeless> yeah, it will need a db script
[03:27] <jamesh> lifeless: I tried debugging the ekiga/siproxd problem a bit more over anzac day: when going through siproxd, ekiga seems to time out on the INVITE request almost immediately and retries 3 more times
[03:27] <jamesh> shtoom doesn't do the retries, and gets through
[03:27] <lifeless> interesting
[03:28] <lifeless> ekiga works with siproxd for me
[03:28] <lifeless> are you doing it transparently, or with a configred sip proxy ?
[03:28] <jamesh> tried both (was doing non-transparent mostly)
[03:28] <lifeless> I have non-transparent
[03:29] <lifeless> because I believe transparent is evil evil evil ;)
[03:29] <lifeless> well, intercepting.
[03:29] <jamesh> the logging/debugging code in siproxd is very buggy too ...
[03:29] <jamesh> had to fix that to get useful debugging output
[03:46] <mpt> http://validator.w3.org/check?uri=https%3A%2F%2Flaunchpad.net%2Fmalone ... Just as I suspected
[03:59] <spiv> Good morning!
[03:59] <spiv> Or should I say... "GOOD MORNING CRISPNESS LOVERS?" ;)
[04:03] <jmg> hi spiv
[04:04] <mpool> lifeless: the problem is i think this is not en_AU, but rather "all 400 Australian aboriginal languages in one bucket"
[04:04] <jamesh> hi spiv
[04:05] <jamesh> mpool: so you knew 400 australian languages before, but now you don't?
[04:05] <lifeless> mpool: its en_AU
[04:05] <lifeless> I have the same visible ui symptoms, and I explicitly added en_AU way back
[04:10] <jamesh> lifeless: mbp is talking about the language with code "aus"
[04:11] <jamesh>  code |     englishname      | visible
[04:11] <jamesh> ------+----------------------+---------
[04:11] <jamesh>  aus  | Australian languages | f
[04:12] <lifeless> jamesh: ah, which is weird
[04:12] <lifeless> jamesh: I wonder why it ever got added to us
[04:12] <jamesh> lifeless: it was probably in some languages list we used to prime the database
[04:14] <lifeless> possibly
[04:14] <lifeless> more likely 
[04:14] <lifeless> en_AU -> aus
[04:14] <lifeless> aus -> removed
[04:15] <jamesh> lifeless: check /usr/share/iso-codes/iso_639.tab
[04:16] <lifeless> jamesh: I realise they are not meant to be related
[04:16] <lifeless> jamesh: I'm considered the evolution of rosetta here
[04:17] <mpool> jamesh: just to see what would happen
[04:18] <mpool> jamesh: my memory's not what it used to be
[04:18] <jamesh> mpool: fair enough.  I wonder how many personlanguage records we have for non-visible languages?
[04:18] <mpool> it should be easy to find out...
[04:19] <jamesh> 319
[04:21] <jamesh> lifeless: so it doesn't sound like a language that rosetta automatically added to mbp's account (I don't think it ever does that ..)
[04:21] <lifeless> jamesh: right
[04:36] <mpool> jamesh: actually i think it suggested it under "languages used in australia"?
[06:59] <stub> Yay repositories. Can't rsync a branch without pulling down the entire repo, although that may still turn out to be faster than waiting for a sftp: merge to complete :-(
[07:18] <jamesh> stub: for something like Launchpad, a shared repository probably won't differ in size much compared to a branch with its own repo
[07:19] <lifeless> dont use rsync with repos
[07:19] <lifeless> -really-
[07:20] <stub> lifeless: So don't merge? I really don't have time to wait for sftp
[07:21] <stub> Thankfully ddaa is asleep so his repo will be static
[07:21] <lifeless> stub: hey, I haven't suggested anyone switch to repos yet. 
[07:21] <lifeless> until we switch rf to a knit repo its all massively premature
[07:22] <stub> Yup.
[07:22] <lifeless> stub: what are you merging ?
[07:22] <stub> Patches from a ddaa branch. I can't just generate a diff on chinstrap as that bzr doesn't want to know about repos
[07:23] <lifeless> /home/warthogs/source/bzr.dev/bzr 
[07:23] <lifeless> use that, or the one in sourcec/rollouts/bzr.dev
[07:33] <jamesh> mpt: it is the part of a bzr branch storing information about the revisions in the ancestry of the branch, and the contents of the files in those revisions (to simplify things)
[07:34] <jamesh> mpt: the new feature is being able to share this data between multiple branches (since a lot of it will be the same if the two branches are related)
[08:45] <jamesh> spiv: out of interest, how difficult would it be to get SQLObject working with the authserver?
[08:45] <jamesh> (and do you think it would be a good idea?)
[08:46] <spiv> jamesh: moderate, and I'm unsure if it's a good idea.
[08:46] <carlos> morning
[08:46] <jamesh> I suppose the big thing to consider is the authserver caching spec
[08:47] <spiv> The authserver is hit a lot, but doesn't need very complex abstraction of the SQL it uses, so hand-written SQL feels like it's a good trade-off to me.
[08:47] <spiv> But it could be that I'm kidding myself, and SQLObject will produce perfectly reasonable queries without much effort, and with simpler code.
[08:48] <jamesh> yeah.  It is a single statement for most method calls
[08:48] <spiv> It's worth experimenting with.
[08:49] <spiv> Mostly though, it is returning results pretty raw from the database, so I think it at least some places converting rows to SQLObjects to the XML-RPC results would be more complex than the current rows to XML-RPC results fiddling.  But it's probably a win in other parts...
[08:50] <spiv> In theory, AuthServerCaching could be done just fine with SQLObject in the mix, but probably SQLObject's own connection pool layer would make it slightly harder to understand.
[08:51] <spiv> Layers upon layers of database connection pools is the sort of thing that just drives you mad :)
[09:09] <lifeless> how happy is sqlobject with multiple transactions in a single thread ?
[09:10] <spiv> lifeless: At the worst, you can explicitly pass the 'connection' kwarg to every SQLObject operation.
[09:11] <spiv> It might not even be as bad as that.
[09:11] <lifeless> erk
[09:11] <spiv> The authserver doesn't need that, though.
[09:11] <lifeless> branch updates need transactions
[09:11] <carlos> hmm
[09:12] <carlos> I got an error from pqm that I don't understand...
[09:12] <carlos> I have this test:
[09:12] <carlos> https://chinstrap.ubuntu.com/~dsilvers/paste/filebTU22d.html
[09:12] <carlos> and get this: https://chinstrap.ubuntu.com/~dsilvers/paste/filewAodP6.html
[09:12] <carlos> but if I run that test in my computer, the test pass
[09:13] <spiv> carlos: somehow the DB is in a different state when PQM runs the tests vs. when you do.
[09:13] <carlos> spiv: no, the exception is ok
[09:13] <spiv> Have you merged in the latest rocketfuel?  Maybe there's been sampledata or other changes.
[09:13] <carlos> but pqm is getting a ProgrammingError and I'm getting an IntegrityError
[09:14] <spiv> Oh, I see.
[09:14] <spiv> That's either a psycopg version difference, or a postgres version difference.
[09:14] <carlos> that sucks
[09:14] <spiv> Yep.
[09:14] <carlos> is there any other way to do that test without depending on a concrete software version?
[09:15] <spiv> Yep.
[09:15] <spiv> >>> try:
[09:15] <spiv> ...  
[09:15] <spiv> ...     posubmission.destroySelf()
[09:15] <carlos> checking for both exceptions...
[09:15] <spiv> ... except (IntegrityError, ProgrammingError):
[09:15] <carlos> ok
[09:16] <spiv> ...     # XXX carlos <date>: postgres hates me ;)
[09:16] <carlos> ;-)
[09:16] <spiv> Well, probably a slightly better XXX than that ;)
[09:16] <spiv> But yeah, it sucks.
[09:16] <carlos> ok, thanks
[09:18] <carlos> spiv: hmmm I suppose I should raise an exception after posubmission.destroySelf to be able to check that either an IntegrityError or a Programming Error is raised, right?
[09:22] <jordi> carlos: hey dyde
[09:22] <jordi> carlos: got my messages last night?
[09:22] <carlos> no, sorry...
[09:23] <jordi> regarding uzbek?
[09:23] <spiv> carlos: Right, you need an "else: raise AssertionError('blah')" or similar.
[09:23] <lifeless> jordi: theres some panicing guy about translations
[09:24] <lifeless> jordi: a 'Michael Hamberg' - have you seen his email?
[09:24] <jordi> 20:06 < jordi> carlos: ping
[09:24] <jordi> 20:07 < jordi> https://launchpad.net/people/uzbek/+review was never added to ubuntu translators
[09:24] <jordi> 20:07 < jordi> err
[09:24] <jordi> 20:07 < jordi> https://launchpad.net/people/ubuntu-l10n-uz
[09:24] <BjornT> carlos: you can also print something in the except clause and check for that string.
[09:25] <carlos> spiv, BjornT: I found another solution from bradb's tests:
[09:25] <carlos> note that DatabaseError is a superclass of both IntegrityError and
[09:25] <carlos> ProgrammingError
[09:26] <carlos> hmm, nevermind, the traceback will not print that name
[09:26] <spiv> carlos: Right :)
[09:26] <spiv> You still need the explicit except.
[09:26] <carlos> right
[09:27] <lifeless> jordi: ?
[09:27] <carlos> jordi: done
[09:28] <carlos> lifeless: I got it, I'm going to answer this morning
[09:28] <lifeless> carlos: sweet
[09:28] <lifeless> I think hes overreacting, but it understandable
[09:28] <carlos> BjornT: is that better than just raise an assertion error?
[09:29] <lifeless> carlos: unfortunately, because doctests are not good at this sort of precise testing, yes it is better
[09:29] <carlos> ok
[09:29] <lifeless> But I consider the need to do that a *strong* hint to convert the test to pyunit rather than doctest
[09:30] <BjornT> carlos: i think it's better to match against something. compare it to when you check if something is None. you usually write:
[09:30] <BjornT> >>> foo is None
[09:30] <BjornT> True
[09:30] <BjornT> instead of simply:
[09:30] <BjornT> >>> foo
[09:31] <carlos> BjornT: right
[09:32] <carlos> lifeless: well, that's only a part of the doctest, I think is more clear if we leave it together with the other related doctests
[09:32] <jordi> lifeless, carlos: I already replied
[09:32] <carlos> jordi: oh, cool, thanks ;-)
[09:32] <jordi> overreacted, yes. And spamming any possible address he finds is not the way either :)
[09:33] <SteveA> hi
[09:33] <lifeless> jordi: did you copy us, so that we know not to also reply ?
[09:35] <jordi> lifeless: I cut the CC list a bit not to spam yet another time
[09:36] <lifeless> jordi: sigh. 
[09:37] <lifeless> jordi: thats a sure fire way to leave the spamming going on. There needs to be a 'its handled' message.
[09:37] <lifeless> so I've sent one
[09:40] <jordi> lifeless: I see
[09:40] <lifeless> because all the other people *dont know* that hes being helped until they see one.
[09:41] <jordi> yeah, I understand
[09:57] <carlos> spiv: Is there a way to do an order by with sqlobject using two tables? I mean something like 'order by Language.code, POFile.variant' where Language is joined with POFile.language
[09:59] <jamesh> carlos: orderBy=[Language.q.code, POFile.q.variant] 
[10:01] <carlos> jamesh: does it work with SQLMultipleJoin?
[10:01] <jamesh> carlos: it'll work with select() if you include those tables.  I haven't tried with SQLMultipleJoin, but it would probably work there too
[10:01] <jamesh> give it a go and find out
[10:02] <carlos> but I guess I would need to note the join between Language and POFile, right?
[10:02] <carlos> the SQLMultipleJoin is not joining Language and POFile tables
[10:02] <carlos> but POTemplate and POFile
[10:03] <jamesh> yep
[10:03] <jamesh> you'll get an error if the table isn't used in the join
[10:06] <carlos> jamesh: no, it doesn't work anyway from a select
[10:07] <carlos> hmm
[10:07] <carlos> sorry
[10:07] <carlos> forget that
[10:07] <carlos> I did a bad query 
[10:08] <carlos> jamesh: next question is... I cannot note the POFile <-> Language join with an SQLMultipleJoin that links POFile and POTemplate, right?
[10:09] <jamesh> don't think so.
[10:10] <carlos> jamesh: thanks for your help
[10:10] <SteveA> hi jamesh 
[10:11] <jamesh> hi SteveA 
[10:11] <SteveA> i tried calling kiko on skype yesterday, after a dapper update and reboot
[10:11] <SteveA> and it wouldn't work, even for the echo service
[10:12] <SteveA> oh...
[10:12] <SteveA> it's trying to use /dev/dsp-1 for some reason
[10:14] <jamesh> if you have a USB headset, check to see if it got renumbered on reboot
[10:15] <SteveA> in the skype setup, it says /dev/dsp
[10:15] <SteveA> so i don't know why it is dsp-1 when it runs
[10:16] <SteveA> i don't have a USB headset
[10:16] <jamesh> okay
[10:16] <jamesh> I had my headset detected as the first sound card on a reboot once
[10:24] <SteveA> aha!
[10:24] <SteveA> esd is the DEVIL
[10:24] <SteveA> jamesh: skype call?
[10:25] <jamesh> okay.  Just starting it up
[10:27] <jamesh> are you calling me or vice versa?
[10:28] <SteveA> i'm waiting for the little green tick to appear against your name
[10:28] <jamesh> hmm
[10:28] <jamesh> it says you aren't online
[10:28] <jamesh> when I try to call
[10:29] <SteveA> i'm trying to call... runging
[10:35] <carlos> stub: hi, around?
[10:36] <stub> carlos: yes
[10:36] <carlos> stub: what's the status of my request to remove some oo translations?
[10:37] <carlos> did you have time to look into it?
[10:37] <stub> carlos: not yet
[10:37] <carlos> ok
[10:42] <C-O-L-T> Hello, I have made a Launchpad team, but it was just a mistake, would like to delete, how?
[10:48] <SteveA> mpt: ping
[10:49] <mpt> SteveA, pong
[10:49] <SteveA> mpt: menu style?
[10:49] <mpt> SteveA, working on that right now
[10:49] <mpt> getting some hover effects going
[10:50] <C-O-L-T> Anybody?
[10:51] <ddaa> Good mernoing
[10:52] <SteveA> Pixies!
[10:52] <C-O-L-T> ddaa: can you help me? Good morning
[10:52] <ddaa> C-O-L-T: I can hardly help myself right now, but just ask. There's a bunch of knowledgeable people here whose job is to make you happy.
[10:53] <SteveA> C-O-L-T: best thing is for you to file a support request.
[10:53] <C-O-L-T> ddaa: :)))))
[10:53] <C-O-L-T> SteveA: I have written an email to one of the Launchpad admins and he said come to here because here people will help 
[10:53] <SteveA> https://launchpad.net/products/launchpad/+tickets
[10:53] <SteveA> okay
[10:54] <SteveA> if you file a support request, it will be seen to, even if there's no one on irc who can help right now
[10:55] <C-O-L-T> SteveA: ok I will write one now :D
[10:56] <C-O-L-T> SteveA: how to do that, i am in Launchpad support section but I can not write a request
[10:56] <SteveA> "Request support" menu item on the left
[10:57] <ddaa> maybe mpt will call that crack, but maybe it's something for next year
[10:59] <ddaa> in the global search field typing some things like "request launchpad support", "file ubuntu bug" or "free linexcd" would lead the the appropriate page with a message for the use to click on this on that link.
[11:04] <SteveA> and we have an army of call centre operators reading the text people enter...
[11:08] <stub> carlos: where is the 'remove-upstream-translations' script?
[11:10] <stub> oh... its not in rf
[11:10] <carlos> stub: it's being merged now
[11:10] <carlos> stub: but you have it available from my branch
[11:11] <carlos> or just wait, it should be on rocketfuel soon
[11:19] <carlos> where is dilys?
[11:19] <carlos> SteveA: is daf hosting it?
[11:20] <SteveA> carlos: yes.  we may need a new dilys
[11:20] <carlos> is there any chance to get it hosted on our DC?
[11:21] <SteveA> maybe
[11:21] <SteveA> do you know what dilys is written in?
[11:23] <carlos> SteveA: python
[11:23] <SteveA> pure python, or using some library for an irc bot?
[11:24] <carlos> SteveA: let me check where is the source code..., daf was using bazaar to publish it
[11:24] <carlos> SteveA: no idea
[11:24] <carlos> stub: my branch landed 
[11:24] <carlos> you should have the script on rocketfuel
[11:29] <carlos> SteveA: I don't find it.
[11:29] <carlos> I will mail daf to ask him
[11:29] <SteveA> ok, thanks
[11:34] <carlos> done
[12:53] <stub> dilys needs a rewrite.
[12:53] <stub> parsing email messages is fragile and silly when you have access to the appserver and the database.
[12:59] <carlos> stub: yeah, if we move it inside launchpad servers we could use XML-RPC
[12:59] <carlos> or direct database access
[01:00] <carlos> stub: but daf didn't have such access at the time he wrote it
[01:03] <lifeless> what does dilys do these days?
[01:03] <lifeless> I thought it was just commit messages
[01:17] <murrayc> How can I report a launchpad/malone bug?
[01:17] <lifeless> http://launchpad.net/products/malone/+bugs
[01:18] <lifeless> or replace 'malone' with 'launchpad' if its not malone specific
[01:18] <murrayc> I don't know the difference between launchpad and malone.
[01:18] <lifeless> then just file it on launchpad
[01:18] <lifeless> http://launchpad.net/products/launchpad/+bugs
[01:20] <murrayc> Too late. Done it for malone. Thanks.
[01:20] <SteveA> stub: you thinking of having dilys connect to launchpad and poll for updates?
[01:20] <murrayc> Can I attach files to bugs in launchpad?
[01:21] <SteveA> you can
[01:21] <stub> There is a spec on dilys-ng. Basically an XML-RPC server that stuff on the LAN can send events to and it spits them out to IRC channels.
[01:21] <lifeless> stub: heh. theres a bunch of canned bots to do that. 
[01:21] <stub> Make it easy.
[01:22] <SteveA> we'll just apt-get install dylis then...
[02:01] <cprov> good morning, hackers
[02:03] <SteveA> hi celso!
[02:03] <SteveA> cprov: can you arrange that we have a skype call today about advanced permissions things?
[02:04] <SteveA> i'm busy for the next few hours, but later would be good for me.
[02:04] <cprov> SteveA: sure, after my lunch time 15 or 16 UTC or earlier ?
[02:04] <SteveA> 15UTC please
[02:05] <cprov> SteveA: okay, will se everything up 
[02:05] <SteveA> cool
[02:05] <SteveA> i got my skype working -- had to kill esd
[02:06] <cprov> SteveA: good to know, haven't tried in dapper yet
[02:10] <matsubara> good morning!
[02:21] <kiko> morning
[02:24] <kiko> how's it going guys
[02:31] <kiko> hey there
[02:31] <kiko> BjornT, stub, jamesh: would it be possible to make SoftRequestTimeout more useful? it's currently not very
[02:31] <ddaa> no good, I feel sick and have not managed to spend more than 20 mins at the computer in a row so far
[02:31] <SteveA> more useful like how?
[02:32] <SteveA> i mean, what is useless about them at present?
[02:32] <kiko> SteveA, all the exception messages are identical:
[02:32] <kiko> SoftRequestTimeout: <security proxied zope.app.pagetemplate.simpleviewclass.SimpleViewClass from
[02:32] <kiko> +/srv/launchpad.net/production/launchpad/lib/canonical/launchpad/templates/distroarchrelease-search.pt
[02:32] <kiko> +instance at INSTANCE-ID>
[02:33] <kiko> I find it unuseful to report what view class timed out -- I'd rather see something that suggested to me where the slowness was. mmmm
[02:33] <SteveA> that's hard to find out
[02:33] <SteveA> you have the timings of all the SQL statements
[02:34] <SteveA> we'd have to instrument the security proxy between the view and content classes, or something like that for other things
[02:34] <SteveA> or record the stack trace on every statement recorded
[02:34] <kiko> okay, never mind then.
[02:34] <kiko> here's a question
[02:35] <SteveA> worth talking through
[02:35] <SteveA> i'd like to hear the other folks' ideas
[02:35] <kiko> can we make any mixed-case URL redirect to a lower-case version?
[02:35] <SteveA> we could do
[02:35] <SteveA> what's the use-case?
[02:35] <kiko>       50 https://launchpad.net/distros/Ubuntu        
[02:35] <SteveA> we could get apache to normalize that
[02:35] <kiko> via http://trends.newsforge.com/trends/06/04/19/1527202.shtml
[02:36] <SteveA> ensuring the regex used was just the path part, not the query part
[02:36] <SteveA> or the anchor part
[02:36] <kiko> is that "yeah we could do that" or "let's do that today"?
[02:37] <SteveA> i don't see a risk in doing it
[02:37] <kiko> me neither
[02:37] <SteveA> because we are very careful with URLs in launchpad
[02:37] <SteveA> so, the only thing i'd ask is to get signoff from stub and lifeless
[02:37] <kiko> can you do that?
[02:38] <SteveA> and get someone who knows regexes to look at the URL RFCs and make a good regex
[02:38] <SteveA> and get lifeless to review it
[02:38] <SteveA> you can do a specific one for distros right away, if that's important
[02:38] <SteveA> or just for Ubuntu
[02:38] <stub> We have Foo.name's that are case sensitive (eg. sourcepackagenames)
[02:38] <kiko> not really important
[02:38] <kiko> stub, really? case sensitive spns?!
[02:38] <SteveA> stub: hmm... i don't approve of that :-/
[02:38] <stub> No reason not to do it in cases where we know the .name's are always lower
[02:39] <SteveA> is it possible to have two SPNs that are the same except for case, but are different SPs?
[02:39] <stub> SteveA: Yup. Unfortunately, we had to run with what already existed, and debian packages are case sensitive.
[02:39] <ddaa> hey stub
[02:39] <kiko> I didn't even know we had uppercase package names!
[02:39] <stub> I think it was packagenames
[02:39] <SteveA> that sucks
[02:39] <ddaa> I'm here if you need any help with branch handling on people merging
[02:40] <kiko> I have never heard of this
[02:40] <stub> branch names allow uppercase
 pitti, does debian have mixed-case package names?
 kiko: no.
 always lower case
[02:40] <kiko> that's more like it
[02:40] <kiko> branch names allow uppercase, eh? I thought all ".name"s were lowercase always
[02:41] <stub> version numbers are case sensitive
[02:41] <Keybuk> stub: no they're not
[02:41] <Keybuk> again, they can only be lower case
[02:42] <stub> Hey - I kicked and screamed every time someone insisted they needed to allow uppercase to be stored!
[02:43] <Keybuk> the sorting algorithm allows them to be upper case
[02:43] <Keybuk> but I don't think dpkg does
[02:44] <Keybuk> nope, sorry, I'm wrong :)
[02:44] <Keybuk> stub's right for versions, they can be mixed case
[02:44] <stub> IIRC, Branch.name needed to allow uppercase and '@' to map in existing arch branch names.
[02:45] <ddaa> That's an interesting point, but I'm not really convinced we want to do that.
[02:46] <ddaa> you mean, we _do_ allow that already?
[02:46] <SteveA> hmm... kiko, we can do this in traversal code instead then.   redirect, on a case by case basis
[02:46] <SteveA> do a perm redirect
[02:46] <stub> We _do_ allow it already. I'm happy to change it and rename branches with ugly names - I  don't think we need to keep that constraint the way it is any more.
[02:47] <ddaa> well, if it's there already, I'm not sure it's worth the trouble changing it until that becomes a problem
[02:47] <salgado> lifeless, "Unable to import paramiko (required for sftp support): No module named paramiko"
[02:47] <kiko> SteveA, yeah, that sounds reasonable. is it a trivial fix?
[02:47] <salgado> lifeless, that's one example of what we have on branch.mirror_status_message
[02:48] <ddaa> salgado: lifeless is going to call that a deployment problem, on the ground that it's conceivable that some people may use anonymous sftp.
[02:49] <SteveA> kiko: it's a trivial test...
[02:49] <ddaa> I should reply by mail, but my position is that this sort of thing should cause error mail, not crashing.
[02:50] <ddaa> salgado: OTOH I think it's appropriate to show that in the UI even if it's a problem with our system, just to explain why it did not work.
[02:52] <salgado> I'm not sure I agree
[02:53] <SteveA> kiko: we can do this in the Navigation base class, or a new Navigation base class
[02:54] <kiko> SteveA, or manually in the individual navigation classes?
[02:54] <SteveA> maybe do distro manually
[02:54] <SteveA> then we'll refactor for the second one
[02:55] <SteveA> it is important to do with with a perm. redirect
[02:55] <ddaa> You get to decide. In summary my position is that: 1. branch-puller should not crash unless it hits a serious problem 2. problems which are not strictly user-side should be logged so we know about them 3. as long as we have an intelligible error message, we should display it to the user instead of having to display "no error message".
[02:56] <ddaa> But anything that just keeps the damn thing running will make me happy.
[02:58] <kiko> SteveA, mpt: https://chinstrap.ubuntu.com/~jamesh/oops.cgi/2006-04-25/A28 
[02:58] <kiko> is that from somebody with an old CSS file?
[02:59] <SteveA> possibly
[02:59] <kiko> "possibly"?
[02:59] <SteveA> more likely something hardcoded into the menus system
[02:59] <SteveA> i don't really care -- it will go away very soon
[02:59] <SteveA> and the 404 isn't particularly visible to users
[03:03] <kiko> BjornT, bradb: what's this AssertionError in OOPS-115A198 -- ?
[03:03] <Ubugtu> https://chinstrap.ubuntu.com/~jamesh/oops.cgi/115A198
[03:04] <bradb> interesting...
[03:04] <kiko> matsubara, salgado: OOPS-115A330?
[03:04] <Ubugtu> https://chinstrap.ubuntu.com/~jamesh/oops.cgi/115A330
[03:05] <BjornT> kiko: my guess would be that debian doesn't have a current release
[03:05] <kiko> it doesn't
[03:05] <kiko> nor does fedora
[03:05] <kiko> code needs to cope though
[03:06] <matsubara> kiko: salgado reported that one yesterday
[03:06] <matsubara> kiko: and assigned it to me
[03:06] <kiko> okay
[03:06] <BjornT> yeah, and IDistribution should tell that currentrelease can be None
[03:06] <kiko> get that password nonsense DONE!
[03:06] <matsubara> kiko: I'm about to report the other oops you pointed to bradb and BjornT 
[03:06] <kiko> BjornT, agreed
[03:07] <bradb> kiko: I can land a quick fix for that oops if you want.
[03:08] <kiko> bradb, plus test? sure, rs=kiko
[03:08] <kiko> guys, remember, oopses are top-priority fixes
[03:08] <kiko> we get few enough that it shouldn't be immensely disruptive to land fixes
[03:12] <ddaa> got to let my body debug itself for a while, see you tomorrow
[03:16] <lucasvo> somenone should look at https://launchpad.net/products/distro-release-notes
[03:16] <matsubara> bradb: bug 41574
[03:16] <Ubugtu> Malone bug 41574 in malone "AssertionError while search in distribution context with currentrelease None" [Normal,Confirmed]  http://launchpad.net/bugs/41574
[03:18] <bradb> matsubara: thanks
[03:22] <kiko> BjornT, are we mapping REOPENED to UNCONFIRMED? it's actually Confirmed
[03:24] <BjornT> kiko: we map it to Confirmed. i think we used to map it to Unconfirmed, though.
[03:25] <kiko> really?
[03:25] <kiko> https://launchpad.net/products/ekiga/+bug/31763
[03:25] <Ubugtu> Malone bug 31763 in ekiga "Killing the panel makes ekiga disapear from the panel." [Unknown,Unconfirmed]  
[03:26] <kiko> BjornT, that's odd, because it still says Unconfirmed in the UI (and the last sync was on 2006-04-18 -- why?)
[03:26] <kiko> BjornT, when a bug in bugzilla goes from Unconfirmed -> Invalid - <reopen> > it goes back to Unconfirmed
[03:27] <kiko> the Reopened status is only used when the bug was New -> Invalid/etc - <reopen> -- then the status is Reopened.
[03:27] <kiko> (there is a special everconfirmed attribute in the Bug table that handles that)
[03:29] <BjornT> kiko: hmm, the syncing is broken due to the debbugs syncing breaking things :( i'll take a look at it.
[03:29] <kiko> BjornT, I am unhappy!
[03:49] <salgado> stub, is OOPS-115A436 the issue you've been working together with ddaa?
[03:49] <Ubugtu> https://chinstrap.ubuntu.com/~jamesh/oops.cgi/115A436
[03:55] <matsubara> salgado: for the record that's bug 41398
[03:55] <Ubugtu> Malone bug 41398 in launchpad "Oops On Merging Duplicate Account" [Normal,In progress]  http://launchpad.net/bugs/41398
[03:56] <bradb> kiko: Should the component search widget be disabled if we don't have an IDistribution.currentrelease?
[03:56] <bradb> Alternatively, it could search all releases.
[03:57] <kiko> bradb, you might even choose to not display it. search all releases? do you mean all components?
[03:57] <kiko> if so, then yes
[03:57] <bradb> all releases
[03:57] <kiko> all releases? how odd
[03:57] <kiko> what does the component search widget have to do with releases?
[03:58] <bradb> kiko: a package might be published in a different component in an earlier release
[03:58] <kiko> and?
[03:59] <bradb> we have no useful way of "guessing" which release this component search should be done in, unless there's a currentrelease
[03:59] <bradb> so it seems like search all releases, or don't allow component filtering
[03:59] <bradb> i thought of hiding the widget, but i think that's likely to be confusing
[04:00] <bradb> see what i mean?
[04:03] <kiko> hide the widget, IMO.
[04:04] <bradb> that's easiest to implement, so ok :P
[04:06] <kiko> cool.
[04:06] <kiko> you might need an additional assert somewhere 
[04:10] <BjornT> kiko: can you do a small review? https://chinstrap.ubuntu.com/~dsilvers/paste/filegmlnd1.html
[04:11] <kiko> BjornT, is debian_bug.severity None for valid reasons? is it a bug in debbugs?
[04:12] <kiko> BjornT, also, would you consider fixing the update-watches script to not blow up completely if something goes wrong?
[04:13] <BjornT> kiko: not sure actually, but that's what causing the breakage. i'll ask in #canonical to see if someone knows.
[04:13] <kiko> BjornT, other than that, r=kiko
[04:17] <BjornT> kiko: yes, i'll certainly consider it, i'll file a bug about it. it's quite trivial to make sure that all the other bug trackers get synced if one fails. to make all other bug watches for a specific bug tracker sync even if one fails is a bit trickier, though.
[04:17] <kiko> BjornT, really? why? is there internal state to consider?
[04:19] <BjornT> kiko: well, actually, now that i looked at the code, it's quite trivial to do that latter as well.
[04:20] <kiko> that's more like it!
[04:20] <kiko> I'd suggest making that change as well as we've already had a few crashes that caused everything with watch syncing to go haywire and I really want the feature to be bulletproof so we can pimp it effectively
[04:21] <BjornT> yeah, i'm going to include it in this patch.
[04:21] <Surak> is this heaven? https://launchpad.net/distros/ubuntu/dapper/+bugs Bugs in Dapper: 1                  1         of         1 result
[04:22] <kiko> Surak, no, it's just a confusing UI.
[04:22] <bradb> This is why I think distroreleases having their own bug listing is very confusing. :)
[04:24] <kiko> bradb, the bug listing would be a bit different -- +targetedbugs or +releasebugs or something
[04:25] <kiko> bradb, this has to do with targeting to releases which is what we need to start working on as soon as bug dates are sorted
[04:25] <bradb> I've been nagging since Friday for a response to my code review response, unfortunately. Halt, screeching, etc.
[04:26] <bradb> (on bug dates, that is)
[04:27] <kiko> get another reviewer
[04:27] <kiko> don't ask steve or me for reviews this week
[04:27] <kiko> we need to do staff reviews and that eats up a lot of time
[04:29] <bradb> I don't ask anyone for reviews anymore. I just use the General Queue, and they seem to automatically get redirected to the appropriate people.
[04:29] <kiko> okay then
[04:29] <bradb> salgado: Can you please followup on the bug dates review today?
[04:32] <salgado> bradb, yeah, sorry for not doing that before. I got sidetracked with some mirror-prober things yesterday
[04:32] <kiko> mirror probing is farked
[04:33] <bradb> no worries
[04:34] <Surak> thanks kiko
[04:36] <kiko> carlos, yo, what's up
[04:36] <carlos> kiko: hi
[04:36] <kiko> where's my fix!
[04:36] <carlos> answering a loooong queue of pending mail...
[04:36] <carlos> kiko: on the pending reviews queue
[04:37] <carlos> ;-)
[04:37] <kiko> was it a big fix? you could have pastebinned it for me if not
[04:37] <carlos> no it's a small one
[04:37] <carlos> kiko: one line change and the test
[04:37] <kiko> then!
[04:38] <carlos> let me show you the diff
[04:39] <carlos> kiko: https://chinstrap.ubuntu.com/~dsilvers/paste/fileqXo6Dc.html
[04:39] <SteveA> BjornT: http://www.mkuncaitis.com/lbw06/
[04:40] <kiko> carlos, the "..." in the test before </textarea> is what I don't approve
[04:40] <SteveA> BjornT: the linux bier wanderung is in lithuania this year
[04:40] <carlos> kiko: why?
[04:41] <kiko> carlos, because it might match something else more bizarre. I don't know, but I don't like it. can you fix it easily?
[04:42] <carlos> kiko: you want the whole html page there??
[04:42] <kiko> the </textarea> should be closeby, no?
[04:42] <BjornT> kiko: https://chinstrap.ubuntu.com/~dsilvers/paste/fileiSHmip.html (basically wrapping two sections into try...except)
[04:43] <carlos> kiko: oh, sorry, I misunderstood you
[04:43] <kiko> I mean, there shouldn't be a lot of text after the ";] "
[04:43] <carlos> the ... before the closing tag...
[04:43] <kiko> right
[04:43] <kiko> right
[04:43] <carlos> well, the sample data has 12 lines
[04:43] <carlos> I could either leave the whole text
[04:43] <carlos> or add the last two lines
[04:43] <carlos> with ... in the middle
[04:44] <kiko> carlos, maybe change the sampledata? or will it kill you?
[04:44] <carlos> well, I prefer if we don't change sampledata...
[04:44] <carlos> hmm, let's change it
[04:44] <carlos> and if nothing breaks
[04:44] <carlos> it's ok
[04:44] <kiko> good man
[04:45] <carlos> but if other test fail I prefer to leave it as it's atm
[04:45] <carlos> I'm using a language I'm not using usually in our tests so it should not be an issue
[04:45] <BjornT> SteveA: cool, that could be nice to go to.
[05:05] <matsubara> kiko, SteveA: could you give some input to the comment I added in bug 28908?
[05:05] <Ubugtu> Malone bug 28908 in launchpad "phishing vulnerability" [Normal,Confirmed]  http://launchpad.net/bugs/28908
[05:06] <dilys> Merge to devel/launchpad/: [trivial]  Add UNIQUE to branch table and update people merge code to cope (r1824: Stuart Bishop)
[05:06] <kiko> yay stubber
[05:08] <SteveA> matsubara: hmm, looks good to me at a glance, but i'd like to think further about this.  maybe you can ask ian jackson (the reporter of the bug) what he thinks of your solution?
[05:16] <kiko> matsubara, SteveA, stub's the right person to ask there, I think
[05:16] <kiko> I remember he and salgado had a good idea of why we asked for the password as part of that step
[05:18] <salgado> IIRC it was just to make sure it the email validation (or whatever it is) wasn't done simply by a person clicking on the link
[05:19] <salgado> IOW, we wanted them to read, see what's going on and confirm that they want that
[05:19] <kiko> they could just press an OK button though
[05:20] <salgado> right, that's why I suggested removing the password to matsubara
[05:24] <kiko> stub might remember
[05:24] <kiko> matsubara, email him directly?
[05:25] <matsubara> kiko: I'll. I also left a note to iwj to take a look at the bug and give some input.
[05:25] <kiko> thanks
[05:32] <SteveA> cprov: ping
[05:32] <cprov> SteveA: setting up the skype sh#$, one sec
[05:35] <cprov> SteveA: seems to work, how is your contact ? ehe 'global-gypsy' ?
[05:35] <SteveA> cprov: i need to get a glass of water.  i'll start up the program
[05:36] <cprov> SteveA: okay
[05:40] <jordi> woah, what's going on with the spamfest at rosetta-users...
[05:46] <carlos> jordi: I'm scared...
[05:47] <jordi> the volume of spam is rising so much it's not funny
[05:48] <carlos> jordi: are you banning the emails from where we get more than one message?
[05:49] <jordi> yes
[05:50] <jordi> there was one address with like 20 posts the other day
[05:50] <dilys> Merge to devel/launchpad/: [rs=kiko]  Fix bug 41574 (AssertionError while search in distribution context with currentrelease None) (r1825: Brad Bollenbach)
[06:24] <dilys> Merge to devel/launchpad/: [r=kiko]  Fixed a pagetemple that was using 'struct' and was rendering '<' and '>' instead of '&lt;' and '&gt;'. Includes a test. (r1826: Carlos Perello Marin)
[06:24] <carlos> cool
[06:24] <carlos> dilys: thanks!
[06:25] <kiko-fud> carlos, remember to fix the db when the time comes. congratulations -- but you forgot the bug number and oops ID. talk to matsubara :)
[06:25] <kiko-fud> fuderinos!
[06:25] <carlos> hmm, rigth.... :-(
[06:25] <matsubara> carlos: bug 39879
[06:25] <Ubugtu> Malone bug 39879 in rosetta "Translation string is crashing replacer function" [Major,Fix committed]  http://launchpad.net/bugs/39879
[06:26] <carlos> kiko-fud: I will do it once it's on production
[06:26] <matsubara> carlos: OOPS-104D147
[06:26] <Ubugtu> https://chinstrap.ubuntu.com/~jamesh/oops.cgi/104D147
[06:29] <carlos> matsubara: well, is a bit late to add the OOPS... but thanks 
[06:29] <matsubara> carlos: np, I don't know why kiko asked you to talk to me.
[06:30] <carlos> matsubara, kiko-fud: bug #41371 is weird and produced by #39879
[06:30] <Ubugtu> Malone bug 41371 in rosetta "& strings not stayed "as-is" on Rosetta" [Normal,Needs info]  http://launchpad.net/bugs/41371
[06:30] <carlos> I didn't know we could get those transformations on submit...
[06:31] <carlos> &gt; became '>' after two submits
[06:32] <carlos> not visually but in our database
[06:32] <carlos> is shop time, see you!
[06:33] <BjornT> carlos: i think that's because 'structure' was used
[06:33] <carlos> BjornT: well, structure prevented that we escape chars
[06:34] <BjornT> carlos: first enter '&lt;' -> '&lt;' gets stored the database, but displayed as '>' in the text area
[06:34] <carlos> but you submit &gt; and we render '>' but the source code has &gt;
[06:34] <BjornT> carlos: if you submit the textarea again, you'll store '>' in the database, since that's the value in the text area.
[06:34] <carlos> and next time you submit it, we get directly '>' 
[06:34] <carlos> right
[06:35] <carlos> anyway, it's fixed ;-)
[06:35] <BjornT> oh, it sounded like you thought that it wasn't fixed :)
[06:35] <carlos> no, I set it as duplicate already
[07:08] <dilys> Merge to devel/launchpad/: [r=kiko]  fix crash in checkwatches.py. also makes the script more robust, so that unexpected exceptions are simply logged instead of breaking the script. (r1827: Bjorn Tillenius)
[07:48] <heyko> /j #esens
[07:49] <heyko> sry
[08:54] <crimsun> if I suspect that my uploads to Ubuntu universe/multiverse are being dropped silently due to a GPG key issue, against which package(s) should I file a bug?
[09:05] <poningru> I wanted to create a new spec for easyencryption in the wiki but it wont let me edit the page
[09:05] <poningru> https://launchpad.net/distros/ubuntu/+spec/easy-encryption
[09:05] <kiko> poningru: hmmm?
[09:06] <poningru> hmm it might be problem at my end hold on
[09:17] <matsubara> kiko: I think poningru is having the same problem someone was having a couple of days ago. Remeber when someone asked you to change the wiki page of a spec? I think it was yesterday or the day before.
[09:17] <kiko> yesterday evening
[09:17] <kiko> and I suspect the same
[09:17] <poningru> nm it was a cookie problem
[09:17] <poningru> it works now
[09:18] <kiko> wonderful
[09:24] <crimsun> cprov: (referred to you by -devel.) Hi, I suspect my uploads to Ubuntu universe/multiverse have begun being dropped silently within the past day due to a GPG key issue (0xC88ABDA3). Is there protocol for providing information to ease debugging?
[09:26] <kiko> that's unfortunate, crimsun. is no answer received, and no email sent to -changes? also, what packages are they?
[09:26] <kiko> hey bradb*
[09:27] <bradb_> hey
[09:28] <sfllaw> Is there a fridge.ubuntu.com team that mirrors its calendar?
[09:30] <crimsun> kiko: I receive nothing whatsoever when I use crimsun@ubuntu.com in the changelog. When I use crimsun@fungus.sh.nu in the changelog, I receive accept notifications when someone else uploads. I don't receive anything when I upload. Mail is sent to changes only when someone else signs and uploads. The source package in question is flashplugin-nonfree (multiverse). I attempted to upload it three times yesterday and received nothing, no reje
[09:31] <kiko> crimsun, I think it's time for a bug report. you have a lot of detailed information. :)
[09:31] <cprov> crimsun: I remember your package being processed this morning
[09:31] <crimsun> yeah, I asked earlier for the name of the package/component against which I should file a bug
[09:32] <crimsun> cprov: jani signed and uploaded the latest.
[09:32] <crimsun> cprov: janimo, that is.
[09:32] <crimsun> the revision prior to that one was signed and uploaded by laserjock (jordan mantha).
[09:34] <crimsun> my last upload that is known to have worked using my own key is https://lists.ubuntu.com/archives/dapper-changes/2006-April/009419.html
[09:38] <cprov> crimsun: investigating the log it looks like sending email to you @u.c, is your redirec working, preferred email set ?
[09:38] <cprov> crimsun: to better debug the issue with your key, please upload something else and warn me
[09:39] <crimsun> cprov: redirect is currently working, but I don't receive notifications from archive@ubuntu.com when I use crimsun@ubuntu.com
[09:41] <crimsun> cprov: I'm not terribly concerned with not receiving notifications @ubuntu.com, which seems orthogonal. I've had trouble before with my key and launchpad, which is sign-only.
[09:41] <cprov> crimsun: ideally it should send info to your preferred_email (crimsun@fungus.sh.nu) is it working ?
[09:42] <crimsun> cprov: my preferred email is working, and mails sent to crimsun@ubuntu.com from elsewhere are delivered to crimsun@fungus.sh.nu
[09:42] <cprov> crimsun: duderino, this sign-only key issue ... nevermind :(
[09:43] <cprov> crimsun: right, it requires some investigation on redirect system so far
[09:44] <salgado> hey bradb_. the bug-dates branch looks good
[09:44] <cprov> crimsun: just for up to date debug info, upload something signed by your own key and we can investigate the issue w/o any expeculation, okay ? 
[09:44] <crimsun> cprov: yes, I'm looking for a test patch so I can upload
[09:45] <cprov> crimsun: good
[09:45] <bradb_> salgado: cool, thanks
[10:10] <cprov> kiko: crimsun is another victim of bug # 41102
[10:10] <cprov> hell bug 41102
[10:10] <Ubugtu> Malone bug 41102 in qprocd "Could not upload any Universe packages; email parsing bug?" [Major,In progress]  http://launchpad.net/bugs/41102
[10:10] <kiko> cprov, yeah, I was thinking that half of his problem was that.
[10:10] <cprov> duhh
[10:10] <kiko> but there's something else as well, right?
[10:11] <cprov> kiko: not really, let me paste the log message for you
[10:11] <cprov> kiko: https://chinstrap.ubuntu.com/~dsilvers/paste/fileCgwn2b.html
[10:12] <kiko> hey bradb 
[10:12] <bradb> hey again
[10:13] <kiko> cprov, yeah. but what about the key-problem he was suggesting?
[10:13] <kiko> I thought crimsun was having two different problems?
[10:14] <cprov> kiko: I thought he was using his key this time, so it works 
[10:20] <crimsun> thanks again, kiko, cprov.
[10:24] <jordi> hmm, carlos, why is rosetta-@ subscribed to that xfce bug?
[10:24] <jordi> the one about USB devices
[10:25] <kiko> jordi, BjornT's working on unsubscribing teams, btw
[10:25] <jordi> oh... so I can't do it atm now I realise
[10:26] <kiko> bradb, could we add warning icons the checkboxes in +filebug?
[10:26] <kiko> s/the/to the/
[10:27] <carlos> jordi: someone added us
[10:27] <kiko> mdz, bradb, another question is: should the assignee be messaged on private bugs?
[10:28] <mdz> kiko: the assignee should be treated the same as a subscriber in that respect, I'd say
[10:28] <kiko> yeah
[10:28] <kiko> okay
[10:28] <kiko> bradb_, bradb: internet problems today?
[10:28] <bradb_> something like that. pfff
[10:29] <bradb_> my other machine's fine though
[10:34] <jordi> I wanted to habve a nap of 40 mins
[10:34] <jordi> it was 4h by accident
[10:34] <jordi> there's no way I'm going to sleep tonight
[10:35] <kiko> wow
[10:35] <jordi> ooh
[10:35] <jordi> and I missed Barcelona
[10:35] <jordi> oh man
[10:35] <jordi> But Bara is in the final!
[10:37] <bradb_> kiko: Yes, assignee should get messaged no private bugs. The real issue, I think, is not "should" but "how" do we make that work.
[10:38] <bradb_> s/no private/on private/
[10:38] <kiko> bradb_, really?
 bradb, could we add warning icons to the checkboxes in +filebug?
[10:39] <bradb_> kiko: How could it make sense for someone to be assigned to a bug but not get email about it?
[10:39] <kiko> right
[10:39] <kiko> I agree. I was just confused as to why "how" was an issue
[10:39] <bradb_> ah
[10:40] <bradb_> Well, the issues I see are:
[10:40] <bradb_> 1. Should setting the assignee subscribe them to the bug? (i.e. add them to the Cc list) The answer seems obvious, given how privacy works, but then,
[10:41] <bradb_> 2. What if they are unassigned?
[10:41] <bradb_> it's hard to know if un-Cc'ing them will be right
[10:42] <kiko> mmmm
[10:42] <bradb_> We could have some UI for this workflow which could help make it understandable.
[10:43] <bradb_> Any time the assignee value is changed, we could confirm that the user is sure they want to subscribe this new assignee/unassignee the previous one.
[10:44] <bradb_> (Same deal for subscriptions. We could special-case private bug subscriptions to make it much harder for a typo to expose a bug to the wrong person.)
[10:45] <kiko> bummer.
[10:45] <bradb_> er, s/unassignee/unsubscribe/
[10:45] <kiko> the other option is to have the assignee be implicitly subscribed even in private bugs.
[10:46] <bradb_> I thought about that...it could almost make sense, specifically for assignee, because it's someone that has to do work on the bug, so it's clear they should be getting email about it.
[10:46] <bradb_> Just wondering when that wouldn't work...
[10:48] <bradb_> kiko: re: warning icons, you mean just add icons to the left of the labels?
[10:48] <kiko> bradb_, yes
[10:49] <kiko> for private bugs I think we should add it, but then.. it makes the security option a bit confusing
[11:02] <bradb_> kiko: fwiw, I haven't heard to many people be confused about those options on +filebug
[11:02] <bradb_> s/to/too/
[11:02] <kiko> mmmm
[11:02] <kiko> mdz says it happens ALL THE TIME
[11:03] <kiko> :)
[11:03] <bradb_> hmph
[11:04] <mdz> I see it a few times a week if I am paying attention to bugs
[11:04] <mdz> but I mostly go through old bugs
[11:04] <mdz> the one ogra just pointed out is a new bug though; it's clearly still happening
[11:05] <mdz> perhaps we should ask the reporter what happened
[11:07] <bradb_> mdz: which bug?
[11:10] <mdz> bradb_: bug 41649
[11:10] <Ubugtu> Malone bug 41649 in dhcp3 dhcp3-server "Lease not released on shutdown" [Normal,Unconfirmed]  http://launchpad.net/bugs/41649
[11:13] <bradb_> mdz: What's the issue with that bug reported, related to private/security-related filebug options?
[11:13] <bradb_> s/reported/report/
[11:13] <mdz> bradb_: it was filed as private with no apparent reason
[11:13] <kiko> correct.
[11:13] <mdz> the reporter un-privated it, and I subscribed ubuntu-bugs to clean up
[11:14] <bradb_> ah
[11:53] <ychahibi> I read in the Rosetta mailing-list , that you are planning to add glossary feature to Rosetta, I'd interested to know how you are proceeding since I am preparing a draft glossary for Arabic.
[11:54] <kiko> ychahibi, the best person to ask would be carlos, but he's not around at the moment 
[11:54] <kiko> jordi may be able to help as well
[11:56] <jordi> ychahibi: the plan is there, but I don't think there are plans to start on that right away
[11:59] <ychahibi> jordi: Gnome has a PO file glossary in many languages : http://l10n-status.gnome.org/HEAD/PO/
[12:01] <jordi> yes
[12:01] <jordi> it's unmaintained though
[12:03] <ychahibi> jordi, I am actually looking for a maximal number of terms . There is also http://l10n.openoffice.org/localization/OpenOffice_Glossary.html