[00:15] <slangasek> powersj: thanks. dmesg output there shows no cdroms detected; which suggests a separate kernel issue from the ones we knew about :/
[00:15] <slangasek> powersj: looks like this is inside of a VM, how is the CD set up - virtio?
[00:22] <infinity> slangasek: virtio did indeed go modular between 4.4 and 4.8.  Could be yet another missing module in a udeb.
[00:23] <infinity> Or a missing udeb in the initrd.
[00:23]  * infinity looks.
[00:24] <infinity> virtio-modules-udeb is included in the cdrom initrd.  But it could be missing modules.
[00:25] <infinity> Hrm, no.  virtio-udeb looks complete to me.
[00:27] <infinity> -16 in the kernel team PPA has some more potentially relevant fixes, though.
[00:27] <infinity> Like re-enabling CONFIG_ATA...
[00:28] <infinity> powersj: A dump of the qemu commandline would be quite helpful there.
[00:29] <slangasek> I imagine he's replicating the qa smoketest
[00:29] <slangasek> so wherever that code lives, again
[00:31] <slangasek> this may mean that the actual qemu commandline is somewhere in utah
[00:33] <cyphermox> yep
[00:33] <infinity> Well, if he has access to the host, it's in "ps"
[00:33] <infinity> Which is the CLI I really want to see, not some libvirt xml or something.
[00:33] <slangasek> yes, if he's not EOD
[00:33] <infinity> Ds E?
[00:34] <cyphermox> I think the command-line might have been 2016-09-22 13:47:50,824 utah-21462-yakkety-server-amd64 INFO: Boot command line is: netcfg/get_hostname=utah-21462-yakkety-server-amd64 log_host=192.168.122.1 log_port=0 DEBCONF_DEBUG=developer debconf/priority=critical
[00:35] <infinity> The qemu commandline, not the kernel commandline.
[00:35] <slangasek> right
[00:35] <cyphermox> oh, right :)
[00:48] <powersj> slangasek, qemu-system-x86_64 -enable-kvm -boot d -hda vdisk.img -cpu host -m 1024 -cdrom yakkety-server-amd64.iso -serial mon:stdio
[00:49] <powersj> that is probably not what the qa smoke test uses, but what I have been using to do installs with preseeded isos, so just copied it over today for this
[00:49] -queuebot:#ubuntu-release- Unapproved: gsfonts (yakkety-proposed/main) [1:8.11+urwcyr1.0.7~pre44-4.2ubuntu1 => 1:8.11+urwcyr1.0.7~pre44-4.3] (desktop-core, ubuntu-server) (sync)
[00:49] <nacc> doko: --^ taht should fix the gsfonts ftbfs as well
[00:49] <cyphermox> powersj: the smoke tests run something very similar, but it's in ugly xml
[00:49] <cyphermox> infinity: ide cdrom.
[00:50] <slangasek> so indeed that sounds like the next kernel fixes it
[00:50] <infinity> Seems likely indeed.
[00:51] <cyphermox> fwiw I went to look at config/utah/default-vm.xml in utah source; that gets rewritten to something-default-bridged-vm.xml but the cd bits don't change.
[00:54] <powersj> slangasek, infinity, anything else you'd like me to run before I jet off again?
[00:55] <slangasek> powersj: sounds like you've given us enough to reproduce the problem, thanks
[00:55] <powersj> ok!
[00:57] <slangasek> doko: pygobject sync, looks like that's nothing that needs an FFe, it's just the stable release?  should I release it from unapproved for you?
[01:00] -queuebot:#ubuntu-release- Unapproved: accepted libabw [source] (yakkety-proposed) [0.1.1-4ubuntu1]
[01:04] -queuebot:#ubuntu-release- New binary: libabw [ppc64el] (yakkety-proposed/main) [0.1.1-4ubuntu1] (kubuntu, ubuntu-desktop)
[01:05] -queuebot:#ubuntu-release- New binary: libabw [amd64] (yakkety-proposed/main) [0.1.1-4ubuntu1] (kubuntu, ubuntu-desktop)
[01:05] -queuebot:#ubuntu-release- New binary: libabw [arm64] (yakkety-proposed/main) [0.1.1-4ubuntu1] (kubuntu, ubuntu-desktop)
[01:06] -queuebot:#ubuntu-release- New binary: libabw [armhf] (yakkety-proposed/main) [0.1.1-4ubuntu1] (kubuntu, ubuntu-desktop)
[01:06] -queuebot:#ubuntu-release- New binary: libabw [i386] (yakkety-proposed/main) [0.1.1-4ubuntu1] (kubuntu, ubuntu-desktop)
[01:17] -queuebot:#ubuntu-release- New binary: libabw [s390x] (yakkety-proposed/main) [0.1.1-4ubuntu1] (kubuntu, ubuntu-desktop)
[01:24] -queuebot:#ubuntu-release- New binary: libabw [powerpc] (yakkety-proposed/main) [0.1.1-4ubuntu1] (kubuntu, ubuntu-desktop)
[02:24] -queuebot:#ubuntu-release- Unapproved: gnome-software (yakkety-proposed/main) [3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu2 => 3.20.1+git20160923.1.0c571f1-0ubuntu1] (ubuntu-desktop)
[02:25] <rcj> infinity, yakkety cloud builds are failing for powerpc.  I'm seeing "No kernel output for powerpc64-smp!" in the livecd-rootfs output.
[02:26] <rcj> And maybe that's the relevant failure, and maybe it isn't.  I'm not 100%
[02:29] <rcj> cjwatson, ^
[02:30] <rcj> wgrant, ^
[02:30] <rcj> :)
[02:30] <wgrant> rcj: Do you have a build link?
[02:31] <rcj> wgrant, https://launchpad.net/~cloudware/+livefs/ubuntu/yakkety/cpc/+build/76265
[02:32] <wgrant> rcj "cp: cannot stat '/usr/bin/qemu-powerpc-static': No such file or directory" looks like the fatal line to me.
[02:32] <wgrant> Why's it trying to cross when it's native?
[02:32] <rcj> oh, that is or'ed with 'true'
[02:32] <wgrant> Fri, 23 Sep 2016 01:48:23 +0000: arch: powerpc rel: yakkety host_arch: ppc
[02:32] <wgrant> Fri, 23 Sep 2016 01:48:23 +0000: qemu_arch=powerpc cross=true
[02:33] <rcj> You'll see that traceback is followed by "BUILD FAILED; continuing without blocking" so we trapped on the exit and exit'ed 0
[02:34] <rcj> I'm leaving the maas bit in there so they can see that particular error and fix it.
[02:37] <wgrant> Ah, indeed.
[02:37] <wgrant> The kernel thing probably is fatal.
[02:38] <wgrant> rcj: The powerpc64-smp flavour doesn't exist in yakkety.
[02:39] <wgrant> powerpc-smp and powerpc64-emb do.
[02:39] <wgrant> I haven't followed the flavour changes this cycle, so I'm not sure what the intent is.
[02:39] <rcj> Maybe our livecd-rootfs is old?
[02:40] <gaughen_> rcj, this worked the other day though right?
[02:40] <wgrant> livecd-rootfs (2.432) yakkety; urgency=medium
[02:40] <wgrant>   * Use the virtual kernel for the powerpc64 cpc images (LP: #1625368)
[02:40] <ubot5`> Launchpad bug 1625368 in Ubuntu CD Images "Rename powerpc64-smp kernel to generic" [Undecided,New] https://launchpad.net/bugs/1625368
[02:40] <wgrant> Do you have that change?
[02:40] <wgrant> https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1625368
[02:40] <wgrant> I suspect you're missing that.
[02:40] <gaughen> rcj, we have a successful daily from 0918
[02:40] <rcj> wgrant, that would do it.
[02:41]  * gaughen nods
[02:41] <rcj> wgrant, so I'll try that, so what are your thoughts on this arm64 failure... https://launchpad.net/~cloudware/+livefs/ubuntu/yakkety/cpc/+build/76263
[02:42] <wgrant> rcj: Hm, is flash-kernel needed now that the images are UEFI?
[02:43] -queuebot:#ubuntu-release- Unapproved: gnome-software (xenial-proposed/main) [3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1 => 3.20.1+git20160923.1.0c571f1-0ubuntu1~xenial1] (ubuntu-desktop)
[02:44] <wgrant> Oh, it's removing the kernel, huh.
[02:44] <wgrant> Why is it removing the kernel
[02:44] <rcj> it's creating a squashfs for container deployment (lxd and others)
[02:44] <wgrant> Ah
[02:44] <wgrant> When did that appear to break?
[02:45] <wgrant> There are no recent relevant changes to flash-kernel.
[02:45] <rcj> It last worked on sept20th
[02:46] <rcj> https://launchpad.net/~cloudware/+livefs/ubuntu/yakkety/cpc/+build/76008
[02:48] <wgrant> rcj: Oh, the kernel hook might be dodgy.
[02:48] <wgrant> It's not passing in the abi, I suspect.
[02:48] <wgrant> To zz-flash-kernel
[02:48]  * wgrant checks.
[02:50] <infinity> rcj: Is this in a livecd-rootfs fork?
[02:51] <infinity> rcj: Cause the archive version doesn't reference powerpc64-smp.
[02:51] <infinity> rcj: Ahh, I see wgrant got there.
[02:52]  * xnox says 20101020ubuntu476 is good on s390x. no cdroms, and no efi either.
[02:52] <rcj> infinity, yes.  We were told to run production from a fork because lp:livecd-rootfs trunk wasn't considered stable by foundations.
[02:52] <infinity> rcj: Err, really?
[02:52] <infinity> *blink*
[02:52]  * gaughen once again nods
[02:52] <infinity> I'd really rather you get everything into trunk and not use a fork.
[02:53] <xnox> infinity vs slangasek
[02:53] <rcj> infinity, we're not forked with changes, we're just running older code so as not to be at tip
[02:53] <xnox> infinity, some bits of gaughen & rcj are proprietary.
[02:53] <infinity> rcj: Yeah, which leads to this. :/
[02:53] <gaughen> xnox, sssh nobody is supposed to know about  my bionic pinky
[02:53] <infinity> Oh well.
[02:54] <rcj> infinity, but clearly that's not well known since we didn't know to move forward to pick up a commit with 'cpc' in the title
[02:55] <rcj> infinity, so we're not syncing from trunk often enough.
[02:55] <gaughen> yup, sounds like we need to revisit the frequency, but I think that's a discussion for after  final beta
[02:55] <rcj> and we're back at r1386, so this will be fun tonight.
[02:56] <rcj> gaughen, absolutely
[02:57] <wgrant> rcj: I can't obviously see why flash-kernel is broken. It looks like it for some reason wasn't running the trigger in the successful build.
[02:57] <wgrant> It should have always failed.
[02:57] <wgrant> AFAICS
[02:58] <wgrant> Oh, there's an exit 0 there.
[02:58] <rcj> wgrant, This is the hook http://bazaar.launchpad.net/~ubuntu-core-dev/livecd-rootfs/trunk/view/head:/live-build/ubuntu-cpc/hooks/032-root-squashfs.binary
[02:58] <rcj> wgrant, where?
[03:00] <wgrant> Removing linux-image-extra-4.8.0-15-generic (4.8.0-15.16) ...
[03:00] <wgrant> run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.8.0-15-generic /boot/vmlinuz-4.8.0-15-generic
[03:00] <wgrant> Why is removal of -extra executing postinst.d?
[03:00] <wgrant> That's the thing that is newly firing the trigger that eventually causes the failure during removal of the next package.
[03:00] <rcj> infinity, and we're updating from released packages, so we wouldn't get your change yet anyhow. :/
[03:01] <wgrant> It seems deliberate, in control-scripts/extra-post, hm.
[03:02] <wgrant> Oh
[03:02] <wgrant> rcj: So the breakage is because linux-image-extra-$version is being installed now.
[03:02] <wgrant> I wonder if the linux linux-image-$version Recommends it.
[03:02] <wgrant> There's an underlying bug in the triggers that's been there for a while, but it's only tickled now because linux-image-extra's removal is refiring the postinst trigger.
[03:04] <wgrant> Or the 4.4 arm64 linux-image-generic didn't depend on linux-image-extra, I suppose.
[03:05] <wgrant> rcj: So you can either get flash-kernel's zz-flash-kernel to not die in these conditions, or avoid installing linux-image-extra in the first place.
[03:09] <bjf> gaughen, here
[03:09] <bjf> gaughen, reading
[03:11] <wgrant> I imagine this is reproducible on any yakkety arm64 system by installing flash-kernel and linux-image-generic, then removing linux-image-*
[03:11] <bjf> infinity, how is kernel? do i need to call in reinforcements?
[03:11] <wgrant> Which will cause the flash-kernel trigger to be queued by linux-image-extra-*'s removal, then uninstall linux-image-*, then run the trigger and crash.
[03:13] <bjf> wgrant, arm64 needs linux-image-extra now .. that's a recent change
[03:13] <infinity> rcj: Oh, if you're having issues with arm64, you need to s/generic/virtual/
[03:14] <infinity> But f-k being triggered twice is also a bug.
[03:14] <wgrant> This is just flash-kernel's hackish existence finally biting.
[03:14] <wgrant> Seems to not enjoy life when rerun without any kernels installed.
[03:20] <gaughen> thanks bjf
[03:24] <infinity> gaughen: Note that he means generic now depends on extra, but you guys should switch to virtual.
[03:25] <infinity> rcj: ^
[03:25] <gaughen> infinity, arm64 using generic is an intentional change, afaik
[03:26] <gaughen> well not a change, it's been using generic for a while now
[03:26] <gaughen> and I don't think we should make that switch to virtual today/tomorrow
[03:27] <rcj> gaughen, infinity: I'm looking for 'bzr blame' right now to see if we have a reason
[03:29] <infinity> gaughen: Yes, because virtual didn't used to exist.
[03:29] <infinity> gaughen: The virtual/extra split is new.
[03:29] <infinity> Should be the same as the fix I did for powerpc.
[03:29] <gaughen> aaah okay
[03:31] <infinity> rcj: ^
[03:32] <rcj> infinity, thank you
[03:39] <rcj> infinity, Shall I submit an MP for lp:livecd-rootfs  to drop that for arm64?  Or is it better from foundations?
[03:46] <infinity> rcj: Don't care who does it.
[03:46] <infinity> rcj: I can commit and upload in ~15m.
[03:47] <rcj> infinity, I would be grateful
[03:55] <infinity> rcj: r1444.
[03:58] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (yakkety-proposed/main) [2.432 => 2.433] (desktop-core)
[03:58] <rcj> infinity, Thank you
[04:20] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (yakkety-proposed) [2.433]
[04:20] -queuebot:#ubuntu-release- Unapproved: kdeclarative (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[04:20] -queuebot:#ubuntu-release- Unapproved: kdbusaddons (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[04:30] <slangasek> infinity: yes, because running from lp:livecd-rootfs leads to regressions on their side that we can't debug and have no CI for.  They should have a gate, which they control, for when they take new code from trunk
[04:31] <slangasek> and if it happens to be a gate downstream from the existing gate we already have (i.e. proposed-migration), even better for us
[04:32] -queuebot:#ubuntu-release- Unapproved: accepted docker.io [source] (xenial-proposed) [1.12.1-0ubuntu12~16.04.1]
[04:41] -queuebot:#ubuntu-release- New binary: docker.io [amd64] (xenial-proposed/universe) [1.12.1-0ubuntu12~16.04.1] (no packageset)
[04:51] -queuebot:#ubuntu-release- Unapproved: accepted kboot-installer [source] (yakkety-proposed) [0.0.1ubuntu10]
[04:51] <slangasek> is it a bug that packages seeded as 'supported' are not being auto-accepted?
[04:54] -queuebot:#ubuntu-release- Unapproved: accepted emacs24 [source] (yakkety-proposed) [24.5+1-7ubuntu1]
[04:56] <infinity> slangasek: Sure, running trunk itself isn't ideal, but being in sync with the archive would be nice.
[04:56] <infinity> slangasek: *shrug*
[04:57] <slangasek> infinity: yes, the dial may have been turned too far the other way ;)
[04:58] <infinity> slangasek: And if they were actually using the archvie version itself (ie: not a PPA fork), then this bug would have been fixed.
[04:58] <infinity> So, would be nice to see if we could get there.
[04:58] <infinity> Secret sauce could live in another package that dumps hooks in, or similar.
[05:06] <pitti> good morning!
[05:17] <rcj> infinity, it's the archive version and we have a recipe that adds in our additional hooks.  And slangasek is right, the dial is turned too far back
[05:25] <slangasek> xnox: should these software-properties changes not require an FFe?
[05:26] -queuebot:#ubuntu-release- Unapproved: accepted attica-kf5 [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[05:31] -queuebot:#ubuntu-release- Unapproved: qtmir (yakkety-proposed/universe) [0.4.8+16.10.20160906-0ubuntu1 => 0.4.8+16.10.20160909-0ubuntu1] (ubuntu-qt-packages) (sync)
[05:31] -queuebot:#ubuntu-release- Unapproved: qtmir-gles (yakkety-proposed/universe) [0.4.8+16.10.20160906-0ubuntu1 => 0.4.8+16.10.20160909-0ubuntu1] (ubuntu-qt-packages) (sync)
[05:32] -queuebot:#ubuntu-release- Unapproved: ubuntu-settings-components (yakkety-proposed/universe) [0.9+16.10.20160818.1-0ubuntu1 => 0.9+16.10.20160909-0ubuntu1] (no packageset) (sync)
[05:32] -queuebot:#ubuntu-release- Unapproved: unity-api (yakkety-proposed/universe) [7.118+16.10.20160830-0ubuntu1 => 7.119+16.10.20160909-0ubuntu1] (no packageset) (sync)
[05:32] -queuebot:#ubuntu-release- Unapproved: unity8 (yakkety-proposed/universe) [8.14+16.10.20160831.3-0ubuntu1 => 8.14+16.10.20160922-0ubuntu1] (ubuntu-qt-packages) (sync)
[05:32] -queuebot:#ubuntu-release- Unapproved: ubuntu-system-settings (yakkety-proposed/universe) [0.4+16.10.20160913-0ubuntu1 => 0.4+16.10.20160916-0ubuntu1] (no packageset) (sync)
[05:32] -queuebot:#ubuntu-release- Unapproved: unity-system-compositor (yakkety-proposed/universe) [0.7.1+16.10.20160824-0ubuntu1 => 0.7.1+16.10.20160909.1-0ubuntu1] (no packageset) (sync)
[05:34] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-settings-components [sync] (yakkety-proposed) [0.9+16.10.20160909-0ubuntu1]
[05:34] -queuebot:#ubuntu-release- Unapproved: accepted unity-system-compositor [sync] (yakkety-proposed) [0.7.1+16.10.20160909.1-0ubuntu1]
[05:40] -queuebot:#ubuntu-release- Unapproved: accepted baloo-kf5 [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[05:48] <rcj> infinity, bjf, wgrant: fun fact, I don't see a linux-virtual for arm64 @ https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+build/10939754
[05:49] <rcj> So it's true that arm64 just gained an linux-image-extra package and dependency which causes us to hit the flash-kernel bug but we can't use the virtual kernel yet, and the commit to livecd-rootfs from infinity has the build die when it can't find linux-virtual
[05:58] <doko> slangasek: pygobject should be covered by the gnome ffe, plus it should fix the ftbfs
[05:58] -queuebot:#ubuntu-release- New: accepted libabw [amd64] (yakkety-proposed) [0.1.1-4ubuntu1]
[05:58] -queuebot:#ubuntu-release- New: accepted libabw [armhf] (yakkety-proposed) [0.1.1-4ubuntu1]
[05:58] -queuebot:#ubuntu-release- New: accepted libabw [powerpc] (yakkety-proposed) [0.1.1-4ubuntu1]
[05:58] -queuebot:#ubuntu-release- New: accepted libabw [s390x] (yakkety-proposed) [0.1.1-4ubuntu1]
[05:58] -queuebot:#ubuntu-release- New: accepted libabw [arm64] (yakkety-proposed) [0.1.1-4ubuntu1]
[05:58] -queuebot:#ubuntu-release- New: accepted libabw [ppc64el] (yakkety-proposed) [0.1.1-4ubuntu1]
[05:58] -queuebot:#ubuntu-release- New: accepted libabw [i386] (yakkety-proposed) [0.1.1-4ubuntu1]
[05:58] -queuebot:#ubuntu-release- New: accepted wine [amd64] (yakkety-proposed) [1.8.4-1ubuntu2]
[06:06] -queuebot:#ubuntu-release- Unapproved: accepted nagios3 [source] (yakkety-proposed) [3.5.1.dfsg-2.1ubuntu2]
[06:21] <flexiondotorg> infinity, Can you accept ubuntu-mate-welcome 16.10.8 please.
[06:26] <pitti> flexiondotorg: that diff is unreviewable; you tested it?
[06:27] <pitti> well, it'll be blocked in -proposed anyway, accepted
[06:27] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-mate-welcome [source] (yakkety-proposed) [16.10.8]
[06:45] <flexiondotorg> pitti, Yes, it has been tested over 3 days. Most of the changes are as a result of the testing.
[06:48] <flexiondotorg> pitti, What is the process for getting ubuntu-mate-welcome from proposed to release at this stage in the cycle? I don't recall.
[06:49] <pitti> flexiondotorg: coordinate with whomever does the image respins for mate, and  ask anyone in ~ubuntu-release to add a britney unblock hint
[06:49] <pitti> flexiondotorg: if you do the image rebuilds/testing coordination, that'll be particularly easy :)
[06:49] <flexiondotorg> pitti, It isn't required for Beta 2 image.
[06:50] <pitti> oh, ok
[06:50] <flexiondotorg> Just available for updates is fine.
[06:50] <pitti> then no further action is required
[06:50] <flexiondotorg> Perfect. Thanks.
[06:55] -queuebot:#ubuntu-release- Unapproved: atomix (yakkety-proposed/universe) [3.22.0-0ubuntu1 => 3.22.0-1] (edubuntu) (sync)
[06:55] <Saviq> hey, can we plaease have qtmir, qtmir-gles, ubuntu-system-settings, unity-api, unity8 pushed through the unapproved queue? thanks
[06:56] -queuebot:#ubuntu-release- Unapproved: hitori (yakkety-proposed/universe) [3.20.0-1 => 3.22.0-1] (no packageset) (sync)
[06:57] -queuebot:#ubuntu-release- Unapproved: accepted hitori [sync] (yakkety-proposed) [3.22.0-1]
[06:57] -queuebot:#ubuntu-release- New sync: xdg-desktop-portal (yakkety-proposed/primary) [0.3-1]
[07:02] -queuebot:#ubuntu-release- Unapproved: debian-handbook (yakkety-proposed/universe) [8.20160826 => 8.20160922] (no packageset) (sync)
[07:03] -queuebot:#ubuntu-release- Unapproved: accepted debian-handbook [sync] (yakkety-proposed) [8.20160922]
[07:03] -queuebot:#ubuntu-release- Unapproved: kdesignerplugin (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[07:03] -queuebot:#ubuntu-release- Unapproved: eiciel (yakkety-proposed/universe) [0.9.11-2 => 0.9.11-3] (no packageset) (sync)
[07:04] -queuebot:#ubuntu-release- Unapproved: accepted eiciel [sync] (yakkety-proposed) [0.9.11-3]
[07:12] -queuebot:#ubuntu-release- Unapproved: tablix2 (yakkety-proposed/universe) [0.3.5-3ubuntu1 => 0.3.5-3.1] (no packageset) (sync)
[07:13] -queuebot:#ubuntu-release- Unapproved: accepted tablix2 [sync] (yakkety-proposed) [0.3.5-3.1]
[07:15] -queuebot:#ubuntu-release- Unapproved: root-tail (yakkety-proposed/universe) [1.2-3ubuntu1 => 1.2-4] (no packageset) (sync)
[07:16] -queuebot:#ubuntu-release- Unapproved: petris (yakkety-proposed/universe) [1.0.1-8ubuntu2 => 1.0.1-9] (no packageset) (sync)
[07:17] -queuebot:#ubuntu-release- Unapproved: accepted petris [sync] (yakkety-proposed) [1.0.1-9]
[07:17] -queuebot:#ubuntu-release- Unapproved: accepted root-tail [sync] (yakkety-proposed) [1.2-4]
[07:17] -queuebot:#ubuntu-release- Unapproved: elk (yakkety-proposed/universe) [3.99.8-4ubuntu1 => 3.99.8-4.1] (no packageset) (sync)
[07:19] -queuebot:#ubuntu-release- Unapproved: accepted elk [sync] (yakkety-proposed) [3.99.8-4.1]
[07:43] <apw> xnox, are you intending that NotShownIn change in software-properties, i don't see it in the changelog
[07:51] -queuebot:#ubuntu-release- Unapproved: rejected libertine [sync] (yakkety-proposed) [1.4.1+16.10.20160914-0ubuntu1]
[07:51] -queuebot:#ubuntu-release- Unapproved: rejected quadrapassel [sync] (yakkety-proposed) [1:3.22.0-1]
[07:51] -queuebot:#ubuntu-release- Unapproved: kded (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[07:51] -queuebot:#ubuntu-release- Unapproved: rejected libphonenumber [sync] (yakkety-proposed) [7.1.0-5ubuntu1]
[07:51] -queuebot:#ubuntu-release- Unapproved: kdelibs4support (yakkety-proposed/universe) [5.24.0-0ubuntu2 => 5.26.0-0ubuntu1] (kubuntu)
[07:52] -queuebot:#ubuntu-release- Unapproved: kdeclarative (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[08:00] <jbicha> apw: yes, it's intentional https://code.launchpad.net/~jbicha/software-properties/use-gi-require_version/+merge/304193
[08:19] <davmor2> Morning all
[09:50] -queuebot:#ubuntu-release- Unapproved: ceilometer (yakkety-proposed/main) [1:7.0.0~rc1-0ubuntu2 => 1:7.0.0~rc2-0ubuntu1] (openstack, ubuntu-server)
[09:54] <Odd_Bloke> apw: slangasek: infinity: We're proposing https://code.launchpad.net/~rcj/livecd-rootfs/yakkety_arm64/+merge/306599 to get arm64 builds working again; this simply switches us back to the generic kernel and skips the flash-kernel calls when we are constructing the squashfs.
[10:00] <Odd_Bloke> (I don't really know who else to ping, but this is blocking beta cloud images being built.)
[10:09] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (yakkety-proposed/main) [2.433 => 2.434] (desktop-core)
[10:10] <apw> Odd_Bloke, given the risk profile of the various options it seems reasonable to me, that ^^ is your merge, i'll let someone else review it again
[10:21] -queuebot:#ubuntu-release- Unapproved: firefox (yakkety-proposed/main) [48.0+build2-0ubuntu1 => 49.0+build4-0ubuntu1] (kubuntu, mozilla, ubuntu-desktop)
[10:32] <infinity> Odd_Bloke: Given you build from a fork, and using -virtual is the right thing going forward, not sure why you'd revert my change on trunk.
[10:32] <infinity> (Also, virtual will exist momentarily)
[10:33] <Odd_Bloke> infinity: Oh, OK, I got the impression we wouldn't have -virtual until the next kernel (which I assumed to not be landing in time for beta).
[10:34] <davmor2> infinity: so we need to wait on cyphermox shim to get signed, land in the iso and then respin again right is that the last thing we are waiting on then? I'm going to test that the 3rd party drivers thing is gone in the meantime
[10:34] <infinity> davmor2: Err, what?
[10:34] <infinity> davmor2: "waiting on shim to get signed" is a thing that can take months.
[10:34] <apw> a microsoft signing?  those take weeks
[10:35] <Odd_Bloke> infinity: (We're only forked insofar as we point at a specific version of the archive's livecd-rootfs; we try not to merge things there unless there's a very compelling reason to.)
[10:35] <davmor2> infinity: oh so we are just stuck with a none boot iso then
[10:35] <infinity> davmor2: In what scenario?
[10:36] <davmor2> infinity: securebooted machines
[10:36] <Odd_Bloke> infinity: (And I've just opened up an MP for our tooling to keep that "fork" up-to-date hourly in development releases, so we should never see this sort of issue again once that's merged)
[10:36] <infinity> Odd_Bloke: Why only "in development releases"?
[10:37] <infinity> Odd_Bloke: I'd really like you to benefit from bugfixes without a manual step. :P
[10:37] <Odd_Bloke> infinity: We have SLAs with partners for released releases; perhaps I'm being overcautious. :)
[10:37] <infinity> Odd_Bloke: The reason this all happened was because you were tracking *trunk* before.  The answer isn't to freeze at a point in time, but to track the archive instead.
[10:38] <davmor2> infinity: https://bugs.launchpad.net/ubuntu/+source/debian-cd/+bug/1624096
[10:38] <ubot5`> Ubuntu bug 1624096 in shim (Ubuntu) "yakkety: backport (or rebase to) fix eliminating a double-close in shim" [High,In progress]
[10:41] <apw> davmor2, why don't the older releases suffer the same issue?  do we no longer have a fallback.efi or something ?
[10:41] <Mirv> repeating Saviq's request to allow qtmir, qtmir-gles, ubuntu-system-settings, unity-api, unity8 in from yakkety unapproved queue
[10:41] <infinity> apw: No, the commit with the double-free is new.
[10:42] <xnox> jbicha, apw, mis-merged changelog entry. I guess i should fix it up and reupload. please reject current software properties.
[10:43] <apw> infinity, oh we have missmatched shim was not expecting that, cyphermox implies in the bug we can work round it by shipping a fallback.efi ?
[10:43] <infinity> No, we can't.
[10:43] <infinity> Read more bug.
[10:45] -queuebot:#ubuntu-release- Unapproved: rejected software-properties [source] (yakkety-proposed) [0.96.24.7]
[10:45] <infinity> Anyhow, there's precious little we can do about it for beta2, except document it.
[10:45] <apw> xnox, ^
[10:46] <davmor2> jibel: ^
[10:47] <infinity> I'm somewhat concerned that the Microsoft signing might not happen before GA, and we'll have to figure out a way to revert to the old shim without reverting any functionality...
[10:47] <infinity> Which sounds "fun".
[10:48]  * infinity is so glad that our release process gates on a 3rd party's code review and signing.
[10:50] -queuebot:#ubuntu-release- Unapproved: solid (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[10:50] -queuebot:#ubuntu-release- Unapproved: sonnet (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[10:51] -queuebot:#ubuntu-release- Unapproved: kunitconversion (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[10:51] -queuebot:#ubuntu-release- Unapproved: kwayland (yakkety-proposed/universe) [4:5.24.0-0ubuntu1 => 4:5.26.0-0ubuntu1] (kubuntu)
[10:51] -queuebot:#ubuntu-release- Unapproved: kwallet-kf5 (yakkety-proposed/universe) [5.24.0-0ubuntu2 => 5.26.0-0ubuntu1] (kubuntu)
[10:51] -queuebot:#ubuntu-release- Unapproved: software-properties (yakkety-proposed/main) [0.96.24.6 => 0.96.24.7] (desktop-core, ubuntu-server)
[10:53] -queuebot:#ubuntu-release- Unapproved: kjsembed (yakkety-proposed/universe) [5.24.0-0ubuntu2 => 5.26.0-0ubuntu1] (kubuntu)
[10:53] -queuebot:#ubuntu-release- Unapproved: knewstuff (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[10:53] -queuebot:#ubuntu-release- Unapproved: knotifyconfig (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[10:53] -queuebot:#ubuntu-release- Unapproved: kmediaplayer (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[10:53] -queuebot:#ubuntu-release- Unapproved: knotifications (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[10:56] -queuebot:#ubuntu-release- Unapproved: kinit (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[10:56] -queuebot:#ubuntu-release- Unapproved: kitemmodels (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[10:56] -queuebot:#ubuntu-release- Unapproved: kio (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[11:10] -queuebot:#ubuntu-release- Unapproved: account-plugins (yakkety-proposed/main) [0.13+16.10.20160830.1-0ubuntu1 => 0.13+16.10.20160831-0ubuntu1] (ubuntu-desktop) (sync)
[11:10] -queuebot:#ubuntu-release- Unapproved: breeze-icons (yakkety-proposed/universe) [4:5.24.0-0ubuntu1 => 4:5.26.0-0ubuntu1] (kubuntu)
[11:10] -queuebot:#ubuntu-release- Unapproved: frameworkintegration (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[11:10] -queuebot:#ubuntu-release- Unapproved: kactivities-stats (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (no packageset)
[11:10] -queuebot:#ubuntu-release- Unapproved: signon-plugin-oauth2 (yakkety-proposed/main) [0.23+16.04.20151209-0ubuntu1 => 0.24+16.10.20160818-0ubuntu1] (kubuntu, ubuntu-desktop) (sync)
[11:10] -queuebot:#ubuntu-release- Unapproved: bluez-qt (yakkety-proposed/universe) [5.24.0-0ubuntu2 => 5.26.0-0ubuntu1] (kubuntu)
[11:10] -queuebot:#ubuntu-release- Unapproved: kactivities-kf5 (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[11:10] -queuebot:#ubuntu-release- Unapproved: ubuntu-system-settings-online-accounts (yakkety-proposed/universe) [0.7+16.10.20160718-0ubuntu1 => 0.7+16.10.20160830.2-0ubuntu1] (no packageset) (sync)
[11:10] -queuebot:#ubuntu-release- Unapproved: extra-cmake-modules (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[11:10] -queuebot:#ubuntu-release- Unapproved: pygobject (yakkety-proposed/main) [3.21.92-1 => 3.22.0-1] (core) (sync)
[11:11] -queuebot:#ubuntu-release- Unapproved: ki18n (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[11:11] -queuebot:#ubuntu-release- Unapproved: kidletime (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[11:11] -queuebot:#ubuntu-release- Unapproved: kinit (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[11:11] -queuebot:#ubuntu-release- Unapproved: kitemmodels (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[11:11] -queuebot:#ubuntu-release- Unapproved: kjobwidgets (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[11:11] -queuebot:#ubuntu-release- Unapproved: kjsembed (yakkety-proposed/universe) [5.24.0-0ubuntu2 => 5.26.0-0ubuntu1] (kubuntu)
[11:11] -queuebot:#ubuntu-release- Unapproved: knewstuff (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[11:11] -queuebot:#ubuntu-release- Unapproved: kiconthemes (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[11:11] -queuebot:#ubuntu-release- Unapproved: kio (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[11:11] -queuebot:#ubuntu-release- Unapproved: kjs (yakkety-proposed/universe) [5.24.0-0ubuntu4 => 5.26.0-0ubuntu1] (kubuntu)
[11:11] -queuebot:#ubuntu-release- Unapproved: knotifications (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[11:11] -queuebot:#ubuntu-release- Unapproved: kimageformats (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[11:11] -queuebot:#ubuntu-release- Unapproved: kmediaplayer (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[11:11] -queuebot:#ubuntu-release- Unapproved: kitemviews (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[11:12] -queuebot:#ubuntu-release- Unapproved: account-plugins (yakkety-proposed/main) [0.13+16.10.20160830.1-0ubuntu1 => 0.13+16.10.20160831-0ubuntu1] (ubuntu-desktop) (sync)
[11:12] -queuebot:#ubuntu-release- Unapproved: signon-plugin-oauth2 (yakkety-proposed/main) [0.23+16.04.20151209-0ubuntu1 => 0.24+16.10.20160818-0ubuntu1] (kubuntu, ubuntu-desktop) (sync)
[11:12] -queuebot:#ubuntu-release- Unapproved: ubuntu-system-settings-online-accounts (yakkety-proposed/universe) [0.7+16.10.20160718-0ubuntu1 => 0.7+16.10.20160830.2-0ubuntu1] (no packageset) (sync)
[11:12] -queuebot:#ubuntu-release- Unapproved: libertine (yakkety-proposed/main) [1.4+16.10.20160908-0ubuntu1 => 1.4.1+16.10.20160914-0ubuntu1] (no packageset) (sync)
[11:12] -queuebot:#ubuntu-release- Unapproved: ubuntu-keyboard (yakkety-proposed/universe) [0.100+16.10.20160818-0ubuntu1 => 0.100+16.10.20160921-0ubuntu1] (no packageset) (sync)
[11:13] -queuebot:#ubuntu-release- Unapproved: kdesu (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[11:13] -queuebot:#ubuntu-release- Unapproved: kdnssd-kf5 (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[11:13] -queuebot:#ubuntu-release- Unapproved: kemoticons (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[11:13] -queuebot:#ubuntu-release- Unapproved: kglobalaccel (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[11:13] -queuebot:#ubuntu-release- Unapproved: kdewebkit (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[11:13] -queuebot:#ubuntu-release- Unapproved: kfilemetadata-kf5 (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[11:13] -queuebot:#ubuntu-release- Unapproved: kdoctools (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[11:13] -queuebot:#ubuntu-release- Unapproved: kguiaddons (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[11:17] <Odd_Bloke> infinity: apw: I'll be grabbing some lunch soon; can you ping me when we have a -virtual for arm64 that I can build against?
[11:20] <davmor2> infinity, pitti: good news we have 3rd party drivers \o/
[11:20] <pitti> davmor2: party!!!!
[11:21] <davmor2> Now to see if they install on the system too
[11:21] <pitti> davmor2: so the cdimage mirror is up to date again, good
[11:21] <davmor2> pitti: sounds it
[11:43] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Yakkety Beta 2] has been disabled
[11:43] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop i386 [Yakkety Beta 2] has been disabled
[11:53] <davmor2> \o/ I can haz Wifi on the installed system too \o/
[12:10] -queuebot:#ubuntu-release- Unapproved: rejected livecd-rootfs [source] (yakkety-proposed) [2.434]
[12:10] -queuebot:#ubuntu-release- Unapproved: kdesignerplugin (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[12:24] -queuebot:#ubuntu-release- New: accepted xdg-desktop-portal [sync] (yakkety-proposed) [0.3-1]
[12:29] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (yakkety-proposed/main) [4.8.0-16.17] (core, kernel)
[12:29] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (yakkety-proposed) [4.8.0-16.17]
[12:29] -queuebot:#ubuntu-release- New binary: xdg-desktop-portal [ppc64el] (yakkety-proposed/none) [0.3-1] (no packageset)
[12:30] -queuebot:#ubuntu-release- New binary: xdg-desktop-portal [amd64] (yakkety-proposed/none) [0.3-1] (no packageset)
[12:30] -queuebot:#ubuntu-release- New binary: xdg-desktop-portal [i386] (yakkety-proposed/none) [0.3-1] (no packageset)
[12:30] -queuebot:#ubuntu-release- New binary: xdg-desktop-portal [arm64] (yakkety-proposed/none) [0.3-1] (no packageset)
[12:31] -queuebot:#ubuntu-release- New binary: xdg-desktop-portal [armhf] (yakkety-proposed/none) [0.3-1] (no packageset)
[12:38] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (vivid-proposed) [3.19.0-70.78]
[12:40] -queuebot:#ubuntu-release- New binary: xdg-desktop-portal [powerpc] (yakkety-proposed/none) [0.3-1] (no packageset)
[12:41] -queuebot:#ubuntu-release- New binary: xdg-desktop-portal [s390x] (yakkety-proposed/none) [0.3-1] (no packageset)
[13:09] <ChrisTownsend> Hey, could anyone tell me why the recent libertine upload was rejected?
[13:09] <apw> ChrisTownsend, the reason was in the reject email ... but i believe that was becasue it was in there twice
[13:09] <davmor2> cyphermox: the fact that there is no efi entry for ubuntu in the bios I assume is because of shim right?  IE install the system drop into UEFI look at boot options and there is no Ubuntu option that is normally there pointing to shimx64.efi on the harddrive
[13:10] <apw> ChrisTownsend, yes, livertine is still sitting in the queue
[13:11] <ChrisTownsend> apw: I didn't get an email.  Oh, I haven't seen the other one.
[13:12] <ChrisTownsend> apw: Bileto had me all worried with it's status saying REJECTED.
[13:12] <ChrisTownsend> apw: Thanks!
[13:12] <ogra_> livertine ? is your brain already at beer o'clock ?
[13:35] <cyphermox> davmor2: no
[13:37] <cyphermox> davmor2: if you don't have the ubuntu entry in the EFI firmware after install is at this point most likely to be because you started qemu wrong ;)
[13:37] <davmor2> cyphermox: oh weird it shows when there is no usb pendrive in the xps 13, let me check it when I finish this install it might just not be permanently there now
[13:37] <davmor2> cyphermox: this is on Hardware
[13:37] <cyphermox> oh, on a Dell?
[13:38] <cyphermox> you may be hitting another firmware bug
[13:38] <davmor2> cyphermox: yeap it boots from the harddrive no issues, it just doesn't show in the menu is that the infamous old there is no BOOT.efi file in BOOT or something
[13:38] <cyphermox> I'm not sure it happens on all Dell BIOS but I've seen one be very unhappy about adding our boot entry and just removing it after a reboot
[13:39] <cyphermox> davmor2: yes
[13:39] <davmor2> cyphermox: that's fine then I can live with that one it boots which it is the important thing
[13:39] <cyphermox> we'll fix that one too though
[13:41] <davmor2> cyphermox: thems fighting words
[13:42] <cyphermox> well, it's been on my list for a while, and it involves the fallback.efi
[13:48] <davmor2> cyphermox: okay so it show ubuntu when there is no pendrive but the minute I boot with a pendrive in it only shows the efi entries on the pendrive which is a bit weird but I assume that is a dell firmware issue so I don't care enough at this point :)
[13:51] -queuebot:#ubuntu-release- Unapproved: unity-scope-click (yakkety-proposed/universe) [0.1.1+16.10.20160920.1-0ubuntu1 => 0.1.1+16.10.20160922-0ubuntu1] (no packageset) (sync)
[13:52] -queuebot:#ubuntu-release- Unapproved: accepted unity-scope-click [sync] (yakkety-proposed) [0.1.1+16.10.20160922-0ubuntu1]
[13:52] -queuebot:#ubuntu-release- Unapproved: kdesignerplugin (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:54] <cyphermox> davmor2: great
[13:57] -queuebot:#ubuntu-release- Unapproved: unity8-desktop-session (yakkety-proposed/universe) [1.0.13+16.10.20160919-0ubuntu1 => 1.0.13+16.10.20160921-0ubuntu1] (no packageset) (sync)
[13:59] <davmor2> willcooke: oh interesting mini.iso netboot installs install unity8-desktop-session too no wonder it took so much longer to install :)
[13:59] <willcooke> hmm
[13:59] <willcooke> that doesnt sound like it should be there
[13:59] -queuebot:#ubuntu-release- Unapproved: accepted unity8-desktop-session [sync] (yakkety-proposed) [1.0.13+16.10.20160921-0ubuntu1]
[13:59] -queuebot:#ubuntu-release- Unapproved: kdesignerplugin (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:59] <davmor2> willcooke: netboot install from archive don't forget
[14:00] <willcooke> ah, right
[14:10] -queuebot:#ubuntu-release- Unapproved: postgresql-common (yakkety-proposed/main) [175ubuntu1 => 176+git1] (kubuntu, ubuntu-server)
[14:23] -queuebot:#ubuntu-release- Unapproved: heat (xenial-proposed/main) [1:6.0.0-0ubuntu1.1 => 1:6.1.0-0ubuntu1] (openstack, ubuntu-server)
[15:06] -queuebot:#ubuntu-release- Unapproved: accepted pygobject [sync] (yakkety-proposed) [3.22.0-1]
[15:06] <jderose> infinity: as far as the shim signing... would a reasonable plan be to only land the new shim package if it gets signed in time, otherwise keep the current one?
[15:06] <jderose> or mabye that's already the plan, wasn't quite sure what you meant by "we'll have to figure out a way to revert to the old shim without reverting any functionality..."
[15:08] <cyphermox> jderose: the argument is that not being able to boot the CD images on EFI is kinda bad
[15:10] -queuebot:#ubuntu-release- Unapproved: unadf (yakkety-proposed/universe) [0.7.11a-3 => 0.7.11a-3+deb7u1] (no packageset)
[15:11] <jderose> cyphermox: agreed. what's your assessment of the percentage of hardware effected by this? i know you mentioned you had a laptop that wouldn't boot. by luck, no System76 products seem "crushingly" effected by this (the memory corruption doesn't cause a hardware exception, doesn't prevent booting)
[15:11] -queuebot:#ubuntu-release- Unapproved: accepted unadf [source] (yakkety-proposed) [0.7.11a-3+deb7u1]
[15:11] -queuebot:#ubuntu-release- Unapproved: kdesu (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[15:11] <cyphermox> well, for starters all thinkpads
[15:12] <cyphermox> otoh it could just have been blocking boot becuase I have shim debugging enabled
[15:12] <jderose> cyphermox: but i am a bit concerned about the potential security issue here... memory corruption is happing silently, and who knows what fun opportunities that might open
[15:12] <cyphermox> but I'm not willing to take a guess to find out at release time :)
[15:12] <cyphermox> oh of course
[15:12] <jderose> cyphermox: "effects all thinkpads" <-- that's a pretty strong data point right there :)
[15:13] <cyphermox> that's why infinity suggested reverting
[15:13] <jderose> cyphermox: ah, okay, so you did land the new shim package then?
[15:13] -queuebot:#ubuntu-release- Unapproved: accepted bluez-qt [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[15:13] <cyphermox> I suppose we could cheat and use the old shim on the CD, but then the source for that shim wouldn't be anywhere
[15:14] <cyphermox> jderose: when I say old and new I mean "new" being the one currently in the archive, and old the one before that
[15:14] <jderose> yeah, true
[15:14] <jderose> ah, okay
[15:14] <cyphermox> the new new shim is in the grinder now.
[15:16] <jderose> i guess we could also just say, "go home secure boot, you're drunk" and return to the glory days of not depending on microsoft :P
[15:16] <cyphermox> not really, because it probably won't boot any better with secure boot disabled
[15:16] <infinity> jderose: I meant revert to the version before the bug was introduced.
[15:17] <cyphermox> I don't remember what the state was for SB on my laptop when I tried to boot these images
[15:17] <cyphermox> infinity: if you care, shim signing is RT #95907
[15:17] <jderose> infinity: ah, okay. hmm... so this would need a new epoch in the version then? that doesn't seem terribly difficult... but is it?
[15:17] <apw> cyphermox, the source for that would be in an old release still no ?
[15:18] <infinity> jderose: Not an epoch, just an ugly version. :P
[15:18] <apw> cyphermox, presumably we use a .is. version ?
[15:18] <cyphermox> apw: yes, since we haven't copied it to all releases yet
[15:18] <cyphermox> well, last signing only took a few days, I see no reason for it to take much longer
[15:19] <jderose> infinity: ah, i always thought the epoch was the way one wouldn't likely handle needing to go backward version wise. but i've never had to do this, nor i'm i familiar with the debian policy on this matter
[15:19] <cyphermox> last signing took two weeks.
[15:20] <cyphermox> jderose: for that we do something like 1.2.really.1.1 and be done with it
[15:20] <jderose> cyphermox: okay, gotcha
[15:20] <cyphermox> because we're likely to go to 1.3 next
[15:20] <cyphermox> epochs are forever.
[15:21] <jderose> gotcha, just like diamonds :P
[15:21] <ogra_> but epochs arent girls best friends i fear
[15:21] <jderose> hehe
[15:22] <cyphermox> my rules are 1) if you think you need to use epoch, you're wrong, don't use epoch 2) if you still think you need it, refer to 1), and 3) maybe you need it in this one very special circumstance, but make sure there is no other option first
[15:22] <jderose> cyphermox: thanks, i'm adding that to my permanent record of packaging wisdom
[15:22] <ogra_> 4) screw it, just invent a new package name and add -ng :P
[15:22] <cyphermox> ahaha
[15:23] <cyphermox> ^ what if you're wrong and get back to 1) ?
[15:24] <ogra_> you're screwed ?
[15:27] <infinity> Burning an epoch on a temporary revert is silly.  Using them when upstream versions change permanently is sane.
[15:27] -queuebot:#ubuntu-release- Unapproved: accepted breeze-icons [source] (yakkety-proposed) [4:5.26.0-0ubuntu1]
[15:30] -queuebot:#ubuntu-release- Unapproved: accepted extra-cmake-modules [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[15:36] -queuebot:#ubuntu-release- Unapproved: accepted frameworkintegration [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[15:51] -queuebot:#ubuntu-release- Unapproved: rejected kactivities-kf5 [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[15:56] -queuebot:#ubuntu-release- Unapproved: accepted kactivities-stats [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[15:59] -queuebot:#ubuntu-release- Unapproved: debian-installer (yakkety-proposed/main) [20101020ubuntu476 => 20101020ubuntu477] (core)
[15:59] -queuebot:#ubuntu-release- Unapproved: accepted debian-installer [source] (yakkety-proposed) [20101020ubuntu477]
[16:00] -queuebot:#ubuntu-release- Unapproved: openssl (yakkety-proposed/main) [1.0.2g-1ubuntu8 => 1.0.2g-1ubuntu9] (core)
[16:05] <acheronuk> Hi. can I ask why? 'rejected kactivities-kf5'. Thanks
[16:06] <xnox> reject reasons should be in the email to the uploader.....
[16:07] <slangasek> acheronuk: because debian/control was broken. the uploader received mail
[16:08] -queuebot:#ubuntu-release- Unapproved: accepted kapidox [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[16:09] <acheronuk> slangasek: thank you. I'll talk to him
[16:16] -queuebot:#ubuntu-release- Unapproved: accepted karchive [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[16:18] -queuebot:#ubuntu-release- Unapproved: accepted kauth [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[16:24] -queuebot:#ubuntu-release- Unapproved: accepted kbookmarks [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[16:25] -queuebot:#ubuntu-release- Unapproved: accepted kcmutils [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[16:26] -queuebot:#ubuntu-release- Unapproved: accepted kcodecs [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[16:31] -queuebot:#ubuntu-release- Builds: Netboot amd64 [Yakkety Beta 2] has been updated (20101020ubuntu477)
[16:31] -queuebot:#ubuntu-release- Builds: Netboot arm64 [Yakkety Beta 2] has been updated (20101020ubuntu477)
[16:31] -queuebot:#ubuntu-release- Builds: Netboot armhf [Yakkety Beta 2] has been updated (20101020ubuntu477)
[16:31] -queuebot:#ubuntu-release- Builds: Netboot i386 [Yakkety Beta 2] has been updated (20101020ubuntu477)
[16:31] -queuebot:#ubuntu-release- Builds: Netboot powerpc [Yakkety Beta 2] has been updated (20101020ubuntu477)
[16:31] -queuebot:#ubuntu-release- Builds: Netboot ppc64el [Yakkety Beta 2] has been updated (20101020ubuntu477)
[16:31] -queuebot:#ubuntu-release- Builds: Netboot s390x [Yakkety Beta 2] has been updated (20101020ubuntu477)
[16:32] -queuebot:#ubuntu-release- Unapproved: accepted kcompletion [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[16:36] -queuebot:#ubuntu-release- Unapproved: unity-scopes-api (yakkety-proposed/universe) [1.0.6+16.10.20160617-0ubuntu2 => 1.0.7+16.10.20160921-0ubuntu1] (no packageset) (sync)
[16:36] -queuebot:#ubuntu-release- Unapproved: unity-scopes-shell (yakkety-proposed/universe) [0.5.7+16.10.20160624.2-0ubuntu2 => 0.5.8+16.10.20160921-0ubuntu1] (no packageset) (sync)
[17:16] <flexiondotorg> infinity, How is the release looking from your point of view?
[17:18] -queuebot:#ubuntu-release- Unapproved: accepted openssl [source] (yakkety-proposed) [1.0.2g-1ubuntu9]
[17:18] -queuebot:#ubuntu-release- Unapproved: kdnssd-kf5 (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[17:28] <nacc> working the ftbfs of pacemaker per doko's last e-mail, was wondering if anyone could quikly glance at http://paste.ubuntu.com/23221134/ for sanity?
[17:28] <nacc> i'm not sure why it changed from dist to site-packages, but i verified this in the sbuild environment as well
[17:30] <cjwatson> that really doesn't seem right
[17:31] <cjwatson> should be /usr/lib/python3/dist-packages/
[17:31] <nacc> yeah it's weird
[17:31] <cjwatson> perhaps a missing/misconfigured dh_python3 call?
[17:31] <nacc> there's no  mention of python in the debian/rules file at all, otehr than this one line
[17:31] <nacc> which is also strange :)
[17:32] <cjwatson> well, dh often handles stuff automatically
[17:33] <nacc> cjwatson: from teh build log: http://paste.ubuntu.com/23221146/
[17:34] <davmor2> infinity: i386 done, amd64 done, netboot for i386 and amd64 done, 1 major issue is the shim that needs a note other than that the only other things are minor or aesthetic as far as I can tell so over to you
[17:34] <infinity> flexiondotorg: Messy.
[17:34] <acheronuk> if something is rejected in the queue for small error in control file, can it be corrected and uploaded with the same original version?
[17:34] <infinity> flexiondotorg: So, I'm considering a potention respin of literally everything to stuff the new kernel in, but if I do that, the kernel team will be on the hook for smoketesting everyone's ISOs so the flavours don't have to.
[17:35] <tsimonq2> a lot of Kubuntu things will migrate when beta freeze is undone, we're holding our breath...
[17:35] <cjwatson> nacc: yeah, that's not unusual but the packaging helpers are supposed to move stuff to the right place
[17:35] <cjwatson> nacc: would need to see the full log
[17:35] <tsimonq2> it would also be nice to have hardinfo uploaded, so Lubuntu is wanting that as well
[17:35] <tsimonq2> fun stuff
[17:36] <slangasek> acheronuk: if it was in the queue when it was rejected, yes you can reuse the version number
[17:36] <davmor2> infinity: say what now????
[17:36] <infinity> davmor2: what not????
[17:36] <slangasek> infinity: why respin everything for new kernel instead of releasing as-is those images that already passed?
[17:36] <infinity> s/not/now/
[17:36] <nacc> cjwatson: http://paste.ubuntu.com/23221157/
[17:37] <acheronuk> slangasek: ty. I guessed that was the case, but confirmation is appreciated
[17:37] <davmor2> slangasek: let it land as an update
[17:37] <davmor2> infinity: ^ even sorry slangasek
[17:37] <cjwatson> nacc: ah, maybe needs --with python3
[17:37] <cjwatson> (and care!)
[17:37] <infinity> slangasek: Consistency, binary images matching source images, same kernel bugs apply to everyone.  But yeah, I'm willing to fudge it on a beta.
[17:38] -queuebot:#ubuntu-release- Unapproved: gnome-software (yakkety-proposed/main) [3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu2 => 3.20.1+git20160923.2.7374bdc-0ubuntu1] (ubuntu-desktop)
[17:38] <nacc> cjwatson: ack, i'll dig into it more
[17:38] <flexiondotorg> infinity, OK.
[17:38] <flexiondotorg> I can smoke test Ubuntu MATE and Ubuntu.
[17:38] <slangasek> infinity: are there any of these kernel bugs that we think are a problem on those images we haven't already respun for?
[17:38] <cjwatson> nacc: those SyntaxErrors in the log don't look great either
[17:38] <flexiondotorg> If a respin happens.
[17:39] <flexiondotorg> But not PowerPC.
[17:39] <nacc> cjwatson: yeah, i wonder if it only is python2 compatible in practice?
[17:39] <davmor2> infinity: whatever it is it can't be worse that not being able to boot it
[17:39] <infinity> davmor2: Not being able to boot is actually not the worst bug a kernel can have, by far. :P
[17:39] <flexiondotorg> infinity, If a respin is on the cards on chance ubuntu-mate-welcome can be moved from proposed to release?
[17:39] <infinity> Unbootable is the ultimate in security.
[17:39] <ogra_> and saves power !
[17:40] <infinity> flexiondotorg: If, yes.  Still mulling it all over.
[17:40] <flexiondotorg> s/on/any/
[17:40] <ogra_> green kernel
[17:40] <slangasek> yes, "ohai I set your GPU on fyur" is a worse kernel bug
[17:40] <nacc> cjwatson: ah, looks like very recently they made it python2 and python3 compatible in the source, but probably not packaged yetd. Also, note this is a delete line, in particular, because we don't actually ship the python files
[17:40] <davmor2> ogra_: no it doesn't it spins up the system and leaves it in a loop of some sort so it would use more power ;)
[17:40] -queuebot:#ubuntu-release- Unapproved: gnome-software (xenial-proposed/main) [3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1 => 3.20.1+git20160923.2.7374bdc-0ubuntu1~xenial1] (ubuntu-desktop)
[17:40] <ogra_> pffft
[17:41] <davmor2> ogra_: snappy fixes it though right ;)
[17:41] <ogra_> definitely !
[17:42] <Odd_Bloke> Then you can rollback from the kernel that leaves your system in a loop to one that just doesn't boot!
[17:42] <ogra_> yeah, aint we great ?
[17:42] <infinity> slangasek: Anyhow, I'm going to wait for a tiny bit more testing to roll in, promote the new kernel, and respin server for the "it can't even smoketest" thing.
[17:42] <infinity> slangasek: And then we can take a decision on skew versus retesting, blah blah.
[17:42] <infinity> Also, I need food of some sort.
[17:42] <slangasek> infinity: ok
[17:43] <slangasek> infinity: fwiw xnox and I kind of agree that using ATA for the smoketests is probably not the best anyway, since that's not a representative test
[17:44] <infinity> slangasek: I don't disagree.
[17:44] <slangasek> of course, fixing that may not be faster than respinning with the new kernel
[17:45] <slangasek> powersj: ^^ not a blocker for beta AIUI, but IMHO the server smoketests should be changed to use something closer to a "default" libvirt config instead of one that trips over this particular ATA driver problem
[17:46] <powersj> slangasek, ok I believe that means modifying utah to use something different. Is there a suggested qemu command line option or libvit change?
[17:46] <davmor2> infinity: oh and don't forget to mention that unity8 is on by default yet :(
[17:47] <davmor2> isn't on even
[17:48] <slangasek> powersj: xnox might be able to provide some input there
[17:49] <slangasek> powersj: but he may be EOD; so perhaps log a bug against whatever's the right place for utah, and subscribe him?
[17:49] <slangasek> davmor2: "on by default"?
[17:49] <powersj> slangasek, yep, I have avoided messing with utah so far :)
[17:49]  * wxl quickly marks Lubuntu as ready to avoid having to retest because of this silly respin idea
[17:50] <davmor2> slangasek: unity8 session will be on the final desktop image but the mir's didn't finish yet so it isn't on in the beta
[17:50] <slangasek> powersj: I do see from the scripts that utah is driving qemu via libvirt, so it'll be all xml
[17:50] <davmor2> slangasek: unless you do netboot installs
[17:50] <slangasek> davmor2: you said "on by default", it's not going to be the default...
[17:50] <slangasek> just making sure we're on the same page :)
[17:50] -queuebot:#ubuntu-release- Builds: Lubuntu Alternate amd64 [Yakkety Beta 2] has been marked as ready
[17:50] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop amd64 [Yakkety Beta 2] has been marked as ready
[17:50] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop i386 [Yakkety Beta 2] has been marked as ready
[17:50] -queuebot:#ubuntu-release- Builds: Lubuntu Alternate i386 [Yakkety Beta 2] has been marked as ready
[17:50] <davmor2> slangasek: and then underneath said isn't on even :)
[17:50] <slangasek> infinity: is there a release notes page up btw?
[17:50] <davmor2> slangasek: I missed the n't
[17:51] <nacc> cjwatson: sending a fix for the syntax errors upstream
[17:52] -queuebot:#ubuntu-release- Unapproved: accepted kconfig [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[17:53] <xnox> powersj, davmor2, slangasek - to get sample configs (qemu command line) I would use vm-manager to graphically change cdrom from IDE bus to SATA bus, or SCSI bus. Then it uses e.g. -device scsi-cd,bus=scsi0.0,scsi-id=0,drive=drive-scsi0-0-0,id=scsi0-0-0,bootindex=1
[17:54] <xnox> not sure what we want to test, most people dd the iso to a usb stick these days and boot. so maybe providing a usb device to the VM might be a more realistic example =)
[17:54] <xnox> together with scsi cdrom boot test.
[17:55] <davmor2> xnox: I use hardware mostly, there's no easy way to test nvidia and amd setups and amd cpu vs intel cpu
[17:55] <xnox> true.
[17:55] <xnox> davmor2, and what bus do normal machines use for cdrom these days?
[17:55]  * xnox has not had a CDROM for 6 years now
[17:55] <davmor2> xnox: sata on the whole
[17:56] <xnox> and i believe qemu defaults to IDE for cdroms
[17:56] <xnox> which is a mismatch with reality
[17:58] <powersj> Is there a plan to get the often default, IDE cdrom to work?
[18:02] <slangasek> powersj: yes, the next kernel should fix that
[18:02] <powersj> slangasek, great!
[18:03] <slangasek> it's just a bad smoketest because only people using qemu from the commandline, and booting the server ISO instead of a cloud image, are affected
[18:03] <slangasek> (affected by this default)
[18:04] <davmor2> xnox: you can change it with the -drive command but I have to go now so you would need to look it up
[18:07] -queuebot:#ubuntu-release- Unapproved: accepted kconfigwidgets [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[18:15] -queuebot:#ubuntu-release- Unapproved: accepted qtmir-gles [sync] (yakkety-proposed) [0.4.8+16.10.20160909-0ubuntu1]
[18:15] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-system-settings [sync] (yakkety-proposed) [0.4+16.10.20160916-0ubuntu1]
[18:15] -queuebot:#ubuntu-release- Unapproved: accepted unity8 [sync] (yakkety-proposed) [8.14+16.10.20160922-0ubuntu1]
[18:15] -queuebot:#ubuntu-release- Unapproved: accepted qtmir [sync] (yakkety-proposed) [0.4.8+16.10.20160909-0ubuntu1]
[18:15] -queuebot:#ubuntu-release- Unapproved: accepted unity-api [sync] (yakkety-proposed) [7.119+16.10.20160909-0ubuntu1]
[18:23] -queuebot:#ubuntu-release- Unapproved: animals (yakkety-proposed/universe) [201207131226-1build1 => 201207131226-2] (no packageset) (sync)
[18:24] -queuebot:#ubuntu-release- Unapproved: libweather-com-perl (yakkety-proposed/universe) [0.5.3-2 => 0.5.3-3] (no packageset) (sync)
[18:24] -queuebot:#ubuntu-release- Unapproved: ndiswrapper (yakkety-proposed/universe) [1.60-2 => 1.60-3] (no packageset) (sync)
[18:25] -queuebot:#ubuntu-release- Unapproved: accepted animals [sync] (yakkety-proposed) [201207131226-2]
[18:25] -queuebot:#ubuntu-release- Unapproved: accepted ndiswrapper [sync] (yakkety-proposed) [1.60-3]
[18:25] -queuebot:#ubuntu-release- Unapproved: kdesu (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[18:25] -queuebot:#ubuntu-release- Unapproved: accepted libweather-com-perl [sync] (yakkety-proposed) [0.5.3-3]
[18:25] -queuebot:#ubuntu-release- Unapproved: kdesignerplugin (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[18:34] -queuebot:#ubuntu-release- Unapproved: accepted kcoreaddons [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[18:39] -queuebot:#ubuntu-release- Unapproved: accepted kcrash [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[18:43] -queuebot:#ubuntu-release- Unapproved: accepted kdbusaddons [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[18:47] <nacc> cjwatson: so did some digging and it seems like pacemaker's cts/Makefile has that path hardcoded at build-time. BUt we end up not shipping any of the cts (which is the testsuite) for pacemaker in any package. So is it reasonable to just not build it at all?
[18:47] -queuebot:#ubuntu-release- Unapproved: accepted kdeclarative [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[18:51] <cjwatson> nacc: sorry, you're well past what I know about pacemaker (~nothing) at this point
[18:52] <nacc> cjwatson: yeah, kinda in the same boat :)
[18:52] <nacc> cjwatson: thanks for your guidance so far, though!
[18:53] <nacc> it feels like a lot of work just to delete a bunch of files to have it put the files in right place -- but it's probably good to do it right now
[18:55] <nacc> barry: would you be a good reference for a dh_python3 question? :)
[18:58] -queuebot:#ubuntu-release- Unapproved: accepted kded [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[19:01] -queuebot:#ubuntu-release- Unapproved: snapcraft (yakkety-proposed/universe) [2.18+16.10 => 2.18.1+16.10] (no packageset)
[19:02] -queuebot:#ubuntu-release- Unapproved: accepted snapcraft [source] (yakkety-proposed) [2.18.1+16.10]
[19:02] -queuebot:#ubuntu-release- Unapproved: kdelibs4support (yakkety-proposed/universe) [5.24.0-0ubuntu2 => 5.26.0-0ubuntu1] (kubuntu)
[19:04] -queuebot:#ubuntu-release- Unapproved: ghostscript (yakkety-proposed/main) [9.19~dfsg+1-0ubuntu4 => 9.19~dfsg+1-0ubuntu5] (desktop-core, ubuntu-server)
[19:11] -queuebot:#ubuntu-release- Unapproved: accepted kdelibs4support [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[19:11] -queuebot:#ubuntu-release- Unapproved: zeromq3 (yakkety-proposed/universe) [4.1.5-2ubuntu3 => 4.1.5+git20160811+2fc86bc-0ubuntu2] (kubuntu) (sync)
[19:11] -queuebot:#ubuntu-release- Unapproved: unity-scopes-api (yakkety-proposed/universe) [1.0.6+16.10.20160617-0ubuntu2 => 1.0.7+16.10.20160921-0ubuntu2] (no packageset) (sync)
[19:11] -queuebot:#ubuntu-release- Unapproved: zmqpp (yakkety-proposed/universe) [3.2.0-0ubuntu4 => 4.1.2-0ubuntu1] (no packageset) (sync)
[19:15] <barry> nacc: possibly :)
[19:16] -queuebot:#ubuntu-release- Unapproved: accepted kdesignerplugin [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[19:19] <nacc> barry: so i'm trying to fix the ftfbs of pacemaker, which is due to a line like `rm -r debian/tmp/usr/lib/python2.7/dist-packages/cts`. This doesn't work with python3, obviously, and ends up failing the build with no-arch-all builds. When i looked in the schroot, though, the resulting path was debian/tmp/usr/lib/python3.5/site-packages/cts -- rather than the expected
[19:20] <nacc> debian/tmp/usr/lib/python3/dist-packages/cts. And I'm not sure I understand why. The package currently doens't use dh_python{,3} and really I just need to `rm` the correct directory (no python files are shipped)
[19:22] <barry> nacc: i believe that one of the things that dh_python3 does is exactly that move (after verification) of .../python3.5 -> .../python3.  it will only do that after it checks that the contents of .../python3.X is the same for all X (and we've run into rare cases where that doesn't happen, so you still end up with python3.4, python3.5, etc. directories.  not on ubuntu though because right now we only have 3.5, but think about e.g. when 3.6
[19:22] <barry> is released
[19:22] <barry> nacc: so dh_python3 is doing that and if you're not using it, you have to fiddle with things manually
[19:24] <nacc> barry: ah i see, so i could in theory invoke dh_python3 from rules and it might dtrt?
[19:24] <barry> nacc: in theory :)
[19:25] <barry> nacc: the only thing is to get the timing right
[19:25] -queuebot:#ubuntu-release- Unapproved: accepted kdesu [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[19:25] -queuebot:#ubuntu-release- Unapproved: accepted kdewebkit [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[19:25] <nacc> barry: right, that's what i'll need to read up on :) after build but before install seems to be the right place
[19:27] <barry> nacc: it *might* be after install, because without that things might not be in right place.  i don't remember exactly, but you can probably figure it out with some experimentation
[19:28] <nacc> barry: yeah, the issue is the rm is being done as the first thing in override_dh_install
[19:28] <nacc> barry: but i think you've pointed me in the right direction :)
[19:29] <barry> nacc: cool, good luck!  i'll need to do a quick reboot in a few moments, but i'll be back (hopefully :) if you have more questions
[19:29] <nacc> barry: thanks!
[19:31] <slangasek> acheronuk: extra-cmake-modules has been failing its autopkgtests since May; is someone taking responsibility for this? http://autopkgtest.ubuntu.com/packages/e/extra-cmake-modules/yakkety/armhf
[19:33] -queuebot:#ubuntu-release- Unapproved: accepted kdnssd-kf5 [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[19:33] -queuebot:#ubuntu-release- Unapproved: probert (yakkety-proposed/universe) [0.0.7 => 0.0.9] (no packageset)
[19:37] -queuebot:#ubuntu-release- Unapproved: accepted probert [source] (yakkety-proposed) [0.0.9]
[19:40] <acheronuk> slangasek: I'm relatively new with that side of things, but I will check..
[19:40] <slangasek> acheronuk: ok :)
[19:50] -queuebot:#ubuntu-release- Unapproved: subiquity (yakkety-proposed/universe) [0.0.15 => 0.0.18] (no packageset)
[19:52] -queuebot:#ubuntu-release- Unapproved: accepted subiquity [source] (yakkety-proposed) [0.0.18]
[20:03] -queuebot:#ubuntu-release- Unapproved: accepted kdoctools [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[20:09] -queuebot:#ubuntu-release- Unapproved: accepted kemoticons [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[20:18] <nacc> barry: ok, i think i figured out why, at least, dh_python{2,3} wasn't already being used. There are no python{,3}- packages, nor are there any with ${python3:Depends}. To be clear, this is a really weird case. Upstream has set of python files under cts/ which are used for testing only. They are not intended to be shipped by any debian/ubuntu package. My original debdiff works for this case, but looks
[20:18] <nacc> weird.
[20:27] <slangasek> beta release notes skeleton up: https://wiki.ubuntu.com/YakketyYak/ReleaseNotes
[20:27] <slangasek> cyphermox: ^^ can you please make sure the no-uefi-on-qemu bug gets documented there?
[20:27] <tkamppeter> Hi, I have uploaded Ghostscript (not yet approved) and need to do another fix in it now. How to proceed? Simply upload Ghostscript again with the same release number?  Or with the release number +1?
[20:28] -queuebot:#ubuntu-release- Unapproved: accepted kfilemetadata-kf5 [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[20:29] <barry> nacc: so it's an app but not a library?
[20:30] <nacc> barry: not sure how to answer that, the underlying code that's being rm'd in the install target is an application (called cts afaict)
[20:32] <barry> nacc: if it's shipping files under cts/ and importing them under that package name but doesn't intend for that to be a public api importable by third parties, then yeah dh_python3 may not be entirely useful, although i have used it in those cases
[20:32] <nacc> barry: i think that's the source of confusion. No files under cts/ are to be shipped
[20:33] <slangasek> tkamppeter: you can reuse the version number and I'll dump the one currently in the queue
[20:33] <nacc> that's what the one line in the override_dh_install effectively is doing (afaict), it's deleting any such potential files
[20:33] <jderose> slangasek: i can add the bit about qemu+uefi no-go to the notes, since i filed the bug. on it now...
[20:33] <barry> nacc: okay, then it makes sense.  probably just want to rm ../python3.*/dist-packages?
[20:33] <tkamppeter> slangasek, OK, let us do it this way. Thank you.
[20:33] <barry> nacc: ie you don't care which version of python3 was used
[20:34] -queuebot:#ubuntu-release- Unapproved: rejected ghostscript [source] (yakkety-proposed) [9.19~dfsg+1-0ubuntu5]
[20:34] <jderose> slangasek: cyphermox says it effects most thinkpads also, so i'll mention that also
[20:35] <nacc> barry: i'd say so, except 'it' (whereby i mean `make`) has put them in python3.5/site-packages
[20:35] <cyphermox> jderose: don't worry, I'm listing it as soon as the wiki lets me through
[20:35] <slangasek> huh
[20:35] <slangasek> lucky we didn't get this SRUed into xenial yet, then
[20:35] -queuebot:#ubuntu-release- Unapproved: initramfs-tools (xenial-proposed/main) [0.122ubuntu8.1 => 0.122ubuntu8.2] (core)
[20:35] <barry> nacc: ah, right it's probably not using setuptools
[20:35] <barry> nacc: ie, our hacked version thereof :)
[20:35] <nacc> barry: correct, it's not
[20:35] <slangasek> lamont, cyphermox: ^^ so one of you has uploaded, then - thanks ;)
[20:36] <jderose> cyphermox: ah, okay. or we could have one more person racing for the lock to add fun :) just kidding, it's all you
[20:36] <barry> nacc: that's why it doesn't end up in dist-packages
[20:36] <nacc> barry: so i wonder if it could do 'rm debian/tmp/usr/lib/python*/*packages/cts' ?
[20:36] <cyphermox> 503...
[20:36] <nacc> barry: that would catch either case?
[20:36] <nacc> barry: and also the case for python2 if that was to be the case on debian?
[20:37] <barry> nacc: yep, and yep
[20:37] <nacc> barry: ack, let me try that then
[20:37] <nacc> barry: thanks for being patient and helping clarify!
[20:37] <barry> nacc: yw!
[20:38] <lamont> slangasek: working through it
[20:38] <cyphermox> slangasek: when I said affects thinkpads, I meant that it doesn't only fail to boot the ISO on qemu, but also on actual hardware.
[20:38] <slangasek> cyphermox: yes, that's what I understood you to mean
[20:38] <cyphermox> so SRUing that to other releases wouldn't have been an issue... except for building the dailies
[20:38] <lamont> slangasek: and thanks to smoser, we can test trivially from -proposed!!  /me owes that man a $BEVERAGE
[20:38] <slangasek> but that means nobody's run yakkety on a thinkpad in a month?
[20:38] <cyphermox> no
[20:39] <slangasek> oh, the bug only applies when shim == /EFI/boot/bootx64.efi?
[20:39] <cyphermox> yes
[20:39] <slangasek> gotcha
[20:39] <barry> yikes, i just noticed that kernel 4.8.0-15 hangs during boot in my vm, but 4.4.0-9136 works okay
[20:39] -queuebot:#ubuntu-release- Unapproved: isc-dhcp (xenial-proposed/main) [4.3.3-5ubuntu12.2 => 4.3.3-5ubuntu12.3] (core)
[20:39] <slangasek> so it affects people running ubuntu-core on their thinkpads ;)
[20:39] <barry> i see 4.8.0-16.17 is in proposed though, so i wont start bisecting until that lands and is tested
[20:39] <cyphermox> slangasek: and it seems dependent on the actual firmware too, as jderose has it working on hardware, from what I understand
[20:40] <cyphermox> slangasek: probably
[20:40] <slangasek> barry: what sort of vm?
[20:40] <cyphermox> slangasek: I expect Dell hardware might break too.
[20:40] <barry> slangasek: fusion 8.5
[20:40] <cyphermox> (but I don't have Dell EFI harware)
[20:40] <slangasek> barry: 4.8.0-15 is still likely to go out as the beta kernel for a number of flavors
[20:41] <barry> slangasek: maybe i should look more closely then.  i always take a snapshot when dist-upgrading, so i can revert and bisect the package list.  it just takes a while
[20:41] -queuebot:#ubuntu-release- Unapproved: open-iscsi (xenial-proposed/main) [2.0.873+git0.3b4b4500-14ubuntu3 => 2.0.873+git0.3b4b4500-14ubuntu3.1] (ubuntu-desktop, ubuntu-server)
[20:43] <slangasek> cyphermox: while you're editing, please fix the missing '>' at the end of 'Less Popular Ubuntu Images' :)
[20:47] <cyphermox> done.
[20:50] -queuebot:#ubuntu-release- Unapproved: accepted kglobalaccel [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[20:51] -queuebot:#ubuntu-release- New binary: linux-signed-lts-trusty [amd64] (precise-proposed/main) [3.13.0-97.144~precise1] (kernel)
[20:51] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (trusty-proposed/main) [3.13.0-97.144] (core, kernel)
[20:51] -queuebot:#ubuntu-release- Unapproved: accepted kguiaddons [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[20:53] <nacc> barry: http://paste.ubuntu.com/23221902/ , thoughts?
[20:53] -queuebot:#ubuntu-release- New: accepted linux-signed-lts-trusty [amd64] (precise-proposed) [3.13.0-97.144~precise1]
[20:53] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (trusty-proposed) [3.13.0-97.144]
[20:53] <barry> nacc: i'd put that comment in d/rules instead of d/changelog, but otherwise +1
[20:54] <gaughen> barry, could you try what's in -proposed?
[20:55] <gaughen> slangasek, do you think that would be useful ^^. cloud-images is going to go out with the kernel in proposed, so I'd like to have an idea if there's trouble lurking sooner rather than later.
[20:55] <barry> gaughen: can do, but i want to narrow down the package set first.  generally on boot problems i restore a known good snapshot (if i've been smart enough to capture ;) and then narrow it down to the 1 or 2 offending packages.  if it's linux i'll try proposed
[20:56] <gaughen> awesome
[20:56] -queuebot:#ubuntu-release- Unapproved: cloud-init (yakkety-proposed/main) [0.7.8-4-g970dbd1-0ubuntu1 => 0.7.8-8-g0439d8a-0ubuntu1] (edubuntu, ubuntu-cloud, ubuntu-server)
[20:56] <lamont> slangasek: smoser's tossing a new upload of cloud-init at xenial-proposed, and beyond that it's my uploads of isc-dhcp, open-iscsi, and initramfs-tools.
[20:56] <lamont> slangasek: as always, thank you for your assistance.
[20:57] <lamont> oh haha.
[20:57] <lamont> dammit cyphermox
[20:57] -queuebot:#ubuntu-release- Unapproved: ghostscript (yakkety-proposed/main) [9.19~dfsg+1-0ubuntu4 => 9.19~dfsg+1-0ubuntu5] (desktop-core, ubuntu-server)
[20:57] <lamont> slangasek: I owe you a new initramfs-tools with the Breaks.
[20:57] <slangasek> mmk
[20:57] -queuebot:#ubuntu-release- Unapproved: accepted khtml [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[20:58] <flexiondotorg> Any decision on if there is a respin coming?
[20:58] <nacc> barry: ack! good point :)
[20:59] <slangasek> acheronuk: why does your ki18n upload replace the python:any dep with python?
[20:59] <tkamppeter> slangasek, Ghostscript is re-uploaded now.
[20:59] <lamont> slangasek: actually... thoughts?  initramfs-tools will break isc-dhcp << 4.3.3-5ubuntu12.3, and also 4.3.3-5ubuntu13.early... can I even capture that in Breaks: ?
[21:00] -queuebot:#ubuntu-release- Unapproved: accepted ki18n [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[21:01] -queuebot:#ubuntu-release- Unapproved: snapcraft (xenial-proposed/universe) [2.18 => 2.18.1] (no packageset)
[21:02] -queuebot:#ubuntu-release- Unapproved: cloud-init (xenial-proposed/main) [0.7.8-1-g3705bb5-0ubuntu1~16.04.1 => 0.7.8-8-g0439d8a-0ubuntu1~16.04.1] (edubuntu, ubuntu-cloud, ubuntu-server)
[21:02] <slangasek> lamont: you can have disjoint sets of versions in breaks... Breaks: isc-dhcp (<< 4.3.3-5ubuntu12.3), isc-dhcp (= 4.3.3-5ubuntu13)
[21:03] <slangasek> addressing it for knock-off builds of 4.3.3-5ubuntu13 isn't critical
[21:03] <slangasek> tkamppeter: cheers
[21:03] <lamont> slangasek: oh, goodl
[21:03] <nacc> barry: does this seem better? http://paste.ubuntu.com/23221941/
[21:04] <barry> nacc: looks great!
[21:04] -queuebot:#ubuntu-release- Unapproved: rejected initramfs-tools [source] (xenial-proposed) [0.122ubuntu8.2]
[21:04] -queuebot:#ubuntu-release- Unapproved: rejected isc-dhcp [source] (xenial-proposed) [4.3.3-5ubuntu12.3]
[21:05] -queuebot:#ubuntu-release- Unapproved: cloud-initramfs-tools (yakkety-proposed/main) [0.28ubuntu1 => 0.29ubuntu1] (edubuntu, ubuntu-server)
[21:06] <sergiusens> slangasek when you have time can you look into letting snapcraft 2.18.1 into xenial-proposed (yakkety is still running though)
[21:06] -queuebot:#ubuntu-release- Unapproved: accepted kiconthemes [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[21:06] -queuebot:#ubuntu-release- Unapproved: pacemaker (yakkety-proposed/main) [1.1.15-1ubuntu1 => 1.1.15-1ubuntu2] (ubuntu-server)
[21:07] <nacc> doko: --^ should fix pacemaker
[21:07] <slangasek> sergiusens: I can commit to getting it reviewed today; or do you need a queue jump so I can unblock you before your EOD?
[21:07] <nacc> i'm sending the same to debian as i type
[21:07] <cjwatson> nacc: oh, you know what, in my earlier remarks I totally failed to notice that that was on a rm command
[21:07] <nacc> cjwatson: it's ok :) i should have made that clearer!
[21:07] <nacc> cjwatson: still learned something about dh_python3, so it's all good :)
[21:07] <sergiusens> slangasek your EOD is fine; I am EOD 7 minutes ago :-)
[21:08] <cjwatson> nacc: so I apologise for the confusion - I agree that just turning that into a wider glob seems right
[21:08] <slangasek> sergiusens: copy
[21:08] <nacc> cjwatson: np! thanks!
[21:09] -queuebot:#ubuntu-release- Unapproved: accepted kidletime [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[21:10] -queuebot:#ubuntu-release- Unapproved: accepted kimageformats [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[21:14] <slangasek> infinity: linux 4.8.0.16 is currently lingering in -proposed.  that's the one needed for fixing server, correct?  Were you planning to bypass autopkgtests to promote it, or are we waiting for those to clear?
[21:14] -queuebot:#ubuntu-release- Unapproved: initramfs-tools (xenial-proposed/main) [0.122ubuntu8.1 => 0.122ubuntu8.2] (core)
[21:14] -queuebot:#ubuntu-release- Unapproved: open-iscsi (xenial-proposed/main) [2.0.873+git0.3b4b4500-14ubuntu3 => 2.0.873+git0.3b4b4500-14ubuntu3.1] (ubuntu-desktop, ubuntu-server)
[21:14] -queuebot:#ubuntu-release- Unapproved: isc-dhcp (xenial-proposed/main) [4.3.3-5ubuntu12.2 => 4.3.3-5ubuntu12.3] (core)
[21:14] <acheronuk> slangasek: looks like that python change was a result of a script meant to bump frameworks build deps for all our frameworks. I'm checking to see if that was an unintended side effect
[21:15] <lamont> slangasek: all 4 are in the queue
[21:17] -queuebot:#ubuntu-release- Unapproved: accepted kinit [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[21:23] <slangasek> acheronuk: ok, cheers.  next up, kio has "Remove a couple of deprecated symbols".  Why is removing these symbols not an ABI-breaking change requiring a binary package name change?
[21:23] <slangasek> (the whole point of symbols files is to guard against accidentally breaking your reverse-dependencies)
[21:25] <barry> gaughen: okay, so it's definitely the kernel.  upgrading all other packages gives me a usable system.  will try proposed now
[21:25] <barry>  
[21:26] -queuebot:#ubuntu-release- Unapproved: accepted kitemmodels [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[21:27] -queuebot:#ubuntu-release- Unapproved: rejected open-iscsi [source] (xenial-proposed) [2.0.873+git0.3b4b4500-14ubuntu3.1]
[21:28] <acheronuk> slangasek: the author of that commit is the same person I need to ask on the other, so I will deal with that tomorrow OK? He's gone out for a few 'refreshments' and is not best placed to respond right now
[21:28] <slangasek> acheronuk: ok
[21:28] -queuebot:#ubuntu-release- Unapproved: accepted kitemviews [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[21:31] <slangasek> lamont: your isc-dhcp upload has debian/initramfs-tools cruft in the diff
[21:31] <lamont> sigh
[21:31] <slangasek> lamont: er, sorry, hangon
[21:31] <slangasek> lamont: it's not cruft, it's just me jumping to conclusions before reading all the way through ;)
[21:31] <lamont> haha
[21:31]  * lamont does the debdiff anyway
[21:32] <lamont> yeah - that looks just like I expect it to
[21:34] <slangasek> ok, so the thing I still don't like about this is that we're making everyone's initramfs .5MB bigger (uncompressed) in SRU
[21:34] <slangasek> if we were dropping klibc in the same go, that would be a fair trade
[21:35] <lamont> fair point..  I understand killing klibc with fire is in-plan, at least..
[21:36]  * lamont cannot speak to the decision process involved there..
[21:36] -queuebot:#ubuntu-release- Unapproved: accepted kjobwidgets [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[21:39] -queuebot:#ubuntu-release- Unapproved: accepted kjs [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[21:41] <slangasek> cyphermox, lamont: can one of you explain /run/net-eth0.conf to me, briefly?  what consumes that?
[21:41] <lamont> cloud-init
[21:41] <lamont> it's a bunch of config vars which then get sourced and used
[21:41] <slangasek> ok
[21:41] <slangasek> and did something else do this elsewhere, before dhclient?
[21:41] <lamont> and open-iscsi (hahahaha *sob*) is the one that creates resolv.conf
[21:41] <lamont> I. Don't. Even.
[21:42] <lamont> klibc's ipconfig
[21:42] <lamont> the change was "use dhclient, and make the output look like ipconfig did  it"
[21:42] <slangasek> so, no, klibc's ipconfig did not do this
[21:42] <lamont> with the logical change being the s/4/6/
[21:42] <slangasek> the code is in /usr/share/initramfs-tools/scripts/functions
[21:42] <lamont> ok. that
[21:42]  * lamont was fuzzy on what exactly did the writing
[21:43] <lamont> I do know that it went from synchronous to async (now done in dhclient hooks)
[21:43] <slangasek> this leaves me wondering if dhclient is the right package to own this, or if it belongs in initramfs-tools
[21:44] <barry> gaughen: 4.0.8-16 from -proposed is *not* happy.  i can't tell exactly wheere it's hanging but the last thing on my console is "Started Bluetooth service".  now it's just sitting there
[21:44] <bjf> apw, ^
[21:44] <barry> gaughen: happy to report bug, do more analysis, etc if you can point me to the right incantations
[21:45] <barry> or apw :)
[21:45] <bjf> barry, we need a bug
[21:45] <barry> bjf: okay.  can't ubuntu-bug it obviously.  file on linux-meta or linux?
[21:45] <bjf> barry, do any of the 4.8 kernels work for you?
[21:45] <barry> bjf: nope
[21:45] <bjf> barry, "linux"
[21:45] <barry> 4.4 does tho
[21:45] <slangasek> lamont: oh - nope, you're right, it's ipconfig spitting this out and initramfs-tools is just picking it up once available
[21:47] -queuebot:#ubuntu-release- Unapproved: accepted kjsembed [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[21:49] <barry> bjf, apw, gaughen LP: #1627198
[21:49] <ubot5`> Launchpad bug 1627198 in linux (Ubuntu) "4.4.8 kernels do not complete boot process on VM" [Undecided,New] https://launchpad.net/bugs/1627198
[21:49] <barry> i'll be around for a while so ping me if you need more information
[21:49] -queuebot:#ubuntu-release- Unapproved: accepted kmediaplayer [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[21:51] <slangasek> lamont, cyphermox: the Breaks: ensure that if there is a dhclient available, it's the one that has the initramfs hook support.  The Breaks: do not guarantee that dhclient is available.  I guess we're ok with this because isc-dhcp-client is in minimal?
[21:51] <lamont> that's my thinking - I verfied that I was conssitent with yakkety
[21:51] <slangasek> and if it's ok to not use Depends: because we know isc-dhcp-client is always available, is there really any reason not to make it a versioned Depends: anyway?
[21:51] <lamont> slangasek: I would have no objection
[21:52] <Saviq> can someone please push qtmir, qtmir-gles, ubuntu-system-settings, unity-api, unity8 through the unapproved queue?
[21:52] <slangasek> Saviq: I can, but it'll be a bit; somewhat contended, sorry
[21:52] <lamont> esp if we don't care about the one-off in current yakkety
[21:52] <lamont> and just go >= isc-dhcp.$UPLOAED
[21:52] <Saviq> slangasek, as long as it happens...
[21:53] <slangasek> lamont: maybe still keep the Breaks: (=)
[21:53] <lamont> ah, works
[21:53] <slangasek> cyphermox: ^^ thoughts?
[21:55] -queuebot:#ubuntu-release- Unapproved: accepted knewstuff [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[21:59] <lamont> slangasek: so...
[21:59] <lamont> Depends: initramfs-tools-core (= ${binary:Version}), linux-base, ${misc:Depends}, isc-d
[21:59] <lamont> hcp-client (>= 4.3.3-5ubuntu12.3)
[21:59] <lamont> Breaks: ... isc-dhcp-client (<< 4.3.3-5ubuntu12.3), isc-dhcp-client (= 4.3.3-5ubuntu13)
[21:59] <lamont> yes?
[21:59] -queuebot:#ubuntu-release- Unapproved: accepted knotifications [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[21:59] <slangasek> lamont: or just Breaks: isc-dhcp-client (= 4.3.3-5ubuntu13)
[22:00] <lamont> slangasek: oh, right,k because of the versiuoned dep.  doh
[22:00] <lamont> so just the equals
[22:00]  * slangasek nods
[22:00] <lamont> you wann push the mulligan button then?
[22:00] -queuebot:#ubuntu-release- Unapproved: accepted knotifyconfig [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[22:04] <lamont> slangasek: say when and I'll re-upload initramfs-tools
[22:04] -queuebot:#ubuntu-release- Unapproved: open-iscsi (xenial-proposed/main) [2.0.873+git0.3b4b4500-14ubuntu3 => 2.0.873+git0.3b4b4500-14ubuntu3.1] (ubuntu-desktop, ubuntu-server)
[22:06] <lamont> and open-iscsi should have bug # now
[22:39] <slangasek> lamont: yah, since cyphermox isn't weighing in, go for it
[22:39] <slangasek> (initramfs-tools)
[22:40] <lamont> pay no attention to the duplicate isc-dhcp upload then
[22:41] -queuebot:#ubuntu-release- Unapproved: initramfs-tools (xenial-proposed/main) [0.122ubuntu8.1 => 0.122ubuntu8.2] (core)
[22:41] -queuebot:#ubuntu-release- Unapproved: isc-dhcp (xenial-proposed/main) [4.3.3-5ubuntu12.2 => 4.3.3-5ubuntu12.3] (core)
[22:43] <infinity> slangasek: I was planning to hint in -16 once I had a few results to say it wasn't entirely broken.
[22:43] <slangasek> infinity: results of what sort?
[22:44] <infinity> slangasek: Some autopkgtest results that show it installs and reboots and one or two dkms modules still work, that sort of thing.
[22:44] <slangasek> infinity: mmk. so is x86 autopkgtest stalled? a lot of 'Test in progress' there
[22:45] <infinity> slangasek: I'd say kde ate the queue. :/
[22:45] <slangasek> hmm
[22:45] <slangasek> those were all released after linux-meta, I thought
[22:46] <slangasek> apw: ^^
[22:46]  * lamont afk
[22:46] <valorie> we ate the queue?
[22:47] <valorie> oh my
[22:47] <slangasek> not really
[22:47] <slangasek> I think the runners are AWOL
[22:49] <slangasek> infinity: http://autopkgtest.ubuntu.com/running shows precisely 2 running amd64 tests and 0 for i386
[22:49] <slangasek> so our runners are missing
[22:49] <slangasek> pitti: halp
[22:49] <infinity> slangasek: That seems suboptimal indeed.
[22:49] <infinity> slangasek: We can just smoketest this x86 the old fashioned way.
[22:50] <infinity> ogasawara: *bat signal*
[22:52] -queuebot:#ubuntu-release- Unapproved: tickcount (yakkety-proposed/main) [0.1-0ubuntu17 => 0.1-0ubuntu18] (ubuntu-server)
[22:57] <infinity> slangasek: Spinning up two VMs to smoketest amd64 and x86, then will unblock.
[22:57] <infinity> s/x86/i386/
[22:57] <slangasek> infinity: ack
[22:58] <tsimonq2> :O
[23:04] <infinity> amd64 installs/reboots and looks good.
[23:05] <ogasawara> infinity: ack
[23:05] <infinity> Bonus points, that was on an old skool ATA qemu interface, not virtio.
[23:05] -queuebot:#ubuntu-release- Unapproved: rejected initramfs-tools [source] (xenial-proposed) [0.122ubuntu8.2]
[23:06] <tsimonq2> y'all need netboot testing?
[23:06] <tsimonq2> I can help
[23:06] <infinity> And i386 same story.  So hinting.
[23:06] <slangasek> infinity: cheers
[23:08] <slangasek> lamont: sorry, I should get better at doing single pass reviews
[23:08] <slangasek> +       set -x
[23:08] <slangasek> lamont: ^^ is that really expected?
[23:09] <slangasek> looks like development cruft that should've been dropped
[23:13] <slangasek> cyphermox: ^^?
[23:18] -queuebot:#ubuntu-release- Unapproved: rejected open-iscsi [source] (xenial-proposed) [2.0.873+git0.3b4b4500-14ubuntu3.1]
[23:18] -queuebot:#ubuntu-release- Unapproved: rejected isc-dhcp [source] (xenial-proposed) [4.3.3-5ubuntu12.3]
[23:26] <slangasek> lamont: lastly... LP: #1621507 includes no test case or regression risk analysis
[23:26] <ubot5`> Launchpad bug 1621507 in isc-dhcp (Ubuntu) "initramfs-tools configure_networking() fails to dhcp ipv6 addresses" [High,In progress] https://launchpad.net/bugs/1621507
[23:36] -queuebot:#ubuntu-release- Unapproved: accepted kpackage [source] (yakkety-proposed) [5.26.0-0ubuntu1]
[23:38] <slangasek> Saviq: ah, so you had asked about putting them through the unapproved queue... they did go through the queue already and are just stalled in proposed now, I thought you were asking after the latter
[23:39] <Saviq> slangasek, yeah, but that happened just around the time I asked you, or at least that was their status then - I saw they're in proposed now, thanks
[23:39] <slangasek> Saviq: actually they were accepted about 3 hours before you asked <shrug> :)
[23:40] <slangasek> but no worries
[23:40] <Saviq> yeah, must've been stale data on my side
[23:44] -queuebot:#ubuntu-release- Unapproved: accepted libphonenumber [sync] (yakkety-proposed) [7.1.0-5ubuntu1]
[23:47] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-keyboard [sync] (yakkety-proposed) [0.100+16.10.20160921-0ubuntu1]
[23:47] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-keyboard [sync] (yakkety-proposed) [0.100+16.10.20160921-0ubuntu1]