/srv/irclogs.ubuntu.com/2016/09/12/#ubuntu-release.txt

LocutusOfBorgpitti, ping, please autopkgtest for ignition-transport/1.3.0-4: amd64: Regression ♻ , armhf: Always failed, i386: Always failed, ppc64el: Always failed, s390x: Always failed06:49
LocutusOfBorgignition-transport has a autpkgtestuite that runs well with protobuf3, and this is the last protobuf blocker for migration06:50
LocutusOfBorgdoko_, ^^^06:50
LocutusOfBorgfor your happiness :)06:50
LocutusOfBorgprotobuf should be run against ignition proposed, and vice-verssa06:51
* LocutusOfBorg exit06:51
pittiLogan: done06:52
pittiLogan: sorry, tab failure06:55
flocculantpitti: you know anything about images and archive sync lock? or will that be someone else later in the day07:01
pittiflocculant: I'm afraid I don't07:06
flocculantokey doke :)07:07
LocutusOfBorgplease accept mia from new, the rdeps are already in place thanks07:36
LocutusOfBorgthanks pitti and thanks irclogs service :)07:41
LocutusOfBorgmmm pitti I'm not sure it worked retrying against -proposed...07:49
pittiLocutusOfBorg: well, it's still in the queue07:56
pittihttp://autopkgtest.ubuntu.com/running#queue-ubuntu-yakkety-amd6407:56
LocutusOfBorgoh thanks, I though the queue wasn't visible with the new service08:01
LocutusOfBorglets see if protobuf can migrate today08:02
apwLocutusOfBorg, it was awol for a while (queues) and are now back with us08:51
-queuebot:#ubuntu-release- Unapproved: init-system-helpers (xenial-proposed/main) [1.29ubuntu2 => 1.29ubuntu3] (core)09:02
-queuebot:#ubuntu-release- Packageset: Added libmatemixer to ubuntu-mate in yakkety09:45
=== ant__ is now known as antdillon
LocutusOfBorgcjwatson, FYI, when a build goes ENOSPACE seems to be stuck forever https://launchpad.net/ubuntu/+source/insighttoolkit4/4.10.0-dfsg1-3ubuntu1/+build/1071295711:21
cjwatsonYeah, known11:23
cjwatsonJust cancel it, at some point I'll get round to working out how to test my fix for that in launchpad-buildd11:24
LocutusOfBorgthanks11:27
LocutusOfBorgif you need a tester, I'm here :)11:27
cjwatsonLocutusOfBorg: No, I don't mean manual testing.11:33
LocutusOfBorgok thanks11:33
LocutusOfBorgbtw, many packages started failing for ENOMEM or some other similar issues11:33
LocutusOfBorgI usually "fix" them by reducing parallellism in ubuntu, or by retrying them e.g. https://launchpad.net/ubuntu/+source/mia/2.4.3-2ubuntu111:34
LocutusOfBorgarm64 built after three retries11:34
LocutusOfBorgI don't want such delta from Debian, but seems the infra has some issues :(11:34
flocculantanyone about who's got the power to fix the iso's and tracker, nothing landed for anyone since the 10th :)11:50
cjwatsonDepends.  What's broken?11:50
flocculantcjwatson: 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
cjwatsonOh, reboot damage11:51
flocculantat least Xubuntu and Ubuntu are like that currently, gnome and lubuntu were yesterday11:51
cjwatsonShould be fixed now11:51
flocculantcjwatson: thanks :) - Xubuntu is probably stuck re-building from Saturday (manually) I assume that'll sort itself when the next one builds?11:52
cjwatsonShould do11:53
flocculantk - thanks again :)11:53
LocutusOfBorgbye protobuf! /cc doko_12:35
LocutusOfBorgstill some rebuilds are missing, but fcl migrated12:39
LocutusOfBorgbut should we really rebuild stuff such as dialer-app address-book-app camera-app to have protobuf3 migrate?13:24
* LocutusOfBorg fixes libphonenumber, that seems a blocker for the transition to end13:54
-queuebot:#ubuntu-release- Unapproved: accepted nvidia-graphics-drivers-367 [source] (xenial-proposed) [367.44-0ubuntu0.16.04.2]14:08
sergiusensinfinity what are my options to get snapcraft-2.17 allowed into xenial-proposed?15:43
apwsergiusens, i see the yakkety version is failing its self-tests ?16:12
sergiusensapw yes, because snapd in yakkety is older than in xenial16:35
apwsergiusens, erp ... that isn't menat to happen16:35
sergiusensapw our xenial tests pass just fine fwiw https://github.com/snapcore/snapcraft/pull/787 (View Details there)16:36
sergiusensapw and right, that's why I ask, what are my options :-)16:36
apwsergiusens, i've asked (i hope) for a test of the yakkety one with the proposed snapd, which might clear that regression out16:37
sergiusensapw oh, is that possible from my end?16:37
sergiusensI "hope" it works, I am not sure, cjwatson do you know? ^16:38
cjwatsonsergiusens: Well, apw said he's already triggered it.  It's not possible from your end16:39
cjwatsonBut archive admins can request that kind of thing16:40
cjwatsonAssuming apw is talking about autopkgtests16:40
sergiusenscjwatson right, I was thinking of the key work you've done on snapd, I've been told that gpg transistions was one of the cultprits16:41
sergiusenscjwatson yeah, he is, well yeah, I assume as much16:41
cjwatsonsergiusens: I don't see gpg failures in the log?16:41
cjwatsonsergiusens: There was a lot of noise about the gpg transition, but it shouldn't actually break anything in snapd16:42
apwi am talking about adt indeed, though in the new world it is hard to tell if it has worked16:42
apwyep the failure i see in yakkety is using snap --force-something which is not present in the one in -release16:42
sergiusensgood to know Colin (avoiding over pinging triggers now)16:43
sergiusensyeah, --force-dangerous was an unexpected surprise for us16:43
ogra_sergiusens, like ...everything ... related .... to ... snaps  ?16:45
ogra_(like having "grade: " added to snap.yaml in the ubuntu-core snap on release day ... and the store choking on it :P )16:47
ogra_the wonderful inter-team communication in snappy is resulting in a constant flow of suprises :)16:48
cjwatsonAlso everything is a huge rush and communication is the first thing to go16:51
ogra_yeah, sadly ... and it usually bites16:52
sergiusensogra_ funny thing about grade was that it was a store folk contribution ;-)16:56
ogra_heh, yeah16:56
ogra_i still dont know what it is suppposed to do :)16:58
sergiusenscjwatson btw, why did it work at all given the dependency on snapd (>= 2.14.2~)? Maybe that is a pitti question17:36
cjwatsonsergiusens: That dependency is only on integrationtest, and I think it's snapstest that failed17:37
cjwatsonEr, integrationtests / snapstests respectively17:38
sergiusensyeah, I got it17:38
sergiusensthanks17:38
cjwatsonsnapstest has a tighter dep now17:38
cjwatsonBut maybe that wasn't in that release?17:38
cjwatsonHaven't looked very closely17:38
apwsergiusens, ok there is now a yakkety ADT run which appears to have the yakkety-proposed version of snapd, but the tests appear to fail still17:53
apwGet:44 http://ftpmaster.internal/ubuntu yakkety-proposed/main amd64 snapd amd64 2.14.2+gitcc9d039-0ubuntu5 [7,665 kB]17:53
sergiusensapw where are those logs?17:59
apwsergiusens, http://autopkgtest.ubuntu.com/packages/s/snapcraft/yakkety/amd6418:01
apwsergiusens, note the one at the top with twin triggers18:01
sergiusensapw great, snapd 2.14 in xenial has `--force-dangerous` while snapd in yakkety has just `--dangerous` :-(18:11
* sergiusens blames ogra_18:11
ogra_haha+18:12
ogra_sergiusens, xenial-proposed should have --dangerous too18:12
ogra_yay for stable APIs18:12
apwogra_, there is no snapd in xenial-proposed18:13
ogra_well, there will be :)18:13
sergiusensogra_ 2.14 in xenial does NOT have `--dangerous`18:13
ogra_(i havent invented that option btw)18:14
ogra_complain to gustavo18:14
sergiusensogra_ 2.14 is in xenial-updates!18:14
ogra_i know that trunk has --dangerous18:14
ogra_and that it is supposed to land ASAP18:14
ogra_(if it doesnt get renamed inbetween :P )18:15
apwogra_, without backwards compatibility ?18:16
apwsergiusens, it sounds like we need to work out what is meant to be where here18:16
ogra_apw, really ask sommeone who is in charge ... i'm suffering the same way as you do18:16
ogra_afaik it is a gustavo thing18:17
ogra_though perhaps he is also just the messenger18:17
sergiusensapw I have no words18:23
* sergiusens is jus upset18:23
sergiusensjust*18:23
apwsergiusens, just trying to help18:29
sergiusensapw and I appreciate that :-) I am not upset at you, just the situtation really18:34
sergiusensapw if I upload tests that use --dangerous instead of --force-dangerous to yakkety will you trigger that magic to use snapd from proposed?18:51
apwsergiusens, can do18:55
-queuebot:#ubuntu-release- New binary: wireshark [ppc64el] (yakkety-proposed/universe) [2.2.0+g5368c50-1] (no packageset)19:47
-queuebot:#ubuntu-release- New binary: wireshark [s390x] (yakkety-proposed/universe) [2.2.0+g5368c50-1] (no packageset)19:49
-queuebot:#ubuntu-release- New binary: wireshark [i386] (yakkety-proposed/universe) [2.2.0+g5368c50-1] (no packageset)19:51
-queuebot:#ubuntu-release- New binary: wireshark [powerpc] (yakkety-proposed/universe) [2.2.0+g5368c50-1] (no packageset)19:55
-queuebot:#ubuntu-release- New binary: wireshark [amd64] (yakkety-proposed/universe) [2.2.0+g5368c50-1] (no packageset)19:56
-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:10
-queuebot:#ubuntu-release- New binary: wireshark [armhf] (yakkety-proposed/universe) [2.2.0+g5368c50-1] (no packageset)20:11
elopiosergiusens: ah, I remember why I wasn't in this channel. queuebot triggers a notification for me on every message.20:11
-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:18
-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:21
-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:22
-queuebot:#ubuntu-release- New binary: clblas [powerpc] (yakkety-proposed/universe) [2.10-4] (no packageset)20:25
-queuebot:#ubuntu-release- New binary: wireshark [arm64] (yakkety-proposed/universe) [2.2.0+g5368c50-1] (no packageset)20:26
-queuebot:#ubuntu-release- New binary: clblas [armhf] (yakkety-proposed/universe) [2.10-4] (no packageset)20:30
-queuebot:#ubuntu-release- New binary: clfft [arm64] (yakkety-proposed/universe) [2.12.2-1] (no packageset)20:31
sergiusensapw if you don't mind, the latest snapcraft is already published in yakkety-proposed20:42
-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)20:47
-queuebot:#ubuntu-release- Unapproved: rejected init-system-helpers [source] (xenial-proposed) [1.29ubuntu3]21:06
-queuebot:#ubuntu-release- Unapproved: init-system-helpers (xenial-proposed/main) [1.29ubuntu2 => 1.29ubuntu3] (core)21:07
-queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (xenial-proposed) [2.408.4]22:36

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!