[02:02] <lifeless> OOPS-1643B1230
[02:04] <poolie> what controls whether people are allowed to set the priority etc when filingL
[02:05] <lifeless> I'm not sure
[02:05] <lifeless> 'driver' perhaps
[02:05] <lifeless> it seems to be inconsistent with the set of people that can set it later
[02:08] <poolie> :/
[04:38] <rCX> I made a mistake...
[04:39] <rCX> Does anyone know how to remove the "acpi" project (the 1st one) from bug #552880
[05:13] <poolie> rcx just redirect it to project 'null'
[05:16] <rCX> poolie: thanks
[05:27] <maxb> losa ping: Hi, pear:~importd/.bazaar/subversion.conf has managed to corrupt itself again.
[05:27] <poolie> maxb, spm, it'd be useful to save that for vila
[05:27] <poolie> perhaps
[05:27] <poolie> there's an upstream bzr bug about locking on them
[05:27] <lifeless> theres a sample already
[05:28] <lifeless> by which I mean - good thought, but we've got plenty of data
[05:30] <spm> maxb: ta
[05:30] <maxb> line 600 ftr
[05:31] <spm> it'll be the last ones, ish. 20cent bet down. ;-)
[05:32] <spm> maxb: should be fine now. the [blah] bit was corrupted. missing the opening '[' and maybe half that field.
[05:32] <maxb> thanks
[06:51] <vila> maxb, spm: please attach the corrupted subversion.conf to bug #525571
[06:51] <vila> I'll check it when I'll come online (rsn)
[06:52] <spm> vila: sure, fiwiw, the corruption is pretty trivial: <Start-of-line>52-e9e23c5afa6a]<end of line>
[06:53] <spm> vila: and updated.
[07:00] <poolie> are ppa packages really waiting 18 hours to build? :-(
[07:00] <poolie> https://edge.launchpad.net/~bzr-beta-ppa/+archive/ppa/+build/1850070
[07:01] <wgrant> poolie: Yes. buildd-manager sucks.
[07:01] <wgrant> But it's being rewritten.
[07:01] <poolie> the estimate's accurate?
[07:01] <wgrant> (it's due to the rebuild archive -- even though it's scored below everything else)
[07:01] <wgrant> Yes. Possibly even slightly optimistic.
[07:02] <wgrant> Actually, yeah, probably quite optimistic indeed.
[07:15] <vila> spm: thanks ! trivial, yes, but this one makes sense, the one in the bug description wasn't. Can I ask for the *full* subversion.conf ? Just to check the offset where the error occurred ?
[07:15] <spm> vila: that's easy - it's always the same place - the very last entry.
[07:15] <vila> offset in bytes
[07:16] <lifeless> it may be a line buffered file
[07:16] <spm> Ahh. fair enough. sure.
[07:16] <lifeless> spm: does the corruption occur midline ?
[07:17] <spm> lifeless: good question. I don't recall having ever seen that. it's been per that example- just gets chopped somewhere.
[07:17] <vila> the code is a single write() if the offset is some power of 2 multiple I'll feel better
[07:17] <spm> heh
[07:18] <lifeless> vila: line buffered file - we can write() but it serialises; possibly.
[07:18] <vila> the proposed fix should protect against concurrent writers anyway, but since the theory implies that the bug should be very hard to reproduce I don't want to waste an occasion to investigate an occurrence
[07:18] <lifeless> vila: anyhow, its all academic, we know the issue :)
[07:18]  * vila nods
[07:19] <vila> lifeless: by the way, is it too late for you to review https://code.edge.launchpad.net/~vila/bzr/525571-lock-bazaar-conf-files/+merge/28898 ?
[07:19] <lifeless> I mean, we could just change it to use transport.put_bytes and the crashes in production would go away.
[07:20] <lifeless> vila: I don't see why you say its hard to know what happened
[07:20] <spm> vila: file attached to the bug report
[07:21] <lifeless> we know enough to be pretty sure its the write-in-place-with-no-lock breaking things
[07:21] <vila> lifeless: true, except for the one reported in the bug description :)
[07:22] <vila> lifeless: I don't have an explanation for a file ending with only a section header and no content
[07:22] <vila> lifeless: a second writer truncating the first writer output ?
[07:22] <lifeless> vila: didn't the content appear twice
[07:23] <vila> lifeless: no, only the header is duplicated but there is *no* content after that
[07:23] <lifeless> anyway
[07:23] <lifeless> review
[07:23] <lifeless> so - you really don
[07:23] <lifeless> 't need to guard against concurrent readers
[07:23] <lifeless> you *do* need to make the writer guard against FileInUse
[07:24] <lifeless> because thats what a reader will show up as, on Windows
[07:24] <lifeless> but that is a problem today
[07:24] <lifeless> so don't put it in this patch.
[07:24] <lifeless> keep it small and auditable for launchpad to cherrypick.
[07:24] <lifeless> -> #bzr
[07:52] <poolie> spm can you increase the priority of the builds in https://edge.launchpad.net/~bzr/+archive/2.1-proposed/+builds?build_state=pending
[07:52] <poolie> pretty please
[07:52] <spm> with sugar on top?
[07:53] <spm> poolie: all done
[07:55] <poolie> thanks
[08:01] <poolie> oh spm can you make them all succeed for me too? :)
[08:02]  * spm gets out the magic wand, aka small-lart, and waves in the direction of the buildds....
[09:55] <vila> spm: what bzr version version is in use for the code importer (and bzr-svn too, since the fix will need to be applied there too)
[09:55] <vila> ?
[09:55] <lifeless> vila: check sourcedeps.conf
[09:55] <lifeless> IIRC
[09:56] <vila> hmm, never saw that filename :) Where is this file ?
[09:57] <lifeless> launchpad code base
[09:58]  * vila updates its lp branch
[09:59] <lifeless> http://bazaar.launchpad.net/~launchpad-pqm/launchpad/db-devel/annotate/head:/versions.cfg
[09:59] <lifeless> but http://bazaar.launchpad.net/~launchpad-pqm/launchpad/devel/annotate/head:/versions.cfg is probably the deployed on on the machines in question
[09:59] <lifeless> oh, also, #launchpad-dev
[10:02] <vila> hmpf. 2.1.0 :(
[10:03] <lifeless> we should get lp running 2.2 releases
[10:59] <geser> is the cause of OOPS-1644EC2039 already filed as a bug? it OOPSes everytime for me when I try to access a +build page for the current test-rebuild
[11:03] <wgrant> geser: Bug #599824
[11:11] <lifeless> hm fun
[11:11] <lifeless> I wonder how the bug matching is done
[11:16] <wgrant> lifeless: Which?
[11:17] <lifeless> the oops knows the bug number
[11:18] <wgrant> lifeless: The bug references an OOPS number. oops-tools guesses at similarities between OOPSes.
[11:18]  * bigjools is going to start fixing that right now
[11:19] <deryck> lifeless, hi.  I want to respond to your "trunk can be broken" email.  But I'm not sure how just yet.  What do you mean by "broken?"
[11:19] <lifeless> a few things
[11:20] <lifeless> most of them summarise as 'not fit for purpose', I think
[11:20] <lifeless> (should we -> launchpad-dev?)
[11:21] <deryck> lifeless, yeah, probably so.  I'll ask there and we can continue.
[13:04] <gnomefreak> any chance of getting "Also Notified" to be collapsed to speed up Launchpad bugs. Right now it is really slow with any of my browsers
[13:08] <deryck> gnomefreak, we could possibly take that on as part of our better subscriptions/notifications work in progress now.
[13:09] <deryck> gnomefreak, can you make sure there's a bug for that request and ping me with the bug #?
[13:09] <gnomefreak> deryck: ok that sounds good to me
[13:09] <gnomefreak> deryck: yes
[13:15] <gnomefreak> deryck: under launchpad bug or under launchpad itself
[13:15] <deryck> gnomefreak, under malone.  That's the launchpad bugs app name.
[13:15] <gnomefreak> deryck: ok thanks i will look in a few minutes
[13:16] <deryck> gnomefreak, thank you.
[13:16] <gnomefreak> deryck: np
[13:26] <gnomefreak> deryck: ill be back but here is the bug 601007
[13:27] <deryck> gnomefreak, got it, thanks!
[13:32] <gnomefreak> deryck: would condensing the "apport-collect" attachments into one comment be related to that bug?
[13:33] <deryck> gnomefreak, that work has already been.  Should be released in the coming rollout.
[13:33] <deryck> s/been/been done/
[13:33] <gnomefreak> deryck: ok thanks
[15:11] <Kangarooo> hello if bug is reported to ubuntu (package) then how to make that also project <packagename> is also beeing affected? i tryd also affects project and distribution and cant make to projectname be also affected
[15:25] <Jonathan_R> my launchpad account is disabled or something
[15:50] <maxb> Jonathan_R: or something?
[15:50] <Jonathan_R> yeah
[15:50] <Jonathan_R> i dont know exactly what happened
[15:51] <Jonathan_R> i just cant log in anymore
[15:52] <Ursinha> Kangarooo, If the project is in Launchpad, "also affects project" should work
[16:05] <jcastro> ok so I am testing the daily builds and my recipe worked and all that good stuff, does anyone have power to cancel lp builds? I iinadvertantly sent them to the wrong ppa.
[16:06] <bigjools> jcastro: it's not something we can do via the UI, it needs SQL hackery.  Is it bad if the build ends up in the wrong PPA?
[16:06] <jcastro> no it's not bad, just didn't want to waste resources.
[16:06] <jcastro> I'll file a bug for a confirmation screen or something for the UI
[16:06] <bigjools> what package is it?
[16:06] <jelmer_> actually, that happened to me too
[16:06] <jcastro> shotwell
[16:06] <jcastro> https://code.edge.launchpad.net/~jorge/+recipe/shotwell-daily/+build/163
[16:06] <bigjools> ok
[16:06] <jcastro> and https://code.edge.launchpad.net/~jorge/+recipe/shotwell-daily/+build/162
[16:07] <bigjools> confirmations would be good
[16:07] <jcastro> other than me overclicking, everything else was pretty awesome!
[16:07] <bigjools> file it on codehosting - chees
[16:07] <steffan>  /1
[16:07] <bigjools> cheers, even
[16:07] <bigjools> great!  we're looking forward to a bit more use of it to get those bumps smoothed
[16:08] <jcastro> bigjools: dholbach and I will be testing today, monday, and tuesday for you
[16:08] <bigjools> rawk
[16:10] <jcastro> jelmer_: lp:601095
[16:11] <jcastro> oops, lp# 601095
[16:11] <jcastro> man, what a day I am having
[16:11]  * jelmer_ hits "Affects me too"
[16:11] <jelmer_> jcastro, thanks :-)
[16:23] <jcastro> bigjools: do you have any insight on the hardware behind daily builds? At UDS someone mentioned that there would be seperate machines
[16:23] <bigjools> jcastro: not separate, but more builders were on order for the general pool
[16:24] <jcastro> ok
[16:31] <fta> https://edge.launchpad.net/~chromium-daily/+archive/ppa/+build/1849914 "created 13 hours ago" "Start in 18 hours (2505)"  :(
[16:34] <bigjools> fta: I've scored it up
[16:34] <bigjools> the rebuild is hogging too many builders :/
[16:49] <Kangarooo> how to move from sourceforge to launchpad?
[18:01] <Kangarooo> hello i have some questions i hope to get statistical info on. how often LP has problems? loading freezes, ooops,  maintaince ... And overall LP zealots ?
[18:06] <Kangarooo> back again.. got pidgin crash.. any answer? :)
[19:45] <Kangarooo> in https://launchpad.net/bugs/bugtrackers theres 62.166.198.202/                                         http://62.166.198.202/                                                                             My Project,                                                      xAccount                                                                                          Mantis             1 ant my project links to Lost Something page https://launchpad.net/eagle
[20:41] <Kangarooo> sinzui: hello if u read that bug till end ull see that bug is all about LP and in it im not talking about ubuntu.. one of LP non-users quote has mentioned LP and ubuntu somehow
[20:44] <sinzui> What is the bug in the code?
[20:44] <sinzui> I think you described a behavioural issue
[20:48] <Kangarooo> sinzui: yes on that i can agree.. so whats there about ubuntu? nothing. about LP? a lot.. and this is big bug
[20:48] <Kangarooo> so why then its incomplete?
[20:50] <Kangarooo> behavior that ppl managing projects described there dont use LP becouse of problems described there.. so thats LP problem making less projects to be on LP so thats a LP bug
[20:53] <Kangarooo> ah ok i need to assign it to myself and then it wont be incomplete? i just need answers to Q posted there. sinzui
[21:02] <tedg> So I'm trying to use the API.  How do I get the list of series off of the distribution object?
[21:06] <Kangarooo> sinzui: Problem 1 in that bug can be solved if problem 2 and/or 3 is solved. so for problem 3 to know is it problem i need info where else i could ask for LP related info then in LP bugs?
[21:13] <sinzui> Kangarooo, there are to many problems, that is not a bug, it may be several bugs, but I think the issues described are social. I do not see an error in the code that an engineer can fix. I think talking on launchpad-users will help clarify issues. If there are bugs that engineers can fix, then we can report them. The ones about performance are already reported and have a team of engineers working on them
[21:15] <Muscovy> Can I give a team's PPA to a project?
[21:15] <sinzui> Muscovy, no :(
[21:16] <sinzui> Muscovy, many of us add a line at the end of the project description pointing to official or test PPAs.
[21:16] <Muscovy> Ah. Thanks.
[21:50] <Kangarooo> can somebody tell me why ubuntu bug links not clickable in one comment ? https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/587528/comments/6
[21:54] <micahg> Kangarooo: what are you referring to?
[21:55] <Kangarooo> micahg: in that commend LP Janitor coment bug numbers- some are clickable most not
[21:55] <micahg> Kangarooo: a bug :)
[21:56] <Kangarooo> micahg: is it report? im writing now so.. is it?
[21:56] <micahg> Kangarooo: it's fine here: https://edge.launchpad.net/ubuntu/+source/vlc/1.1.0-1ubuntu1, so file a bug against malone if one doesn't exist
[22:59] <Kangarooo> after update to latest kernel last numbers 32-23 got xorg crash and it asked about getting gdb and i said yes and then it gave The problem cannot be reported: This is not a genuine Ubuntu package