[00:38] bdmurray: That would be because I haven't given ubuntu-sru queue admin perms on yakkety-updates yet, and you're not an AA. Accepted your copy. :P [00:38] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-release-upgrader [sync] (yakkety-updates) [1:16.10.7] [00:49] valorie: that'll fix it [00:49] infinity: hmm, I think sru-release didn't complain [01:19] -queuebot:#ubuntu-release- Unapproved: accepted initramfs-tools [source] (xenial-proposed) [0.122ubuntu8.5] [01:30] thanks, bdmurray [01:32] xnox: it's a toy on my laptop, and mostly just a passive-aggressive thing that there's no way I'm committing anywhere [01:35] hmmm, http://archive.ubuntu.com/ubuntu/dists/yakkety/main/dist-upgrader-all/current/ReleaseAnnouncement.html still links to the Xenial wiki page https://wiki.ubuntu.com/XenialXerus/ReleaseNotes [01:35] valorie: http://archive.ubuntu.com/ubuntu/dists/yakkety-updates/main/dist-upgrader-all/current/ReleaseAnnouncement.html [01:35] \o/ [01:35] I wanted a good link to send to my lists [01:35] thanks cjwatson [01:55] valorie: I'll be changing where the meeta-release file points now so it goes to yakkety-updates [01:56] cool [02:09] bdmurray: i don't think the vegetarians will like that [02:20] bdmurray: sru-release wouldn't complain, the copy worked. It just got stuck in unapproved. :P [05:29] roaksoax: someone recently copied it already, so maas is all good [06:21] -queuebot:#ubuntu-release- Unapproved: fcitx (xenial-proposed/main) [1:4.2.9.1-1ubuntu1 => 1:4.2.9.1-1ubuntu1.16.04.1] (input-methods, kubuntu, ubuntu-desktop) [09:01] Updated to Yakkety at work now aswell :) [09:49] -queuebot:#ubuntu-release- Unapproved: multipath-tools (trusty-proposed/main) [0.4.9-3ubuntu7.14 => 0.4.9-3ubuntu7.15] (core) [11:22] -queuebot:#ubuntu-release- Unapproved: mate-optimus (yakkety-proposed/universe) [16.10.0-1 => 16.10.1-1] (ubuntu-mate) (sync) === Guest76323 is now known as tlbr [12:50] pitti: Incoming xenial glibc SRU. [12:50] pitti: If you want to pre-review, the source is in https://launchpad.net/~adconrad/+archive/ubuntu/staging/+packages [12:50] pitti: (Sadly, LP seems to have failed to provide a useful diff, so you get to diff locally) [12:53] apw: ^-- Or you. [12:57] * apw looks up, huh what, ok [12:59] infinity: my minions will be pleased! [12:59] * pitti kills the xenial linux test, apparenlty that's affected by the "kill sshd" bug as well [12:59] pitti: You have minions? [13:00] you don't? [13:00] pitti: Oh, the signal6 XFAIL? [13:00] infinity: no, bug 1632252 [13:00] bug 1632252 in linux (Ubuntu Yakkety) "linux autopkgtest kills sshd in testbed" [Medium,Confirmed] https://launchpad.net/bugs/1632252 [13:00] It'll certainly make autopkgtest results look less crap. [13:01] pitti: I meant the XFAIL would make your minions happy. :P [13:01] I have no idea how to fix your other bug, sorry. :P [13:10] infinity, will pm you some questions on this upload [13:18] -queuebot:#ubuntu-release- New: accepted python-mock-services [source] (xenial-proposed) [0.2-0ubuntu0.16.04.1] [13:23] -queuebot:#ubuntu-release- New binary: python-mock-services [amd64] (xenial-proposed/universe) [0.2-0ubuntu0.16.04.1] (no packageset) [13:24] -queuebot:#ubuntu-release- New: accepted python-mock-services [amd64] (xenial-proposed) [0.2-0ubuntu0.16.04.1] [13:28] infinity, overall that looks "large" but as it is coming from a stable upstream i think that looks fine to me [13:29] apw: I assure you that the glibc stable branches are much more stable than a certain package you maintain. ;) [13:29] infinity, indeed fully believed :) [14:13] -queuebot:#ubuntu-release- Unapproved: glibc (xenial-proposed/main) [2.23-0ubuntu3 => 2.23-0ubuntu4] (core) (sync) [14:19] -queuebot:#ubuntu-release- Unapproved: accepted glibc [sync] (xenial-proposed) [2.23-0ubuntu4] [15:34] -queuebot:#ubuntu-release- Unapproved: accepted neutron [source] (xenial-proposed) [2:8.3.0-0ubuntu1] [15:40] -queuebot:#ubuntu-release- Unapproved: accepted neutron-lbaas [source] (xenial-proposed) [2:8.3.0-0ubuntu1] [15:58] -queuebot:#ubuntu-release- Unapproved: accepted sudo [source] (trusty-proposed) [1.8.9p5-1ubuntu1.3] [16:16] -queuebot:#ubuntu-release- Unapproved: rejected multipath-tools [source] (trusty-proposed) [0.4.9-3ubuntu7.15] [16:16] -queuebot:#ubuntu-release- Unapproved: rejected multipath-tools [source] (trusty-proposed) [0.4.9-3ubuntu7.15] [16:21] -queuebot:#ubuntu-release- Unapproved: accepted strongswan [source] (trusty-proposed) [5.1.2-0ubuntu2.5] [16:27] -queuebot:#ubuntu-release- Unapproved: multipath-tools (trusty-proposed/main) [0.4.9-3ubuntu7.14 => 0.4.9-3ubuntu7.15] (core) [16:28] -queuebot:#ubuntu-release- Unapproved: accepted preseed [source] (trusty-proposed) [1.62ubuntu1.1] [16:37] -queuebot:#ubuntu-release- Packageset: Added directfb to lubuntu in yakkety [16:37] -queuebot:#ubuntu-release- Packageset: Added libgsf to lubuntu in yakkety [16:37] -queuebot:#ubuntu-release- Packageset: Added nemo to lubuntu in yakkety [16:37] -queuebot:#ubuntu-release- Packageset: Added makedev to lubuntu in yakkety [16:37] -queuebot:#ubuntu-release- Packageset: Added libdca to lubuntu in yakkety [17:22] -queuebot:#ubuntu-release- Unapproved: accepted multipath-tools [source] (trusty-proposed) [0.4.9-3ubuntu7.15] [17:51] Can someone have a look at juju-core upload into xenial? [17:52] Happy post-release day to you all! [17:56] -queuebot:#ubuntu-release- Unapproved: ifupdown (yakkety-proposed/main) [0.8.13ubuntu2 => 0.8.13ubuntu3] (core) [18:01] bdmurray: you available to look at a SRU for juju-core? [18:01] I think its slangasek's day [18:01] thanks [18:03] what happens if a package is uploaded to yakkety-proposed while the archive is closed? [18:04] does it go into zany automatically or do you have to reupload? [18:05] stokachu: well, z will open with a copy-forward of y, i think [18:05] i'm not sure how that plays with -proposed only packages, though [18:05] -queuebot:#ubuntu-release- Unapproved: python-pylxd (xenial-proposed/main) [2.0.5-0ubuntu1 => 2.0.5-0ubuntu1.1] (ubuntu-server) [18:08] nacc: ok thanks for the info [18:09] stokachu: funnily enough, i just asked slangasek the same sort of question in #ubuntu-devel :) [18:12] aiui we copy y-proposed forward to z-proposed normally when it opens [18:13] apw: that would make sense [18:18] ok cool === nacc_ is now known as nacc === xnox_ is now known as xnox === mterry_ is now known as mterry === Trevinho_ is now known as Trevinho === wolsen_ is now known as wolsen === kees_ is now known as kees [19:34] -queuebot:#ubuntu-release- New source: ibm-java80 (xenial-proposed/partner) [8.0.3.0-3] === cjwatson_ is now known as cjwatson [20:17] stokachu, balloons: I have some concerns about this xenial-proposed upload [20:18] slangasek, ok, what's up? [20:24] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (vivid-proposed/main) [3.19.0-72.80] (core, kernel) [20:25] balloons: - changelog not derived from previous SRU, which makes it impossible to read; this should be condensed to a single changelog entry with a single bug reference for SRU tracking bug. - re-vendorizing of golang-golang-x-crypto, which I let into yakkety because of timing but am not willing to accept into xenial without an explicit Security Team signoff (I would prefer to see [20:25] golang-golang-x-crypto updated first). - juju-2.0 changed from arch: any to arch: all, which is 100% wrong and broken. - unnecessary call to dpkg --print-architecture in config script, you can just use $DPKG_MAINTSCRIPT_ARCH from the environment instead. - would like to see the "your architecture not supported" message be more verbose, "not supported" doesn't quite express "this package no [20:25] longer does anything on your system" [20:27] fwiw your architecture matching can also be more succinctly written as case $ARCH in amd64|arm64|ppc64el|s390x) ;; esac [20:28] slangasek: i think the arch: any to arch: all we were told would not match existing systems with the 32bit package installed [20:28] slangasek, I was hoping there was a better way to get arch, ack. [20:28] stokachu: who told you this? [20:29] cyphermox i believe [20:29] it was for the upgrade from xenial to yakkety [20:29] stokachu: changing it to arch: all means that the package will be built precisely once, on the amd64 builders [20:29] right -- wow [20:29] so then you would be installing amd64 binaries on all architectures, and that's not what you want [20:29] why is it all [20:30] I'm guessing cyphermox was describing something else when he said that [20:30] perhaps the juju metapackage, which does makes sense as all [20:31] anyways, slangasek I will update the package to GA then after fixing your concerns [20:31] ok [20:31] it makes the diff even bigger, but I suppose makes more sense in this case. [20:31] I was hoping to avoid the big diff [20:32] -queuebot:#ubuntu-release- Unapproved: rejected juju-core [source] (xenial-proposed) [2.0~rc3-0ubuntu1.16.04.1] [20:32] the diff is already big, and I'm not going to be line-by-line'ing the upstream diff anyway [20:32] slangasek, yea, we're just adding more debian changes as we go.. GA will have more [20:34] balloons: it's probably worth then pulling the latest source down and updating your changelog with whats already there [20:34] that'll keep the changelog diff down to just a few lines [21:06] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (vivid-proposed) [3.19.0-72.80] [22:23] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (yakkety-proposed/main) [4.8.0-25.27] (core, kernel)