[00:48] <Saviq> robru, I will need to ask you to upload oxide to silo 10 after all, do you need .orig file if it comes from the archive?
[00:48] <robru> Saviq: please just put it in a PPA and I'll use copyPackage rather than trying to dget and dput it myself
[00:48] <Saviq> robru, ack, makes sense
[01:56] <robru> Saviq: did you put it in a ppa somewhere? I'm heading out in 30 mins and won't be back for 2 hours
[02:00] <Saviq> robru, hopefully will be done within that time
[02:00] <Saviq> robru, have all kinds of troubles with this fucking thing
[02:00] <robru> Saviq: that's why I didn't want to do it ;-)
[02:00] <Saviq> robru, I know! :)
[02:01] <Saviq> but it's looking hopeful now
[02:01] <Saviq> that source is just too big
[02:01] <Saviq> ETOOMANYFILES
[02:01] <Saviq> btrfs choked on that on my laptop
[02:01] <Saviq> not sure if it will recover
[02:02] <robru> ouch
[02:03] <Saviq> 40G free and ENOSPC, btrfs is great at that
[02:11] <Saviq> fortunately tbird offers to free 600G on this 256G drive by purging folders... wonder what else would it purge
[02:13] <Saviq> w00t
[02:14] <Saviq> vivid uploaded, now xenial
[02:14] <robru> nice
[02:22] <Saviq> robru, ok, ppa:saviq/train - oxide-qt for vivid (building) and xenial (should show up within a minute)
[02:23] <Saviq> thanks!
[02:23] <Saviq> into silo 10, that is
[02:23] <robru> Saviq: ok, hopefully that shows up within 7 minutes ;-)
[02:24] <robru> Saviq: check your email for rejection notices
[02:25] <robru> Saviq: ones' 0.12.6 and one's 0.12.5?
[02:26] <Saviq> robru, yeah, xenial got an upload just a few hours ago
[02:26] <Saviq> robru, and the same for vivid is waiting in silo
[02:26] <Saviq> so decided to not jump the gun
[02:26] <robru> Saviq: ok copied, train should notice them within 15 minutes.
[02:26] <Saviq> robru, THANK  YOU
[02:27] <robru> Saviq: you're welcome!
[02:27] <robru> Saviq: I'll be back in 2hrs for when you inevitably find a problem and need me to upload the second iteration ;-)
[02:27] <Saviq> it's only gonna take 8h to build now, it's fine ;)
[02:27] <robru> ah ok
[02:27] <robru> Saviq: you should probably cancel the builds in your PPA
[02:27] <Saviq> robru, right, will do
[02:28] <robru> Saviq: IIRC we added chris as a person who has permission to upload directly to train packages, i guess we might also consider adding you to that if this happens a lot. even better would be getting oxide-qt train-ready so you can just use MPs like everybody else ;-)
[02:28] <Saviq> :)
[02:29] <Saviq> robru, I don't intend to touch oxide EVER AGAIN
[02:29] <robru> Saviq: TOUCHED IT LAST!!!!!!
[02:29] <robru> Saviq: it's yours forever now, as it is written!
[02:29] <robru> alright, I gotta bounce. bbl
[10:30] <chrisccoulson> dbarth, I published the Oxide 1.12.6 security update yesterday
[11:26] <sil2100> Saviq: hey! From what davmor2 is saying things look good in OTA-9.1 so we probably won't need silo 46 anymore
[11:26] <sil2100> Saviq: any objections for freeing it?
[11:26] <Saviq> sil2100, please merge, first, thanks!
[11:27] <sil2100> Oh, merge? You have a valid trunk for cherry-picks like this?
[11:31] <Saviq> sil2100, yeah, lp:$project/stable
[13:23] <dbarth> chrisccoulson: i validated it for webapps in silo 77
[13:23] <dbarth> should approve today
[13:30] <dbarth> chrisccoulson: well, i'll do the browser smoke testing now
[14:54] <rvr> pstolowski: ping
[14:54] <pstolowski> rvr, hey
[14:55] <rvr> pstolowski: http://paste.ubuntu.com/15132112/
[14:55] <rvr> pstolowski: I got a crash testing silo 80
[14:55] <rvr> pstolowski: Take a look, I don't think it's related to the changes, but just in case
[14:56] <pstolowski> rvr, it's a scope crash right? no, there no chance for this to be related to the changes in the silo
[14:57] <rvr> pstolowski: Ok
[14:58] <rvr> pstolowski: The crash was reported by _usr_lib_arm-linux-gnueabihf_unity-scopes_scoperunner
[14:58] <pstolowski> rvr, yeah, noticed that in the backtrace. do you know what scope crashes? Apps?
[14:59] <rvr> pstolowski: El Pais (news)
[14:59] <dobey> ToyKeeper: any luck?
[15:00] <pstolowski> rvr, something for kyleN's team then
[15:03] <rvr> pstolowski: Silo approved
[15:03] <pstolowski> rvr, thanks!
[15:11] <dbarth_> hey guys, just a quick heads up about https://requests.ci-train.ubuntu.com/#/ticket/923 (silo 036)
[15:12] <dbarth_> getting this landed would help us unblock further OA / oxide build issues and empty our own silo queue
[17:36] <alesage> robru, is it possible to un-pass a QA signoff?
[17:52] <robru> alesage: if you clear the lander signoff it'll clear the other ones too
[17:52] <robru> alesage: or if you do a build it'll clear the signoffs
[17:53] <alesage> robru, just clearing the "qa signoff" doesn't have the effect I want?
[17:53] <alesage> robru, comfortable with that control :)
[17:57] <robru> alesage: oh do you have permission to clear it yourself?
[17:58] <alesage> robru, unknown
[17:58] <robru> alesage: it's restricted who can touch the qa field. Are you qa? I literally just woke up, can't brain yet
[17:59] <alesage> robru, I'm QA, able to edit the "qa signoff" field
[17:59] <alesage> robru, just trying to prevent breaking the world if this goes into the build
[18:00] <alesage> robru, here's the request FWIW https://requests.ci-train.ubuntu.com/#/ticket/1013
[18:00] <robru> alesage: OK you can set it then. Setting it to failed doesn't actually prevent it from being published, but it does make the whole page turn red
[18:01] <alesage> robru, I'd like to "take back" my approval, also I'm assuming this means I want it not to be published--can you help?
[18:02] <robru> alesage: yeah that approval is taken back. The qa field is just advisory, so if somebody felt like publishing they can. I won't ;-)
[18:03] <robru> I should really step up train security. Currently anybody can delete anybody else's silos
[18:03] <alesage> robru, ok I was imagining a colossal machine spinning into action
[18:04] <robru> alesage: nope the colossal machine monitors the situation at all times but nothing if triggered by qa approval. Humans need to click publish
[18:16] <popey> robru: what rights does a community person need to submit to citrain?
[18:37] <robru> popey: they would need to be **EXTREMELY** well trusted as being granted train permissions means they can rebuild or delete any silo at any time.
[18:37] <robru> popey: also core devs have full train power already.
[18:38] <popey> okay.
[18:38] <popey> The people I'm thinking of are long time contributors, who would obviously be careful.
[18:38] <robru> popey: in terms of "careful", mistakes are ok, it's actively malicious people I'm concerned about
[18:39] <popey> sure, none of these people are
[18:39] <robru> great
[18:39] <popey> I'm only thinking one or two
[18:39] <popey> but they aren't currently beating down the door to have this authorisation
[18:39] <popey> I'm just speculatively asking :)
[18:39] <robru> popey: so basically they need to be added to ci-train-users team, and told to read the documentation about it.
[18:39] <popey> okay
[18:39] <popey> DanChapman: ^
[18:39] <robru> popey: but I'd probably want to run that by steve
[18:39] <popey> sure. no problem.
[20:19] <camako> robru, just wanna confirm my understanding, on silo 051, is Britney stuck due to the autopkgtest for unity8?
[20:41] <robru> camako: everything in excuses.html that says "Not considered" prevents out from being approved