[02:19] <JoshBrown> I don't get blueprints. When should a blueprint be created, and when should a bug be created?
[02:23] <lifeless> for what projet
[02:23] <lifeless> personally, I don't use blueprints much/at all.
[02:23] <lifeless> but different projects have different needs
[02:24] <lifeless> Ubuntu is by far the heaviest user of blueprints
[03:00] <JoshBrown> lifeless: Oh, I'm part of a small project called Photostory, they seem to focus heavily on blueprints.
[03:00] <JoshBrown> I just can't get my head round them.
[03:01] <JoshBrown> https://launchpad.net/photostory
[03:16] <wgrant> Hmm.
[03:16] <wgrant> I just had edge send me an incomplete page.
[03:16] <wgrant> And one of my API cronjobs just died similarly.
[03:16] <wgrant> Seems to be working OK now, though.
[03:34] <lifeless> wgrant: link glitch?
[03:37] <wgrant> lifeless: Hm?
[03:47] <lifeless> wgrant: did your internets go boom for a brief period
[03:48] <wgrant> lifeless: Well, the browser was on my laptop, and the API script is running in the UK... so I doubt it.
[03:49] <lifeless> me too
[03:49] <lifeless> had to ask
[04:01] <MTecknology> edge having issues?
[04:01] <MTecknology> eh.. nvm
[04:32] <wgrant> lifeless: API script just did it again.
[04:32] <wgrant> Odd.
[04:40] <lifeless> weird
[04:55] <micahg> lifeless: if I just had a bug timeout on edge that fits the title of bug 583553 happen, is the one filed sufficient?
[04:55] <ubot5`> Launchpad bug 583553 in Launchpad Bugs "Timeout accessing bug with lots of comments and attachments (affected: 1, heat: 6)" [High,Fix committed] https://launchpad.net/bugs/583553
[04:56] <lifeless> micahg: whats the oops :)
[04:57] <lifeless> I /always/ want the oops
[04:57] <micahg> OOPS :)          OOPS-1716ED446
[04:57] <ubot5`> https://lp-oops.canonical.com/oops.py/?oopsid=1716ED446
[04:57] <lifeless> lp seems sluggish right now,
[04:57] <lifeless> I'm going to poke at graphs and see if something is obviously wrong
[04:57]  * micahg just got on from 3 days off, so I'm a little out of the loop
[04:58] <lifeless> wow
[04:58] <lifeless> 600 lookups
[04:58] <lifeless> and many are memcached
[04:58] <lifeless> and many of those are 14ms or so
[04:59] <lifeless> hmm
[05:00] <lifeless> micahg: pleae file a new bug
[05:00] <micahg> lifeless: will do, thanks
[05:00] <lifeless> micahg: thats not 'many attachments'
[05:00] <micahg> lifeless: I can't see the bug to tell :)
[05:00] <lifeless> micahg: try now
[05:00] <lifeless> micahg: it just worked for me
[05:00] <lifeless> anyhow, please file a bug
[05:00]  * micahg tries in a new tab
[05:00] <lifeless> it looks like 'many bugtasks' to me.
[05:01] <lifeless> and 'many nominations'
[05:01] <lifeless> include your OOPS in there.
[05:01] <micahg> nope, timesout again on edge
[05:01] <lifeless> thanks!
[05:01] <micahg> now I have 2 :)
[05:01] <lifeless> worked for me on edge, what can I say :)
[05:01] <lifeless> anyhow, OOPS shows:
[05:01] <lifeless>  - clearly a problem
[05:01] <lifeless>  - lots of repeated nearly-identical queries
[05:01] <lifeless>  - fixables
[05:01] <lifeless> simples
[09:28] <humphreybc> Hi
[09:28] <humphreybc> Anyone around who can help me with team mailing list privacy?
[10:11] <JoshBrown> staging.launchpad.net is down: "The staging server is currently getting a code and db update. If the situation persists, let us know in the #launchpad IRC channel on Freenode."
[10:17] <wgrant> JoshBrown: How long has it been saying that?
[10:36] <lifeless> !ask | humphreybc
[10:41] <humphreybc> lifeless: I want to make our OMG! Ubuntu! team mailing list
[10:41] <humphreybc> private
[10:42] <lifeless> we don't support changing the privacy of teams with list post creation.
[10:42] <wgrant> Also, team privacy and mailing list privacy are linked.
[10:42] <lifeless> Its a valid bug that we don't support it, but technically, things blow up when we try, and noone has had time to fix it.
[10:44] <humphreybc> okay
[10:44] <humphreybc> so how should I go about it?
[10:44] <humphreybc> recreate a new ML?
[10:44] <humphreybc> change to a google apps ML?
[10:44] <lifeless> I think you need a commerical entitlement as well to do private lists
[10:44] <humphreybc> what do you mean?
[11:55] <LinuxJedi|away> anyone else getting this in Laundpad's bzr? "bzr: ERROR: Invalid http response for https://xmlrpc.edge.launchpad.net/bazaar/: Unable to handle http code 503: Service Unavailable"
[11:55] <LinuxJedi|away> both me and Drizzle's build bots are seeing it today
[12:11] <JoshBrown> wgrant: It's fixed now
[16:13] <Vorpal> What is the correct way to upgrade a launchpad repo from pack-0.92 to current format?
[16:14] <Vorpal> hm launchpad branch I guess rather
[16:33] <fta> gasp, the LP API is in a bad shape since yesterday. lots of IncompleteRead from lazr :(
[16:42] <Vorpal> bzr: ERROR: Invalid http response for https://xmlrpc.edge.launchpad.net/bazaar/: Unable to handle http code 503: Service Unavailable
[16:42] <Vorpal> hm
[16:42] <Vorpal> worked on 5th retry
[18:08] <LinuxJedi|away> Vorpal: yep, I've had that locally and the drizzle test servers have been getting that error all day
[18:17] <Vorpal> LinuxJedi|away, managed to get the conversion from pack-0.92 to 2a done in the end though. It didn't error out every time. Just some 70% or such
[20:08] <shadeslayer> hi i cant seem to be able to get maverick daily builds for one of my PPA's
[20:09] <shadeslayer> are those still disabled?
[20:10] <shadeslayer> https://code.edge.launchpad.net/~rekonq/+recipe/rekonq-daily
[20:10] <shadeslayer> ^ that one
[20:11] <shadeslayer> ill delete and try again
[20:11] <shadeslayer> oh..wow
[20:11] <shadeslayer> i get OOPS-1716ED2264
[20:17] <slacker_nl> hello
[20:18] <slacker_nl> i have a package and it keeps building and building: https://launchpad.net/~wesleys/+archive/ppa/+builds?build_text=&build_state=building
[20:19] <slacker_nl> E: There are problems and -y was used without --force-yes
[20:59] <lifeless> shadeslayer:   IntegrityError: update or delete on table "sourcepackagerecipebuild" violates foreign key constraint "sourcepackagerecipebuildjob_sourcepackage_recipe_build_fkey" on table "sourcepackagerecipebuildjob" DETAIL: Key (id)=(544) is still referenced from table "sourcepackagerecipebuildjob".
[20:59] <lifeless> shadeslayer: you might like to file a bug
[20:59] <lifeless> referencing that OOPS
[21:07] <shadeslayer> lifeless: alright.. and yeah LP feels slow :(
[21:10] <lifeless> there is something weird, in th eneighbourhood
[22:08] <lifeless> lbieber: hi
[22:08] <lifeless> lbieber: what bzr symptoms were you experiencing
[22:23] <lbieber> lifeless: its very very slow and was periodically getting time outs
[22:23] <lifeless> lbieber: are you using edge or production ?
[22:23] <lifeless> lbieber: what was happening with bzr for you?
[22:23] <lbieber> lifeless :  using production
[22:25] <Laney> yeah there's definitely a problem
[22:25] <Laney> pull-lp-source (downloading source packages from LP) is extremely slow
[22:27] <lifeless> Laney: does it make API calls?
[22:27] <lifeless> Laney: if so, what server is it using - lpnet or edge?
[22:31] <Laney> lifeless: yes, it uses edge
[22:31] <lifeless> ok
[22:31] <lifeless> thanks
[22:31] <lifeless> can you please get it to use prod ?
[22:38] <Laney> lifeless: yeah that's it, much better on production
[22:39] <lifeless> Laney: everything using lp should use production by default :)
[22:40] <Laney> ah, a crafty way to enforce this
[22:40] <lifeless> well no
[22:40] <lifeless> its a serious issue
[22:40] <lifeless> but whatever it is, could occur to prod too, so we're being careful to really get the guts of whats up
[22:41] <lifeless> Laney: anyhow, we're going to eliminate edge soon anyhow
[22:41] <lifeless> turn it into a massive redirect
[22:41] <Laney> no more beta programme?
[22:41] <lifeless> we'll still have beta programme
[22:41] <lifeless> but it will be code based not branch based
[22:41] <lifeless> few features actually go from start to finish in one month
[22:42] <lifeless> so we already hide them from lpnet when the first months worth of code is deployed there
[22:42] <lifeless> we'll just start hiding by being in the beta group or not
[22:42] <lifeless> rather than on the edge url or not
[22:42] <Laney> makes sense
[22:43] <lifeless> we'll get much simpler production environment
[22:43] <lifeless> with less ops-leve variation
[22:43] <lifeless> and we'll get fixes for timeouts and issues out to everyone much quicker (because we'll deploy to prod daily or so)
[22:43] <Laney> it seems like there's a convoluted process to push rapid fixes out atm
[22:44] <lifeless> its pretty straight forward but because its the exception not the rule its not as polished or easy, and its not the default