/srv/irclogs.ubuntu.com/2016/10/14/#ubuntu-release.txt

infinitybdmurray: 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. :P00:38
-queuebot:#ubuntu-release- Unapproved: accepted ubuntu-release-upgrader [sync] (yakkety-updates) [1:16.10.7]00:38
bdmurrayvalorie: that'll fix it00:49
bdmurrayinfinity: hmm, I think sru-release didn't complain00:49
-queuebot:#ubuntu-release- Unapproved: accepted initramfs-tools [source] (xenial-proposed) [0.122ubuntu8.5]01:19
valoriethanks, bdmurray01:30
cjwatsonxnox: it's a toy on my laptop, and mostly just a passive-aggressive thing that there's no way I'm committing anywhere01:32
valoriehmmm, 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/ReleaseNotes01:35
cjwatsonvalorie: http://archive.ubuntu.com/ubuntu/dists/yakkety-updates/main/dist-upgrader-all/current/ReleaseAnnouncement.html01:35
valorie\o/01:35
valorieI wanted a good link to send to my lists01:35
valoriethanks cjwatson01:35
bdmurrayvalorie: I'll be changing where the meeta-release file points now so it goes to yakkety-updates01:55
valoriecool01:56
wxlbdmurray: i don't think the vegetarians will like that02:09
infinitybdmurray: sru-release wouldn't complain, the copy worked.  It just got stuck in unapproved. :P02:20
pittiroaksoax: someone recently copied it already, so maas is all good05:29
-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)06:21
bittinUpdated to Yakkety at work now aswell :)09:01
-queuebot:#ubuntu-release- Unapproved: multipath-tools (trusty-proposed/main) [0.4.9-3ubuntu7.14 => 0.4.9-3ubuntu7.15] (core)09:49
-queuebot:#ubuntu-release- Unapproved: mate-optimus (yakkety-proposed/universe) [16.10.0-1 => 16.10.1-1] (ubuntu-mate) (sync)11:22
=== Guest76323 is now known as tlbr
infinitypitti: Incoming xenial glibc SRU.12:50
infinitypitti: If you want to pre-review, the source is in https://launchpad.net/~adconrad/+archive/ubuntu/staging/+packages12:50
infinitypitti: (Sadly, LP seems to have failed to provide a useful diff, so you get to diff locally)12:50
infinityapw: ^-- Or you.12:53
* apw looks up, huh what, ok12:57
pittiinfinity: my minions will be pleased!12:59
* pitti kills the xenial linux test, apparenlty that's affected by the "kill sshd" bug as well12:59
infinitypitti: You have minions?12:59
pittiyou don't?13:00
infinitypitti: Oh, the signal6 XFAIL?13:00
pittiinfinity: no, bug 163225213:00
ubot5bug 1632252 in linux (Ubuntu Yakkety) "linux autopkgtest kills sshd in testbed" [Medium,Confirmed] https://launchpad.net/bugs/163225213:00
infinityIt'll certainly make autopkgtest results look less crap.13:00
infinitypitti: I meant the XFAIL would make your minions happy. :P13:01
infinityI have no idea how to fix your other bug, sorry. :P13:01
apwinfinity, will pm you some questions on this upload13:10
-queuebot:#ubuntu-release- New: accepted python-mock-services [source] (xenial-proposed) [0.2-0ubuntu0.16.04.1]13:18
-queuebot:#ubuntu-release- New binary: python-mock-services [amd64] (xenial-proposed/universe) [0.2-0ubuntu0.16.04.1] (no packageset)13:23
-queuebot:#ubuntu-release- New: accepted python-mock-services [amd64] (xenial-proposed) [0.2-0ubuntu0.16.04.1]13:24
apwinfinity, overall that looks "large" but as it is coming from a stable upstream i think that looks fine to me13:28
infinityapw: I assure you that the glibc stable branches are much more stable than a certain package you maintain. ;)13:29
apwinfinity, indeed fully believed :)13:29
-queuebot:#ubuntu-release- Unapproved: glibc (xenial-proposed/main) [2.23-0ubuntu3 => 2.23-0ubuntu4] (core) (sync)14:13
-queuebot:#ubuntu-release- Unapproved: accepted glibc [sync] (xenial-proposed) [2.23-0ubuntu4]14:19
-queuebot:#ubuntu-release- Unapproved: accepted neutron [source] (xenial-proposed) [2:8.3.0-0ubuntu1]15:34
-queuebot:#ubuntu-release- Unapproved: accepted neutron-lbaas [source] (xenial-proposed) [2:8.3.0-0ubuntu1]15:40
-queuebot:#ubuntu-release- Unapproved: accepted sudo [source] (trusty-proposed) [1.8.9p5-1ubuntu1.3]15:58
-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:16
-queuebot:#ubuntu-release- Unapproved: accepted strongswan [source] (trusty-proposed) [5.1.2-0ubuntu2.5]16:21
-queuebot:#ubuntu-release- Unapproved: multipath-tools (trusty-proposed/main) [0.4.9-3ubuntu7.14 => 0.4.9-3ubuntu7.15] (core)16:27
-queuebot:#ubuntu-release- Unapproved: accepted preseed [source] (trusty-proposed) [1.62ubuntu1.1]16:28
-queuebot:#ubuntu-release- Packageset: Added directfb to lubuntu in yakkety16:37
-queuebot:#ubuntu-release- Packageset: Added libgsf to lubuntu in yakkety16:37
-queuebot:#ubuntu-release- Packageset: Added nemo to lubuntu in yakkety16:37
-queuebot:#ubuntu-release- Packageset: Added makedev to lubuntu in yakkety16:37
-queuebot:#ubuntu-release- Packageset: Added libdca to lubuntu in yakkety16:37
-queuebot:#ubuntu-release- Unapproved: accepted multipath-tools [source] (trusty-proposed) [0.4.9-3ubuntu7.15]17:22
balloonsCan someone have a look at juju-core upload into xenial?17:51
balloonsHappy post-release day to you all!17:52
-queuebot:#ubuntu-release- Unapproved: ifupdown (yakkety-proposed/main) [0.8.13ubuntu2 => 0.8.13ubuntu3] (core)17:56
stokachubdmurray: you available to look at a SRU for juju-core?18:01
bdmurrayI think its slangasek's day18:01
stokachuthanks18:01
stokachuwhat happens if a package is uploaded to yakkety-proposed while the archive is closed?18:03
stokachudoes it go into zany automatically or do you have to reupload?18:04
naccstokachu: well, z will open with a copy-forward of y, i think18:05
nacci'm not sure how that plays with -proposed only packages, though18:05
-queuebot:#ubuntu-release- Unapproved: python-pylxd (xenial-proposed/main) [2.0.5-0ubuntu1 => 2.0.5-0ubuntu1.1] (ubuntu-server)18:05
stokachunacc: ok thanks for the info18:08
naccstokachu: funnily enough, i just asked slangasek the same sort of question in #ubuntu-devel :)18:09
apwaiui we copy y-proposed forward to z-proposed normally when it opens18:12
naccapw: that would make sense18:13
stokachuok cool18:18
=== 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
-queuebot:#ubuntu-release- New source: ibm-java80 (xenial-proposed/partner) [8.0.3.0-3]19:34
=== cjwatson_ is now known as cjwatson
slangasekstokachu, balloons: I have some concerns about this xenial-proposed upload20:17
balloonsslangasek, ok, what's up?20:18
-queuebot:#ubuntu-release- New binary: linux-signed [amd64] (vivid-proposed/main) [3.19.0-72.80] (core, kernel)20:24
slangasekballoons: - 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 see20:25
slangasekgolang-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 no20:25
slangaseklonger does anything on your system"20:25
slangasekfwiw your architecture matching can also be more succinctly written as case $ARCH in amd64|arm64|ppc64el|s390x) <do stuff> ;; esac20:27
stokachuslangasek: i think the arch: any to arch: all we were told would not match existing systems with the 32bit package installed20:28
balloonsslangasek, I was hoping there was a better way to get arch, ack.20:28
slangasekstokachu: who told you this?20:28
stokachucyphermox i believe20:29
stokachuit was for the upgrade from xenial to yakkety20:29
slangasekstokachu: changing it to arch: all means that the package will be built precisely once, on the amd64 builders20:29
balloonsright -- wow20:29
slangasekso then you would be installing amd64 binaries on all architectures, and that's not what you want20:29
balloonswhy is it all20:29
slangasekI'm guessing cyphermox was describing something else when he said that20:30
balloonsperhaps the juju metapackage, which does makes sense as all20:30
balloonsanyways, slangasek I will update the package to GA then after fixing your concerns20:31
slangasekok20:31
balloonsit makes the diff even bigger, but I suppose makes more sense in this case.20:31
balloonsI was hoping to avoid the big diff20:31
-queuebot:#ubuntu-release- Unapproved: rejected juju-core [source] (xenial-proposed) [2.0~rc3-0ubuntu1.16.04.1]20:32
slangasekthe diff is already big, and I'm not going to be line-by-line'ing the upstream diff anyway20:32
balloonsslangasek, yea, we're just adding more debian changes as we go.. GA will have more20:32
stokachuballoons: it's probably worth then pulling the latest source down and updating your changelog with whats already there20:34
stokachuthat'll keep the changelog diff down to just a few lines20:34
-queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (vivid-proposed) [3.19.0-72.80]21:06
-queuebot:#ubuntu-release- New binary: linux-signed [amd64] (yakkety-proposed/main) [4.8.0-25.27] (core, kernel)22:23

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