[06:55] <flexiondotorg> infinity, Laney There were no new iso images built, for any flavour last night.
[06:56] <flexiondotorg> I'd also requested an Ubuntu MATE rebuild yesterday which, from what I have access too, built a livefs but no iso materialised and the rebuild request is stuck in a rebuild state in the UI.
[06:58] <flexiondotorg> https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/yakkety/ubuntu-mate
[06:58] <flexiondotorg> http://people.canonical.com/~ubuntu-archive/cd-build-logs/ubuntu-mate/yakkety/daily-live-20160623.1.log
[07:38] <infinity> flexiondotorg: We had a massive datacenter outage yesterday.
[07:40] <infinity> Err... And cdimage is busted.
[07:44] <infinity> flexiondotorg: Might be happier now.
[08:06] <flexiondotorg> infinity, Thanks.
[08:53] <apw> doko, did you intend that version to be ubuntu2.1 rather than 1.1 ?
[08:55] <doko> apw, ahh, I can change that
[08:56] <apw> doko, not looked at the diff just noticed the anomoly in queuebot output
[08:57] <apw> doko, looking at the diff it looks more like a backport of yakkety's version, but whatever you normally do, do indeed
[08:57] <doko> apw, yeah, the no-pie is a no-op for xenial, anyway, fixing the version ...
[09:11] <doko> apw, fixed
[11:01] <flexiondotorg> An Ubuntu MATE rebuild request is stuck in that state.
[11:01] <flexiondotorg> Seems to be caused by a failed sync lock request.
[11:02] <flexiondotorg> http://people.canonical.com/~ubuntu-archive/cd-build-logs/ubuntu-mate/yakkety/daily-live-20160624.log
[12:50] <cjwatson> bdmurray: can you have a look at the dpkg/trusty crash rate increase?  I don't *think* it can possibly be related to my SRU, but I can't see the crash reports (errors.ubuntu.com says "Sorry, you are not a member of a group that is allowed to see the data from error reports" which has got to be nonsense)
[15:18] <apw> ^ clashing upload of dkms
[17:40] <jbicha> hi, nacc and I would like to upgrade the drupal7 xenial proposed sru to that one ^
[18:15] <cjwatson> bdmurray: thanks for giving me access.  So I think this must be https://errors.ubuntu.com/oops/2d0a3dda-39a8-11e6-ba18-fa163eec78fa, but I don't think that can be related to the update as if it were I'd have seen it when upgrading the package to do QA; it's probably just somebody with a slightly broken perl installation for some reason.  Could you override this?
[18:20] <slangasek> hmm so apparently nusakan's archive sync lock doesn't do well in the face of a system reboot?
[19:17] <infinity> slangasek: Oh, did that asplode?
[19:18] <slangasek> seems so
[19:18] <slangasek> lock cleared now
[19:19] <infinity> slangasek: PS: I'm home.
[19:24] <yofel> could someone please review kinit in xenial-proposed? It's a CVE fix
[19:24] <yofel> * in unapproved
[22:06] <infinity> yofel: If it's a security fix, it should go through the security team, not the SRU queue.
[22:06] <infinity> mdeslaur: ^
[22:08] <yofel> even for universe components?
[22:08] <infinity> yofel: Yes.  We still want security updates to be in the security pocket.
[22:08] <yofel> ok
[22:08] <infinity> yofel: The Canonical security team is happy to usher community security updates through their process.
[22:09] <infinity> sbeattie: Around still? ^
[22:12] <sbeattie> infinity, yofel: I am
[22:13] <sbeattie> yofel: is there a bug report? Happy to sponser a security update.
[22:14] <infinity> LP: #1595507
[22:15] <infinity> sbeattie: There's a rejected upload in https://launchpad.net/ubuntu/xenial/+queue?queue_state=4&queue_text= if you can read that.
[22:15] <sbeattie> infinity: I can, thanks