[00:18] <tsimonq2> nacc: *takes this here* so I've been told upload NOTHING during freezes (prospective MOTU :P), is it an exception if seeded-in-ubuntu doesn't find anything, or do I still just not upload?
[00:18] <teward> tsimonq2: FFe policies
[00:19] <tsimonq2> teward: Which I'm asking about.
[00:19] <teward> exceptions are security issues, bugfix-only, no version bumps.
[00:19] <teward> FFe process: https://wiki.ubuntu.com/FreezeExceptionProcess  |  FeatureFreeze details: https://wiki.ubuntu.com/FeatureFreeze
[00:19] <nacc> tsimonq2: it does depend on which freeze you mean
[00:19] <teward> tsimonq2: FeatureFreeze, it needs approval by the release team I think it is to 'accept new features for a package.
[00:20] <teward> final freeze is ***really*** really restrictive
[00:20] <teward> and usually nothing is touched then
[00:20] <tsimonq2> Confused after RTFMing: seeded-in-ubuntu - Determine whether a package is safe to upload during a freeze
[00:20] <teward> tsimonq2: depending on *which* freeze, depends on the true answer
[00:20] <teward> on Thurs, I think, we start FeatureFreeze
[00:20] <teward> and FFe policies go into effect
[00:20] <nacc> tsimonq2: yeah, i think that manpage probably needs an update too :)
[00:21] <teward> ^ this
[00:21] <teward> tsimonq2: #ubuntu-motu would also be a valid place to ask this, though it's far less active
[00:21] <tsimonq2> teward: Ok, yeah, I thought this seemed like a releasey question :P
[00:21] <teward> tsimonq2: well, true, but still
[00:22]  * teward is more concerned about Perl holding **everything** up
[00:38] -queuebot:#ubuntu-release- Unapproved: accepted flatpak [source] (yakkety-proposed) [0.8.2-1~ubuntu16.10.1]
[00:41] -queuebot:#ubuntu-release- Unapproved: accepted ostree [source] (yakkety-proposed) [2016.15-2ubuntu1~ubuntu16.10.1]
[00:48] -queuebot:#ubuntu-release- Unapproved: accepted gtk+3.0 [source] (xenial-proposed) [3.18.9-1ubuntu3.2]
[00:59] <jbicha> RAOF: are you willing to accept bubblewrap, ostree and flatpak as new packages into xenial too?
[01:01] <RAOF1> jbicha: I'm not able to do that, sorry. Need a fully-fledged AA to do NEW.
[01:04] <jbicha> who are the real AAs then? https://launchpad.net/~ubuntu-archive/+members
[01:07] <RAOF1> Both slangasek and infinity are real AAs and have been recently active :)
[01:08]  * RAOF1 really should get to fully-fledged AA.
[01:12] <slangasek> jbicha: what's the rationale for these as new SRUs in xenial?
[01:20] <jbicha> slangasek: it's basically the same rationale as snap in trusty: it's a way to get new apps on a stable release
[01:29] <jbicha> I'm trying to SRU chrome-gnome-shell too, for trusty and xenial bug 1652537
[01:33] <slangasek> jbicha: ok, but snapd is part of the core Ubuntu platform in xenial and later; providing consistency with that would seem to have a bit more value in an SRU than $arbitrary_app_store?
[01:35] <jbicha> slangasek: Ubuntu GNOME 17.04 includes flatpak now
[01:36] <slangasek> jbicha: and are there things you currently go through cumbersome SRUs of that you would propose to provide instead via flatpak?
[01:37] <mdeslaur> rbasak, nacc: thanks!
[01:37] <slangasek> SRUing of snapd into trusty is a win because it means we can reduce the number of process-heavy SRU exceptions
[01:38] <jbicha> The Flatpak maintainer asked if I could get flatpak into Ubuntu 16.04 LTS as they would like Flatpak 0.8 to be available in all LTS distros
[01:38] <jbicha> currently, they are recommending xenial users use a PPA to get flatpak: http://flatpak.org/getting.html
[01:43] <jbicha> honestly, I don't really use snap or flatpak; the target audience isn't someone who runs the Ubuntu development release
[01:43] <jbicha> many GNOME apps are available via flatpak but I don't think are in the snap store yet and obviously the latest stable GNOME is not going to be SRU'd to xenial
[01:48] <slangasek> jbicha: right.  I don't think I see any reason that this should be disallowed in xenial, but I also don't see any reason to prioritize it relative to SRUs of existing packages
[01:49] <jbicha> sure, I can wait
[01:50] <jbicha> I've been working on it since December but 2 bubblewrap security bugs had to be fixed in yakkety first
[01:50] <jbicha> how about chrome-gnome-shell, which should be in -updates before Firefox 52 gets there next month?
[01:53] <slangasek> jbicha: I don't understand, what's the relationship between those two things?
[01:58] <jbicha> because Firefox 52 drops support for browser plugins so this is the workaround
[01:58] <jbicha> the package name is unfortunate but it implement the chrome webextension api and was originally for chrome/chromium
[02:02] <slangasek> jbicha: so what existing functionality is this replacing that will regress when firefox 52 drops?
[02:04] <jbicha> does bug 1652537 answer your question?
[02:05] <slangasek> jbicha: got it, thanks
[02:22] <powersj>  /quit
[02:22] <powersj> woops :P
[06:12] <ginggs> apw: please check rev 2195 in your hints file, should be armhf ther instead of s390x
[06:26] <apw> ginggs, bah fixed
[06:27] <ginggs> apw: thanks
[07:55] -queuebot:#ubuntu-release- New binary: lorene [s390x] (zesty-proposed/universe) [0.0.0~cvs20161116+dfsg-1ubuntu1] (no packageset)
[08:08] -queuebot:#ubuntu-release- New binary: lorene [powerpc] (zesty-proposed/universe) [0.0.0~cvs20161116+dfsg-1ubuntu1] (no packageset)
[08:08] -queuebot:#ubuntu-release- New binary: lorene [ppc64el] (zesty-proposed/universe) [0.0.0~cvs20161116+dfsg-1ubuntu1] (no packageset)
[08:10] -queuebot:#ubuntu-release- New binary: lorene [amd64] (zesty-proposed/universe) [0.0.0~cvs20161116+dfsg-1ubuntu1] (no packageset)
[08:16] -queuebot:#ubuntu-release- New binary: lorene [i386] (zesty-proposed/universe) [0.0.0~cvs20161116+dfsg-1ubuntu1] (no packageset)
[08:26] -queuebot:#ubuntu-release- New: accepted python-scrapy-djangoitem [amd64] (zesty-proposed) [1.1.1-1]
[08:28] -queuebot:#ubuntu-release- New: accepted lorene [amd64] (zesty-proposed) [0.0.0~cvs20161116+dfsg-1ubuntu1]
[08:28] -queuebot:#ubuntu-release- New: accepted lorene [powerpc] (zesty-proposed) [0.0.0~cvs20161116+dfsg-1ubuntu1]
[08:28] -queuebot:#ubuntu-release- New: accepted lorene [s390x] (zesty-proposed) [0.0.0~cvs20161116+dfsg-1ubuntu1]
[08:28] -queuebot:#ubuntu-release- New: accepted lorene [i386] (zesty-proposed) [0.0.0~cvs20161116+dfsg-1ubuntu1]
[08:28] -queuebot:#ubuntu-release- New: accepted lorene [ppc64el] (zesty-proposed) [0.0.0~cvs20161116+dfsg-1ubuntu1]
[08:29] -queuebot:#ubuntu-release- New: accepted budgie-wallpapers [amd64] (zesty-proposed) [17.04]
[10:10] -queuebot:#ubuntu-release- Unapproved: makedumpfile (xenial-proposed/main) [1:1.5.9-5ubuntu0.3 => 1:1.5.9-5ubuntu0.4] (core)
[11:10] -queuebot:#ubuntu-release- New binary: npd6 [amd64] (zesty-proposed/none) [1.1.0-1] (no packageset)
[11:10] -queuebot:#ubuntu-release- New binary: npd6 [ppc64el] (zesty-proposed/none) [1.1.0-1] (no packageset)
[11:11] -queuebot:#ubuntu-release- New binary: npd6 [arm64] (zesty-proposed/none) [1.1.0-1] (no packageset)
[11:11] -queuebot:#ubuntu-release- New binary: npd6 [i386] (zesty-proposed/none) [1.1.0-1] (no packageset)
[11:11] -queuebot:#ubuntu-release- New binary: npd6 [armhf] (zesty-proposed/none) [1.1.0-1] (no packageset)
[11:12] -queuebot:#ubuntu-release- New binary: npd6 [powerpc] (zesty-proposed/none) [1.1.0-1] (no packageset)
[11:12] -queuebot:#ubuntu-release- New binary: npd6 [s390x] (zesty-proposed/none) [1.1.0-1] (no packageset)
[11:19] -queuebot:#ubuntu-release- Unapproved: accepted xserver-xorg-video-amdgpu [source] (xenial-proposed) [1.1.2-0ubuntu0.16.04.1]
[11:21] -queuebot:#ubuntu-release- Unapproved: accepted makedumpfile [source] (xenial-proposed) [1:1.5.9-5ubuntu0.4]
[11:24] <Odd_Bloke> slangasek: I've updated https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1662491 to add a test for the other udev rule.
[11:24] <Odd_Bloke> Which happens to be most of a fix for another issue GCE have filed. \o/
[11:30] <Odd_Bloke> slangasek: Hmm, actually, the rest of the fix is just dropping a file in /etc/rsyslog.d, so I think it's probably worth doing that as part of this SRU rather than having to do all the busywork again.
[11:31] -queuebot:#ubuntu-release- New: accepted npd6 [amd64] (zesty-proposed) [1.1.0-1]
[11:31] -queuebot:#ubuntu-release- New: accepted npd6 [armhf] (zesty-proposed) [1.1.0-1]
[11:31] -queuebot:#ubuntu-release- New: accepted npd6 [powerpc] (zesty-proposed) [1.1.0-1]
[11:31] -queuebot:#ubuntu-release- New: accepted npd6 [s390x] (zesty-proposed) [1.1.0-1]
[11:31] -queuebot:#ubuntu-release- New: accepted npd6 [arm64] (zesty-proposed) [1.1.0-1]
[11:31] -queuebot:#ubuntu-release- New: accepted npd6 [ppc64el] (zesty-proposed) [1.1.0-1]
[11:31] -queuebot:#ubuntu-release- New: accepted npd6 [i386] (zesty-proposed) [1.1.0-1]
[11:35] <Laney> were .manifest files always served up as application/x-ms-manifest?
[11:36] <Trevinho> hi rbasak, can you please unqueue https://launchpad.net/ubuntu/xenial/+queue?queue_state=1&queue_text=libappindicator ?
[11:37] -queuebot:#ubuntu-release- Unapproved: accepted evolution-ews [source] (xenial-proposed) [3.18.5-1ubuntu1]
[11:44] -queuebot:#ubuntu-release- Unapproved: accepted evolution-ews [source] (yakkety-proposed) [3.22.3-0ubuntu1]
[11:49] <Laney> am I going mad?
[11:49] <Laney> It looks like unity8 isn't installable in zesty
[11:49] <Laney> can someone confirm?
[11:54] <apw> Laney, i have it installed, if that counts any
[11:55] <Laney> apw: Probably a component-mismatch
[11:56] <Laney> Although
[11:56] <apw> oh that likely
[11:57] <apw> though if you mean in -proposed, then ... i am not helping :)
[11:57] <Laney> wtf
[11:58] <Laney> apw: Do you have the newest version?
[11:58] <apw> Laney, from zesty-release yes
[11:58] <Odd_Bloke> Same here.
[11:58] <apw> unity8 is already the newest version (8.15+17.04.20170206-0ubuntu1).
[11:59] <Laney> As far as I can see unity8-common has Depends: unity-application-impl-26 which doesn't exist
[12:00] <Laney> Oh, unity8-tests in zesty/universe
[12:00] <Laney> eww
[12:01] <apw> oh did something move from main to universe while installed on your box perhaps
[12:02] <jbicha> Laney: bug 1662608 and https://irclogs.ubuntu.com/2017/02/07/%23ubuntu-desktop.html#t16:45 :)
[12:02] <Laney> Right, but I didn't link that to a component mismatch
[12:03] <apw> Laney, hehe that was you :)
[12:03] <apw> quite how it got out of -proposed with that though
[12:06] <Laney> at a guess, the thing doesn't deal with provides
[12:11] <infinity> How is that bug still in the archive? :/
[12:11] <infinity> I've been avoiding upgrading to not pull all that crap in.
[12:12] -queuebot:#ubuntu-release- Unapproved: systemd (xenial-proposed/main) [229-4ubuntu16 => 229-4ubuntu17] (core)
[12:12] -queuebot:#ubuntu-release- Unapproved: rejected systemd [source] (xenial-proposed) [229-4ubuntu17]
[12:14] <infinity> Laney: Can you escalate and/or jfdi a fix for that bug?  Pulling in the whole X dev stack on upgrade is unpleasant, to say the least.
[12:14] <infinity> Oh, I see an MP from a week ago.
[12:14] <infinity> FFS.
[12:14] <Laney> I'm asking in #-ci-eng
[12:18] <jbicha> I set apt-mark hold on the unity8 tests because I didn't want that -dev stuff either :)
[12:19] <infinity> I've just been upgrading instead of dist-upgrading for now.
[12:19] <Laney> So it should be within a day, if this all-proposed run makes their tests go green
[12:20] <Laney> There are lots of other fixes bundled up with the one we want
[12:20] <Laney> The usual thing...
[12:23] <apw> won't it autoremove off again when the bits are fixed ?
[12:26] <infinity> In theory.
[12:27] <Laney> I don't know
[12:27] <infinity> Actually, no.
[12:27] <Laney> Will you be moved from one provider to another?
[12:27] <infinity> It won't.
[12:27] <Laney> I don't see how
[12:27] <infinity> Yeah, that.
[12:27] <apw> hrm, why so, that seems counter-intuitive
[12:27] <infinity> apw: It's not that it had a spurious dependency on foo-tests, it's that foo-tests and qtmir-thing both provide virtual-$version, but $version was wrong on qtmir.
[12:28] <infinity> apw: So, you got foo-tests instead.  When qtmir is fixed, foo-tests will stick around because it still satisfies the dep.
[12:30] <Laney> MMMmmmmmmmmmm
[12:30] <Laney> So there's a libmirplatform transition
[12:30] <Laney> qtmir -> miral -> libmirplatform
[12:30] <jbicha> bump the depends/provides to impl-27?
[12:30] <Laney> and miral FTBFS with a no-change rebuild against this new one
[12:30] <Laney> There's a new upstream release which works apparently
[12:32] <infinity> jbicha: Still wouldn't autoremove, it'd just upgrade unity8-tests to the one that provides the new virtual. :P
[12:33] <apw> crap, and my machine is already infected with this mess
[12:33] <apw> ii  unity8-tests:amd64
[12:33] <jbicha> drop the unity8-tests package and create a new unity8-tests-oops-our-bad package ;)
[12:33] <apw> so once i get a fixed unity (and a couple of pints of beer in compensation) i assume i can purge that one
[12:39] <infinity> apw: Yeah, manually removing unity8-tests should autoremove all the rest of the junk at least.
[12:39] <infinity> Manually removing it right now would also do very little harm, except for the bit where we have it in the desktop seed.
[12:40] <Laney> Saviq is OKing me just uploading a Provides switch
[12:40] <infinity> Which we never should have, IMO.  Should have been a separate meta, so people could whack it without consequence.
[12:40] <infinity> Laney: Say, why didn't we do that?
[12:41] <infinity> Wait...
[12:41] <infinity> Removing unity8 doesn't remove ubuntu-desktop.
[12:41] <infinity> I could have sworn it was in the desktop seed.
[12:41] <Laney> Recommends
[12:41] <infinity> Ahh.
[12:42] <infinity> Well, that's my solution then.
[12:42] <infinity> I was "dogfooding" it, but it's not like it's actually useful enough for me to do so.
[12:44]  * Laney LA LA LAs at the lintian errors in qtmir
[12:44]  * infinity purges libhybris too, to see what that takes with it.
[12:48] <Laney> there we go
[12:49] <Laney> I think this will not get involved with the mirplatform transition
[13:10] <Odd_Bloke> So what's the solution to get rid of unity8-tests?  Can I just remove it now?
[13:12] <Laney> If you wait for qtmir to migrate, then apt should offer to install (or upgrade) it when you try to remove unity8-tests
[13:13] <Odd_Bloke> Right, whereas removing it now removes all of unity8.
[13:13] <Odd_Bloke> OK, I shall wait.
[13:13] <Saviq> Laney, btw, can you please upload the same change to xenial overlay?
[13:15] <Laney> Saviq: sure, if that's allowed
[13:19] <Saviq> Laney, yeah, it is
[13:20] -queuebot:#ubuntu-release- Unapproved: postgresql-9.3 (trusty-proposed/main) [9.3.15-0ubuntu0.14.04 => 9.3.16-0ubuntu0.14.04] (no packageset) (sync)
[13:23] -queuebot:#ubuntu-release- Unapproved: accepted postgresql-9.3 [sync] (trusty-proposed) [9.3.16-0ubuntu0.14.04]
[13:25] -queuebot:#ubuntu-release- Unapproved: postgresql-9.5 (xenial-proposed/main) [9.5.5-0ubuntu0.16.04 => 9.5.6-0ubuntu0.16.04] (core) (sync)
[13:25] -queuebot:#ubuntu-release- Unapproved: postgresql-9.5 (yakkety-proposed/main) [9.5.5-0ubuntu0.16.10 => 9.5.6-0ubuntu0.16.10] (core) (sync)
[13:26] -queuebot:#ubuntu-release- Unapproved: accepted postgresql-9.5 [sync] (xenial-proposed) [9.5.6-0ubuntu0.16.04]
[13:26] -queuebot:#ubuntu-release- Unapproved: accepted postgresql-9.5 [sync] (yakkety-proposed) [9.5.6-0ubuntu0.16.10]
[14:30] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (zesty-proposed/main) [4.10.0-8.10] (core, kernel)
[14:30] -queuebot:#ubuntu-release- Unapproved: accepted systemd [source] (xenial-proposed) [229-4ubuntu17]
[14:32] -queuebot:#ubuntu-release- Unapproved: accepted nano [source] (xenial-proposed) [2.5.3-2ubuntu2]
[14:35] -queuebot:#ubuntu-release- Unapproved: accepted qemu [source] (xenial-proposed) [1:2.5+dfsg-5ubuntu10.9]
[14:37] -queuebot:#ubuntu-release- Unapproved: accepted qemu [source] (yakkety-proposed) [1:2.6.1+dfsg-0ubuntu5.3]
[14:41] -queuebot:#ubuntu-release- Unapproved: accepted multipath-tools [source] (xenial-proposed) [0.5.0+git1.656f8865-5ubuntu2.4]
[14:43] -queuebot:#ubuntu-release- Unapproved: accepted multipath-tools [source] (yakkety-proposed) [0.5.0+git1.656f8865-5ubuntu7.2]
[14:45] -queuebot:#ubuntu-release- Unapproved: accepted libodb [source] (xenial-proposed) [2.4.0-1build0~16.04.1]
[14:47] -queuebot:#ubuntu-release- Unapproved: accepted libodb [source] (yakkety-proposed) [2.4.0-1build0~16.10.1]
[14:47] -queuebot:#ubuntu-release- Unapproved: gce-compute-image-packages (yakkety-proposed/universe) [20160930-0ubuntu3~16.10.0 => 20160930-0ubuntu5~16.10.0] (ubuntu-cloud)
[14:48] -queuebot:#ubuntu-release- Unapproved: gce-compute-image-packages (xenial-proposed/universe) [20160930-0ubuntu3~16.04.0 => 20160930-0ubuntu5~16.04.0] (ubuntu-cloud)
[14:48] <Odd_Bloke> If anyone has a moment, they could reject gce-compute-image-packages 20160930-0ubuntu4~16.10.0 from the yakkety queue and 20160930-0ubuntu3~16.04.1 from the xenial queue.
[14:50] <Odd_Bloke> slangasek: And these are the new gce-compute-image-packages ^
[14:50] <arges> Odd_Bloke: sure
[14:51] <arges> Odd_Bloke: does that look correct now?
[14:52] -queuebot:#ubuntu-release- Unapproved: rejected gce-compute-image-packages [source] (xenial-proposed) [20160930-0ubuntu3~16.04.1]
[14:52] -queuebot:#ubuntu-release- Unapproved: rejected gce-compute-image-packages [source] (yakkety-proposed) [20160930-0ubuntu4~16.10.0]
[14:52] <Odd_Bloke> arges: Yep, thanks!
[15:10] -queuebot:#ubuntu-release- Unapproved: libappindicator (xenial-proposed/main) [12.10.1+15.04.20141110-0ubuntu1 => 12.10.1+16.04.20170215-0ubuntu1] (ubuntu-desktop) (sync)
[15:16] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (zesty-proposed) [4.10.0-8.10]
[15:31] -queuebot:#ubuntu-release- Unapproved: blktap-dkms (xenial-proposed/universe) [2.0.93-0.5ubuntu1 => 2.0.93-0.7ubuntu2~16.04.1] (no packageset)
[15:32] -queuebot:#ubuntu-release- Unapproved: broadcom-sta (xenial-proposed/multiverse) [6.30.223.271-2 => 6.30.223.271-3~16.04.1] (no packageset)
[15:33] <jgrimm> arges, would you be able to process curtin from Xenial today?
[15:43] -queuebot:#ubuntu-release- Unapproved: dm-writeboost (xenial-proposed/universe) [2.1.1-1 => 2.1.1-1ubuntu1] (no packageset)
[15:47] -queuebot:#ubuntu-release- Unapproved: accepted dm-writeboost [source] (xenial-proposed) [2.1.1-1ubuntu1]
[15:54] -queuebot:#ubuntu-release- Unapproved: lttng-modules (xenial-proposed/universe) [2.7.1-1 => 2.8.0-1ubuntu1~16.04.1] (no packageset)
[16:03] -queuebot:#ubuntu-release- Unapproved: oss4 (xenial-proposed/universe) [4.2-build2010-5 => 4.2-build2010-5ubuntu1~14.04.1] (no packageset)
[16:14] -queuebot:#ubuntu-release- Unapproved: accepted oss4 [source] (xenial-proposed) [4.2-build2010-5ubuntu1~14.04.1]
[16:16] -queuebot:#ubuntu-release- Unapproved: xtables-addons (xenial-proposed/universe) [2.10-1build1 => 2.10-1ubuntu0.1] (no packageset)
[16:32] -queuebot:#ubuntu-release- Unapproved: accepted lttng-modules [source] (xenial-proposed) [2.8.0-1ubuntu1~16.04.1]
[16:34] -queuebot:#ubuntu-release- Unapproved: accepted blktap-dkms [source] (xenial-proposed) [2.0.93-0.7ubuntu2~16.04.1]
[16:37] -queuebot:#ubuntu-release- Unapproved: accepted broadcom-sta [source] (xenial-proposed) [6.30.223.271-3~16.04.1]
[16:38] -queuebot:#ubuntu-release- Unapproved: accepted xtables-addons [source] (xenial-proposed) [2.10-1ubuntu0.1]
[16:48] -queuebot:#ubuntu-release- New binary: nginx [ppc64el] (zesty-proposed/main) [1.10.3-0ubuntu2] (kubuntu, ubuntu-server)
[16:48] -queuebot:#ubuntu-release- Unapproved: libodb-boost (xenial-proposed/universe) [2.4.0-1 => 2.4.0-1build0~16.04.1] (no packageset)
[16:49] -queuebot:#ubuntu-release- Unapproved: libodb-boost (yakkety-proposed/universe) [2.4.0-1 => 2.4.0-1build0~16.10.1] (no packageset)
[16:50] -queuebot:#ubuntu-release- New binary: nginx [i386] (zesty-proposed/main) [1.10.3-0ubuntu2] (kubuntu, ubuntu-server)
[16:50] -queuebot:#ubuntu-release- New binary: nginx [s390x] (zesty-proposed/main) [1.10.3-0ubuntu2] (kubuntu, ubuntu-server)
[16:51] -queuebot:#ubuntu-release- New binary: nginx [powerpc] (zesty-proposed/main) [1.10.3-0ubuntu2] (kubuntu, ubuntu-server)
[16:53] -queuebot:#ubuntu-release- New binary: nginx [arm64] (zesty-proposed/main) [1.10.3-0ubuntu2] (kubuntu, ubuntu-server)
[16:53] -queuebot:#ubuntu-release- New binary: nginx [armhf] (zesty-proposed/main) [1.10.3-0ubuntu2] (kubuntu, ubuntu-server)
[16:55] -queuebot:#ubuntu-release- New binary: nginx [amd64] (zesty-proposed/main) [1.10.3-0ubuntu2] (kubuntu, ubuntu-server)
[16:55] <teward> yes, unfortunately, package structure for nginx changed thanks to Debian and Dynamic Modules >.>
[17:03] -queuebot:#ubuntu-release- Unapproved: ubuntu-image (yakkety-proposed/universe) [0.14+16.10ubuntu2 => 0.15+16.10ubuntu1] (no packageset)
[17:04] -queuebot:#ubuntu-release- Unapproved: ubuntu-image (xenial-proposed/universe) [0.14+16.04ubuntu2 => 0.15+16.04ubuntu1] (no packageset)
[17:44] <dmj_s76> infinity: No new iso this morning?
[17:44] <infinity> dmj_s76: Very shortly.  Just testing a build now.
[17:44] <infinity> Or, rather, it's building so I can test it.
[17:44] <dmj_s76> infinity: oh, great...we're eagerly waiting to test :)
[18:09] <Odd_Bloke> slangasek: I'm EOD now; it would be lovely to wake up to gce-compute-image-packages packages in -proposed. ^_^
[18:31] <slangasek> Odd_Bloke: .changes file ended up with no bug references; having a look at this, probably just a no-change reupload from me
[19:51] -queuebot:#ubuntu-release- Unapproved: gce-compute-image-packages (yakkety-proposed/universe) [20160930-0ubuntu3~16.10.0 => 20160930-0ubuntu5~16.10.0] (ubuntu-cloud)
[19:52] -queuebot:#ubuntu-release- Unapproved: rejected gce-compute-image-packages [source] (yakkety-proposed) [20160930-0ubuntu5~16.10.0]
[19:55] -queuebot:#ubuntu-release- Unapproved: accepted gce-compute-image-packages [source] (yakkety-proposed) [20160930-0ubuntu5~16.10.0]
[20:01] -queuebot:#ubuntu-release- Unapproved: rejected gce-compute-image-packages [source] (xenial-proposed) [20160930-0ubuntu5~16.04.0]
[20:03] -queuebot:#ubuntu-release- Unapproved: gce-compute-image-packages (xenial-proposed/universe) [20160930-0ubuntu3~16.04.0 => 20160930-0ubuntu5~16.04.0] (ubuntu-cloud)
[20:19] -queuebot:#ubuntu-release- Unapproved: accepted gce-compute-image-packages [source] (xenial-proposed) [20160930-0ubuntu5~16.04.0]
[20:25] -queuebot:#ubuntu-release- Builds: Ubuntu Base amd64 [Xenial 16.04.2] has been updated (20170215)
[20:25] -queuebot:#ubuntu-release- Builds: Ubuntu Base arm64 [Xenial 16.04.2] has been updated (20170215)
[20:25] -queuebot:#ubuntu-release- Builds: Ubuntu Base armhf [Xenial 16.04.2] has been updated (20170215)
[20:26] -queuebot:#ubuntu-release- Builds: Ubuntu Base i386 [Xenial 16.04.2] has been updated (20170215)
[20:26] -queuebot:#ubuntu-release- Builds: Ubuntu Base powerpc [Xenial 16.04.2] has been updated (20170215)
[20:26] -queuebot:#ubuntu-release- Builds: Ubuntu Base ppc64el [Xenial 16.04.2] has been updated (20170215)
[20:26] -queuebot:#ubuntu-release- Builds: Ubuntu Base s390x [Xenial 16.04.2] has been updated (20170215)
[20:31] -queuebot:#ubuntu-release- Unapproved: adobe-flashplugin (precise-proposed/partner) [1:20170110.1-0ubuntu0.12.04.1 => 1:20170214.1-0ubuntu0.12.04.1] (no packageset)
[20:31] -queuebot:#ubuntu-release- Unapproved: adobe-flashplugin (xenial-proposed/partner) [1:20170110.1-0ubuntu0.16.04.1 => 1:20170214.1-0ubuntu0.16.04.1] (no packageset)
[20:31] -queuebot:#ubuntu-release- Unapproved: adobe-flashplugin (trusty-proposed/partner) [1:20170110.1-0ubuntu0.14.04.1 => 1:20170214.1-0ubuntu0.14.04.1] (no packageset)
[20:31] -queuebot:#ubuntu-release- Unapproved: adobe-flashplugin (yakkety-proposed/partner) [1:20170110.1-0ubuntu0.16.10.1 => 1:20170214.1-0ubuntu0.16.10.1] (no packageset)
[20:40] -queuebot:#ubuntu-release- Unapproved: accepted adobe-flashplugin [source] (yakkety-proposed) [1:20170214.1-0ubuntu0.16.10.1]
[20:41] -queuebot:#ubuntu-release- Unapproved: accepted adobe-flashplugin [source] (trusty-proposed) [1:20170214.1-0ubuntu0.14.04.1]
[20:41] -queuebot:#ubuntu-release- Unapproved: accepted adobe-flashplugin [source] (xenial-proposed) [1:20170214.1-0ubuntu0.16.04.1]
[20:42] -queuebot:#ubuntu-release- Unapproved: accepted adobe-flashplugin [source] (precise-proposed) [1:20170214.1-0ubuntu0.12.04.1]
[20:47] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Xenial 16.04.2] has been updated (20170215)
[20:47] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop i386 [Xenial 16.04.2] has been updated (20170215)
[20:57] -queuebot:#ubuntu-release- Builds: Ubuntu GNOME Desktop amd64 [Xenial 16.04.2] has been updated (20170215)
[20:57] -queuebot:#ubuntu-release- Builds: Ubuntu GNOME Desktop i386 [Xenial 16.04.2] has been updated (20170215)
[20:58] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop amd64 [Xenial 16.04.2] has been updated (20170215)
[21:02] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Xenial 16.04.2] has been updated (20170215)
[21:02] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop i386 [Xenial 16.04.2] has been updated (20170215)
[21:07] -queuebot:#ubuntu-release- Builds: Ubuntu Server amd64 [Xenial 16.04.2] (20170215.8) has been added
[21:07] -queuebot:#ubuntu-release- Builds: Ubuntu Server arm64 [Xenial 16.04.2] (20170215.8) has been added
[21:07] -queuebot:#ubuntu-release- Builds: Ubuntu Server i386 [Xenial 16.04.2] (20170215.8) has been added
[21:07] -queuebot:#ubuntu-release- Builds: Ubuntu Server powerpc [Xenial 16.04.2] (20170215.8) has been added
[21:07] -queuebot:#ubuntu-release- Builds: Ubuntu Server ppc64el [Xenial 16.04.2] (20170215.8) has been added
[21:26] -queuebot:#ubuntu-release- Builds: Mythbuntu Desktop amd64 [Xenial 16.04.2] has been updated (20170215)
[21:26] -queuebot:#ubuntu-release- Builds: Mythbuntu Desktop i386 [Xenial 16.04.2] has been updated (20170215)
[21:27] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Xenial 16.04.2] has been updated (20170215)
[21:27] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop i386 [Xenial 16.04.2] has been updated (20170215)
[21:33] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Xenial 16.04.2] has been updated (20170215)
[21:33] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop i386 [Xenial 16.04.2] has been updated (20170215)
[21:34] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD amd64 [Xenial 16.04.2] has been updated (20170215)
[21:34] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD i386 [Xenial 16.04.2] has been updated (20170215)
[21:49] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Xenial 16.04.2] has been updated (20170215.2)
[21:49] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop i386 [Xenial 16.04.2] has been updated (20170215.2)
[22:33] <wxl> infinity: what's new with the ISO?
[22:46] <tsimonq2> wxl: I thought HWE stuff but I could be wrong
[22:51] <wxl> tsimonq2: yeah well knowing that is always helpful XD
[22:51] <wxl> if that's all it is, we'll mostly look at smoke testing
[22:52] <tsimonq2> wxl: I could have sworn there was a way we can just diff the freaking ISOs!
[22:52] <wxl> tsimonq2: well you could grab the manifest and diff them for sure
[22:52] <wxl> maybe i'll just do that. sigh. :)
[22:54] <wxl> of course the old manifest is overwritten :/
[22:54] <wxl> and all the flavours have already built soooooo
[22:55]  * tsimonq2 changes wxl's locale back to en_US from en_GB
[22:55] <tsimonq2> :P
[22:55] <wxl> no way man i use en_CA XD
[23:11] -queuebot:#ubuntu-release- New binary: ht-el [amd64] (zesty-proposed/none) [2.1-1] (no packageset)
[23:12] <tsimonq2> wxl: Aw what really? :P
[23:13] -queuebot:#ubuntu-release- New binary: py-isort-el [amd64] (zesty-proposed/none) [2016.1-1] (no packageset)
[23:15] <slangasek> the manifest for the previous image would still be under the previous build serial
[23:15] -queuebot:#ubuntu-release- Unapproved: proftpd-dfsg (trusty-proposed/universe) [1.3.5~rc3-2.1ubuntu2.1 => 1.3.5~rc3-2.1ubuntu2.2] (no packageset)
[23:15] <slangasek> for images where the old one rotated off, well, not so much
[23:19] <wxl> tsimonq2: no. :)
[23:20] <tsimonq2> wxl: Good. :P
[23:21] <wxl> slangasek: yeah it's weird cuz when i looked this morning there was both 20170209 and 20170208 but now there's just one.
[23:21] <slangasek> yes, they're expired based on age
[23:21] <wxl> booo
[23:21] <tsimonq2> slangasek: Where's the tooling that builds the images again?
[23:22] <slangasek> tsimonq2: which piece? lp:ubuntu-cdimage?
[23:22] <tsimonq2> slangasek: I mean the thing that builds the dailies.
[23:22] <tsimonq2> slangasek: Like, installs the packages and such.
[23:23] <slangasek> do you mean lp:livecd-rootfs?
[23:23] <tsimonq2> Maaaybe...
[23:23]  * tsimonq2 checks
[23:25] <tsimonq2> slangasek: Hm so it doesn't LOOK like it. Maybe I'm not looking right?
[23:26] <slangasek> well, I'm not sure which piece you're looking for
[23:26] <wxl> hold on
[23:26] <wxl> i think i can answer this
[23:26] <tsimonq2> wxl: Yes siree please do :)
[23:26] <slangasek> the chain is ubuntu-cdimage -> (launchpad-buildd -> livecd-rootfs -> live-build), debian-cd
[23:27] <tsimonq2> Ooh, mkay.
[23:27] <wxl> yeah that's what i was going to say based on the crontab