[00:05] -queuebot:#ubuntu-release- New binary: paxrat [amd64] (zesty-proposed/universe) [1.0-2] (no packageset)
[00:05] -queuebot:#ubuntu-release- New binary: paxrat [i386] (zesty-proposed/universe) [1.0-2] (no packageset)
[00:11] -queuebot:#ubuntu-release- New binary: libica [s390x] (zesty-proposed/universe) [3.0.1-1] (no packageset)
[00:32] -queuebot:#ubuntu-release- Unapproved: squirrelmail (yakkety-proposed/universe) [2:1.4.23~svn20120406-2ubuntu1 => 2:1.4.23~svn20120406-2ubuntu1.16.10.1] (no packageset)
[00:33] -queuebot:#ubuntu-release- Unapproved: squirrelmail (xenial-proposed/universe) [2:1.4.23~svn20120406-2ubuntu1 => 2:1.4.23~svn20120406-2ubuntu1.16.04.1] (no packageset)
[00:48] -queuebot:#ubuntu-release- Unapproved: php7.0 (yakkety-proposed/main) [7.0.8-3ubuntu3 => 7.0.13-0ubuntu0.16.10.1] (kubuntu, ubuntu-desktop, ubuntu-server)
[00:51] -queuebot:#ubuntu-release- Unapproved: php7.0 (xenial-proposed/main) [7.0.8-0ubuntu0.16.04.3 => 7.0.13-0ubuntu0.16.04.1] (kubuntu, ubuntu-desktop, ubuntu-server)
[01:11] -queuebot:#ubuntu-release- Unapproved: cloud-initramfs-tools (xenial-proposed/main) [0.27ubuntu1.2 => 0.27ubuntu1.3] (edubuntu, ubuntu-server)
[01:13] <smoser> can someone NACK that ^ please ?
[01:13] <smoser> i missed a changelog entry
[01:13] <smoser> stgraber, ? slangasek ?
[01:16] <rbasak> smoser: done
[01:16] <smoser> thanks!
[01:17] -queuebot:#ubuntu-release- Unapproved: rejected cloud-initramfs-tools [source] (xenial-proposed) [0.27ubuntu1.3]
[01:24] -queuebot:#ubuntu-release- Unapproved: cloud-initramfs-tools (yakkety-proposed/main) [0.30ubuntu1 => 0.30ubuntu1.1] (edubuntu, ubuntu-server)
[01:27] <smoser> :-(. and nack ^ one too ?
[01:27] <smoser> stupid changelog messages again
[01:28] -queuebot:#ubuntu-release- Unapproved: rejected cloud-initramfs-tools [source] (yakkety-proposed) [0.30ubuntu1.1]
[01:28] -queuebot:#ubuntu-release- Unapproved: cloud-initramfs-tools (xenial-proposed/main) [0.27ubuntu1.2 => 0.27ubuntu1.3] (edubuntu, ubuntu-server)
[01:29] -queuebot:#ubuntu-release- Unapproved: cloud-initramfs-tools (yakkety-proposed/main) [0.30ubuntu1 => 0.30ubuntu1.1] (edubuntu, ubuntu-server)
[01:37] <smoser> bah.
[01:37] <smoser> this really stinks. but changelog for xenial *still* incomplete
[01:37] <smoser> please nack the one currently in the queue
[01:40] <slangasek> smoser: done
[01:41] <smoser> thank you.
[01:41] -queuebot:#ubuntu-release- Unapproved: rejected cloud-initramfs-tools [source] (xenial-proposed) [0.27ubuntu1.3]
[01:43] -queuebot:#ubuntu-release- Unapproved: cloud-initramfs-tools (xenial-proposed/main) [0.27ubuntu1.2 => 0.27ubuntu1.3] (edubuntu, ubuntu-server)
[02:00] -queuebot:#ubuntu-release- Unapproved: hexchat (yakkety-proposed/universe) [2.12.0-2ubuntu2 => 2.12.0-2ubuntu2.1] (no packageset)
[02:33] -queuebot:#ubuntu-release- Unapproved: opencc (yakkety-proposed/universe) [1.0.4-1 => 1.0.4-1ubuntu0.16.10.1] (input-methods, kubuntu, ubuntu-desktop)
[03:36] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (trusty-proposed/main) [3.13.0-103.150] (core, kernel)
[03:37] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (xenial-proposed/main) [4.4.0-51.72] (core, kernel)
[09:31] <JerryKao> rbasak, ping
[09:50] <JerryKao> bdmurray, ping
[10:02] <JerryKao> tjaalton, ping
[10:13] <tjaalton> JerryKao: pong
[10:17] <JerryKao> tjaalton, hi, https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1642662 is verified. could you help to publish?
[10:17] <ubot5`> Ubuntu bug 1642662 in HWE Next "SRU request: handle EGL alternatives and use different drivers for the LTS stacks" [Critical,In progress]
[10:26] <tjaalton> JerryKao: sure, after lunch
[10:26] <JerryKao> tjaalton, thanks!!
[10:34] <Laney> xnox: can you confim that the dist-upgrader tarballs are signed with the old archive key?
[11:04] -queuebot:#ubuntu-release- New: accepted imagemagick [amd64] (zesty-proposed) [8:6.9.6.6+dfsg-1ubuntu1]
[11:04] -queuebot:#ubuntu-release- New: accepted imagemagick [armhf] (zesty-proposed) [8:6.9.6.6+dfsg-1ubuntu1]
[11:04] -queuebot:#ubuntu-release- New: accepted imagemagick [powerpc] (zesty-proposed) [8:6.9.6.6+dfsg-1ubuntu1]
[11:04] -queuebot:#ubuntu-release- New: accepted imagemagick [s390x] (zesty-proposed) [8:6.9.6.6+dfsg-1ubuntu1]
[11:04] -queuebot:#ubuntu-release- New: accepted imagemagick [arm64] (zesty-proposed) [8:6.9.6.6+dfsg-1ubuntu1]
[11:04] -queuebot:#ubuntu-release- New: accepted imagemagick [ppc64el] (zesty-proposed) [8:6.9.6.6+dfsg-1ubuntu1]
[11:04] -queuebot:#ubuntu-release- New: accepted imagemagick [i386] (zesty-proposed) [8:6.9.6.6+dfsg-1ubuntu1]
[11:05] -queuebot:#ubuntu-release- New: accepted ubuntu-budgie-meta [amd64] (zesty-proposed) [0.0.1]
[11:05] -queuebot:#ubuntu-release- New: accepted ubuntu-budgie-meta [armhf] (zesty-proposed) [0.0.1]
[11:05] -queuebot:#ubuntu-release- New: accepted ubuntu-budgie-meta [powerpc] (zesty-proposed) [0.0.1]
[11:05] -queuebot:#ubuntu-release- New: accepted ubuntu-budgie-meta [arm64] (zesty-proposed) [0.0.1]
[11:05] -queuebot:#ubuntu-release- New: accepted ubuntu-budgie-meta [ppc64el] (zesty-proposed) [0.0.1]
[11:05] -queuebot:#ubuntu-release- New: accepted ubuntu-budgie-meta [i386] (zesty-proposed) [0.0.1]
[11:08] -queuebot:#ubuntu-release- New: accepted linux [amd64] (zesty-proposed) [4.9.0-3.4]
[11:08] -queuebot:#ubuntu-release- New: accepted linux [armhf] (zesty-proposed) [4.9.0-3.4]
[11:08] -queuebot:#ubuntu-release- New: accepted linux [powerpc] (zesty-proposed) [4.9.0-3.4]
[11:08] -queuebot:#ubuntu-release- New: accepted linux [s390x] (zesty-proposed) [4.9.0-3.4]
[11:08] -queuebot:#ubuntu-release- New: accepted linux [arm64] (zesty-proposed) [4.9.0-3.4]
[11:08] -queuebot:#ubuntu-release- New: accepted linux [ppc64el] (zesty-proposed) [4.9.0-3.4]
[11:08] -queuebot:#ubuntu-release- New: accepted linux [i386] (zesty-proposed) [4.9.0-3.4]
[11:08] -queuebot:#ubuntu-release- New: accepted opencc [amd64] (zesty-proposed) [1.0.4-2]
[11:08] -queuebot:#ubuntu-release- New: accepted ppl [arm64] (zesty-proposed) [1:1.2-1]
[11:08] -queuebot:#ubuntu-release- New: accepted ppl [i386] (zesty-proposed) [1:1.2-1]
[11:08] -queuebot:#ubuntu-release- New: accepted ppl [ppc64el] (zesty-proposed) [1:1.2-1]
[11:08] -queuebot:#ubuntu-release- New: accepted ppl [amd64] (zesty-proposed) [1:1.2-1]
[11:08] -queuebot:#ubuntu-release- New: accepted ppl [powerpc] (zesty-proposed) [1:1.2-1]
[11:08] -queuebot:#ubuntu-release- New: accepted ppl [armhf] (zesty-proposed) [1:1.2-1]
[11:08] -queuebot:#ubuntu-release- New: accepted ppl [s390x] (zesty-proposed) [1:1.2-1]
[11:09] -queuebot:#ubuntu-release- New: accepted paxrat [amd64] (zesty-proposed) [1.0-2]
[11:09] -queuebot:#ubuntu-release- New: accepted paxrat [armhf] (zesty-proposed) [1.0-2]
[11:09] -queuebot:#ubuntu-release- New: accepted paxrat [powerpc] (zesty-proposed) [1.0-2]
[11:09] -queuebot:#ubuntu-release- New: accepted paxrat [s390x] (zesty-proposed) [1.0-2]
[11:09] -queuebot:#ubuntu-release- New: accepted paxrat [arm64] (zesty-proposed) [1.0-2]
[11:09] -queuebot:#ubuntu-release- New: accepted paxrat [ppc64el] (zesty-proposed) [1.0-2]
[11:09] -queuebot:#ubuntu-release- New: accepted paxrat [i386] (zesty-proposed) [1.0-2]
[11:10] -queuebot:#ubuntu-release- New: accepted libica [s390x] (zesty-proposed) [3.0.1-1]
[11:12] <Odd_Bloke> Could someone reject gce-compute-image-packages from xenial, please?
[11:30] <tjaalton> Odd_Bloke: I don't see it on the queue
[11:31] <Odd_Bloke> tjaalton: It's new, if that makes a difference?
[11:33] <tjaalton> ah
[11:33] <tjaalton> what's the reason to reject?
[11:45] <Odd_Bloke> It's missing a xenial-specific change.
[11:45] <Odd_Bloke> (tjaalton: ^)
[11:46] -queuebot:#ubuntu-release- New binary: qgis [ppc64el] (zesty-proposed/universe) [2.14.9+dfsg-1] (no packageset)
[11:51] <tjaalton> Odd_Bloke: huh?
[11:51] <tjaalton> you mean it's incomplete?
[11:52] <Odd_Bloke> tjaalton: Yeah, it will Replace an existing package which we don't want except on upgrade to later-than-xenial.
[11:52] <tjaalton> ok, done
[11:53] -queuebot:#ubuntu-release- New: rejected gce-compute-image-packages [source] (xenial-proposed) [20160930-0ubuntu3~16.04.0]
[11:56] <Odd_Bloke> tjaalton: Thanks. :)
[11:58] -queuebot:#ubuntu-release- New binary: python-distro [amd64] (zesty-proposed/universe) [1.0.1-1] (no packageset)
[12:03] -queuebot:#ubuntu-release- New binary: qgis [s390x] (zesty-proposed/universe) [2.14.9+dfsg-1] (no packageset)
[12:06] -queuebot:#ubuntu-release- New binary: qgis [powerpc] (zesty-proposed/universe) [2.14.9+dfsg-1] (no packageset)
[12:07] -queuebot:#ubuntu-release- New: accepted python-distro [amd64] (zesty-proposed) [1.0.1-1]
[12:25] -queuebot:#ubuntu-release- New binary: qgis [armhf] (zesty-proposed/universe) [2.14.9+dfsg-1] (no packageset)
[12:29] -queuebot:#ubuntu-release- New binary: qgis [arm64] (zesty-proposed/universe) [2.14.9+dfsg-1] (no packageset)
[12:29] -queuebot:#ubuntu-release- New binary: qgis [i386] (zesty-proposed/universe) [2.14.9+dfsg-1] (no packageset)
[12:31] -queuebot:#ubuntu-release- Unapproved: zeromq3 (yakkety-proposed/main) [4.1.5+git20160811+2fc86bc-0ubuntu2 => 4.2.0-2ubuntu0.16.10] (kubuntu)
[12:37] -queuebot:#ubuntu-release- New binary: qgis [amd64] (zesty-proposed/universe) [2.14.9+dfsg-1] (no packageset)
[12:39] -queuebot:#ubuntu-release- New: accepted qgis [amd64] (zesty-proposed) [2.14.9+dfsg-1]
[12:39] -queuebot:#ubuntu-release- New: accepted qgis [armhf] (zesty-proposed) [2.14.9+dfsg-1]
[12:39] -queuebot:#ubuntu-release- New: accepted qgis [powerpc] (zesty-proposed) [2.14.9+dfsg-1]
[12:39] -queuebot:#ubuntu-release- New: accepted qgis [s390x] (zesty-proposed) [2.14.9+dfsg-1]
[12:39] -queuebot:#ubuntu-release- New: accepted qgis [arm64] (zesty-proposed) [2.14.9+dfsg-1]
[12:39] -queuebot:#ubuntu-release- New: accepted qgis [ppc64el] (zesty-proposed) [2.14.9+dfsg-1]
[12:39] -queuebot:#ubuntu-release- New: accepted qgis [i386] (zesty-proposed) [2.14.9+dfsg-1]
[12:54] <xnox> Laney, they are, there is in progress branch to get them to be signed with the new key.
[12:54] <xnox> let me find that.
[12:58] <Laney> xnox: found it
[12:58] <Laney> just noticed because it breaks ubuntu-release-upgrader tests
[12:59] <Laney> and of course because apt-key can't verify it now
[12:59] <xnox> Laney, once that branch lands everything will be fine again.
[13:00] <xnox> and once we resign things.
[13:00] <Laney> i'm sure they will
[13:00] <Laney> broken right now though
[13:04] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (zesty-proposed/main) [4.9.0-3.4] (core, kernel)
[14:35] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (xenial-proposed) [4.4.0-51.72]
[14:35] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (trusty-proposed) [3.13.0-103.150]
[15:16] <rbasak> tjaalton: are you done with SRUs for today? I was going to look at python-django in Trusty for ScottK.
[15:17] <tjaalton> rbasak: yeah, I just handled these
[15:18] <tjaalton> *those, three packages
[15:20] <lamont> any chance someone could let cloud-init and cloud-initramfs into {x,y}-proposed?
[15:20] <lamont> cloud-init/xenial is already in, fwiw
[15:20] <lamont> that will let me test them.
[15:30] <Trevinho> Hey, can anyone unblock https://bileto.ubuntu.com/#/ticket/2192 from SRU waiting queue?
[15:43] <slangasek> Trevinho: only bug #1635625 appears to have the SRU info in its bug description; can you please fix up the others?
[15:43] <ubot5`> bug 1635625 in unity (Ubuntu) "Some indicator icons are missing after unlocking the screen" [High,Fix released] https://launchpad.net/bugs/1635625
[15:44] <Trevinho> slangasek: ah, sorry... I thought they all were fixed... andyrock, can you take care of that please ^
[15:44] <slangasek> Trevinho: maybe it's just the standard headers that are missing, since several of these look like they might have test case / regression potential analysis under other names; but using the standard headers would help with clarity
[15:44] <andyrock> oki
[15:48] <Trevinho> slangasek: yeah, that's the thing in fact... I remember we discussed that very topic.
[15:49] <andyrock> slangasek Trevinho should be ok now
[15:50] <Trevinho> thanks andyrock
[16:11] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (xenial-proposed) [2.17.1ubuntu1]
[17:09] -queuebot:#ubuntu-release- New source: gce-compute-image-packages (xenial-proposed/primary) [20160930-0ubuntu3~16.04.0]
[17:09] <Odd_Bloke> RAOF: If you have time today, getting ^ accepted would be good. :)
[17:26] -queuebot:#ubuntu-release- New binary: linux-signed-lts-xenial [amd64] (trusty-proposed/main) [4.4.0-51.72~14.04.1] (kernel)
[17:28] -queuebot:#ubuntu-release- New binary: linux-signed-lts-trusty [amd64] (precise-proposed/main) [3.13.0-103.150~precise1] (kernel)
[17:29]  * rbasak reviews python-django in the trusty queue
[17:30] <rbasak> RAOF: ^
[17:41] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (zesty-proposed) [4.9.0-3.4]
[18:04] <xnox> google-perftools appears to be stuck waiting on juju-mongodb3.2 amd64 test results, which does not appear anywhere yet is "test in progress"
[18:04] <xnox> i've tried to trigger that test with: https://autopkgtest.ubuntu.com/request.cgi?release=zesty&arch=amd64&package=juju-mongodb3.2&trigger=google-perftools%2F2.5-0ubuntu3
[18:04] <xnox> but that fails with "A server error occurred.  Please contact the administrator."
[18:04] <xnox> what can I do to unstuck it?
[18:10] -queuebot:#ubuntu-release- Unapproved: keepalived (yakkety-proposed/main) [1:1.2.23-1 => 1:1.2.23-1ubuntu0.1] (ubuntu-server)
[18:15] <nacc> can someone reject the above? i need to adjust the backported patch
[18:15] <nacc> (keepalived in y-p)
[18:18] <nacc> or am I able to do that myself as a core-dev?
[18:18] -queuebot:#ubuntu-release- New: accepted transcode [source] (yakkety-proposed) [3:1.1.7-9ubuntu0.1]
[18:19] <infinity> nacc: Yes I can, and no you can't.
[18:19] <nacc> infinity: thanks :)
[18:20] <infinity> xnox: The retriggering CGI WFM.
[18:20] -queuebot:#ubuntu-release- Unapproved: rejected keepalived [source] (yakkety-proposed) [1:1.2.23-1ubuntu0.1]
[18:22] -queuebot:#ubuntu-release- New binary: transcode [ppc64el] (yakkety-proposed/none) [3:1.1.7-9ubuntu0.1] (mythbuntu, ubuntustudio)
[18:22] <nacc> infinity: thank you!
[18:23] -queuebot:#ubuntu-release- Unapproved: apport (xenial-proposed/main) [2.20.1-0ubuntu2.1 => 2.20.1-0ubuntu2.2] (core)
[18:24] -queuebot:#ubuntu-release- New binary: transcode [s390x] (yakkety-proposed/none) [3:1.1.7-9ubuntu0.1] (mythbuntu, ubuntustudio)
[18:25] -queuebot:#ubuntu-release- New binary: transcode [i386] (yakkety-proposed/none) [3:1.1.7-9ubuntu0.1] (mythbuntu, ubuntustudio)
[18:26] -queuebot:#ubuntu-release- Unapproved: keepalived (yakkety-proposed/main) [1:1.2.23-1 => 1:1.2.23-1ubuntu0.1] (ubuntu-server)
[18:28] -queuebot:#ubuntu-release- New binary: transcode [amd64] (yakkety-proposed/multiverse) [3:1.1.7-9ubuntu0.1] (mythbuntu, ubuntustudio)
[18:36] -queuebot:#ubuntu-release- New binary: transcode [arm64] (yakkety-proposed/multiverse) [3:1.1.7-9ubuntu0.1] (mythbuntu, ubuntustudio)
[18:36] -queuebot:#ubuntu-release- New binary: transcode [armhf] (yakkety-proposed/multiverse) [3:1.1.7-9ubuntu0.1] (mythbuntu, ubuntustudio)
[18:39] -queuebot:#ubuntu-release- Unapproved: keepalived (xenial-proposed/main) [1:1.2.19-1 => 1:1.2.19-1ubuntu0.1] (ubuntu-server)
[18:41] -queuebot:#ubuntu-release- Unapproved: rejected apport [source] (xenial-proposed) [2.20.1-0ubuntu2.2]
[18:41] -queuebot:#ubuntu-release- Unapproved: apport (xenial-proposed/main) [2.20.1-0ubuntu2.1 => 2.20.1-0ubuntu2.2] (core)
[19:11] -queuebot:#ubuntu-release- Unapproved: init-system-helpers (xenial-proposed/main) [1.29ubuntu3 => 1.29ubuntu4] (core)
[19:29] <bdmurray> given that https://code.launchpad.net/~xnox/ubuntu-archive-publishing/migrate-dist-upgrade-to-4k/+merge/311181 was merged how can we get the dist-upgrade tarballs resigned?
[19:38] <bdmurray> slangasek, infinity: ^^
[19:38] <slangasek> bdmurray: I'm assuming you don't want to trigger a new one, right?
[19:40] <slangasek> if not then I imagine I'll need to dig around on pepo to re-sign manually
[19:40] <bdmurray> slangasek: Does trigger mean upload another version? If that's what needs to happen that's fine.
[19:40] <slangasek> bdmurray: you could do it that way, yes
[19:40] <slangasek> for each release
[19:41] <slangasek> and I guess that would also let us validate it in -proposed before pushing it to -updates
[19:41] <slangasek> which is good
[19:42] <bdmurray> okay
[20:08] <slangasek> andyrock, Trevinho: I am allowing this SRU through, but for the record, the "regression potential" sections are not properly filled out on several of these bugs.  "regression potential" is for describing the potential risk of regression from this SRU, not restating the impact of the bug.
[20:09] -queuebot:#ubuntu-release- Unapproved: accepted unity [sync] (yakkety-proposed) [7.5.0+16.10.20161112-0ubuntu1]
[20:39] <nacc> i take it the perl5 and glibc updates are hammering the zesty queue?
[20:48] -queuebot:#ubuntu-release- New binary: transcode [powerpc] (yakkety-proposed/multiverse) [3:1.1.7-9ubuntu0.1] (mythbuntu, ubuntustudio)
[20:51] -queuebot:#ubuntu-release- Unapproved: isc-dhcp (xenial-proposed/main) [4.3.3-5ubuntu12.4 => 4.3.3-5ubuntu12.5] (core)
[20:51] -queuebot:#ubuntu-release- Unapproved: isc-dhcp (yakkety-proposed/main) [4.3.3-5ubuntu15.1 => 4.3.3-5ubuntu15.2] (core)
[21:05] -queuebot:#ubuntu-release- Unapproved: initramfs-tools (xenial-proposed/main) [0.122ubuntu8.5 => 0.122ubuntu8.6] (core)
[21:08] -queuebot:#ubuntu-release- Unapproved: initramfs-tools (yakkety-proposed/main) [0.125ubuntu6.1 => 0.125ubuntu6.2] (core)
[21:13] <lamont> who is my favorite archive-admin on the SRU hook for the day?
[21:14] -queuebot:#ubuntu-release- Unapproved: software-properties (xenial-proposed/main) [0.96.20.4 => 0.96.20.5] (desktop-core, ubuntu-server)
[21:14] <lamont> rbasak: is it you?
[21:16]  * lamont needs to get the following into xenial-proposed and yakkety-proposed, so that they can be fix-verified: cloud-init cloud-initramfs-tools initramfs-tools isc-dhcp
[21:16] <lamont> it would seem that cloud-init/xenial is already landed
[21:17] <lamont> yep
[21:27] <infinity> bdmurray, slangasek: Well, "landed" isn't landed until someone pulls on pepo (which I did).
[21:27] <infinity> (just now)
[21:30] <infinity> slangasek: As for verification that it's doing the right thing, given that none of this will trigger without new uploads (or fiddling), I'd suggest we might actually want to rm *.gpg on the upgrade tarballs to force resigning and verify it's working correctly *now* rather than leaving a ticking timebomb to debug when someone uploads trusty or precise in three months and it breaks.
[21:31] <infinity> Oh, you suggested brian upload for *every* release, that would do it too.
[21:35] <rbasak> lamont: I'm tomorrow.
[21:35] <lamont> yeah.  RAOF is today, I see from the wiki that I got faceslapped with.
[21:37] <bdmurray> infinity: every release includes P and T?
[21:38] <lamont> rbasak: however, since I expect you'll ask/grumble at me about it, isc-dhcp... I'm thinking it'll be easier to verify the currently pending SRU by overwriting it, since I don't really have any way to verify it without the other pieces..
[21:38] <infinity> bdmurray: Every release would include everything we still publish and support.  So, either you can upload all of 'em, or I can force them all the be re-signed in-place on ftpmaster, but my point is that we want them all re-signed one way or the other so we can verify we didn't break them in the process.
[21:39] <infinity> bdmurray: Because in N months, when an innocent SRU is broken by this, we'll be far enough detached from it that someone will go wild-goose-hunting to figure out WTF broke.
[21:54] <slangasek> infinity, bdmurray: so what about copying into -proposed directories, resigning there for testing?
[21:54] <infinity> slangasek: pocket copy *-updates to *-proposed, the rm *-proposed/dist-upgrade/*gpg, and check results?
[21:54] <infinity> slangasek: Seems reasonable.
[21:55] -queuebot:#ubuntu-release- New binary: lxde-common [amd64] (zesty-proposed/universe) [0.99.2-2] (no packageset)
[21:55] <slangasek> infinity: yah (does the pocket copy cover the dist-upgrade bits?)
[21:55] <infinity> slangasek: If it didn't, we'd never have them in updates.
[21:56] <slangasek> ok!
[21:57] <infinity> Oh, that said, dist-upgrader-all, being custom whee, never gets *removed* from proposed.
[21:57] <infinity> So, we could just re-sign proposed right now.
[21:57] <infinity> And have someone verify they all look sane.
[21:57] <infinity> Then re-sign updates.
[21:57] <bdmurray> I'll do the verification but already uploaded zesty fwiw.
[21:58] <infinity> See: http://archive.ubuntu.com/ubuntu/dists/yakkety-proposed/main/dist-upgrader-all/
[21:58] <infinity> Versus: http://archive.ubuntu.com/ubuntu/dists/yakkety-updates/main/dist-upgrader-all/
[21:58] <infinity> bdmurray: Sure, no big deal on zesty, but no point in a round of no change SRUs to verify just to check sigs.
[22:01] <infinity> bdmurray, slangasek: http://paste.ubuntu.com/23555294/
[22:01] -queuebot:#ubuntu-release- New: accepted linux-signed-lts-trusty [amd64] (precise-proposed) [3.13.0-103.150~precise1]
[22:01] -queuebot:#ubuntu-release- New: accepted linux-signed-lts-xenial [amd64] (trusty-proposed) [4.4.0-51.72~14.04.1]
[22:01] <infinity> bdmurray, slangasek: That's what I propose deleting, letting LP regenerate, someone verifying they all seem to be what we think they should be and that dist-upgrade from $previous-release doesn't hate them, then I can do the same for s/proposed/updates/ ... Seem sane?
[22:02] <infinity> (Or just cp them from proposed to updates, cause having differing sigs might be weird, but *shrug*)
[22:03] <bdmurray> infinity: how long will the regeneration take?
[22:04] <infinity> Oh, I might do zesty too.  Since I think your upload beat my bzr pull.
[22:04] <infinity> bdmurray: A publisher cycle.
[22:04] <infinity> bdmurray: So, less than half an hour, more than 2 minutes.
[22:04] <infinity> Actually, pretty quick if I'm quick.
[22:05] <bdmurray> infinity: okay
[22:06] <infinity> bdmurray: Alright, all deleted from dists.in-progress (a publisher run was under way, I'm being sneaky) should re-gen in a few minutes, push to mirrors a bit later, blah blah.
[22:07] <barry> is it just me or have we not seen any debian imports for zesty in a while?
[22:09] <infinity> barry: Logs at http://people.canonical.com/~ubuntu-archive/auto-sync/ disagree.
[22:11] <barry> infinity: yeah okay
[22:18] <infinity> Oh, well, that's confusing and annoying.
[22:19] <infinity> These signature changes might never make it to mirrors anyway. :P
[22:20] <infinity> We touch --reference foo.gpg to foo's timestamp, so any mirror that uses timestamp and filesize to determine the rsync list (ie: pretty much all of them) won't ever see updated files.
[22:21] <infinity> bdmurray, slangasek: ^-- Based on that, it may be that the only way to reliably verify (and more importantly, push) this change is, indeed, no-change uploads.
[22:23] <infinity> Because even if someone out there attempts to mirror by hash, I imagine IS blocks that server-side to prevent one bad actor from crippling our infra.
[22:25] <infinity> Other option is, I guess, for me to touch those all to a different time, wait a day for tertiary mirrors to pick up the change, then touch 'em back.
[22:25] <infinity> But ew.
[22:37] <bdmurray> infinity: would it be worth testing your change then doing a no-change upload?
[22:37] <infinity> bdmurray: Good luck testing it.
[22:38] <infinity> bdmurray: Mirrors won't see the change, they'll have the old sigs.
[22:39] <infinity> bdmurray: And everything that isn't ftpmaster is a mirror.  Soo....
[22:44] <bdmurray> infinity: okay, I'll start with yakkety I guess
[23:01] -queuebot:#ubuntu-release- Unapproved: accepted initramfs-tools [source] (xenial-proposed) [0.122ubuntu8.6]
[23:01] -queuebot:#ubuntu-release- Unapproved: accepted isc-dhcp [source] (xenial-proposed) [4.3.3-5ubuntu12.5]
[23:03] <lamont> RAOF: please reject isc-dhcp 4.3.3-5ubuntu15.2 from yakkety-proposed queue, and I'll reupload
[23:04] <RAOF> lamont: Done.
[23:05] <lamont> gpg: checking the trustdb
[23:05] <lamont> sigh
[23:05] -queuebot:#ubuntu-release- Unapproved: rejected isc-dhcp [source] (yakkety-proposed) [4.3.3-5ubuntu15.2]
[23:05] <RAOF> Oh, wow. cloud-initramfs-tools fixes *all the bugs*
[23:06] <lamont> it has a "all the shiny" exception on SRUs
[23:09] -queuebot:#ubuntu-release- New: accepted transcode [amd64] (yakkety-proposed) [3:1.1.7-9ubuntu0.1]
[23:09] -queuebot:#ubuntu-release- New: accepted transcode [armhf] (yakkety-proposed) [3:1.1.7-9ubuntu0.1]
[23:09] -queuebot:#ubuntu-release- New: accepted transcode [powerpc] (yakkety-proposed) [3:1.1.7-9ubuntu0.1]
[23:09] -queuebot:#ubuntu-release- New: accepted transcode [s390x] (yakkety-proposed) [3:1.1.7-9ubuntu0.1]
[23:09] -queuebot:#ubuntu-release- New: accepted transcode [arm64] (yakkety-proposed) [3:1.1.7-9ubuntu0.1]
[23:09] -queuebot:#ubuntu-release- New: accepted transcode [ppc64el] (yakkety-proposed) [3:1.1.7-9ubuntu0.1]
[23:09] -queuebot:#ubuntu-release- New: accepted transcode [i386] (yakkety-proposed) [3:1.1.7-9ubuntu0.1]
[23:09] <RAOF> Eh, I'm happy to accept SRUs that fix bugs :)
[23:10] <lamont> uploaded
[23:11] -queuebot:#ubuntu-release- Unapproved: isc-dhcp (yakkety-proposed/main) [4.3.3-5ubuntu15.1 => 4.3.3-5ubuntu15.2] (core)
[23:12] -queuebot:#ubuntu-release- Unapproved: accepted cloud-initramfs-tools [source] (xenial-proposed) [0.27ubuntu1.3]
[23:17] <RAOF> Whelp, sorry. Same applies to yakkety initramfs-tools?
[23:17] <RAOF> lamont: ^
[23:17] <lamont> so it would seem.  grabbing the bits now
[23:19] <lamont> fetched.  reject pls?
[23:19] <RAOF> Done.
[23:19] <RAOF> queuebot will notice soon :)
[23:19] -queuebot:#ubuntu-release- Unapproved: rejected initramfs-tools [source] (yakkety-proposed) [0.125ubuntu6.2]
[23:20] <lamont> and upload complete
[23:20] -queuebot:#ubuntu-release- Unapproved: initramfs-tools (yakkety-proposed/main) [0.125ubuntu6.1 => 0.125ubuntu6.2] (core)
[23:23] <lamont> RAOF: sometime next week, I'll get the SRU template into the freeipmi packge in x-p.  because of sigh.
[23:23] <lamont> actually, let me see if next week is today
[23:23] <RAOF> Heh.
[23:24] -queuebot:#ubuntu-release- Unapproved: ubuntu-release-upgrader (yakkety-proposed/main) [1:16.10.8 => 1:16.10.9] (core)
[23:26] <bdmurray> slangasek, infinity: u-r-u in the yakkety queue
[23:27] -queuebot:#ubuntu-release- Unapproved: accepted initramfs-tools [source] (yakkety-proposed) [0.125ubuntu6.2]
[23:27] -queuebot:#ubuntu-release- Unapproved: accepted isc-dhcp [source] (yakkety-proposed) [4.3.3-5ubuntu15.2]
[23:30] <lamont> RAOF: is your plan to let the first two publish, and then add the other two?
[23:30] <lamont> RAOF: and then I have a different question for you on freeipmi/xenial-proposed
[23:31] <RAOF> lamont: I was not planning on doing that, unless you think that there are sufficient people running from -proposed who will be broken if they update in the window where netboot breaks.
[23:31] <lamont> I'm good with not waiting
[23:31] <lamont> if they all land reasonably close, then all is well.
[23:32] <lamont> esp if they all land together
[23:33] <lamont> https://launchpad.net/ubuntu/+source/freeipmi/1.4.11-1.1ubuntu2 <-- RAOF you'll notice from that, and the craptastic changelong in the xenial-proposed upload that the upload does not, in fact, completely address bug 1618543.  it is however, sufficient to address some operational concerns (with the fix, we can control power over ipv6 ipmi, but cannot discover the ipv6 address of the bmc, hence
[23:33] <ubot5`> bug 1618543 in MAAS "freeipmi lacks IPv6 support" [Critical,Triaged] https://launchpad.net/bugs/1618543
[23:33] <lamont> "not done yet")
[23:33] <lamont> do you want that split into a separate bug?
[23:37] <lamont> actually, 5 blades.  I'm going to just do that.  Please reject freeipmi/xenial <-- RAOF
[23:37] <RAOF> lamont: If you plan to upload multiple times, it'd be nice to have a bug per upload. If you plan to wait before *all* IPv6 support lands, then.
[23:38] <RAOF> Oh, I missed the xenial-unapproved upload. Ooops. :)
[23:38] <RAOF> Whee! Cloud init also does all the things.
[23:39] -queuebot:#ubuntu-release- Unapproved: rejected freeipmi [source] (xenial-proposed) [1.4.11-1.1ubuntu2~0.16.04]
[23:40] <doko> bdmurray: fyi, accepted the transcode binary builds: ^^^
[23:41] -queuebot:#ubuntu-release- Unapproved: accepted cloud-init [source] (yakkety-proposed) [0.7.8-49-g9e904bb-0ubuntu1~16.10.1]
[23:48] -queuebot:#ubuntu-release- Unapproved: freeipmi (xenial-proposed/main) [1.4.11-1ubuntu1 => 1.4.11-1.1ubuntu2~0.16.04] (ubuntu-desktop, ubuntu-server)
[23:50] -queuebot:#ubuntu-release- Unapproved: accepted cloud-initramfs-tools [source] (yakkety-proposed) [0.30ubuntu1.1]
[23:51] -queuebot:#ubuntu-release- Unapproved: freeipmi (yakkety-proposed/main) [1.4.11-1ubuntu1 => 1.4.11-1.1ubuntu2~0.16.10] (ubuntu-desktop, ubuntu-server)
[23:51] <lamont> RAOF: please accept freeipmi into x and y
[23:51] <lamont> and then I think I'll be able to stop bugging you for at least the rest of the week!
[23:53] <lamont> the -1 vs -1.1 was basically a non-change for binNMU happiness and seemed safe to this uploader.
[23:56] <RAOF> And then I'll decamp to a café!
[23:56] <RAOF> Why isn't that spelt *imp*i? :(
[23:57] <lamont> it stands for "it pleases me immensely"
[23:58] <lamont> or somethign like that
[23:59] <RAOF> But they missed the opportunity to have ‘imp’ as a substring.