[00:13] -queuebot:#ubuntu-release- Unapproved: rejected tftp-hpa [source] (xenial-proposed) [5.2+20150808-1ubuntu1.16.04.1]
[00:13] -queuebot:#ubuntu-release- Unapproved: rejected tftp-hpa [source] (trusty-proposed) [5.2-7ubuntu3.1]
[00:13] -queuebot:#ubuntu-release- Unapproved: rejected tftp-hpa [source] (yakkety-proposed) [5.2+20150808-1ubuntu1.16.10.1]
[01:00] -queuebot:#ubuntu-release- New: accepted gcc-6-cross-ports [amd64] (zesty-proposed) [17ubuntu1]
[01:00] -queuebot:#ubuntu-release- New: accepted gcc-6-cross-ports [i386] (zesty-proposed) [17ubuntu1]
[01:00] -queuebot:#ubuntu-release- New: accepted pakcs [amd64] (zesty-proposed) [1.14.1-4]
[01:00] -queuebot:#ubuntu-release- New: accepted pakcs [armhf] (zesty-proposed) [1.14.1-4]
[01:00] -queuebot:#ubuntu-release- New: accepted pakcs [ppc64el] (zesty-proposed) [1.14.1-4]
[01:01] -queuebot:#ubuntu-release- New: accepted pakcs [arm64] (zesty-proposed) [1.14.1-4]
[01:01] -queuebot:#ubuntu-release- New: accepted pakcs [s390x] (zesty-proposed) [1.14.1-4]
[01:01] -queuebot:#ubuntu-release- New: accepted pakcs [i386] (zesty-proposed) [1.14.1-4]
[03:42] <wgrant> infinity: Is proposed-migration meant to not be triggering for zesty? It's been several hours. archive-reports logs reveal that component-mismatches is broken and the zesty(-proposed)-powerpc chdists need removing, but neither seems fatal given that p-m is still running OK for trusty/xenial/yakkety.
[03:58] -queuebot:#ubuntu-release- New binary: rustc [i386] (zesty-proposed/universe) [1.16.0+dfsg1-1~exp1ubuntu1] (no packageset)
[06:01] -queuebot:#ubuntu-release- New binary: rustc [amd64] (zesty-proposed/universe) [1.16.0+dfsg1-1~exp1ubuntu1] (no packageset)
[06:02] <infinity> wgrant: p-m for devel is a slightly different beast, it may well be not running due to other things in the pipe being broken.
[06:02] <infinity> wgrant: I'll look after I've eaten... Whatever meal this is.
[06:46] <wgrant> infinity: Hm, I thought the bit in a-r that triggered it looked pretty clear, but there are so many globals maybe I got lost
[07:01] <wgrant> Maybe it is just the obsolete chdists. component-mismatches' trigger condition is different, which I hadn't realised.
[07:13] <infinity> wgrant: Does that mean you figured it out while I was out fooding, or are you still stumped?
[07:13] <wgrant> infinity: It's hopefully kicking off now...
[07:14] <wgrant> infinity: Yeah, there we go.
[07:14] <wgrant> Just needed to remove the two obsolete chdists. No idea why that took six hours to break...
[07:15] <wgrant> Though component-mismatches will also need a fix.
[07:16] <infinity> I'm looking at u-a-t right now.
[07:16] <infinity> (including c-m)
[07:16] <wgrant> Yep
[07:16] <wgrant> Thanks.
[07:20] <infinity> Kay, done.
[14:14] -queuebot:#ubuntu-release- New binary: rustc [armhf] (zesty-proposed/universe) [1.16.0+dfsg1-1~exp1ubuntu1] (no packageset)
[16:20] -queuebot:#ubuntu-release- New binary: rustc [arm64] (zesty-proposed/universe) [1.16.0+dfsg1-1~exp1ubuntu1] (no packageset)