[00:05] -queuebot:#ubuntu-release- Unapproved: appmenu-qt5 (xenial-proposed/main) [0.3.0+16.04.20151130-0ubuntu2 => 0.3.0+16.04.20170216-0ubuntu1] (ubuntu-desktop, ubuntu-qt-packages) (sync)
[00:11] <infinity> wxl: So, moment of truth.  Kubuntu's going out without your say-so, unless you tell me to delete it. :P
[00:11] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Xenial 16.04.2] has been marked as ready
[00:11] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop i386 [Xenial 16.04.2] has been marked as ready
[00:11] -queuebot:#ubuntu-release- Builds: Ubuntu Server amd64 [Xenial 16.04.2] has been marked as ready
[00:11] -queuebot:#ubuntu-release- Builds: Ubuntu Server arm64 [Xenial 16.04.2] has been marked as ready
[00:11] -queuebot:#ubuntu-release- Builds: Ubuntu Server armhf+raspi2 [Xenial 16.04.2] has been marked as ready
[00:11] -queuebot:#ubuntu-release- Builds: Ubuntu Server i386 [Xenial 16.04.2] has been marked as ready
[00:11] -queuebot:#ubuntu-release- Builds: Ubuntu Server powerpc [Xenial 16.04.2] has been marked as ready
[00:11] -queuebot:#ubuntu-release- Builds: Ubuntu Server ppc64el [Xenial 16.04.2] has been marked as ready
[00:11] -queuebot:#ubuntu-release- Builds: Ubuntu Server s390x [Xenial 16.04.2] has been marked as ready
[00:11] <wxl> infinity: do it. sorry. was trying to put some other stuff together
[00:11] <wxl> (unnecessary additional stuff)
[00:12] <infinity> wxl: Alrighty.  Will be pushing big red buttons shortly.
[00:12] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop i386 [Xenial 16.04.2] has been marked as ready
[00:13] -queuebot:#ubuntu-release- Builds: 39 entries have been added, updated or disabled
[01:40] <tsimonq2> infinity: How's button pressing going?
[01:41] <tsimonq2> (no announcement email yet, just wondering)
[01:44] <infinity> tsimonq2: There'll be an email in a few minutes. ;)
[01:45] <tsimonq2> infinity: Thanks. ;)
[01:47] <tsimonq2> infinity: Fancy, thanks
=== infinity changed the topic of #ubuntu-release to: Released: Trusty 14.04.5, Xenial 16.04.2, Yakkety 16.10 | Archive: feature freeze, DIF | Zesty Release Coordination | Please don't upload things during freezes where you shouldn't, or be prepared to apologise to the release team | We accept payment in cash, check or beer | melior malum quod cognoscis
[01:56] <mwhudson> infinity: congrats
[02:05] <tsimonq2> infinity: DuckDuckGo was of no help here, what is DIF?
[02:05] <tsimonq2> :P
[02:06] <infinity> DebianImportFreeze.
[02:06] <tsimonq2> Ahhhhhhh, gotcha.
[02:06] <infinity> ie: we turn off the autosync mojo.
[02:09] <tsimonq2> Yup, I got it, I've read the relevant docs, just didn't know about the acronym. ;)
[02:11] <infinity> I'm not sure anyone uses the acronym, I just guessed Laney's intent based on what time of year it is. :)
[02:12] <tsimonq2> infinity: As long as you don't start abbreviating Zesty to "ZZ," I'm fine. :P
[03:36] -queuebot:#ubuntu-release- Unapproved: curtin (yakkety-proposed/main) [0.1.0~bzr437-0ubuntu1~16.10.1 => 0.1.0~bzr460-0ubuntu1~16.10.1] (ubuntu-server)
[06:49] -queuebot:#ubuntu-release- Unapproved: strongswan (yakkety-proposed/main) [5.3.5-1ubuntu4 => 5.3.5-1ubuntu4.1] (ubuntu-server)
[09:02] <Laney> slangasek: The only new thing with that is that you can see them - previously the requests were just eaten invisibly
[09:03] <slangasek> Laney: oh, ok
[09:25] <ginggs> is there a know problem with i386 tests? tests seem to run, but their results don't go anywhere. update_excuses shows many 'Test in progress' for i386, but they don't seem to be running
[09:37] <Laney> known-ish
[09:38] <Laney> take one of them, for example strongswan
[09:39] <Laney> look at the raw list of results (https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/?format=plain&delimiter=@&prefix=zesty/i386/s/strongswan, documented at https://wiki.ubuntu.com/ProposedMigration/AutopkgtestInfrastructure#Administration)
[09:39] <Laney> take the latest one, find its log.gz: http://10.24.0.175:8080/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/i386/s/strongswan/20170217_045323_1a891@/log.gz
[09:40] <Laney> https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/i386/s/strongswan/20170217_045323_1a891@/log.gz
[09:40] <Laney> -> it broke really early in setup
[09:45] <ginggs> Laney: interesting, thanks
[09:46] <Laney> mmm
[09:47] <acheronuk> if a test has previously been triggered with all-proposed=1, is there a way to go back to re-running it without? looking at packages installed in a test and their versions, it seems to be remembering for the next triggering of the test even if all-proposed is them ommitted
[09:47] <apw> acheronuk, i am not sure that is happening, even if it feels like it
[09:48] <Laney> it's not
[09:48] <Laney> look at the second line of the log
[09:48] <Laney> the --apt-proposed bit
[09:48] <Laney> --apt-pocket*
[09:50] <acheronuk> https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/k/kf5-kdepim-apps-libs/20170217_090015_2a4be@/log.gz
[09:50] <acheronuk> --apt-pocket=proposed=src:kiconthemes
[09:53] <acheronuk> that was triggered without all-proposed, but seems to be installing all the kde frameworks build deps from the proposed pocket
[09:55] <Laney> That suggests that something requires those versions then
[09:59] <acheronuk> right. so there is some flexibility there in the apt-pinning of those pockets, depending on other depends. i.e. if a something in the latest dep chain requires something else from the proposed pocket which is not the source or trigger, then it will get fetched from proposed no matter if all-proposed was set or not?
[10:09] <xnox> Laney, working on zlib migrating from proposed, which leads to 1.2.8 -> 1.2.11 update. It has features, do I need FFe now, given that it did not migrate before the freeze?
[10:10] <Laney> xnox: nah, I don't think so
[10:10] <Laney> xnox: ...
[10:10] <Laney> are you aware of the above udev/i386 bustage?
[10:10] <xnox> as long as it migrates in a timely fashion.
[10:10] <xnox> Laney, kill i386 = problem solved.
[10:10] <xnox> Laney, no, i am not. Is there bug report about it?
[10:10] <xnox> or is it adt only?
[10:11] <Laney> if I could remember the qemu shizzle ...
[10:12] <xnox> oooh, i think i see it
[10:12] <xnox> https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/i386/b/binutils/20170217_025857_c4f0d@/log.gz
[10:12] <xnox> systemd-udevd is activating and fails to start =(
[10:12] <xnox> that can't be good.
[10:12] <Laney> right
[10:13] <xnox> and that's with steve's systemd; let me retrigger that with 18ubuntu1
[10:15] <Laney> no
[10:15] <Laney> https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/i386/s/strongswan/20170217_045323_1a891@/log.gz
[10:15] <Laney> 18ubuntu1
[10:15] <xnox> fun
[10:15] <xnox> thanks i did not spot check find 18ubuntu1 as well.
[10:15] <xnox> ok will debug now.
[10:16] <Laney> just checking if I can get it locally
[10:16] <Laney> https://cloud-images.ubuntu.com/zesty/20170215.1/zesty-server-cloudimg-i386.img <- has 232-8
[10:30] <Laney> well I don't get it with autopkgtest-buildvm-ubuntu-cloud at least :/
[10:38] <xnox> Laney, my host is xenial, and i don't get it either. horum.
[10:38] <Laney> try in canonistack?
[10:38] <xnox> Laney, is it a cloud problem?!
[10:38] <xnox> Laney, yeah, that's what i am thinking now.
[10:38] <xnox> gosh i have not logged into that in a while.
[10:38] <Laney> me neither
[10:39] <Laney> and nova in zesty is busted / incompatible so I can't try it myself
[10:39] <Laney> :-)
[10:41] <xnox> i had saved credentials for hte dashboard
[10:41] <xnox> https://dashboard.canonistack.canonical.com/project/
[10:41] <xnox> and apperantly i have some juju still spinning cycles there =/
[10:41] <xnox> oh, they are shutoff, so that's good.
[10:42] <Laney> heh
[10:44] <xnox> i think it fails to spawn
[10:45] <xnox> Laney, or it's not spawning because udev?
[10:45]  * xnox ponders where CPC test images
[10:46] <Laney> can you get the console-log?
[10:47] <xnox> oooh it's active now.
[10:48] <Laney> mine too
[10:48] <Laney> looks like it's reproducing
[10:48] <xnox> open port 22
[10:48] <xnox> now i can ssh in.
[10:48] <Laney> sudo apt update; sudo apt install udev
[10:49] <xnox> and i guess we want to increase udevd debug level before doing that.
[10:53] <Laney> think it accepts --debug
[10:53] <xnox> Laney, Odd Bloke pointed me at fresh images that did build; test; published on i386 so it must be upgrades that are b0rked
[10:53] <xnox> Laney, well i tweaked /etc/udev/udev.conf first
[10:53] <Laney> well all the failures I saw happened while upgrading it
[10:53] <xnox> Feb 17 10:53:16 testudev systemd-udevd[2399]: Check if link configuration needs reloading.
[10:53] <xnox> Feb 17 10:53:16 testudev systemd-udevd[2399]: error getting socket: Protocol not supported
[10:53] <xnox> fun
[10:54] <Laney> awesome
[10:54] <Laney> that leads to a bug + commit
[10:54] <Laney> https://bugzilla.redhat.com/show_bug.cgi?id=1415358
[10:54] <ubot5> bugzilla.redhat.com bug 1415358 in systemd "systemd-udevd and journald fail to start on i686 (systemd 232)" [Urgent,Closed: rawhide]
[10:56] <xnox> Laney, which is in 232-18ubuntu1....
[10:57] <xnox> and it does start
[10:59] <Laney> doh
[11:00] <xnox> but why did strongswan fail?!
[11:01] <Laney> dist-upgrading the base systemd
[11:01] <Laney> system
[11:02] <xnox> right. so we need new image with -18ubuntu1? or retrigger all tests with extra systemd as trigger?
[11:02] <Laney> why did dist-upgrading to 18u1 fail?
[11:05] <xnox> 232-17ubuntu1 -> 232-18ubuntu1 is success; 232-8 -> 232-18ubuntu1 fails; 232-8 -> 232-17ubuntu1 also fails.
[11:05] <xnox> doing start/stop after upgrade by hand succeeds.
[11:05] <xnox> so e.g. restart fails; or -8 fails to re-exec / restart.... ?!
[11:07] <Laney> we can test this theory by getting an image with 17u1 and trying systemd/i386
[11:09]  * Laney kicks that
[11:10] <xnox> pitti, https://launchpad.net/ubuntu/+source/systemd/+publishinghistory 232-9.. never migrated
[11:13] <xnox> Laney, i think image with 17u1 will not help; as upgrade is still broken.
[11:14] <Laney> you just said it works
[11:14] <xnox> 232-8 -> 232ubuntu17 (timeout fail) -> 232-18ubuntu1 (starts) is what works.
[11:14] <xnox> i didn't boot image with 17ubuntu1 to begin with.
[11:14] <Laney> well this systemd run is going well so far
[11:14] <xnox> =)
[11:14] <Laney> however some of the i386 runs were a pass
[11:15] <Laney> so it could be a fluke
[11:16] <xnox> Laney, i do know that there are almost none i386 test results for src:systemd triggers for 18ubuntu1 =/
[11:16] <xnox> http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#systemd
[11:16] <Laney> right
[11:16] <Laney> but not *actually* none
[11:16] <xnox> and all of those tests are marked in progress and look lost.
[11:16] <xnox> indeed.
[11:17] <Laney> Setting up udev (232-18ubuntu1) ...
[11:17] <Laney> addgroup: The group `input' already exists as a system group. Exiting.
[11:17] <Laney> update-initramfs: deferring update (trigger activated)
[11:17] <xnox> dandy
[11:17] <xnox> does the infra self-update the base image to latest; or does it need manual proding to switch to latest i386 image?
[11:17] <Laney> there's a cron to do that
[11:17] <Laney> I ran it manually though
[12:13] <Trevinho> tjaalton, slangasek: could you please approve the packages I've queued in https://launchpad.net/ubuntu/xenial/+queue?queue_state=1&queue_text= ? :-)
[12:16] <tjaalton> Trevinho: the syncs?
[12:17] <Trevinho> tjaalton: yep
[12:19] <tjaalton> there's not much to review since these don't have a debdiff
[12:21] <infinity> tjaalton: You have to follow the copies back to the PPA, grab the source, and diff against the current xenial source.
[12:21] <infinity> (which sucks, but there you have it)
[12:22] <tjaalton> uh
[12:22] <tjaalton> no wonder they pile up :P
[12:23] <Trevinho> tjaalton: I think bdmurray probably wanted to updat the SRU tools to do this automatically from bileto ppa's or what?
[12:23] <Trevinho> mhmh
[12:25] <tjaalton> the ppa description seems to have diffs
[12:26] <Trevinho> tjaalton: I think the sru-review -p option should help you
[12:31] <tjaalton> still says no debdiff
[12:31] <tjaalton> but the ppa diff is fine
[12:34] -queuebot:#ubuntu-release- Unapproved: accepted unity-control-center [sync] (xenial-proposed) [15.04.0+16.04.20170213.1-0ubuntu1]
[12:35] <tjaalton> oh there were two..
[12:35] -queuebot:#ubuntu-release- Unapproved: accepted unity-control-center [sync] (yakkety-proposed) [15.04.0+16.10.20170214-0ubuntu1]
[12:36] -queuebot:#ubuntu-release- Unapproved: rejected libappindicator [sync] (xenial-proposed) [12.10.1+16.04.20170213.2-0ubuntu1]
[12:36] -queuebot:#ubuntu-release- Unapproved: accepted unity-control-center [sync] (xenial-proposed) [15.04.0+16.04.20170214-0ubuntu1]
[12:42] -queuebot:#ubuntu-release- Unapproved: cups (trusty-proposed/main) [1.7.2-0ubuntu1.7 => 1.7.2-0ubuntu1.8] (core)
[12:45] <tjaalton> Trevinho: are you sure the diff in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2464 is all for that one change?
[13:00] -queuebot:#ubuntu-release- New binary: nut [ppc64el] (zesty-proposed/main) [2.7.4-5ubuntu2] (ubuntu-server)
[13:03] -queuebot:#ubuntu-release- New binary: nut [i386] (zesty-proposed/main) [2.7.4-5ubuntu2] (ubuntu-server)
[13:03] -queuebot:#ubuntu-release- New binary: nut [s390x] (zesty-proposed/main) [2.7.4-5ubuntu2] (ubuntu-server)
[13:04] -queuebot:#ubuntu-release- New binary: nut [arm64] (zesty-proposed/main) [2.7.4-5ubuntu2] (ubuntu-server)
[13:04] -queuebot:#ubuntu-release- New binary: nut [powerpc] (zesty-proposed/main) [2.7.4-5ubuntu2] (ubuntu-server)
[13:05] -queuebot:#ubuntu-release- New binary: nut [amd64] (zesty-proposed/main) [2.7.4-5ubuntu2] (ubuntu-server)
[13:05] -queuebot:#ubuntu-release- New binary: nut [armhf] (zesty-proposed/main) [2.7.4-5ubuntu2] (ubuntu-server)
[13:06] <tsimonq2> infinity, slangasek et al: Who is lucky enough to do Nusakan for Beta 1? ;)
[13:07] <infinity> Not I.
[13:07] <infinity> I've got Beta 2 and Release.
[13:07] <infinity> And I need a break before then. :P
[13:08] <tsimonq2> infinity: So where should I go to "recruit" said person? :P
[13:09] <infinity> tsimonq2: The intersection of ~ubuntu-cdimage and ~canonical
[13:09] <infinity> (I recommend asking Laney nicely)
[13:09] <Laney> when is it?
[13:10] <infinity> Next week.
[13:14] <tsimonq2> infinity: But isn't ~canonical a private team? I was hoping to write a hacky AI irssi script :P
[13:14] <tsimonq2> Laney: Pretty please? *puppy eyes*
[13:17] <Trevinho> tjaalton: yep
[13:17] <Trevinho> a part the vala thing that was needed to get it compiling in xenial
[13:18] <Trevinho> but it's just a GLib. prefix
[13:20] <infinity> tsimonq2: In the absence of a bot, the intersection of people who have access and know the code/tools would be: adconrad (don't ask that guy, he sucks), cjwatson, laney, slangasek, stgraber
[13:20] <infinity> I also note that the cdimage team needs some spring cleaning.
[13:20] <Laney> I can help, sure, if I don't get pinged every 10 seconds to unblock things
[13:21] <tsimonq2> Laney: \o/
[13:21] <infinity> Laney: Just change your nick by one character, they'll never find you.  It's the IRC equivalent of Clark Kent's glasses, or maybe an evil moustache.
[13:22] <tsimonq2> Laney: Put your name on the wiki? ;)
[13:22] <Odd_Bloke> Laneish.
[13:22] <tsimonq2> infinity: Just like it took me a few months to figure out you were Adam Conrad. :P
[13:24] <tsimonq2> Well I'm off to school o/
=== kirkland` is now known as kirkland
[15:07] -queuebot:#ubuntu-release- Unapproved: zfs-linux (yakkety-proposed/main) [0.6.5.8-0ubuntu4.1 => 0.6.5.8-0ubuntu4.2] (no packageset)
[15:12] -queuebot:#ubuntu-release- Unapproved: accepted libappindicator [sync] (xenial-proposed) [12.10.1+16.04.20170215-0ubuntu1]
[15:13] <tjaalton> Trevinho: would be nice to have xenial targets added to the bugs beforehand
[15:14] <Trevinho> tjaalton: I've not the powers for doing that...
[15:15] <tjaalton> https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1606246 did not have ubuntu/appmenu-qt5, surely you can add that?-)
[15:15] <ubot5> Ubuntu bug 1606246 in Mir "Hard-coded X11 calls cause Unity 8 to fail to run on desktop" [Low,Triaged]
[15:20] -queuebot:#ubuntu-release- Unapproved: accepted appmenu-qt5 [sync] (xenial-proposed) [0.3.0+16.04.20170216-0ubuntu1]
[15:27] -queuebot:#ubuntu-release- Unapproved: zfs-linux (xenial-proposed/main) [0.6.5.6-0ubuntu15 => 0.6.5.6-0ubuntu16] (no packageset)
[15:30] -queuebot:#ubuntu-release- Unapproved: sni-qt (xenial-proposed/main) [0.2.7+15.10.20150729-0ubuntu1 => 0.2.7+16.04.20170217.1-0ubuntu1] (kubuntu, ubuntu-desktop) (sync)
[15:30] <Trevinho> tjaalton: thanks, the last one just got added to the queue
[15:30] <Trevinho> https://launchpad.net/ubuntu/xenial/+queue?queue_state=1&queue_text=sni-qt
[15:31] <xnox> Laney, i wonder if we can land perl, zlib, systemd today =/
[15:31] -queuebot:#ubuntu-release- Unapproved: accepted zfs-linux [source] (yakkety-proposed) [0.6.5.8-0ubuntu4.2]
[15:34] <Laney> seems ambitious
[15:35] <Laney> maybe we can run the new devscripts against perl
[15:35] <Laney> and libgnupg-whatsit is the socket length bug
[15:35] <Laney> so that can be skipped
[15:35] <Laney> libembperl-perl wants looking at though
[15:38] <tjaalton> Trevinho: it refers to an old bug which again has no bug target for xenial
[15:38] <tjaalton> or that package for that matter
[15:39] <Trevinho> tjaalton: I was just adding that
[15:39] <Trevinho> it was just hanging
[15:39] <Trevinho> ok now should be there
[15:40] <tjaalton> thx
[15:42] -queuebot:#ubuntu-release- Unapproved: accepted sni-qt [sync] (xenial-proposed) [0.2.7+16.04.20170217.1-0ubuntu1]
[15:42] <tjaalton> Trevinho: the bug needs a test case
[15:43] <Trevinho> yes, and that too... Although i i need to figure out what app is using that atm
[15:43] <Trevinho> as legacy skype was, but not sure who else
[15:44] <Trevinho> Except snaps I mean
[15:45] -queuebot:#ubuntu-release- Unapproved: accepted zfs-linux [source] (xenial-proposed) [0.6.5.6-0ubuntu16]
[15:47] <apw> tjaalton, i was going to review pciutils if you arn't doing it already
[15:47] <tjaalton> apw: go ahead, I'm about to EOW anyway
[15:49] -queuebot:#ubuntu-release- Unapproved: accepted pciutils [source] (yakkety-proposed) [1:3.3.1-1.1ubuntu4.1]
[15:52] -queuebot:#ubuntu-release- Unapproved: accepted pciutils [source] (xenial-proposed) [1:3.3.1-1.1ubuntu1.1]
[15:52] <apw> ^ the two test failures in zesty are bogus, one after the tests completed successfully and the other a known issue with linux.
[15:54] <caribou> Are debian syncs only blocked momentarily around the FF ?
[15:55] <Laney> Autosync is off now for the rest of the release
[15:55] <Laney> Use syncpackage to sync things manually
[15:59] <Trevinho> tjaalton: test case added
[16:00] <caribou> Laney: ok, but since I just found out that it was seeded, looks like it won't be so simple
[16:01] <caribou> I uploaded it to debian early wednesday & hoped that it would make it in before FF
[16:02] <tjaalton> Trevinho: good
[16:03] <apw> caribou, so there are new features in "it" ?
[16:04] <caribou> apw: that the sosreport' iscsi plugin enablement that was missing in Zesty for which I asked you to reject the SRU
[16:09] -queuebot:#ubuntu-release- Builds: Ubuntu GNOME Desktop amd64 [Zesty Beta 1] (20170217) has been added
[16:09] -queuebot:#ubuntu-release- Builds: Ubuntu GNOME Desktop i386 [Zesty Beta 1] (20170217) has been added
[16:13] <Trevinho> tjaalton: I didn't receive any mail about the bug verification, is that still in progress?
[16:13] <apw> caribou, that is annoying ... it should be a slam-dunk regardless
[16:13] <jbicha> wow, that's early for beta rc's
[16:14] <caribou> apw: Looks like a FFE is in order now
[16:16] <tjaalton> Trevinho: I accepted them from the queue page, sru-review -p didn't seem to work
[16:26] <Trevinho> mh, weird
[17:02] -queuebot:#ubuntu-release- Unapproved: accepted curtin [source] (yakkety-proposed) [0.1.0~bzr460-0ubuntu1~16.10.1]
=== sergiusens_ is now known as sergiusens
[17:08] -queuebot:#ubuntu-release- Unapproved: accepted curtin [source] (xenial-proposed) [0.1.0~bzr460-0ubuntu1~16.04.1]
[18:52] -queuebot:#ubuntu-release- Unapproved: accepted strongswan [source] (yakkety-proposed) [5.3.5-1ubuntu4.1]
[18:56] -queuebot:#ubuntu-release- Unapproved: accepted cups [source] (trusty-proposed) [1.7.2-0ubuntu1.8]
[19:14] -queuebot:#ubuntu-release- Unapproved: accepted proftpd-dfsg [source] (trusty-proposed) [1.3.5~rc3-2.1ubuntu2.2]
[20:06] -queuebot:#ubuntu-release- Unapproved: snapd (xenial-proposed/main) [2.22.2 => 2.22.3] (desktop-core, ubuntu-server)
[20:06] -queuebot:#ubuntu-release- Unapproved: snapd (yakkety-proposed/main) [2.22.2+16.10 => 2.22.3+16.10] (desktop-core, ubuntu-server)
[20:31] -queuebot:#ubuntu-release- New source: os-faults (zesty-proposed/primary) [0.1.10-0ubuntu1]
[20:32] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (yakkety-proposed) [2.22.3+16.10]
[20:32] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (xenial-proposed) [2.22.3]
[20:33] -queuebot:#ubuntu-release- Unapproved: snapd (trusty-proposed/universe) [2.22.2~14.04 => 2.22.3~14.04] (no packageset)
[21:00] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (trusty-proposed) [2.22.3~14.04]
[21:35] -queuebot:#ubuntu-release- Unapproved: snapcraft (xenial-proposed/universe) [2.27 => 2.27.1] (no packageset)
[21:36] -queuebot:#ubuntu-release- Unapproved: snapcraft (yakkety-proposed/universe) [2.27+16.10 => 2.27.1+16.10] (no packageset)
[21:36] <sergiusens> slangasek: might letting those into -proposed pretty please? ^
[23:34] <elopio> slangasek: ping in case you are around now. snapcraft in -proposed would be useful :)