[12:19] <bradb_> kiko: I do feel a certain urgency, I think, to moving events into the db, fwiw.
[12:20] <bradb_> considering that i just put xmlrpc up for review, etc.
[12:20] <bradb_> which is another client that publishes the event, and that's generally evil
[12:24] <kiko> my point exactly
[12:24] <bradb_> pastebin seems to be 404'ing, so i'll email the patch
[12:25] <kiko> sure
[12:25] <bradb_> sent
[12:26] <flacoste> nice week-end everybody!
[12:26] <bradb_> interestingly, this would also remove a huge amount of manual notify()'s from our tests as well
[12:27] <kiko> heh
[12:30] <kiko> bradb_, that assert is confusing.
[12:30] <kiko> and PQM is @#!@$! sandbagging me.
[12:30] <kiko> wtf is up with PQM
[12:30] <kiko> no failure
[12:30] <kiko> nothing
[12:31] <bradb_> kiko: it takes time sometimes
[12:31] <kiko> hmmm.
[12:31] <bradb_> though sometimes it doesn't :P
[12:31] <kiko> I think the merge is failing
[12:31] <kiko> http://pqm.launchpad.net/
[12:31] <bradb_> kiko: ok, so how can i improve the assert?
[12:31] <kiko> cleaning working directory
[12:31] <kiko> Executing star-merge sftp://chinstrap.ubuntu.com/home/warthogs/archives/kiko/launchpad/trivialities-xx/ at Fri Jul 14 23:10:33 2006
[12:31] <kiko> cleaning working directory
[12:31] <kiko> let me look at the code first
[12:32] <kiko> bradb_, okay, remove the assert, it's silly.
[12:32] <kiko> I was thinking something that obviously doesn't hold true in this situation
[12:33] <bradb_> removed!
[12:33] <kiko> yeah
[12:33] <kiko> patch is fine, r=kiko
[12:33] <kiko> nice work.
[12:33] <kiko> bradb_, can you land a patch that PQM refuses to merge for me?
[12:34] <kiko> it's the fix for bug 52934
[12:34] <Ubugtu> Malone bug 52934 in malone "bug comment ordering broken" [High,In progress]  http://launchpad.net/bugs/52934
[12:34] <bradb_> sure, but why would it merge for me if not you?
[12:34] <bradb_> kiko: thanks for the review, btw.
[12:34] <bradb_> why they heck is chinstrap asking me for a password
[12:34] <kiko> bradb_, I have no clue, but my branch may be broken and I don't have a lot of time left
[12:35] <kiko> bradb_, uhh same here
[12:35] <bradb_> kiko: they're dragging me out of the office too, but if you can tell me to do, i can do it when i get home
[12:35] <kiko>  merge from  sftp://chinstrap.ubuntu.com/home/warthogs/archives/kiko/launchpad/trivialities-xx/ to sftp://chinstrap.ubuntu.com/home/warthogs/archives/rocketfuel/launchpad/devel
[12:35] <kiko> that's essentially it.
[12:35] <kiko> hmmm
[12:35] <kiko> what if the patch didn't get pushed?
[12:35] <kiko> I'll email you the patch, you know, JIC.
[12:36] <bradb_> kiko: emailing the patch would be easier actually, yeah
[12:37] <kiko> sure thing.
[12:38] <bradb_> +filebug, the DC, gah, what a friday evening
[12:39] <bradb_> kiko: is there any way into chinstrap then?
[12:39] <kiko> nope
[12:39] <kiko> see #canonical
[12:39] <bradb_> yeah, hmph
[12:40] <bradb_> oh well, i've done what i can here, i guess i'll check up on it tonight or tomorrow morning
[12:40] <kiko> sure thing
[12:41] <bradb_> kiko: I'll be looking for your patch in my Inbox too. /me heads off
[12:41] <bradb_> later all
[02:23] <Lord_Athur> hi all
[02:23] <Lord_Athur> in the page: https://launchpad.net/people/alejandro-leonvega/+editpgpkeys I could see the command: "gpg --send-key key-id", what does "key-id" meam?
[02:24] <Lord_Athur> :), I'll be absent for a while, I wait for the answer with respect. :)
[02:40] <Lord_Athur> I'm back
[02:44] <Lord_Athur> No one knows what to do?
[03:08] <Lord_Athur> in the context of a  launchapad webpage, what's karma?
[03:30] <Lord_Athur> I need some help
[03:35] <ruffneck> nice =)
[03:35] <ruffneck> karma? I dunno, sounds Indian
[03:36] <Lord_Athur> I've solved my problem, thanks anyway
[10:27] <Hobbsee> hi all.  i know we've changed the level of people who can set the status for a bug, but can we have a checkbox of "this is a wishlist", just like for security, and that changes the importance of the bug?  
[10:48] <mpt_> Hobbsee, I doubt it
[10:48] <mpt_> If we make any changes to the Wishlist value, it'll probably be removing it
[10:48] <Hobbsee> mpt_: it is rather useful.  although the bugs are more useful filed upstream, i guess
[10:49] <mpt_> since there can be Major wishlist items (our competitor has this feature and we must have it too!), minor wishlist items, trivial wishlist items, etc
[10:49] <mpt_> so maybe a "This is a feature request, not a bug" checkbox
[10:52] <Hobbsee> mpt_: yeah, that's what i'm asking for.  set at the time of bugwriting.
[10:52] <mpt_> but I've found there is no reliable distinction between bugs and feature requests
[10:52] <mpt_> and Trac gets along fine without it
[10:52] <Hobbsee> mpt_: being a part of -qa myself, i dont really mind, but i know some of the other kde devs are finding it a problem, when they cant set anything as a wishlist, etc
[10:52] <mpt_> Why can't they?
[10:52] <mpt_> Are they not a member of the appropriate team?
[10:55] <spiv> I guess you could use specs for this, but specs are rather heavy-weight for a casual user to use to make a feature request.
[10:56] <mpt_> spiv, can I get an rs= on making all Launchpad's <img> elements valid XHTML? Very boring and safe, but touches 19 files
[10:57] <spiv> mpt_: what's an example of the change?
[10:57] <Hobbsee> mpt_: yeah, they're not part of ubuntu-qa, and they're keeping ubuntu-qa pretty small.
[10:57] <mpt_> spiv:
[10:58] <mpt_> - <img src="/@@/user">
[10:58] <mpt_> + <img alt="" srce="/@@/user" />
[10:58] <ivoks> src, instead of srce :)
[10:58] <mpt_> src, yes
[10:58] <mpt_> (that was not copied and pasted :-P )
[10:59] <ivoks> excuses, excuses... :)
[10:59] <ivoks> i'm having big problems with rosetta for couple of weeks now
[10:59] <spiv> So just ensuring they have an alt attribute, basically?  rs=spiv, sure.
[10:59] <mpt_> spiv, and the /> instead of >
[10:59] <mpt_> thanks
[10:59] <ivoks> it refuses to import anything i upload
[11:00] <ivoks> actually, it says it's uploaded, but never gets in import queue or it gets, but stays in "Needs review" state
[11:00] <ivoks> any idea? :/
[11:00] <mpt_> ivoks, you need to prod jordi or carlos
[11:01] <ivoks> ok
[11:01] <mpt_> they're the people who handle the import queue
[11:20] <mpt_> spiv, I can't access chinstrap any more
[11:20] <elmo> mpt: /topic in chinstrap - I'm working on it
[11:20] <elmo> blah
[11:20] <elmo> I suck 
[11:20] <mpt_> oh
[11:20] <elmo>  /topic in #canonical even
[11:20] <elmo> is what I meant to say
[11:21] <mpt_> thanks elmo
[11:21] <elmo> someone restore the topic in here?  I don't have it in history
[11:22] <elmo> thanks
[03:16] <elmo> LP is going offline for a couple of minutes for some necessary maintenance
[03:18] <elmo> (bakc)
[04:29] <omeow> Hi, how can I remove myself from launchpad and everything associated with it? I checked the FAQ and it's not described there.
[04:39] <danilos> omeow: you probably can't if you've authored anything in it (it would mean breaking referential integrity)
[04:40] <omeow> Ok.
[04:40] <omeow> Can you explain to me how the hide email address from other users feature is supposed to work?
[04:40] <omeow> I've got that enabled and clicking on my name points to https://launchpad.net/people/omega-blackcatgames
[04:41] <omeow> Anyone with a brain can figure out that the URL contains a partial email address.
[04:42] <danilos> omeow: at the risk of presenting myself as someone without a brain, I can't figure it out
[04:42] <lifeless> just change your name on https://launchpad.net/people/omega-blackcatgames/+edit
[04:42] <omeow> Ah I see.
[04:43] <omeow> danilos, well, my email address is omega@blackcatgames.com
[04:45] <omeow> Therefor I thought that the hide email address thingy wasn't working very well.
[04:46] <lifeless> btw, this channel is logged
[04:46] <lifeless> so if you wantted to keep that email address private.. :)
[04:47] <omeow> neat :)
[04:48] <LarstiQ> well, it is discoverable from the blackcatgames site anyway
[04:50] <omeow> How's that?
[04:51] <LarstiQ> http://www.blackcatgames.com/team.html
[04:52] <omeow> Hmhm. 
[04:52] <LarstiQ> omeow: I'll wager any of those teammembers has a good chance of working as the local part
[04:53] <omeow> Yeah, anyway, I just figured that hiding it from launchpad would mean that by default, I wouldn't be able to see anything closely related to my email address if the option was switched on.
[04:55] <LarstiQ> pardon?
[04:56] <omeow> Sorry, I'm not a native english speaker so my sentences sometimes come out a little odd.
[04:57] <LarstiQ> Nederlands versta ik ook wel, maar de rest van het kanaal niet.
[04:57] <omeow> I thought that switching on the option "hide email address from other launchpad users" would mean that by default, it wouldn't show part of my email address in the link to my profile.
[04:58] <omeow> That make sense to you? :)
[04:58] <LarstiQ> omeow: Yes. 
[04:59] <LarstiQ> omeow: However, the part after people is entirely your name, so that won't work :)
[06:37] <jordi> woah this has to be kidding me
[06:37] <jordi> the queue has 56K files for the distro branch
[06:46] <LarstiQ> what does that mean?
[09:02] <jenda> Am I mistaken or does LP give insane amounts of karma for specs?
[09:05] <LarstiQ> jenda: you're not mistaken
[09:06] <jenda> Indeed.
[09:06] <LarstiQ> jenda: iirc, this is because each area (specs, bugs, translations, etc) has the same amount of karma, divided over each contributor
[09:06] <LarstiQ> and since not a lot of people write specs, well.
[09:07] <jenda> BTW, my branch is up and running, up to 5 MiB now :)
[09:07] <jenda> I see, that makes sense.
[09:07] <jenda> Would that also explain why karma goes down by bits?
[09:10] <LarstiQ> no, I believe there is some decay mechanism for that
[09:10] <jenda> I see. OK, that's cool.
[09:10] <LarstiQ> but all this I've only gathered by hanging around here and on launchpad-users, for a definitive answer you should ask an lp dev
[09:11] <jenda> It's good enough for me - I'm just curious.
[09:11] <jenda> Would bzr pushes contribute to karma too?
[09:12] <LarstiQ> hmm, I don't think so
[09:13] <LarstiQ> most of my karma comes from bug management, and some from translations
[09:13] <LarstiQ> jenda: so no branches
[09:14] <jenda> OK
[09:17] <mdz> cprov: ping?
[09:17] <cprov> mdz: pong
[09:17] <mdz> cprov: this build seems like it might be wedged: https://launchpad.net/+builds/+build/225738
[09:17] <mdz> Date built:
[09:17] <mdz> 2006-07-14 06:15:17 PDT 
[09:17] <mdz> the build log looks like it completed (failed)
[09:18] <mdz> but it still says Currently building, and the builder isn't taking any more packages
[09:18] <cprov> mdz: I see, something went wrong in the builddmaster
[09:20] <cprov> mdz: I'm running slavescanner by hand with debug
[09:21] <mdz> thanks
[09:23] <mdz> the other amd64 builder is busy with the kernel, so things are queueing up
[09:23] <cprov> mdz: crested seems to be building subversion 
[09:23] <cprov> 2006/07/15 20:19 BST [-]  Build log: Running all tests in history_tests.py...success
[09:23] <mdz> cprov: oh, hmm.  the existing build log is from yellow
[09:23] <mdz> maybe someone reset it then?
[09:24] <cprov> mdz:  can I restart the build ?
[09:24] <cprov> mdz: alright
[09:24] <mdz> cprov: is the build stuck or is it actually going?
[09:24] <mdz> https://launchpad.net/distros/ubuntu/edgy/amd64/+builds?build_state=building&build_text= says Requested 2006-07-10 09:52:59 PDT in pocket RELEASE
[09:24] <mdz> which was of course 5 days ago
[09:25] <mdz> cprov: if you could kill it and just let it take the next builds in priority order, that would be best
[09:25] <mdz> there are more important builds than subversion in the queue
[09:25] <cprov> mdz: will do
[09:33] <cprov> mdz: things seem to fine now, I'll be around ping me if you need
[09:40] <mdz> cprov: thanks
[09:54] <mdz> yay, gnome-python-extras built
[09:54] <mdz> cprov: that should allow a lot of failed builds on i386/amd64/powerpc to finish
[09:55] <mdz> cprov: is there a way to retry them all?
[09:55] <cprov> mdz: not exactly, but we can retry each arch
[09:56] <mdz> I don't remember which builds were failing due to this packa7package
[09:56] <cprov> mdz: let me find them
[09:57] <cprov> mdz: amd64 & powerpc are ok
[09:58] <cprov> mdz: ia64 & sparc failed
[10:02] <cprov> mdz: https://launchpad.net/+builds/+build/226385 & https://launchpad.net/+builds/+build/226384, do you want me to retry them ?
[10:02] <mdz> cprov: I'm not concerned with ia64 or sparc right now, but want to get amd64 and powerpc back into shape for a milestone
[10:03] <mdz> I'll check totem/sparc and see if it's ready
[10:03] <mdz> cprov: totem/sparc built OK
[10:03] <mdz> cprov: so we can retry all release arches
[10:04] <mdz> that is, we should retry failed builds for other packages on amd64 and powerpc now, and sparc after gnome-python-extras builds
[10:04] <mdz> I reset gnome-python-extras/sparc already
[10:04] <cprov> mdz: we can't do massive retries yet :(
[10:05] <mdz> cprov: the buildd admins have some way to do it, maybe a script
[10:05] <cprov> mdz: psql ;)
[10:06] <mdz> probably
[10:13] <LarstiQ> spiv: did you get around to that bzr info -v patch yet?
[10:20] <mdke_> hi all
[10:21] <mdke_> if bzr get is giving me this error, it means that my version of bzr is too old right?
[10:21] <mdke_> bzr: ERROR: Knit header error: '# bzr knit index 8\n' unexpected
[10:21] <jenda> ouch...
[10:21] <jenda> Could the command i gave you be wrong?
[10:21] <LarstiQ> mdke_: yes
[10:22] <LarstiQ> mdke_: you are using either 0.7 or a 0.8 prerelease
[10:22] <LarstiQ> mdke_: you need 0.8 or higher
[10:22] <mdke_> I appear to have 0.8~200603240905 
[10:22] <LarstiQ> right, ditch that asap :)
[10:22] <mdke_> I have deb  http://people.ubuntu.com/~jbailey/snapshot/bzr/ ./
[10:22] <mdke_> is that not up to date?
[10:23] <LarstiQ> apparently not, and the packaging of bzr is in transit from jeff to someone else also
[10:23] <LarstiQ> mdke_: why not use what is in dapper?
[10:23] <mdke_> LarstiQ: because it's a breezy machine
[10:23] <mdke_> the dapper package will work fine I guess?
[10:24] <LarstiQ> mdke_: not sure about dependencies, but in general, yes
[10:24] <mdke_> LarstiQ: is that my best option?
[10:25] <LarstiQ> mdke_: any chance you can upgrade the breezy machine?
[10:25] <mdke_> LarstiQ: it's on one of the external servers that canonical rents, apparently they have had some issues with dist-upgrading so I've been holding off
[10:26] <LarstiQ> mdke_: fair enough
[10:26] <mdke_> ok, I'll try the dapper package
[10:27] <mdke_> oh, some python dependencies
[10:27] <mdke_> thanks
[10:28] <mdke_> who's doing the packaging now?
[10:28] <LarstiQ> mdke_: I personally run bzr from source everywhere
[10:28] <LarstiQ> mdke_: hmm, Etienne I think?
[10:28] <LarstiQ> me neither
[10:30] <mdke_> ok, works. Thanks!
[10:31] <LarstiQ> glad to be of help
[10:35] <mdz> cprov: https://launchpad.net/+builds/+build/227962 says that gnome-applets 2.15.1.1-0ubuntu2 built for powerpc on 2006-07-13, but it isn't in the archive. any idea what happened?
[10:37] <mdz> cprov: locate doesn't find the binaries anywhere on drescher
[10:40] <cprov> mdz: possible a side-effect of bug #36468
[10:40] <Ubugtu> Malone bug 36468 in launchpad-buildd "builddmaster appears to batch process by accident?" [Medium,Fix committed]  http://launchpad.net/bugs/36468
[10:45] <mdz> cprov: if I reset the build, will that fix it?
[10:45] <mdz> cprov: or do I need to upload new source?
[10:46] <cprov> mdz: we can't reset fullybuilt builds, we can rescue the builds with SQL black-magic, another source would fix it easily
[10:47] <mdz> cprov: ok, that will take an extra hour but I can do it
[10:47] <cprov> mdz: I mean, not this build, but the archive absence
[10:47] <mdz> hmm, that will also desync the other architectures though
[10:47] <mdz> cprov: how black is the magic?
[10:47] <cprov> mdz: not much, let me see
[10:58] <cprov> mdz: https://launchpad.net/+builds/+build/227962 fixed 
[10:59] <mdz> cprov: so it should be in this publisher run?
[10:59] <cprov> mdz: no, it would require re-publication 
[11:04] <mdz> cprov: do i need to do something, or just wait another hour?
[11:07] <cprov> mdz: It won't work without a surgery in publication system, give one sec to find the right records
[11:22] <cprov> mdz: you need to re-upload the package, there publishing records acuse they are removed, some mees with domination of empty publications
[11:23] <mdz> cprov: if some of the builds on non-powerpc fail, this will be a big pain for us
[11:23] <mdz> we're trying to get things installable for a milestone and this is the last remaining blocker for amd64/i386/powerpc
[11:24] <cprov> mdz: no, the bug I pointed you is fixed 
[11:24] <mdz> cprov: I'm not talking about the bug; edgy is churning a lot right now and we have spent several days unraveling these dependency problems
[11:26] <cprov> mdz: new source should work fine
[11:26] <mdz> I will upload a new source but will have to leave for my flight before it could be published
[11:37] <cprov> mdz: I can keep my eyes on it