[12:08] <dilys> Merge to devel/launchpad/: [r=jamesh]  better branch listings (r3305: David Allouche)
[12:35] <dilys> Merge to devel/launchpad/: Fix https://launchpad.net/products/malone/+bug/34046 (Default search shouldn't include Fix Released bugs r=bjorn r=kiko (r3306: Diogo Matsubara)
[01:51] <mpt> hooray
[04:05] <SoLAcE1369> hello all
[05:55] <andrewski> is there an autosubscriber option for bug reports that you comment on?
[06:20] <stub> Nope
[06:21] <stub> andrewski: Feel free to put in a feature request if you would find it useful though
[06:24] <andrewski> stub: ok, will do.  thanks.
[06:25] <andrewski> stub: would that be filed on launchpad or malone?
[06:26] <stub> andrewski: In this case, the Malone product
[06:26] <andrewski> excellent.  cheers, mate.
[06:31] <andrewski> stub: looks like bug 516 already covers it, would you agree?
[06:32] <Ubugtu> Malone bug 516 in malone "Should be possible to edit a bug and subscribe to it in one step" [Normal,Confirmed]  http://launchpad.net/bugs/516
[06:32] <andrewski> wow.  that is a nice bot.
[06:35] <stub> andrewski: It is similar, but not covered by that bug. You are after a setting saying 'subscribe me to all bugs I comment on' or a checkbox you can tick when adding a comment. That bug is specific to people doing bug triage, who are editing the bug details rather than adding comments (so adding checkboxes to the bug edit screens saying 'subscribe me' won't help you).
[06:36] <andrewski> hmm, yes, i suppose those are a bit different.  thanks, i'll file a new bug.
[07:39] <dilys> Merge to devel/launchpad/: [trivial]  Don't assign Karma to teams or invalids (Bug 30206) (r3307: Stuart Bishop)
[08:08] <dilys> Merge to devel/launchpad/: [trivial]  Reenable search result ranking tests (r3308: Stuart Bishop)
[08:22] <G0SUB> in Launchpad, what is ``Specification Tracking'' ?
[08:41] <fabbione> stub: ping?
[08:43] <fabbione> anybody that can do some SQL magic for me please?
[08:52] <lifeless> what do you need done ?
[08:54] <fabbione> i need ubuntu-x-swat team subscribed too all xorg bugs
[08:54] <fabbione> xorg as in source package
[08:55] <fabbione> i think...
[08:55] <fabbione> or the same settings as xorg-server pkg
[08:55] <fabbione> the team needs to be autosubbed etc.etc.etc
[09:03] <lifeless> I'll chat with bradb when hes around about this
[09:03] <lifeless> it doesn't sunds like a sql problem o me
[09:07] <fabbione> lifeless: it's not a problem. when we did a batch sql work for the xorg packages, it seems that xorg source has been left out
[09:07] <fabbione> lifeless: it's not a bug, but i need it don
[09:07] <fabbione> done
[09:07] <stub> fabbione: pong
[09:07] <fabbione> i am not going to manually subscribe a team to 232 bugs
[09:07] <fabbione> stub: ^^
[09:08] <fabbione> stub: remember when you did that batch work for me for the xorg packages?
[09:08] <stub> yup
[09:08] <fabbione> stub: we left out somehow source: xorg
[09:08] <stub> I've got the scripts
[09:08] <fabbione> can you please process it for me?
[09:08] <stub> Yup
[09:08] <fabbione> thanks
[09:11] <stub> fabbione: Do you want all open bugs on the xorg package assigned  to ubuntu-x-swat, or just the ones already assigned to some particular user or team?
[09:11] <fabbione> stub: all of them
[09:13] <stub> fabbione: oh... just subscribe. Not assign. Got it.
[09:13] <stub> exactly like last time
[09:13] <fabbione> stub: yes.. exactly
[09:13] <fabbione> i am sorry if i do not remember the exact malone terminology
[09:13] <fabbione> but i am still getting used to it
[09:22] <stub> fabbione: Done
[09:23] <stub> fabbione: You used the correct terminology. I just misinterpreted you to start with ;)
[09:23] <fabbione> stub: thanks a lot
[09:35] <jordi> fuck
[09:35] <jordi> some canonical email is just vanishing somewhere
[09:55] <fabbione> is there any reason why LP is so slow today?
[10:00] <jordi> wow
[10:00] <jordi> I found 3000 mails for me in a frozen postfix queue somewhere
[10:00] <jordi> gotta love spamassassin
[10:02] <carlos> morning
[10:03] <jordi> carlos: I suddenly found all my lost mail, after confirming sindominio was getting all of if from .canonical.com, and it was then sent to me
[10:04] <stub> fabbione: No reason. Any bits in particular? I did have the bug batch size set to 200, but there were still performance issues so I reduced it down to 75. That might still be too high if it is the bug pages you are finding not snappy.
[10:04] <carlos> jordi: cool
[10:04] <stub> Seems pretty fast here anyway
[10:07] <kiko> good morning
[10:07] <bradb> stub: Hi. I'll add some comments to my patch now. What patch number should I use?
[10:08] <stub> bradb: So why fixed_in_revision_id ?
[10:09] <cprov> sladen: ping 
[10:09] <fabbione> guys.. what's wrong with malone or LP?
[10:10] <fabbione> it's taking forever to add a comment/change status of a bug.. and 2 out of 3 times it's timing out
[10:10] <kiko> fabbione, can you give me an oops id?
[10:10] <bradb> stub: Oh, I was going to change that too. fixed_in_revision seems ok.
[10:10] <fabbione> kiko: i don't even get one. it's just stalling on Waiting for launchpad
[10:11] <fabbione> and i know my connection to the DC is ok
[10:11] <stub> bradb: ok. patch-40-38-0.sql
[10:11] <bradb> stub: thanks
[10:11] <kiko> fabbione, so, you're not getting a launchpad timeout page, but an http timeout?
[10:12] <fabbione> kiko: so it seems...
[10:12] <lifeless> we had an apps server go away into cloud land last night
[10:12] <fabbione> kiko: in any case the problem is at the DC.. i have no problems anywhere else
[10:13] <stub> One of the appservers has hung again
[10:13] <lifeless> ahha!
[10:13] <lifeless> stub - I'm thinking we want python2.4-dbg & gdb installed on the appserveres to get a backtrace when this happens
[10:13] <lifeless> stub - agreed ?
[10:13] <stub> lifeless: Sure. I'm not sure how to drive it all though.
[10:14] <lifeless> stub np, I'll write a mail to launchpad@ about how to get a backtrace.
[10:14] <lifeless> or would you rather a wiki page ?
[10:14] <stub> fabbione: better now?
[10:14] <stub> lifeless: whatever ;)
[10:14] <lifeless> lets start with an email
[10:15] <carlos> stub: at what time are you updating staging ? and about what time is safe to use it from a cronscript?
[10:15] <lifeless> ONCE WE AGREE ON THE WAY, A WIKI PAGE IS GOOD
[10:15] <jordi> carlos: so
[10:15] <lifeless> Bah. caps lock is not my friend
[10:15] <jordi> carlos: -- 12694 Kbytes in 3066 Requests.
[10:15] <jordi> carlos: I found my emails.
[10:15] <carlos> *only* 12MB? ;-)
[10:16] <stub> carlos: Last nights update finished at 06:15 UTC. I'd suggest around 08:00 UTC to be sure.
[10:17] <stub> erm.... London time - not UTC
[10:17] <fabbione> how do i retitle a bug?
[10:17] <fabbione> never mind
[10:18] <carlos> stub: ok, I was executing it at 4:30 ...
[10:18] <fabbione> it would be more useful to have the retitle option together with all the fields you can change in a bug instead of a separate link
[10:20] <bradb> fabbione: agreed
[10:21] <jordi> carlos: ok. All my mail should be back now.
[10:21] <jordi> omg, and all my spam too
[10:22] <daf> how many thousands of emails in your inbox these days?
[10:22] <jordi> 4500
[10:22] <jordi> 4554
[10:22] <daf> unread?
[10:22] <BjornT> stub: do you have time to write some sql queries for me? the person merge code needs to update SupportContact when merging accounts, and i'm not quite sure how to do it properly.
[10:22] <carlos> jordi: how are you able to don't detect that you are not being spamming anymore?? ;-)
[10:22] <jordi> unread, only 1240
[10:22] <daf> *cough* "only"
[10:23] <jordi> 67 flagged. Possibly quite important if they are flagged.
[10:23] <jordi> this is a mess.
[10:23] <stub> BjornT: sure
[10:23] <daf> yes
[10:23] <daf> jordi: I have 67 emails in my inbox total
[10:23] <jordi> daf: can we swap inboxes?
[10:24] <BjornT> thanks stub 
[10:24] <daf> jordi: sure; maybe we should switch countries too
[10:25] <daf> I'll sort those valencians for you
[10:25] <lifeless> stub - I have mailed a how to to launchpad
[10:25] <jordi> daf: only when you get a decent temperature
[10:25] <jordi> daf: dude, it's so sunny here.
[10:25] <jordi> SO SUNNY
[10:26] <dilys> Merge to devel/launchpad/: [r=kiko]  tweak 2col layouts of spec tracker (r3309: Mark Shuttleworth)
[10:26] <daf> what's wrong with 7C?
[10:26] <jordi> too cold, obviously.
[10:27] <jordi> so, it seems a lot of poepe are interested in my sex life health.
[10:27] <daf> er
[10:30] <jordi> carlos: wow, carlos
[10:30] <jordi> I see a lot of mail I had been missing
[10:30] <jordi> I'll add all of these faq entries
[10:31] <jordi> On 2005-03-30 10:21+0000 (356 days 2 hours 14 minutes ago), you uploaded 188
[10:31] <jordi> heh, this is funny
[10:31] <daf> !
[10:31] <carlos> jordi: jamesh fixed the poparser
[10:31] <carlos> ;-)
[10:31] <carlos> daf: the chinese .po files
[10:31] <daf> yeah
[10:31] <daf> crazy
[10:34] <doko> carlos: are the OOo language files already imported?
[10:34] <carlos> doko: well, the .pot files are, the .po files are not
[10:34] <stub> BjornT: You need to duplicate the code in merge that deals with BountySubscription (both the UPDATE and the DELETE).
[10:35] <carlos> doko: because they are using special filenames...
[10:35] <carlos> doko: what reminds me...
[10:35] <stub> BjornT: person.py line 1292
[10:35] <carlos> I need to talk with pitti
[10:36] <doko> carlos: please only import the data from today's upload, not anything before
[10:37] <carlos> doko: hmm, I thought the .pot files were already imported... but I don't see anything there so... I will do it that way. is that because the previous one were broken?
[10:39] <carlos> jordi: btw, the import queue edit form on production is autofilled now
[10:39] <BjornT> stub: i'm not sure what the sub-select would look like, so that if Foo is support for Firefox in Ubuntu, and Bar is support contact for Evolution in Ubuntu, the merged account will be support contact for both packages.
[10:40] <jordi> carlos: excellent!
[10:42] <doko> carlos: no, I don't think so, but some .po files didn't contain any translations
[10:42] <fabbione> stub: yes, it's definetely better...
[10:43] <carlos> doko: ok
[10:47] <kiko> stub, can you ping me when you have a moment?
[10:48] <jamesh> lifeless: that info about using gdb with Python processes is also here: https://wiki.launchpad.canonical.com/DebuggingWithGdb
[10:50] <daf> having a python2.4-dbg package that worked with existing extensions would be nice
[10:51] <jamesh> daf: the python2.4-dbg package includes symbols for the standard interpreter and standard extensions
[10:52] <jamesh> as well as a debug interpreter
[10:52] <jamesh> the info on the wiki is a little out of date
[10:52] <daf> having a wiki page that reflects reality would be nice ;)
[10:53] <kiko> stub, did you bounce back the malone batch count to 75?
[10:53] <daf> is rf-built on chinstap up to date?
[10:53] <jamesh> daf: it is a good thing that anyone can update it then :)
[10:53] <daf> it seems to be missing some changes that are in production
[10:54] <daf> jamesh: indeed -- I hope somebody who knows how to correct it does so
[10:55] <daf> oh, no, I'm mistaken
[11:00] <stub> BjornT: https://chinstrap.ubuntu.com/~dsilvers/paste/fileLhnJAC.html
[11:00] <stub> kiko: Yes
[11:00] <stub> kiko: ping
[11:01] <kiko> stub, hello there.
[11:01] <kiko> privmsg?
[11:02] <jamesh> stub: I noticed that we haven't been getting any RequestStatementTimedOut oops's since the PG8.1 upgrade, due to a change in the returned error message
[11:03] <jamesh> stub: I've got the fix queued in PQM now though
[11:03] <BjornT> stub: thanks
[11:03] <stub> jamesh: oops
[11:03] <stub> jamesh: The test suite didn't notice ;)
[11:03] <jamesh> stub: there were tests for this, but it seems they are disabled
[11:04] <jamesh> https://launchpad.net/products/launchpad/+bug/32231
[11:04] <Ubugtu> Malone bug 32231 in launchpad "test_adapter occasionally failing" [Normal,Unconfirmed]  
[11:04] <lifeless> jamesh: heh. Blame stub, he claimed ignorance
[11:05] <stub> oops
[11:17] <dilys> Merge to devel/launchpad/: [trivial]  correctly raise RequestStatementTimedOut exceptions with PG8.1 (r3310: James Henstridge)
[11:32] <SteveA> stub: hello] 
[11:42] <sladen> cprov: pong
[11:42] <SteveA> stub: ping
[11:43] <stub> SteveA: pong
[11:43] <SteveA> stub: who can update the code on staging?
[11:43] <dilys> Merge to devel/launchpad/: [r=lifeless]  first part of Bug/Branch integration. refactor bug-related security to use an IHasBug interface, making it easy for objects linked to bugs to share security characteristics. (r3311: Brad Bollenbach)
[11:43] <stub> SteveA: Me, and currently carlos still has access
[11:44] <SteveA> mark was asking for, during sprints, to have staging update (maybe just code) at lunchtime locally to the sprint
[11:44] <SteveA> i figured a manual method would be more straightforward
[11:44] <SteveA> what do you think?
[11:47] <stub> A staging update with database sync takes about 5 hours. A code drop can be done in a minute or two.
[11:47] <stub> I can schedule code updates as often as you like.
[11:47] <stub> Although any more than once every 30 mins will be pointless, as it uses rocketfuel-built for the source.
[11:48] <SteveA> then can we have a code update at 1.30 UTC each day
[11:48] <SteveA> for the rest of this week
[11:48] <stub> Sure.
[11:48] <SteveA> does the code update run pending database patches?
[11:48] <stub> Yes
[11:48] <SteveA> cool
[11:48] <SteveA> thanks
[11:48] <kiko> I'd do it indefinitely, ftr.
[11:48] <kiko> less work for stub
[11:48] <stub> erm... you mean 13:30 ?
[11:48] <SteveA> yeah
[11:49] <SteveA> we can do it into the future, and see if it helps or hinders our work
[11:49] <SteveA> and yes, i mean 13:30 UTC
[11:56] <bradb> kiko: Search by component patch => https://chinstrap.ubuntu.com/~dsilvers/paste/fileGu9veV.html
[11:57] <kiko> thank you bradb 
[11:57] <bradb> kiko: np. to relay what i wrote in the email then: 1. there's a known issue with a hack I did to workaround a Z3 bug with MultiCheckBoxWidget. BjornT has a patch on the way to rf now that will allow me to fix this.
[11:58] <bradb> and 2. i'm not 100% sure on the query, but the tests i added pass, and it otherwise seems to work
[11:59] <carlos> kiko: nothing weird happen with my local upload...
[12:05] <mpt> stub, ping
[12:05] <stub> mpt: pong
[12:06] <bradb> stub: we just hit an issue with karma and deleting things
[12:06] <bradb> stub: mpt removed shortdesc ("summary" in the API) from bugs
[12:07] <bradb> there's a karma action specific to changing the summary
[12:07] <bradb> each karma action has a row in the KarmaAction table
[12:07] <bradb> each Karma entry points at the action that caused it
[12:07] <bradb> so, do we now blow away all these karma entries and the karmaaction row for editing bug summary?
[12:08] <bradb> (mpt said the loss in karma this will cause is probably ok)
[12:08] <stub> I'd leave both. Otherwise we are rewriting history
[12:08] <bradb> i kind of agree
[12:08] <mpt> so we can remove it in six months once all the karma for that action has expired
[12:09] <stub> I don't have a problem with having KarmaActions that are no longer used, or have yet to be used.
[12:09] <bradb> hm, that's an interesting point, yeah
[12:09] <stub> mpt: 1 year. sure.
[12:09] <mpt> ok
[12:09] <bradb> stub: thanks, we're going to finish updating the test suite accordingly.
[12:57] <dilys> Merge to devel/launchpad/: Fix advanced search in people bug listings returning only UNRESOLVED_BUGTASK_STATUSES even when you select RESOLVED_BUGTASK_STATUSES. r=kiko (r3312: Diogo Matsubara)
[01:03] <jblack> Yesterday somebody mentioned that one of the things we're lacking that sourceforge has is webpage hosting.
[01:04] <jblack> As I work on thse bzr-launchpad userstories, its looking like a retty big hole
[01:06] <jblack> There's a way to track bugs, a way to do translations, a way to upload branches....
[01:06] <jblack> the product page gives a good place to give a general description, which is nice.
[01:07] <jblack> But without a place to publically display documents or perform downloads, one still needs external services
[01:07] <jblack> And if you need that, then you may as well upload your branches there as well
[01:10] <_Dan_> Hi. What happens if I translate messages that refer to FAQ pages and the translated page does either not exist or cannot be found using the translated string ? Will it fall back to the reference in the code ?
[01:12] <carlos> kiko: dude, I'm blocked with the Debian installer thing. All things I have found say that it's not a bug in our side, but I don't have a backup of the initial files uploaded to the system so I cannot confirm that...
[01:13] <kiko> _Dan_, it will not fall back, no.
[01:16] <_Dan_> kiko: So I either have to make sure the page exists and can be found using the translated string or just leave them as they are ?
[01:17] <kiko> correct.
[01:41] <dilys> Merge to devel/launchpad/: [r=jamesh, r=stub for schema change, r=bradb for trivial-ish karma test fix]  Retires bug 'short descriptions', merging existing short descriptions into the beginning of the main description. (r3313: Matthew Paul Thomas)
[01:51] <mpt> woohoo
[03:07] <kiko> he ll o
[03:08] <andrewski> i read that "You can register additional bug trackers from the Malone home page."  however, i can't see how to do that.  do i need to file a bug on malone to do so?
[03:13] <andrewski> is there another channel where malone discussion is more appropriate?
[03:13] <jamesh> andrewski: https://launchpad.net/maloen/bugtrackers
[03:13] <jamesh> s/maloen/malone/
[03:14] <jamesh> andrewski: you're in the right channel, but we've just got back from lunch
[03:14] <andrewski> oh, my apologies. :)
[03:14] <andrewski> did i miss a link somewhere on the malone homepage?
[03:19] <andrewski> alright, well it worked and i must be going.  thanks for the info and for malone; it's a really nice bugtracker!
[03:20] <jjesse> can i ask how "karma" on launchpad is determined?
[03:21] <jjesse> are some things worth more karma? just curious as yesterday my karma was 36 and today its like 1297 or something like
[03:22] <jjesse> also does more karma mean something?
[03:25] <jamesh> andrewski: go to https://launchpad.net/, click bugs on the right hand menu; on that page, click the "see all nnn..." link in the "Top bug trackers"  box on the right
[03:25] <jamesh> andrewski: it should be more obvious.
[03:25] <andrewski> jamesh: should i file a wishlist bug on launchpad and/or malone?
[03:26] <jamesh> andrewski: nah.  I think https://launchpad.net/products/malone/+bug/35728 covers the problem.
[03:26] <Ubugtu> Malone bug 35728 in malone "Registering a bug tracker is prohibitively difficult" [Normal,Unconfirmed]  
[03:27] <andrewski> heh, that's a good title; i'd say so.  i'll subscribe to that one; thanks.
[03:27] <andrewski> jjesse: heh, yeah, my karma just jumped up a lot too.  high-five!
[03:29] <jjesse> andrewski: sweet
[03:29] <jjesse> can i turn in my karma for cool prizes :)
[03:56] <stub> jjesse: We updated the calculations so that the different categories are normalized. It was too easy to score translation karma vs. triaging bugs or answering support requests.
[03:57] <stub> Heh... I should reduce Karma of Canonical employees to give the people who aren't paid for this a chance ;)
[04:13] <jjesse> stub: so answering support requests are now added in?  is that only if the support request is marked as closed?
[04:14] <stub> jjesse: I'm not sure. If you can get support Karma, it will be normalized though ;)
[04:14] <jjesse> stub: thanks for answering my questions 
[04:14] <stub> I remember there was a bug open on support karma but I'm not sure of the number or status
[04:19] <sebest> hello, i guess that question is frequently asked, but how can we know if the bug is specific to one ubuntu release or the other (breezy, dapper, etc...) ?
[04:21] <sebest> for example a bug like #4643 should be marked fixed on dapper, and confirmed in breezy, but right now we have to deduce this from the commentaries
[04:43] <bradb> sebest: You can't, in any way supported by the system, in any case.
[04:43] <bradb> sebest: There's a bug open on this.
[04:45] <bradb> bug 424
[04:45] <Ubugtu> Malone bug 424 in malone "No distribution or version field" [Normal,Confirmed]  http://launchpad.net/bugs/424
[04:47] <bradb> kiko: BTW, I'm also looking for another priority task to be assigned, when you have a minute.
[04:53] <sebest> bradb, thanx for the info
[04:53] <sebest> and what do you think about bug 36025
[04:53] <Ubugtu> Malone bug 36025 in malone "Malone should send a reminder by mail to check validy of bugs" [Wishlist,Unconfirmed]  http://launchpad.net/bugs/36025
[05:00] <kiko> tambaqui!
[05:21] <bradb> jamesh: Search by component => https://chinstrap.ubuntu.com/~dsilvers/paste/fileGu9veV.html
[05:21] <bradb> There's a hack done with MultiCheckBoxWidget, but BjornT has a landing which'll allow me to address it.
[05:27] <jamesh> >>> os.path.commonprefix([(1,2,3,4,5), (1,2,3,5,4)] )
[05:27] <jamesh> (1, 2, 3)
[05:27] <jamesh> this function can do anything
[05:59] <lakin> Holy jumping frogs my karma jumped up high on malone ... /me wonders what happened?
[06:00] <jamesh> lakin: scaling
[06:01] <lakin> scaling?  is there some release notes I can read to figure it out?
[06:02] <jamesh> I don't think kiko has done any for the latest rollout yet
[06:02] <lakin> aaah ok.
[06:02] <lakin> no big deal, was just curious.
[06:02] <jamesh> lakin: essentially it is scaling up the karma for bugs, etc so they are comparable to the amount of karma dished out for translations
[06:02] <jamesh> it may get tweaked a bit
[06:02] <lakin> cool.
[06:09] <SteveA> stub: ...
[06:09] <SteveA> stub: here at the launchpad london sprint, we've been looking at the consequences of the recent change in karma calculation
[06:09] <SteveA> there are some issues in the new world order of karma distribution
[06:11] <lifeless> stub https://launchpad.net/people/rosetta-admins/+karma
[06:11] <lifeless> see the obvious problem ?
 gangotri app server 1/2 is dead again
[06:21] <lifeless> meh
[06:21] <lifeless> nzarcan you please install gdb and python24-dbg
[06:21] <lifeless> erm
[06:21] <lifeless> znarl
[06:22] <lifeless> I'll get a backtrace out of the f*****er
[06:23] <Znarl> lifeless : I already have.
[06:23] <lifeless> Znarl: thanks
[06:25] <lifeless> Znarl: are both dead ?
[06:25] <lifeless> Znarl: or do you not kno wwhich 
[06:29] <Znarl> lifeless : Both are dead.
[06:33] <seb128> hi
[06:33] <seb128> launchpad gives some "Proxy Error"
[06:33] <erdalronahi> yes, here too
[06:34] <lifeless> Znarl: how about the other appserver ?
[06:35] <Znarl> lifeless : Only 1 and 2 on gangotri are down.
[06:35] <lifeless> ok, bouncified
[06:35] <lifeless> Znarl: thanks, we have the backtraces
[06:40] <lifeless> stub:  I think your pmerge has hung :)
[06:47] <jamesh> lifeless: if it helps, the "pystackv" gdb macro will print the stack + locals for each frame
[06:51] <bradb> Kinnison: ping
[06:51] <Kinnison> bradb: yo?
[06:52] <bradb> Kinnison: I'm writing a query that will filter bugtask searches on component. I'm joining through SourcePackagePublishing, and maybe other tables, to do this.
[06:53] <Kinnison> bradb: I see
[06:53] <kiko> lifeless, ping?
[06:53] <bradb> Kinnison: Will a SPP record point to an SPR record, even if this package was never uploaded in that new release?
[06:53] <Kinnison> Whatnow?
[06:54] <kiko> Kinnison, I'll answer that, worry not
[06:56] <lifeless> jamesh: when it doesn't crash the process
[06:56] <lifeless> kiko: pong
[06:57] <kiko> lifeless, can you review a patch with me?
[06:57] <kiko> https://chinstrap.ubuntu.com/~dsilvers/paste/file3jYLUY.html
[06:58] <lifeless> kiko: ok
[07:06] <jamesh> lifeless: http://pqm.launchpad.net/ is showing exceptions
[07:13] <SteveA> stub: i'm ripping the zodb out entirely
[07:14] <SteveA> this should stop these immediate hang problems, seeing as the hang is related to a lock acquired during opening the zodb
[07:14] <SteveA> lifeless will sort out patching production, until the proper rollout friday
[07:15] <kiko> don't we all love the zodb
[07:25] <carlos> kiko: btw, the debian installer bug is found and I'm going to fix it now (under some circumstances, we remove the fuzzy flag)
[07:35] <kiko> carlos, argh
[07:36] <kiko> okay, nice that you found it at least
[07:36] <kiko> and test it!
[07:36] <carlos> kiko: anyway it's a corner case
[07:36] <kiko> yeah, but it had a very non-corner consequence :)
[07:36] <carlos> that's why no one noticied it yet
[07:36] <carlos> kiko: right, but it's not common, that's what I mean ;-)
[07:37] <kiko> it is pretty disastrous when it happens though
[07:37] <kiko> good work
[07:37] <carlos> kiko: right
[07:37] <carlos> thanks
[07:38] <lifeless> stub: ping
[07:39] <bradb> stub: Anything we can do to make "make schema" fail less, with errors like:
[07:39] <bradb> createdb: database creation failed: ERROR:  source database "launchpad_ftest_template" is being accessed by other users
[07:40] <carlos> bradb: closing any db connection first?
[07:45] <spiv> bradb: I suppose we could make it try to print out some diagnostics about the other processes accessing it (select * from pg_stat_activity), but I don't think we can or should automatically kill those connections.
[07:47] <bradb> It seems to be something like overperformance since upgrading to 8.1
[07:47] <bradb> kiko says he's seen the same problem
[07:48] <spiv> Interesting, I haven't heard anything about that.  Just from running make schema?
[07:48] <bradb> Yeah
[07:48] <bradb> I just ran it five times before it finally completed successfully.
[07:48] <spiv> Very weird.
[07:49] <bradb> I've been seeing this behaviour only since upgrading to 8.1.
[07:49] <kiko> I've seen it this week as well
[07:49] <kiko> it's annoying, not terrible
[07:49] <spiv> It's still working perfectly for me, and I have fsync off, 8.1, and a fairly fast laptop.
[07:49] <spiv> 4 failures in a row is verging on terrible.
[07:50] <kiko> I have fsync off as well
[07:58] <stub> lifeless: I committed a patch today to stop teams and invalid people getting karma.
[07:58] <kiko> cool
[07:59] <stub> bradb: There is a script 'pgmassacre.py' in the utilities directory I think - it will terminate a database with extreme predudice. If you are having trouble with 'database still in use' errors, you might want to add this to the database Makefile.
[08:01] <stub> Jesus.... staging update is still going on. I guess needing to delete a few million karma tuples does that :-(
[08:01] <dilys> Merge to devel/launchpad/: [r=jamesh]  change-override tool fixes and publishing interfaces cleanup (r3314: Celso Providelo)
[08:24] <SteveA> sabdfl, kiko: https://wiki.launchpad.canonical.com/PageTemplateHacking
[08:24] <SteveA> i added the precedence rules there
[08:24] <SteveA> i was reading an incorrect list earlier
[08:25] <SteveA> for the record:
[08:25] <SteveA> When an element has multiple statements, they are executed in this order:
[08:25] <SteveA>    1.
[08:25] <SteveA>       define
[08:25] <SteveA>    2.
[08:25] <SteveA>       condition
[08:25] <SteveA>    3.
[08:25] <SteveA>       repeat
[08:25] <SteveA>    4.
[08:25] <SteveA>       content or replace
[08:25] <SteveA>    5.
[08:25] <SteveA>       attributes
[08:25] <SteveA>    6.
[08:25] <SteveA>       omit-tag
[08:25] <SteveA> 
[08:45] <lifeless> stub: bug 36054
[08:45] <lifeless> s/stub/stevea:
[08:49] <bradb> stub: Can you give me a patch number for ==> "ALTER TABLE BugBranch RENAME COLUMN fixed_in_revision TO revision_hint"?
[09:12] <dilys> Merge to devel/launchpad/: r=lifeless Assorted polish, performance fixes and cleanups: stop wrapping translation barcharts, reduce startup cost of various views, split POFileView into basic, upload and translation variants (reducing startup cost and simplifying code), changing translation tables to be rendered in 2 column views, lazify request_languages in places where it matters, add prejoins, refactor and test a couple of database class queries. (r3315: Ch
[09:36] <oohlaf> Hi, In launchpad, what would fix committed as status be? A patch created, committed to a local branch? Or committed upstream?
[09:36] <oohlaf> When editing a bug report
[09:37] <oohlaf> Or would that be fix released
[09:37] <oohlaf> Or is released meant for when a new version of the package is created
[09:39] <daf> it generally means that a patch has been committed upstream
[09:39] <daf> i.e. a patch that will at some point be released in a new version
[09:40] <oohlaf> ok
[10:46] <elmo> [[10:46] <elmo> if I bg that, and logout what are the chances of it continuing?
[10:52] <lifeless> elmo: it should continue fine. but it will clutter your terminal
[10:52] <lifeless> erm
[10:52] <elmo> what terminal?  I'm logging out :)
[10:52] <lifeless> if you nohup it that is
[10:53] <SteveA> not using screen?
[10:53] <elmo> you can't nohup after the fact, can you?
[10:53] <elmo> no, I forgot to use screen because I'm a muppet
[10:53] <SteveA> i wish there were a screen-after-the-fact command
[10:53] <lifeless> SteveA: it is possible with sufficient evil
[10:54] <lifeless> SteveA: only need to change a couple of variables...
[10:54] <elmo> me too - someone else suggested changing my login scripts to startup screen if I'm not already in one
[10:54] <lifeless> elmo: no idea what it will do to be honest, it will probably react t othe HUP by exiting as most good processes will
[10:55] <elmo> whine
[10:55] <lifeless>        The shell exits by default upon receipt of a SIGHUP.  Before exiting, an interactive shell resends the SIGHUP to all jobs, running or stopped.   Stopped  jobs  are
[10:55] <lifeless>        sent  SIGCONT  to  ensure that they receive the SIGHUP.  To prevent the shell from sending the signal to a particular job, it should be removed from the jobs table
[10:55] <lifeless>        with the disown builtin (see SHELL BUILTIN COMMANDS below) or marked to not receive SIGHUP using disown -h.
[10:55] <lifeless> i.e. disown -h it 
[10:55] <lifeless> bg it, disown -h, fg it then log out
[10:56] <lifeless> if you are not using bash, read your man page
[10:56] <lifeless> o course, it is interesting to consider what will happen to the output buffer as it continues to run
[10:57] <lifeless> it may block after some time due to that
[10:58] <spiv> Or attach gdb, and do 'call PyRun_SimpleString("import signal; signal.signal(signal.SIGHUP, signal.SIG_IGN)")' ;)
[10:59] <elmo> spiv: disgusting_hack_points++
[10:59] <kiko> just control-c the reweave
[10:59] <kiko> and try bzr merge again
[11:00] <elmo> that's safe?
[11:00] <elmo> and won't waste the n hours already run
[11:00] <lifeless> it will have to reweave
[11:00] <lifeless> its not a good thing to interrupt
[11:01] <lifeless> kiko: this is different to what you had
[11:02] <kiko> really now
[11:03] <jamesh> this is probably the "make my inventory bigger" inventory reweave
[11:04] <kiko> I hate reweaves of any sort
[11:04] <kiko> they eat up my free time
[11:05] <lifeless> jamesh: nah, thats shows 'adding revisions'.
[11:05] <lifeless> erm, adding inventories
[11:22] <lifeless> night all
[11:28] <dilys> Merge to devel/launchpad/: [trivial]  rip out use of zodb. (r3316: Steve Alexander)
[11:33] <elmo> gandwana 2/2 down, restarting
[11:34] <seb128> elmo broke launchpad!!
[11:34] <elmo> no, elmo's fixing launchpad
[11:34] <seb128> good elmo ;)
[11:35] <seb128> ah, it's back
[11:37] <elmo> GRR
[11:48] <kiko> wth is wrong with that appserver