=== Ursinha-lunch is now known as Ursinha [02:49] sinzui: ping [02:50] I'm looking at https://edge.launchpad.net/ubuntu/maverick/+source/upower/+edit-packaging [02:51] and and https://edge.launchpad.net/upower which seems to be totally different [02:52] whats the process to zap /upower so someone can link the udev upower to it ? [03:31] lifeless: /upower seems to be deactivated -- I can't see it. [04:07] wgrant: it is [04:07] its for a 'User POWER on' crack feature [04:39] mars: have you seen 'shrinksafe' ? [06:19] i wonder why my dapper ppa only seems to be building on i386 [06:19] because its arch:all [06:19] ah of course [06:37] bryceh: Happy Birthday! Have a splendid time! [08:28] good morning === zyga is now known as zyga_away [09:02] Howdty [09:03] bigjools: Morning. [09:03] g'day [09:03] nigelb, thanks :-) [09:05] bigjools: This granting of launchpad.View to P3A subscribers does not sit well with me. I've not seen any rationale for changing the very explicit decision to not grant it in the first place, and it introduces unobvious things like bug #600910. [09:06] le sigh [09:07] wgrant: it's the right thing to do generally, however yes there's going to be some wrinkles [09:07] bryceh: :) [09:09] bigjools: Well, yes, but it would seem wise to identify and iron out the wrinkles before granting a whole lot of unintended privileges... [09:09] wgrant: we thought we had.... [09:10] at least the ones we saw were not important right now [09:10] bigjools: that comment was below the belt (ref wallabies). That is all. ;-) [09:10] spm: bwahaha :) [09:10] bigjools: So the +packages restriction is just to... avoid confusing users? Because all the other subordinate pages and API stuff is still permitted. [09:11] spm: the series in Sydney just gone was very entertaining though [09:11] wgrant: yes that's still a wrinkle that needs to be ironed, but we don't care about it right now [09:11] heh, I'll have to take your word for it. wasn't even aware it was in Sydney. [09:11] OK. [09:11] wgrant: basically because it only really matters when we do commercial PPAs [09:12] wgrant: anyway thanks for filing the bug [09:12] * bigjools proceeds to download another load of security fixes. sigh. [09:13] Heh. === lifeless_ is now known as lifeless === almaisan-away is now known as al-maisan [10:02] hi guys, [10:03] regarding bug #525571, what bzr and bzr-svn versions should I target to simplify the fix backport on launchpad ? [10:03] <_mup_> Bug #525571: No locking when updating files in ~/.bazaar

[10:04] wow, _mup_, you're far verbose than the ubot :) [10:04] far more verbose [10:04] it is entertaining when they were in the same channel. [10:04] http://bazaar.launchpad.net/~launchpad-pqm/launchpad/devel/annotate/head:/versions.cfg says 2.1.0 for bzr but doesn't mention bzr-svn [10:05] vila: 'morning [10:05] omg, yet another nick :) [10:06] jelmer! [10:06] jelmer is around ? Cool :) [10:07] hi lifeless [10:07] vila: bzr-svn trunk should already support LockableConfig [10:08] rinze: wow, supporting un-landed fixes is an impressive break-through :) [10:08] rinze: I guess that answer my question by implying that bzr-svn trunk will be back ported right ? [10:08] errr, deployed I meant [10:09] vila: Yeah, the code team usually just take a known working version of bzr-svn [10:09] s/version/snapshot/ [10:09] ok, I'll focus and targeting the fix to bzr-2.10 then [10:09] thanks [10:10] another typo day... [10:12] _fail_ networking. [10:12] this E160 is so bad === lifeless_ is now known as lifeless [11:02] Morning, all. [11:21] morning [11:21] so you were asking what I mean by 'trunk can be broken' [11:22] I mean a few things, most of them summarise as 'not fit for purpose', I think. [11:23] most obviously, we currently don't trust trunk [11:23] when we release, we insist on a QA step done by each team, for many changes [11:26] also, the way we do commits to trunk, we can have tests failing [11:26] edge trunk = stable though === zyga_away is now known as zyga [11:27] could you expand on that, I'm not entirely sure I'm across everything here. [11:29] we commit to "devel" which is blessed by buildbot and merged to stable [11:29] edge rolls out from stable [11:30] so it's slightly disingenuous to talk about trunk [11:30] 20:27 < lifeless> could you expand on that, I'm not entirely sure I'm across everything here. [11:30] 20:27 -!- zyga_away is now known as zyga [11:30] gar [11:30] and then I lost the magic network [11:30] we commit to "devel" which is blessed by buildbot and merged to stable [11:30] edge rolls out from stable [11:30] so it's slightly disingenuous to talk about trunk [11:30] ah [11:30] we have 4 trunk branches [11:30] all slightly different :) [11:31] what does the merge to stable entail - full test suite ? [11:32] dev.launchpad.net/Trunk and dev.launchpad.net/Trunk/Glue ftw [11:32] you are in a mazy of twisty tunnels. [11:32] There is a grue. === lifeless_ is now known as lifeless [11:33] bigjools: what does the merge to stable entail - full test suite? [11:34] devel -> full test run -> stable [11:34] stable -> full test run -> db-devel [11:34] Er. [11:34] No test run in that second one, sorry. [11:34] db-devel -> full test run -> db-stable [11:36] lifeless, ? [11:37] mwhudson_: thanks [11:37] your links were the last things I saw. [11:37] * lifeless_ hates on this gsm modem. [11:37] lifeless: I'm trying to find a wiki doc explaining this, but basically wot wgrabt says devel -> buildbot -> merge to stable -> merge to db-devel -> buildbot -> merge to db-stable [11:37] lifeless_: 20:27 -!- zyga_away is now known as zyga <- ? [11:38] zyga: showing what I saw before d/c [11:38] lifeless_, ah ok [11:39] so *stable has no test failures modulo really unexpected things [11:39] lifeless_: Right. Any issues in *stable are holes in the test suite. === lifeless_ is now known as lifeless [11:57] <-hate-> === lifeless_ is now known as lifeless [12:30] Sorry I missed the discussion here. I thought lifeless meant take it to the launchpad-dev mailing list. [12:40] deryck: no worries,w list works too :) [12:40] deryck: I wouldn't normally take a realtime conversation to the list though, for future ref [12:40] lifeless, understood. [12:41] thanks for the discussion, though. I really hope we can end up with some form of this. [12:41] Me too [12:41] I'm trying to make sure we exam it critically [12:41] so that its a success [12:42] yes, I don't mind critical examination at all. I want it's success, too. [12:43] :) [12:49] "its" even. Perhaps I stayed up too late playing Champions Online last night. [12:51] StevenK: ping [12:51] StevenK: what happened with that lognamer branch ? === matsubara-afk is now known as matsubara [13:01] deryck: perhaps we can drill into this at the epic [13:02] lifeless, yeah, I think we should somehow. Not sure how to drill into it in a productive way, though. talk or code? [13:02] quick gap analysis, identify the most beneficial thing in the gap to fix, fix it. [13:02] hey, so how do I land an approved branch if I'm not ex2test-ready [13:03] https://code.edge.launchpad.net/~lifeless/launchpad/lognamer/+merge/28574 [13:04] lifeless, I can `ec2 land` it for you. [13:04] awesome [13:04] if it fails, do I get mail ? [13:04] lifeless, and that plan sounds reasonable. An analysis talk, followed by fix something, followed by list of remaining items to fix. [13:04] lifeless, yes, you'll get mail. [13:05] \o/ [13:08] deryck: in general I think knowing the scope of the problem is useful, but detailed talking beyond the first couple of steps is generally wasted, unless you have reason to believe a roadblock will be hit [13:09] lifeless, right, agreed. I think we need a way to better connect lp devs and losas on this issue, too. [13:10] s/on this issue, / [13:10] :P [13:10] theres a pretty good collaboration about operational issues, but significant disconnects in other ways [13:10] right :-) [13:32] Wow. i386 build queue up to 24 hours. [13:36] jml: https://edge.launchpad.net/testtools/0.9/0.9.4 done === lifeless_ is now known as lifeless [13:48] lifeless_: I did send it off to ec2, so that's just odd [13:48] StevenK: yeah [13:48] * rinze waves to StevenK [13:48] StevenK: I trust that you did [13:48] deryck has done it again [13:48] StevenK: I didn't get mail [13:48] Ah, okay [13:49] rinze: your older nicks are better [13:51] lifeless_, thanks! === rinze is now known as ctrlsoft [13:52] jml: my pleasure [13:52] what did I do? [13:52] deryck: ec2test my branch [13:53] ah, ok === henninge_ is now known as henninge [13:57] I really want an 'unreleased code report' for my projects. [13:57] perhaps next year I'll shave that yak. [14:10] I really wish releases were announcements [14:12] http://pypi.python.org/pypi/celery/2.0.0 looks interesting [14:12] and with that, I think I'm going to halt() [14:13] hmm [14:13] I smell inappropriate coupling [14:13] "/var/launchpad/test/lib/lp/services/job/tests/test_runner.py", line 410, in runFromSource [14:13] errorlog.globalErrorUtility.oops_prefix, [14:13] for the weekend [14:13] deryck: thanks for that. [14:17] lifeless_: celery is something I'm interested in [14:18] bigjools: @ the epic, lets talk [14:18] yeppers [14:19] lifeless_: I'm thinking build farm [14:19] bigjools: we have many things that look like an appropriate nail, to me. [14:19] hellyeah [14:19] we *need* a messaging system now [14:20] hanging a job system off it would be great === matsubara is now known as matsubara-afk [14:53] Is there a way I can get an up-to-date milestone bug listing? [14:54] I'm trying to garden an upcoming milestone, but working blind is a bit hard. [14:55] wgrant, you mean un-cached? If so, I don't think there is a way. [14:55] Argh. [14:55] That sucks. [14:59] Ah, production is untainted for the next few days. [14:59] This is good. [15:06] Bug #601051 [15:06] <_mup_> Bug #601051: Caching of primary data sources slashes utility === ctrlsoft is now known as jelmer_ [15:44] bigjools: How is the rebuild archive scored at the moment? All -10, except for main, which is -5? [15:44] wgrant: not quite [15:44] stuff is getting scored up in batches to make it run quicker [15:44] Ah. [15:44] I was wondering why there was so much stuff building. [15:44] When the massive PPA queue should have been building instead... === salgado is now known as salgado-lunch [15:45] there's not much of it left, it'll get disabled when main is done [15:46] Great. [15:46] Because it's... erm... somewhat irksome when using PPAs to manage release distribution, and the queue is a couple of days long. [15:51] How come there's never a help contact in the #launchpad topic these days? === salgado-lunch is now known as salgado === Ursinha is now known as Ursinha-sad === matsubara-afk is now known as matsubara === mwhudson_ is now known as mwhudson [18:45] Anyone know why my Librarian won't restart after an unexpected system shutdown, and what I do about it? [18:47] jtv: stale pid file? [18:47] in /var/tmp/ somewhere i guess === al-maisan is now known as almaisan-away [20:09] jelmer_: ping [20:24] EdwinGrubbs, pong === rinze is now known as jelmer_ [20:25] EdwinGrubbs, pong === mwhudson_ is now known as mwhudson === Ursinha is now known as Ursinha-dinner === matsubara is now known as matsubara-afk