[02:19] I don't get blueprints. When should a blueprint be created, and when should a bug be created? [02:23] for what projet [02:23] personally, I don't use blueprints much/at all. [02:23] but different projects have different needs [02:24] Ubuntu is by far the heaviest user of blueprints [03:00] lifeless: Oh, I'm part of a small project called Photostory, they seem to focus heavily on blueprints. [03:00] I just can't get my head round them. [03:01] https://launchpad.net/photostory [03:16] Hmm. [03:16] I just had edge send me an incomplete page. [03:16] And one of my API cronjobs just died similarly. [03:16] Seems to be working OK now, though. [03:34] wgrant: link glitch? [03:37] lifeless: Hm? [03:47] wgrant: did your internets go boom for a brief period [03:48] lifeless: Well, the browser was on my laptop, and the API script is running in the UK... so I doubt it. [03:49] me too [03:49] had to ask [04:01] edge having issues? [04:01] eh.. nvm [04:32] lifeless: API script just did it again. [04:32] Odd. [04:40] weird [04:55] 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] 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] micahg: whats the oops :) [04:57] I /always/ want the oops [04:57] OOPS :) OOPS-1716ED446 [04:57] https://lp-oops.canonical.com/oops.py/?oopsid=1716ED446 [04:57] lp seems sluggish right now, [04:57] 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] wow [04:58] 600 lookups [04:58] and many are memcached [04:58] and many of those are 14ms or so [04:59] hmm [05:00] micahg: pleae file a new bug [05:00] lifeless: will do, thanks [05:00] micahg: thats not 'many attachments' [05:00] lifeless: I can't see the bug to tell :) [05:00] micahg: try now [05:00] micahg: it just worked for me [05:00] anyhow, please file a bug [05:00] * micahg tries in a new tab [05:00] it looks like 'many bugtasks' to me. [05:01] and 'many nominations' [05:01] include your OOPS in there. [05:01] nope, timesout again on edge [05:01] thanks! [05:01] now I have 2 :) [05:01] worked for me on edge, what can I say :) [05:01] anyhow, OOPS shows: [05:01] - clearly a problem [05:01] - lots of repeated nearly-identical queries [05:01] - fixables [05:01] simples === MTeck is now known as MTecknology === warp11 is now known as warp10 === d1b_ is now known as d1b === beuno_ is now known as beuno === wgrant_ is now known as wgrant [09:28] Hi [09:28] Anyone around who can help me with team mailing list privacy? === popey__ is now known as popey [10:11] 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] JoshBrown: How long has it been saying that? === Lcawte|Away is now known as Lcawte [10:36] !ask | humphreybc [10:36] humphreybc: Please don't ask to ask a question, simply ask the question (all on ONE line and in the channel, so that others can read and follow it easily). If anyone knows the answer they will most likely reply. :-) [10:41] lifeless: I want to make our OMG! Ubuntu! team mailing list [10:41] private [10:42] we don't support changing the privacy of teams with list post creation. [10:42] Also, team privacy and mailing list privacy are linked. [10:42] 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] okay [10:44] so how should I go about it? [10:44] recreate a new ML? [10:44] change to a google apps ML? [10:44] I think you need a commerical entitlement as well to do private lists [10:44] what do you mean? [11:55] 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] both me and Drizzle's build bots are seeing it today === LinuxJedi|away is now known as LinuxJedi [12:11] wgrant: It's fixed now === Adri2000_ is now known as Adri2000 === LinuxJedi is now known as LinuxJedi|away [16:13] What is the correct way to upgrade a launchpad repo from pack-0.92 to current format? [16:14] hm launchpad branch I guess rather [16:33] gasp, the LP API is in a bad shape since yesterday. lots of IncompleteRead from lazr :( [16:42] bzr: ERROR: Invalid http response for https://xmlrpc.edge.launchpad.net/bazaar/: Unable to handle http code 503: Service Unavailable [16:42] hm [16:42] worked on 5th retry === LinuxJedi|away is now known as LinuxJedi === LinuxJedi is now known as LinuxJedi|away [18:08] Vorpal: yep, I've had that locally and the drizzle test servers have been getting that error all day [18:17] 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 === LinuxJedi|away is now known as LinuxJedi === LinuxJedi is now known as LinuxJedi|away === Ursinha is now known as Ursinha-afk === shadeslayer is now known as evilshadeslayer === evilshadeslayer is now known as shadeslayer === LinuxJedi|away is now known as LinuxJedi === Meths_ is now known as Meths [20:08] hi i cant seem to be able to get maverick daily builds for one of my PPA's [20:09] are those still disabled? [20:10] https://code.edge.launchpad.net/~rekonq/+recipe/rekonq-daily [20:10] ^ that one [20:11] ill delete and try again [20:11] oh..wow [20:11] i get OOPS-1716ED2264 [20:11] https://lp-oops.canonical.com/oops.py/?oopsid=1716ED2264 [20:17] hello [20:18] i have a package and it keeps building and building: https://launchpad.net/~wesleys/+archive/ppa/+builds?build_text=&build_state=building [20:19] E: There are problems and -y was used without --force-yes [20:59] 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] shadeslayer: you might like to file a bug [20:59] referencing that OOPS === lifeless changed the topic of #launchpad to: partial / slow pages being investigated | http://launchpad.net/ | Read https://help.launchpad.net/ for help | Help contact: - | Join https://launchpad.net/~launchpad-users | This channel is logged: http://irclogs.ubuntu.com/ | Launchpad is open source: https://dev.launchpad.net/ [21:07] lifeless: alright.. and yeah LP feels slow :( [21:10] there is something weird, in th eneighbourhood === soren_ is now known as soren === Daviey_ is now known as Daviey === LinuxJedi is now known as LinuxJedi|away === Lcawte is now known as Lcawte|Away [22:08] lbieber: hi [22:08] lbieber: what bzr symptoms were you experiencing [22:23] lifeless: its very very slow and was periodically getting time outs [22:23] lbieber: are you using edge or production ? [22:23] lbieber: what was happening with bzr for you? [22:23] lifeless : using production [22:25] yeah there's definitely a problem [22:25] pull-lp-source (downloading source packages from LP) is extremely slow [22:27] Laney: does it make API calls? [22:27] Laney: if so, what server is it using - lpnet or edge? [22:31] lifeless: yes, it uses edge [22:31] ok [22:31] thanks [22:31] can you please get it to use prod ? [22:38] lifeless: yeah that's it, much better on production [22:39] Laney: everything using lp should use production by default :) [22:40] ah, a crafty way to enforce this [22:40] well no [22:40] its a serious issue [22:40] but whatever it is, could occur to prod too, so we're being careful to really get the guts of whats up [22:41] Laney: anyhow, we're going to eliminate edge soon anyhow [22:41] turn it into a massive redirect [22:41] no more beta programme? [22:41] we'll still have beta programme [22:41] but it will be code based not branch based [22:41] few features actually go from start to finish in one month [22:42] so we already hide them from lpnet when the first months worth of code is deployed there [22:42] we'll just start hiding by being in the beta group or not [22:42] rather than on the edge url or not [22:42] makes sense [22:43] we'll get much simpler production environment [22:43] with less ops-leve variation [22:43] 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] it seems like there's a convoluted process to push rapid fixes out atm === stgraber_ is now known as stgraber [22:44] its pretty straight forward but because its the exception not the rule its not as polished or easy, and its not the default === lfaraone_ is now known as lfaraone