[06:49] <LocutusOfBorg> pitti, ping, please autopkgtest for ignition-transport/1.3.0-4: amd64: Regression ♻ , armhf: Always failed, i386: Always failed, ppc64el: Always failed, s390x: Always failed
[06:50] <LocutusOfBorg> ignition-transport has a autpkgtestuite that runs well with protobuf3, and this is the last protobuf blocker for migration
[06:50] <LocutusOfBorg> doko_, ^^^
[06:50] <LocutusOfBorg> for your happiness :)
[06:51] <LocutusOfBorg> protobuf should be run against ignition proposed, and vice-verssa
[06:51]  * LocutusOfBorg exit
[06:52] <pitti> Logan: done
[06:55] <pitti> Logan: sorry, tab failure
[07:01] <flocculant> pitti: you know anything about images and archive sync lock? or will that be someone else later in the day
[07:06] <pitti> flocculant: I'm afraid I don't
[07:07] <flocculant> okey doke :)
[07:36] <LocutusOfBorg> please accept mia from new, the rdeps are already in place thanks
[07:41] <LocutusOfBorg> thanks pitti and thanks irclogs service :)
[07:49] <LocutusOfBorg> mmm pitti I'm not sure it worked retrying against -proposed...
[07:56] <pitti> LocutusOfBorg: well, it's still in the queue
[07:56] <pitti> http://autopkgtest.ubuntu.com/running#queue-ubuntu-yakkety-amd64
[08:01] <LocutusOfBorg> oh thanks, I though the queue wasn't visible with the new service
[08:02] <LocutusOfBorg> lets see if protobuf can migrate today
[08:51] <apw> LocutusOfBorg, it was awol for a while (queues) and are now back with us
[09:02] -queuebot:#ubuntu-release- Unapproved: init-system-helpers (xenial-proposed/main) [1.29ubuntu2 => 1.29ubuntu3] (core)
[09:45] -queuebot:#ubuntu-release- Packageset: Added libmatemixer to ubuntu-mate in yakkety
[11:21] <LocutusOfBorg> cjwatson, FYI, when a build goes ENOSPACE seems to be stuck forever https://launchpad.net/ubuntu/+source/insighttoolkit4/4.10.0-dfsg1-3ubuntu1/+build/10712957
[11:23] <cjwatson> Yeah, known
[11:24] <cjwatson> Just cancel it, at some point I'll get round to working out how to test my fix for that in launchpad-buildd
[11:27] <LocutusOfBorg> thanks
[11:27] <LocutusOfBorg> if you need a tester, I'm here :)
[11:33] <cjwatson> LocutusOfBorg: No, I don't mean manual testing.
[11:33] <LocutusOfBorg> ok thanks
[11:33] <LocutusOfBorg> btw, many packages started failing for ENOMEM or some other similar issues
[11:34] <LocutusOfBorg> I usually "fix" them by reducing parallellism in ubuntu, or by retrying them e.g. https://launchpad.net/ubuntu/+source/mia/2.4.3-2ubuntu1
[11:34] <LocutusOfBorg> arm64 built after three retries
[11:34] <LocutusOfBorg> I don't want such delta from Debian, but seems the infra has some issues :(
[11:50] <flocculant> anyone about who's got the power to fix the iso's and tracker, nothing landed for anyone since the 10th :)
[11:50] <cjwatson> Depends.  What's broken?
[11:51] <flocculant> cjwatson: for those I've looked at > lockfile: Sorry, giving up on "/srv/cdimage.ubuntu.com/etc/.lock-archive-sync" Couldn't acquire archive sync lock!
[11:51] <cjwatson> Oh, reboot damage
[11:51] <flocculant> at least Xubuntu and Ubuntu are like that currently, gnome and lubuntu were yesterday
[11:51] <cjwatson> Should be fixed now
[11:52] <flocculant> cjwatson: thanks :) - Xubuntu is probably stuck re-building from Saturday (manually) I assume that'll sort itself when the next one builds?
[11:53] <cjwatson> Should do
[11:53] <flocculant> k - thanks again :)
[12:35] <LocutusOfBorg> bye protobuf! /cc doko_
[12:39] <LocutusOfBorg> still some rebuilds are missing, but fcl migrated
[13:24] <LocutusOfBorg> but should we really rebuild stuff such as dialer-app address-book-app camera-app to have protobuf3 migrate?
[13:54]  * LocutusOfBorg fixes libphonenumber, that seems a blocker for the transition to end
[14:08] -queuebot:#ubuntu-release- Unapproved: accepted nvidia-graphics-drivers-367 [source] (xenial-proposed) [367.44-0ubuntu0.16.04.2]
[15:43] <sergiusens> infinity what are my options to get snapcraft-2.17 allowed into xenial-proposed?
[16:12] <apw> sergiusens, i see the yakkety version is failing its self-tests ?
[16:35] <sergiusens> apw yes, because snapd in yakkety is older than in xenial
[16:35] <apw> sergiusens, erp ... that isn't menat to happen
[16:36] <sergiusens> apw our xenial tests pass just fine fwiw https://github.com/snapcore/snapcraft/pull/787 (View Details there)
[16:36] <sergiusens> apw and right, that's why I ask, what are my options :-)
[16:37] <apw> sergiusens, i've asked (i hope) for a test of the yakkety one with the proposed snapd, which might clear that regression out
[16:37] <sergiusens> apw oh, is that possible from my end?
[16:38] <sergiusens> I "hope" it works, I am not sure, cjwatson do you know? ^
[16:39] <cjwatson> sergiusens: Well, apw said he's already triggered it.  It's not possible from your end
[16:40] <cjwatson> But archive admins can request that kind of thing
[16:40] <cjwatson> Assuming apw is talking about autopkgtests
[16:41] <sergiusens> cjwatson right, I was thinking of the key work you've done on snapd, I've been told that gpg transistions was one of the cultprits
[16:41] <sergiusens> cjwatson yeah, he is, well yeah, I assume as much
[16:41] <cjwatson> sergiusens: I don't see gpg failures in the log?
[16:42] <cjwatson> sergiusens: There was a lot of noise about the gpg transition, but it shouldn't actually break anything in snapd
[16:42] <apw> i am talking about adt indeed, though in the new world it is hard to tell if it has worked
[16:42] <apw> yep the failure i see in yakkety is using snap --force-something which is not present in the one in -release
[16:43] <sergiusens> good to know Colin (avoiding over pinging triggers now)
[16:43] <sergiusens> yeah, --force-dangerous was an unexpected surprise for us
[16:45] <ogra_> sergiusens, like ...everything ... related .... to ... snaps  ?
[16:47] <ogra_> (like having "grade: " added to snap.yaml in the ubuntu-core snap on release day ... and the store choking on it :P )
[16:48] <ogra_> the wonderful inter-team communication in snappy is resulting in a constant flow of suprises :)
[16:51] <cjwatson> Also everything is a huge rush and communication is the first thing to go
[16:52] <ogra_> yeah, sadly ... and it usually bites
[16:56] <sergiusens> ogra_ funny thing about grade was that it was a store folk contribution ;-)
[16:56] <ogra_> heh, yeah
[16:58] <ogra_> i still dont know what it is suppposed to do :)
[17:36] <sergiusens> cjwatson btw, why did it work at all given the dependency on snapd (>= 2.14.2~)? Maybe that is a pitti question
[17:37] <cjwatson> sergiusens: That dependency is only on integrationtest, and I think it's snapstest that failed
[17:38] <cjwatson> Er, integrationtests / snapstests respectively
[17:38] <sergiusens> yeah, I got it
[17:38] <sergiusens> thanks
[17:38] <cjwatson> snapstest has a tighter dep now
[17:38] <cjwatson> But maybe that wasn't in that release?
[17:38] <cjwatson> Haven't looked very closely
[17:53] <apw> sergiusens, ok there is now a yakkety ADT run which appears to have the yakkety-proposed version of snapd, but the tests appear to fail still
[17:53] <apw> Get:44 http://ftpmaster.internal/ubuntu yakkety-proposed/main amd64 snapd amd64 2.14.2+gitcc9d039-0ubuntu5 [7,665 kB]
[17:59] <sergiusens> apw where are those logs?
[18:01] <apw> sergiusens, http://autopkgtest.ubuntu.com/packages/s/snapcraft/yakkety/amd64
[18:01] <apw> sergiusens, note the one at the top with twin triggers
[18:11] <sergiusens> apw great, snapd 2.14 in xenial has `--force-dangerous` while snapd in yakkety has just `--dangerous` :-(
[18:11]  * sergiusens blames ogra_
[18:12] <ogra_> haha+
[18:12] <ogra_> sergiusens, xenial-proposed should have --dangerous too
[18:12] <ogra_> yay for stable APIs
[18:13] <apw> ogra_, there is no snapd in xenial-proposed
[18:13] <ogra_> well, there will be :)
[18:13] <sergiusens> ogra_ 2.14 in xenial does NOT have `--dangerous`
[18:14] <ogra_> (i havent invented that option btw)
[18:14] <ogra_> complain to gustavo
[18:14] <sergiusens> ogra_ 2.14 is in xenial-updates!
[18:14] <ogra_> i know that trunk has --dangerous
[18:14] <ogra_> and that it is supposed to land ASAP
[18:15] <ogra_> (if it doesnt get renamed inbetween :P )
[18:16] <apw> ogra_, without backwards compatibility ?
[18:16] <apw> sergiusens, it sounds like we need to work out what is meant to be where here
[18:16] <ogra_> apw, really ask sommeone who is in charge ... i'm suffering the same way as you do
[18:17] <ogra_> afaik it is a gustavo thing
[18:17] <ogra_> though perhaps he is also just the messenger
[18:23] <sergiusens> apw I have no words
[18:23]  * sergiusens is jus upset
[18:23] <sergiusens> just*
[18:29] <apw> sergiusens, just trying to help
[18:34] <sergiusens> apw and I appreciate that :-) I am not upset at you, just the situtation really
[18:51] <sergiusens> apw if I upload tests that use --dangerous instead of --force-dangerous to yakkety will you trigger that magic to use snapd from proposed?
[18:55] <apw> sergiusens, can do
[19:47] -queuebot:#ubuntu-release- New binary: wireshark [ppc64el] (yakkety-proposed/universe) [2.2.0+g5368c50-1] (no packageset)
[19:49] -queuebot:#ubuntu-release- New binary: wireshark [s390x] (yakkety-proposed/universe) [2.2.0+g5368c50-1] (no packageset)
[19:51] -queuebot:#ubuntu-release- New binary: wireshark [i386] (yakkety-proposed/universe) [2.2.0+g5368c50-1] (no packageset)
[19:55] -queuebot:#ubuntu-release- New binary: wireshark [powerpc] (yakkety-proposed/universe) [2.2.0+g5368c50-1] (no packageset)
[19:56] -queuebot:#ubuntu-release- New binary: wireshark [amd64] (yakkety-proposed/universe) [2.2.0+g5368c50-1] (no packageset)
[20:10] -queuebot:#ubuntu-release- Unapproved: cloud-init (xenial-proposed/main) [0.7.7~bzr1256-0ubuntu1~16.04.1 => 0.7.7-31-g65ace7b-0ubuntu1~16.04.1] (edubuntu, ubuntu-cloud, ubuntu-server)
[20:11] -queuebot:#ubuntu-release- New binary: wireshark [armhf] (yakkety-proposed/universe) [2.2.0+g5368c50-1] (no packageset)
[20:11] <elopio> sergiusens: ah, I remember why I wasn't in this channel. queuebot triggers a notification for me on every message.
[20:18] -queuebot:#ubuntu-release- New binary: clblas [amd64] (yakkety-proposed/universe) [2.10-4] (no packageset)
[20:18] -queuebot:#ubuntu-release- New binary: clblas [ppc64el] (yakkety-proposed/universe) [2.10-4] (no packageset)
[20:18] -queuebot:#ubuntu-release- New binary: clfft [i386] (yakkety-proposed/universe) [2.12.2-1] (no packageset)
[20:18] -queuebot:#ubuntu-release- New binary: clblas [i386] (yakkety-proposed/universe) [2.10-4] (no packageset)
[20:18] -queuebot:#ubuntu-release- New binary: clfft [ppc64el] (yakkety-proposed/universe) [2.12.2-1] (no packageset)
[20:18] -queuebot:#ubuntu-release- New binary: clfft [amd64] (yakkety-proposed/universe) [2.12.2-1] (no packageset)
[20:21] -queuebot:#ubuntu-release- New binary: clfft [armhf] (yakkety-proposed/universe) [2.12.2-1] (no packageset)
[20:21] -queuebot:#ubuntu-release- New binary: clfft [s390x] (yakkety-proposed/universe) [2.12.2-1] (no packageset)
[20:22] -queuebot:#ubuntu-release- New binary: clblas [arm64] (yakkety-proposed/universe) [2.10-4] (no packageset)
[20:22] -queuebot:#ubuntu-release- New binary: clfft [powerpc] (yakkety-proposed/universe) [2.12.2-1] (no packageset)
[20:22] -queuebot:#ubuntu-release- New binary: clblas [s390x] (yakkety-proposed/universe) [2.10-4] (no packageset)
[20:25] -queuebot:#ubuntu-release- New binary: clblas [powerpc] (yakkety-proposed/universe) [2.10-4] (no packageset)
[20:26] -queuebot:#ubuntu-release- New binary: wireshark [arm64] (yakkety-proposed/universe) [2.2.0+g5368c50-1] (no packageset)
[20:30] -queuebot:#ubuntu-release- New binary: clblas [armhf] (yakkety-proposed/universe) [2.10-4] (no packageset)
[20:31] -queuebot:#ubuntu-release- New binary: clfft [arm64] (yakkety-proposed/universe) [2.12.2-1] (no packageset)
[20:42] <sergiusens> apw if you don't mind, the latest snapcraft is already published in yakkety-proposed
[20:47] -queuebot:#ubuntu-release- New sync: libcmrt (yakkety-proposed/primary) [1.0.6+dfsg1-1]
[20:47] -queuebot:#ubuntu-release- New binary: winff [amd64] (yakkety-proposed/universe) [1.5.3-7ubuntu1] (no packageset)
[21:06] -queuebot:#ubuntu-release- Unapproved: rejected init-system-helpers [source] (xenial-proposed) [1.29ubuntu3]
[21:07] -queuebot:#ubuntu-release- Unapproved: init-system-helpers (xenial-proposed/main) [1.29ubuntu2 => 1.29ubuntu3] (core)
[22:36] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (xenial-proposed) [2.408.4]