[00:01] <marco-parillo> TY
[00:18]  * xnox emerges from bubble bath, just in time for hot chocolate and fresh d-i
[00:19] <xnox> so nice accepted queue allows downloads
[00:31] <xnox> Apart from:
[00:31] <xnox> Sep 21 19:25:00 debootstrap: dpkg: warning: parsing file '/var/lib/dpkg/status' near line 4 package 'dpkg':
[00:31] <xnox> Sep 21 19:25:00 debootstrap:  missing description
[00:31] <xnox> Sep 21 19:25:00 debootstrap: dpkg: warning: parsing file '/var/lib/dpkg/status' near line 4 package 'dpkg':
[00:31] <xnox> Sep 21 19:25:00 debootstrap:  missing maintainer
[00:31] <xnox> Sep 21 19:25:00 debootstrap: dpkg: warning: parsing file '/var/lib/dpkg/status' near line 4 package 'dpkg':
[00:31] <xnox> Sep 21 19:25:00 debootstrap:  missing architecture
[00:31] <xnox> things look fine....
[00:31] <infinity> That's normal.
[00:32] <infinity> debootstrap fakes the dpkg entry on the first pass.
[00:32] <xnox> ah.
[00:32] <xnox> maybe it should fake better?! =)
[00:32] <xnox> nevermind.
[00:34] <slangasek> cjwatson, infinity: not sure how long it's sensible for a livefs build to be paused at 'remove-build', but: https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/yakkety/ubuntustudio/+build/76157
[00:34] <xnox> infinity, slangasek - 4.8.0-14.15 is good, and debian-installer 20101020ubuntu475 are good. Did automated preseed install in z/vm. Will do another one in an LPAR now.
[00:34] <xnox> on s390x that is.
[00:41] <infinity> slangasek: It's not paused at remove-build.
[00:41] <infinity> slangasek: Note that it's already got the full build log, it's just sucking down the livefs.
[00:42] <slangasek> k
[00:42] <infinity> slangasek: Which can take a while, depending on network oddities.
[00:42] <infinity> (Admittedly, I've been annoyed by how we don't give reasonable feedback there either)
[00:42] <infinity> It should probably not show the log tail at all, and be in a "downloading results" state or something.
[00:43] -queuebot:#ubuntu-release- Unapproved: fruit (yakkety-proposed/universe) [2.1.dfsg-6 => 2.1.dfsg-7] (no packageset) (sync)
[00:44] -queuebot:#ubuntu-release- Unapproved: accepted fruit [sync] (yakkety-proposed) [2.1.dfsg-7]
[00:44] <infinity> That's a state that used to last under a minute for most builds, so no one really noticed, but with ddebs and livefses and builders in other DCs, etc, things can seem "hung" there for a very long time, and it's certainly not intuitive.
[00:44] -queuebot:#ubuntu-release- Unapproved: openbabel (yakkety-proposed/universe) [2.3.2+dfsg-2.3 => 2.3.2+dfsg-2.4] (kubuntu) (sync)
[00:45] <slangasek> infinity: clearly we should switch to using rsync for copying the livefses out of the builders
[00:46] <infinity> I suppose we could actually use zsync, if we could reliably identify an ancestor.
[00:46] <infinity> And if twisted's httpd supports range requests.
[00:47] <slangasek> ok I should stop nerdsniping infinity
[00:48] <xnox> meanwhile lpar install works too
[00:48]  * xnox -> Zzzzz
[00:48] <infinity> xnox: Excellent, thanks for testing.
[00:49] <infinity> Will wait for more autopkgtest love and then let that kernel/d-i through.
[00:54] <mwhudson> infinity: twistd's http server does support range requests! i implemented it!
[00:54] <mwhudson> for static.Files anyway
[00:55] <mwhudson> can someone release docker.io from xenial NEW? (there is a new docker-doc package)
[00:57] <xnox> does zope support http/2 ?
[01:09] <mwhudson> xnox: i don't think zope implements http itself, so that's really a question about whatever it's using for that
[01:09] <mwhudson> (and i don't know what that is)
[01:21] <infinity> mwhudson: That may prove useful to know some day.
[01:21] <mwhudson> not for me i hope :)
[01:21] -queuebot:#ubuntu-release- Unapproved: xfce4-session (yakkety-proposed/universe) [4.12.1-3ubuntu2 => 4.12.1-3ubuntu3] (xubuntu)
[01:21] <mwhudson> oh, the Range header support?
[01:22] <infinity> mwhudson: Yeah.
[01:23] <mwhudson> it was part of a secret plan to not use apache for bazaar.launchpad.net that never really got anywhere
[01:31] -queuebot:#ubuntu-release- Builds: Netboot amd64 [Yakkety Beta 2] (20101020ubuntu475) has been added
[01:31] -queuebot:#ubuntu-release- Builds: Netboot arm64 [Yakkety Beta 2] (20101020ubuntu475) has been added
[01:31] -queuebot:#ubuntu-release- Builds: Netboot armhf [Yakkety Beta 2] (20101020ubuntu475) has been added
[01:31] -queuebot:#ubuntu-release- Builds: Netboot i386 [Yakkety Beta 2] (20101020ubuntu475) has been added
[01:31] -queuebot:#ubuntu-release- Builds: Netboot powerpc [Yakkety Beta 2] (20101020ubuntu475) has been added
[01:31] -queuebot:#ubuntu-release- Builds: Netboot ppc64el [Yakkety Beta 2] (20101020ubuntu475) has been added
[01:31] -queuebot:#ubuntu-release- Builds: Netboot s390x [Yakkety Beta 2] (20101020ubuntu475) has been added
[01:31] <Ukikie> If anyone asks, Xubuntu does not need a respin for the xfce4-session upload.
[02:04] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD amd64 [Yakkety Beta 2] (20160921.2) has been added
[02:04] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD i386 [Yakkety Beta 2] has been updated (20160921.2)
[02:16] <infinity> Ukikie: No, but you'll get one for a new kernel.
[02:16] <Ukikie> infinity: And you really think we need a newer one?  I was considering dropping it, we don't need any kernels!
[02:16] <Ukikie> OK, I'll go somewhere else now..
[02:37] -queuebot:#ubuntu-release- Unapproved: accepted snapcraft [source] (xenial-proposed) [2.18]
[02:41] -queuebot:#ubuntu-release- Unapproved: cups (yakkety-proposed/main) [2.2.0-1 => 2.2.0-2] (core) (sync)
[03:07] <Ukikie> infinity: Been presuming syncing gcalcli would be too late at this point, right?
[04:32] -queuebot:#ubuntu-release- Unapproved: gnome-multi-writer (yakkety-proposed/universe) [3.21.92-1 => 3.22.0-1] (no packageset) (sync)
[04:33] -queuebot:#ubuntu-release- Unapproved: accepted gnome-multi-writer [sync] (yakkety-proposed) [3.22.0-1]
[04:36] -queuebot:#ubuntu-release- Unapproved: flatpak (yakkety-proposed/universe) [0.6.10-1 => 0.6.11-1] (no packageset) (sync)
[04:37] -queuebot:#ubuntu-release- Unapproved: accepted flatpak [sync] (yakkety-proposed) [0.6.11-1]
[04:37] -queuebot:#ubuntu-release- Unapproved: linuxinfo (yakkety-proposed/universe) [2.4.1-1 => 2.4.2-1] (no packageset) (sync)
[04:38] -queuebot:#ubuntu-release- Unapproved: accepted linuxinfo [sync] (yakkety-proposed) [2.4.2-1]
[05:18] <pitti> slangasek, cyphermox, lamont: meh, seems nobody else reviewed the changes over night; FWIW, not too happy about using isc-dhcp in the initrd for this (longer-term I think we want to run netplan/networkd from the initrd already), and it's awfully late/intrusive for the beta, but having it do the exercises in -proposed is okay still
[05:19] -queuebot:#ubuntu-release- Unapproved: accepted isc-dhcp [source] (yakkety-proposed) [4.3.3-5ubuntu14]
[05:19] -queuebot:#ubuntu-release- Unapproved: accepted initramfs-tools [source] (yakkety-proposed) [0.125ubuntu4]
[05:20] -queuebot:#ubuntu-release- Unapproved: rejected cups [sync] (yakkety-proposed) [2.2.0-2]
[05:20] -queuebot:#ubuntu-release- Unapproved: rejected cups [sync] (yakkety-proposed) [2.2.0-2]
[05:30] <infinity> pitti: Does networkd also require systemd?
[05:30] <infinity> pitti: Cause I'm pretty opposed to the dracut solution of a full blown init in the initrd.
[05:33] <pitti> infinity: no, it doesn't
[05:34] <infinity> What's the big complaint about dhclient, other than the random grumblings about speed?
[05:34] <infinity> It does a better job at being standards-compliant than just about anything else, at least.
[05:35] <pitti> infinity: mostly just that we are just moving away from it on server/cloud at least
[05:35] <pitti> (and upstream NM as well)
[05:36] <pitti> and for things like open-iscsi it makes much more sense to configure stuff once rather than these eternal special snowflake code in initrd
[05:38] <pitti> infinity: anyway, wrt. coordinating this with beta -- do you want me to unblock/land this as soon as britney is content with it?
[05:39] <pitti> (I hope it was tested with netboot)
[05:40] <infinity> pitti: I'll be around for a bit, babysitting some kernel migration, so let me know when it looks goodish, and we'll make a call then.
[05:47] <pitti> cyphermox: why hooks/zz-dhclient btw? I don't see a particular reason why this needs to run after zz-busybox-initramfs, particular as that one documents that it wants to be last
[05:48] <Skuggen> pitti: Hi
[05:48] <pitti> hey Skuggen
[05:48] <Skuggen> pitti: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#mysql-5.7 I think the two in progress runs are stuck. Any tips on what I should do?
[05:49] <Skuggen> They're both (always failed)
[05:49] <pitti> Skuggen: yes, please just ignore them -- they are blacklisted as they break s390x testbeds, and britney ignores them
[05:49] <pitti> Skuggen: it's fine to land, other than the beta freeze block
[05:49] <Skuggen> Ah, then I guess I should request an unblock for it. It's got an important security update
[05:52] <pitti> meh, new kernel consistently breaks systemd's tests now
[06:36] <doko> infinity: is there a chance to rebuild the chroot images for yakkety?
[06:36] <doko> pitti: same for the autopkg test images now that linux 4.8 is in?
[06:37] <pitti> doko: how do you mean?
[06:37] <pitti> tests run with 4.8 now, yes
[06:37] <pitti> (as soon as it landed)
[06:37] <doko> The following packages were automatically installed and are no longer required:
[06:37] <doko>   linux-headers-4.4.0-9136 linux-headers-4.4.0-9136-generic
[06:37] <doko> Use 'apt autoremove' to remove them.
[06:38] <pitti> yeah, that'll go away as soon as the next cloud image gets built
[06:38] <doko> ahh, ok
[06:38] <pitti> I use whichever is most recent and then dist-upgrade and reboot
[07:13] -queuebot:#ubuntu-release- Unapproved: stress-ng (yakkety-proposed/universe) [0.06.16-1 => 0.06.17-1] (no packageset) (sync)
[07:13] -queuebot:#ubuntu-release- Unapproved: accepted stress-ng [sync] (yakkety-proposed) [0.06.17-1]
[07:21] -queuebot:#ubuntu-release- Unapproved: ldb (yakkety-proposed/main) [2:1.1.26-1ubuntu4 => 2:1.1.26-1ubuntu5] (core)
[07:26] -queuebot:#ubuntu-release- Unapproved: accepted ldb [source] (yakkety-proposed) [2:1.1.26-1ubuntu5]
[07:29] <sakrecoer> thankd slangasek and infinity :) the ubuntu studio iso seems to be build and in the tracker now \o/
[07:35] -queuebot:#ubuntu-release- Unapproved: pygobject (yakkety-proposed/main) [3.21.92-1 => 3.22.0-1] (core) (sync)
[07:47] -queuebot:#ubuntu-release- Unapproved: khtml (yakkety-proposed/universe) [5.24.0-0ubuntu2 => 5.24.0-0ubuntu3] (kubuntu)
[08:05] -queuebot:#ubuntu-release- Unapproved: libabw (yakkety-proposed/main) [0.1.1-2ubuntu2 => 0.1.1-4ubuntu1] (kubuntu, ubuntu-desktop)
[08:22] -queuebot:#ubuntu-release- Unapproved: wine (yakkety-proposed/universe) [1.8.4-1ubuntu1 => 1.8.4-1ubuntu2] (no packageset)
[08:22] -queuebot:#ubuntu-release- Unapproved: accepted wine [source] (yakkety-proposed) [1.8.4-1ubuntu2]
[08:42] <flexiondotorg> infinity, You available to talk yaboot?
[08:43] <flexiondotorg> https://bugs.launchpad.net/ubuntu/+source/yaboot/+bug/1606089
[08:43] <ubot5`> Ubuntu bug 1606089 in yaboot (Ubuntu) "unable to boot after 'entire disk' install (16.10, ppc)" [Undecided,Confirmed]
[08:43] <flexiondotorg> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1607128
[08:43] <ubot5`> Ubuntu bug 1607128 in ubiquity (Ubuntu) "'entire disk' install crashes (16.10, ppc)" [Undecided,New]
[08:44] <flexiondotorg> I notice yaboot has in excuses and has been for some months.
[08:44] <flexiondotorg> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1607128
[08:44] <ubot5`> Ubuntu bug 1607128 in ubiquity (Ubuntu) "'entire disk' install crashes (16.10, ppc)" [Undecided,New]
[08:44] <flexiondotorg> https://launchpadlibrarian.net/282065209/buildlog_ubuntu-yakkety-powerpc.yaboot_1.3.17-2ubuntu1_BUILDING.txt.gz
[08:46] <flexiondotorg> http://metadata.ftp-master.debian.org/changelogs//main/y/yaboot/yaboot_1.3.17-4_changelog
[08:46] <infinity> flexiondotorg: Yeah, I need to fix one of yaboot's build-deps.  It's not been the top of my list, but will do.
[08:46] <flexiondotorg> Anything I can do to help?
[08:47] <infinity> Probably not.
[08:47] <infinity> It's ultimately a dpkg bug.  But I might work around it elsewhere for now to unstick all that.
[08:48] <flexiondotorg> OK
[09:02] <acheronuk> khtml is in the upload queue, but unapproved. I assume that will eventually go in when things unfreeze?
[09:07] -queuebot:#ubuntu-release- New binary: wine [amd64] (yakkety-proposed/universe) [1.8.4-1ubuntu2] (no packageset)
[09:08] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-gnome-meta [source] (yakkety-proposed) [0.69]
[09:12] <pitti> cyphermox, infinity: FTR, the multipath-tools test with/for the new initramfs-tools consistently breaks networking on rebooting the test instances; that's why the test is just looping and never finishes
[09:12] <pitti> happens on all three clouds and arches
[09:13] <infinity> pitti: Fun...
[09:13] -queuebot:#ubuntu-release- Unapproved: accepted khtml [source] (yakkety-proposed) [5.24.0-0ubuntu3]
[09:13] <pitti> so if you are sure that this doesn't break stuff (particularly things like iscsi), we can certainly override it, but I'd like to get some more "it works!" and "yes, force everything into the beta" confirmation
[09:14] <infinity> pitti: Yeah, I'm not convinced myself yet either.
[09:14] -queuebot:#ubuntu-release- Unapproved: accepted xfce4-session [source] (yakkety-proposed) [4.12.1-3ubuntu3]
[09:15]  * pitti runs it again without -proposed on the infra, maybe it's the new kernel too (that already caused at last three regressions, wouldn't totally surprise me)
[09:16] -queuebot:#ubuntu-release- Unapproved: accepted qemu [source] (yakkety-proposed) [1:2.6.1+dfsg-0ubuntu4]
[09:27] <davmor2> infinity, cyphermox: did you manage to resolve the policykit issue that was stopping 3rd party drivers installing?
[09:30] <infinity> davmor2: I'm not sure I was aware of the issue to start with.
[09:32] <davmor2> infinity: but I tagged you in on the bug report yesterday and everything ;) https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1626108
[09:32] <ubot5`> Ubuntu bug 1626108 in ubiquity (Ubuntu) "Ubiquity session isn't setting up 3rd party hardware drivers" [Undecided,New]
[09:32] <davmor2> infinity: critical regression
[09:38] -queuebot:#ubuntu-release- Unapproved: docker.io (xenial-proposed/universe) [1.12.1-0ubuntu7~16.04 => 1.12.1-0ubuntu12~16.04] (no packageset)
[09:40] <pitti> apw: I found out the cause of bug 1626394 -- 4.8 dropped CONFIG_ATA=y and now builds them as a module; that means that we now *always* require an initrd to boot
[09:40] <ubot5`> bug 1626394 in systemd (Ubuntu) "4.8 dropped CONFIG_ATA=y (breaks systemd's TEST-08-ISSUE-2730 upstream test)" [Undecided,In progress] https://launchpad.net/bugs/1626394
[09:40] <pitti> apw: from a POV of "don't break existting installs" and boot speed POV I don't think this is desireable
[09:41] <pitti> apw: was that a deliberate policy decision (must have initrd), or an error? i. e. shoudl the linux task be "wontfix" or triaged?
[09:44] <apw> pitti, i am inclined to say that was an error, especially if something is relying on it
[09:45] <apw> pitti, in general we have always said (in my opinion) in ubuntu that an initrd is "required" but ... making life hard is also undesirable
[09:45] <pitti> we certainly do install one by default (well, not sure about snappy, but I figure it does too), but so far you could actually boot without one just fine
[09:46] <pitti> and conceptually, > 95% of installations (especially if you count in cloud instances) really don't need one
[09:46] <apw> pitti, right on a very limited subset of hardware which likely includes some virtual hardware ... i think that one is wrong regardless of why it was done
[09:47] <apw> pitti, though cloud h/w needs virtio instead in the main, but anyhow, i've added that issue to the pile
[09:47] <pitti> apw: you need an initrd with encrypted root and for zfs and the like; and for root= with a UUID/label (which is simple enough to switch off while you disable initrd)
[09:48] <pitti> apw: yeah, I didn't check which additional drivers beyond CONFIG_ATA are required; I figure at least some CONFIG_PATA_* ones
[09:48] <apw> pitti, yep, i am pretty sure we claim you always need it, and are wrong, and we definaly made it worse and we very likley should not
[09:48] <pitti> although the only one that we enabled in 4.4 was CONFIG_PATA_SIS=y
[09:48] <apw> a long time back we picked 4 which were the most common to build in, so i think we should be making sure that list is the same
[09:50] <apw> pitti, i've hijacked your bug adding that request
[09:50] <pitti> apw: virtio certainly does sound interesting; the initrd is one of the biggest chunks of wasted time in cloud instances (bug 1592684)
[09:50] <ubot5`> bug 1592684 in cloud-init (Ubuntu) "Add MODULES=dep initramfs configuration" [Wishlist,Triaged] https://launchpad.net/bugs/1592684
[09:50] <pitti> apw: please do,  it's meant to be used as a kernel bug, unless you would say "it's intended, deal with it"
[09:51] <pitti> apw: happy to close the systemd task as wontfix and keep the britney override on amd64 until then
[09:51] <apw> pitti, i think we're in the wrong here, but if not i'll get back to you.  i see a beta + day 0 kernel in our future, especially if we nail this kworker thing today
[09:52] <pitti> apw: yeah, not that urgent; it was hidden behind another regression in the systemd tests, so I didn't see it until today
[09:52] <pitti> apw: i. e. this is absolutely not beta critical
[09:53] <apw> pitti, ack on that ...
[09:53] <infinity> pitti: We've had a lot of discussions about minimizing or removing the initrd, but it's certainly current Ubuntu policy that one is required, and you're on your own if you go without.
[09:54] <infinity> And there's always an annoying balance between what you build in to allow initrdless and what's bloat to people who don't need it.
[09:54] <pitti> infinity: yes, I know; hence I was asking whether that was an explicit policy change now
[09:55] <apw> pitti, and we might come back and say that but i do not recall us changing the default set this cycle
[09:56] <pitti> apw: thanks; let me know, if you wontfix the linux task, I'll change the qemu tests in systemd to cope (and force an initrd)
[09:56] <pitti> i. e. I'm not worried much about these tests themselves, more like the effect of actually breaking boot without initrd
[10:24] <pitti> cyphermox: multipath-tools still tests fine in y-release (without -proposed), so definitively some regression there and not the kernel
[10:31] -queuebot:#ubuntu-release- Unapproved: kboot-installer (yakkety-proposed/main) [0.0.1ubuntu9 => 0.0.1ubuntu10] (core)
[10:44] <lamont> pitti: infinity: I know that I have used it to netboot maas images, and I plan to roll things from yakkety-proposed this AM once I actually hit the office
[10:52] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (yakkety-proposed/main) [4.8.0-15.16] (core, kernel)
[10:53] -queuebot:#ubuntu-release- Unapproved: emacs24 (yakkety-proposed/main) [24.5+1-6ubuntu3 => 24.5+1-7ubuntu1] (ubuntu-desktop)
[11:14] -queuebot:#ubuntu-release- Unapproved: gcc-snapshot (yakkety-proposed/universe) [20160902-1ubuntu1 => 20160922-1ubuntu1] (no packageset)
[11:14] -queuebot:#ubuntu-release- Unapproved: accepted gcc-snapshot [source] (yakkety-proposed) [20160922-1ubuntu1]
[11:16] -queuebot:#ubuntu-release- Unapproved: software-properties (yakkety-proposed/main) [<IP_ADDRESS> => <IP_ADDRESS>] (desktop-core, ubuntu-server)
[11:17] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (yakkety-proposed) [4.8.0-15.16]
[11:55] <tkamppeter> I have a problrm with syncpackage. Itry to sync the bugfix-patched cups 2.2.0-2 into yakkety, syncpackage accepts without error message but I do not get a mail telling that it was uploaded to yakkety-proposed, no moderator approval-needed nor rejection. And I can repeat the syncpackage without error messages that I have already done it.
[11:56] <tkamppeter> How do I get this bug fix into yakkety?
[12:01] <infinity> tkamppeter: It's in the queue, it's just a bug that you don't get mails on copies.
[12:01] <infinity> https://launchpad.net/ubuntu/yakkety/+queue?queue_state=1&queue_text=
[12:02] <tkamppeter> infinity, so it is waiting for approval now due to the fact that we are after beta freeze?
[12:02] <infinity> tkamppeter: Yeahp.
[12:03] -queuebot:#ubuntu-release- Unapproved: cups (yakkety-proposed/main) [2.2.0-1 => 2.2.0-2] (core) (sync)
[12:05] <tkamppeter> infinity, thanks, seems all OK then. Seems that I have to open this channel before syncing to get an confirmation message.
[12:05] <tkamppeter> infinity, will the mail notifications get fixed soon?
[12:05] <infinity> tkamppeter: It's been a bug for years, so I doubt it. :P
[12:06] <infinity> tkamppeter: Also, rejecting one of those, cause we don't need two. :)
[12:06] <tkamppeter> infinity, I got mail notifications on syncs up to some days ago.
[12:06] <infinity> tkamppeter: The bug is a lack of mail notification when a sync is held in a queue (ie: new or unapproved)
[12:07] <infinity> tkamppeter: You get a mail when it's accepted.
[12:07] -queuebot:#ubuntu-release- Unapproved: rejected cups [sync] (yakkety-proposed) [2.2.0-2]
[12:07] <tkamppeter> infinity, the additional sync now was simply a test to see what happens.
[12:08] <tkamppeter> infinity, OK, then I know that all is OK. Thanks.
[12:15] -queuebot:#ubuntu-release- Unapproved: debian-installer (yakkety-proposed/main) [20101020ubuntu475 => 20101020ubuntu476] (core)
[12:16] -queuebot:#ubuntu-release- Unapproved: accepted debian-installer [source] (yakkety-proposed) [20101020ubuntu476]
[12:19] <xnox> because efi =) lovely
[12:35] <pitti> oh, that would explain why I'm chasing ever-looping tests because of reboot failures
[12:36]  * pitti already has wondered why yakkety tests seem to crumble away like mad
[12:37] <pitti> hm, acually not that, ubuntu/ubuntu-yakkety-daily-amd64-server-20160918-disk1.img just genuinely refuses to boot on lcy01
[12:40] <davmor2> pitti: in kvm with uefi the latest images refuse to boot it looks to me like it is trying to boot from BOOTx64.efi which then produces a black screen and nothing else
[12:42] <davmor2> pitti: grubx64.efi if I select boot from file just does nothing with secureboot enabled I need to disable secureboot and then sometimes you'll get lucky and it will boot
[12:43] <davmor2> pitti: yey on hardware it boots, however digging into issue I just noticed that there is no EFI entry for the installed system so cyphermox and co won't be too happy
[12:44] <xnox> pitti, davmor2 you did notice https://launchpad.net/ubuntu/+source/linux/4.8.0-15.16 published two hours ago with EFI boot fix for bug #1626158
[12:44] <ubot5`> bug 1626158 in cloud-images "image won't boot after upgrading to yakkety's 4.8 kernel because efi" [Critical,Confirmed] https://launchpad.net/bugs/1626158
[12:44] <xnox> together with d-i in proposed
[12:45] <davmor2> xnox: checking to see if there is a current image with it on
[12:46] <davmor2> xnox: so it isn't on the current images yet which is why I still see it then
[12:46] <xnox>  /o\
[12:47] <xnox> Odd_Bloke, can you pre-respin cloudimages with yakkety-proposed kernel by any chance?
[12:47]  * xnox will pronounce EFI as iffy from now on
[12:47] <davmor2> xnox: oh hang on is it only in proposed?
[12:47] <xnox> davmor2, fixed one, yeah.
[12:47] <pitti> xnox: hmm, for me it's that they don't get any DHCP response, so I suppose that's something else
[12:47] <davmor2> xnox: okay let me grab that image then
[12:48] <xnox> davmor2, /me is talking about kernel package, no idea about cloudimages....
[12:48] <davmor2> xnox: I was grabbing from current which is what we test for release
[12:48] <davmor2> xnox: oh so might not of hit the cdimage infrastructure at all then
[12:48] <xnox> davmor2, check manifests of packages to see what it has.
[12:49] <xnox> well, kernel must be published and migrate to release; then images are usually respun to include things.
[12:50] <davmor2> xnox: on cdimage proposed we have linux-generic-4.8.0-11.12
[12:51] <davmor2> xnox: yeah only I think it has to be manually now because of the freeze infinity would know though
[12:52] <infinity> davmor2: Yeah, new images with the new kernel will happen in a couple of hours, likely.
[12:52] <pitti> oh, kernel 4.8 just boot slooooooooow in scalingstack as well apparently
[12:53] <pitti> sorry, don't rely on getting any testing results soon; I'm fighting broken 4.8, broken images, and broken networking
[12:53] <pitti> i. e. if you want to land the -proposed kernel soon, force it in
[12:54] <infinity> pitti: I was hoping to see *some* results (ie: to prove it installs and boots), but was indeed planning to skip most of the testing based on visual review of the delta.
[12:54] <pitti>       └─cloud-init.service @9.467s +1min 55.581s
[12:54] <pitti> so what's that now
[12:56] <Odd_Bloke> xnox: infinity: AFAIK, we're waiting for the new kernel to land to announce beta cloud images.
[12:56] <infinity> Odd_Bloke: Do you need the new cloud-init too?
[12:57] <infinity> Oh, I see, that's tied up with the initramfs-tools changes we might not land.
[12:57] <Odd_Bloke> infinity: I didn't know about the new cloud-init, but it sounds like you do. :p
[12:59] <xnox> Odd_Bloke, server/desktop/d-i are yet to be fully published, or boot tested.
[13:30] -queuebot:#ubuntu-release- Builds: Netboot amd64 [Yakkety Beta 2] has been updated (20101020ubuntu476)
[13:30] -queuebot:#ubuntu-release- Builds: Netboot arm64 [Yakkety Beta 2] has been updated (20101020ubuntu476)
[13:30] -queuebot:#ubuntu-release- Builds: Netboot armhf [Yakkety Beta 2] has been updated (20101020ubuntu476)
[13:31] -queuebot:#ubuntu-release- Builds: Netboot i386 [Yakkety Beta 2] has been updated (20101020ubuntu476)
[13:31] -queuebot:#ubuntu-release- Builds: Netboot powerpc [Yakkety Beta 2] has been updated (20101020ubuntu476)
[13:31] -queuebot:#ubuntu-release- Builds: Netboot ppc64el [Yakkety Beta 2] has been updated (20101020ubuntu476)
[13:31] -queuebot:#ubuntu-release- Builds: Netboot s390x [Yakkety Beta 2] has been updated (20101020ubuntu476)
[13:40] <pitti> infinity: some results are coming in now
[13:40] <pitti> infinity: note "Unblock request by adconrad ignored due to version mismatch: <IP_ADDRESS>.23"
[13:48] <infinity> pitti: Right, I haven't unblocked the new one yet. :P
[13:54] -queuebot:#ubuntu-release- Unapproved: attica-kf5 (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:54] -queuebot:#ubuntu-release- Unapproved: bluez-qt (yakkety-proposed/universe) [5.24.0-0ubuntu2 => 5.26.0-0ubuntu1] (kubuntu)
[13:54] -queuebot:#ubuntu-release- Unapproved: baloo-kf5 (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:55] -queuebot:#ubuntu-release- Unapproved: breeze-icons (yakkety-proposed/universe) [4:5.24.0-0ubuntu1 => 4:5.26.0-0ubuntu1] (kubuntu)
[13:55] -queuebot:#ubuntu-release- Unapproved: frameworkintegration (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:55] -queuebot:#ubuntu-release- Unapproved: kactivities-stats (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (no packageset)
[13:55] -queuebot:#ubuntu-release- Unapproved: karchive (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:55] -queuebot:#ubuntu-release- Unapproved: kbookmarks (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:55] -queuebot:#ubuntu-release- Unapproved: kcodecs (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:55] -queuebot:#ubuntu-release- Unapproved: kconfig (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:55] -queuebot:#ubuntu-release- Unapproved: extra-cmake-modules (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:55] -queuebot:#ubuntu-release- Unapproved: kapidox (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:55] -queuebot:#ubuntu-release- Unapproved: kcmutils (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:55] -queuebot:#ubuntu-release- Unapproved: kconfigwidgets (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:55] -queuebot:#ubuntu-release- Unapproved: kactivities-kf5 (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:55] -queuebot:#ubuntu-release- Unapproved: kcompletion (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:55] -queuebot:#ubuntu-release- Unapproved: kauth (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:56] -queuebot:#ubuntu-release- Unapproved: kcoreaddons (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:56] -queuebot:#ubuntu-release- Unapproved: kdbusaddons (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:56] -queuebot:#ubuntu-release- Unapproved: kded (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:56] -queuebot:#ubuntu-release- Unapproved: kdesignerplugin (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:56] -queuebot:#ubuntu-release- Unapproved: kdewebkit (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:56] -queuebot:#ubuntu-release- Unapproved: kcrash (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:56] -queuebot:#ubuntu-release- Unapproved: kdelibs4support (yakkety-proposed/universe) [5.24.0-0ubuntu2 => 5.26.0-0ubuntu1] (kubuntu)
[13:56] -queuebot:#ubuntu-release- Unapproved: kdeclarative (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:56] -queuebot:#ubuntu-release- Unapproved: kdesu (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:57] -queuebot:#ubuntu-release- Unapproved: kdnssd-kf5 (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:57] -queuebot:#ubuntu-release- Unapproved: kemoticons (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:57] -queuebot:#ubuntu-release- Unapproved: kglobalaccel (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:57] -queuebot:#ubuntu-release- Unapproved: khtml (yakkety-proposed/universe) [5.24.0-0ubuntu3 => 5.26.0-0ubuntu1] (kubuntu)
[13:57] -queuebot:#ubuntu-release- Unapproved: kiconthemes (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:57] -queuebot:#ubuntu-release- Unapproved: kimageformats (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:57] -queuebot:#ubuntu-release- Unapproved: kio (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:57] -queuebot:#ubuntu-release- Unapproved: kitemviews (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:57] -queuebot:#ubuntu-release- Unapproved: kjs (yakkety-proposed/universe) [5.24.0-0ubuntu4 => 5.26.0-0ubuntu1] (kubuntu)
[13:57] -queuebot:#ubuntu-release- Unapproved: kdoctools (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:57] -queuebot:#ubuntu-release- Unapproved: kguiaddons (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:57] -queuebot:#ubuntu-release- Unapproved: kidletime (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:57] -queuebot:#ubuntu-release- Unapproved: kitemmodels (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:57] -queuebot:#ubuntu-release- Unapproved: kfilemetadata-kf5 (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:57] -queuebot:#ubuntu-release- Unapproved: kinit (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:57] -queuebot:#ubuntu-release- Unapproved: ki18n (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:57] -queuebot:#ubuntu-release- Unapproved: kjobwidgets (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:59] -queuebot:#ubuntu-release- Unapproved: kjsembed (yakkety-proposed/universe) [5.24.0-0ubuntu2 => 5.26.0-0ubuntu1] (kubuntu)
[13:59] -queuebot:#ubuntu-release- Unapproved: knewstuff (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:59] -queuebot:#ubuntu-release- Unapproved: knotifyconfig (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:59] -queuebot:#ubuntu-release- Unapproved: kparts (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:59] -queuebot:#ubuntu-release- Unapproved: kplotting (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:59] -queuebot:#ubuntu-release- Unapproved: kross (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:59] -queuebot:#ubuntu-release- Unapproved: kservice (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:59] -queuebot:#ubuntu-release- Unapproved: ktextwidgets (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:59] -queuebot:#ubuntu-release- Unapproved: kwallet-kf5 (yakkety-proposed/universe) [5.24.0-0ubuntu2 => 5.26.0-0ubuntu1] (kubuntu)
[13:59] -queuebot:#ubuntu-release- Unapproved: kwidgetsaddons (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:59] -queuebot:#ubuntu-release- Unapproved: kmediaplayer (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:59] -queuebot:#ubuntu-release- Unapproved: kpackage (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:59] -queuebot:#ubuntu-release- Unapproved: kpty (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:59] -queuebot:#ubuntu-release- Unapproved: ktexteditor (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:59] -queuebot:#ubuntu-release- Unapproved: kwayland (yakkety-proposed/universe) [4:5.24.0-0ubuntu1 => 4:5.26.0-0ubuntu1] (kubuntu)
[13:59] -queuebot:#ubuntu-release- Unapproved: knotifications (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:59] -queuebot:#ubuntu-release- Unapproved: krunner (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:59] -queuebot:#ubuntu-release- Unapproved: kwindowsystem (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:59] -queuebot:#ubuntu-release- Unapproved: kpeople (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[13:59] -queuebot:#ubuntu-release- Unapproved: kunitconversion (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[14:00] -queuebot:#ubuntu-release- Unapproved: kxmlgui (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[14:00] -queuebot:#ubuntu-release- Unapproved: modemmanager-qt (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[14:00] -queuebot:#ubuntu-release- Unapproved: oxygen-icons5 (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[14:00] -queuebot:#ubuntu-release- Unapproved: solid (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[14:00] -queuebot:#ubuntu-release- Unapproved: threadweaver (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[14:00] -queuebot:#ubuntu-release- Unapproved: kxmlrpcclient (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[14:00] -queuebot:#ubuntu-release- Unapproved: plasma-framework (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[14:00] -queuebot:#ubuntu-release- Unapproved: networkmanager-qt (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[14:00] -queuebot:#ubuntu-release- Unapproved: sonnet (yakkety-proposed/universe) [5.24.0-0ubuntu1 => 5.26.0-0ubuntu1] (kubuntu)
[14:04] <cyphermox> davmor2: so you were saying that sometimes you managed to boot the installer in EFI?
[14:04] <davmor2> cyphermox: on hardware I can on kvm I can't
[14:04] <cyphermox> (or always just a black screen? seems like more likely that it never boots, and always gives you black
[14:04] <cyphermox> I can't here on my Thinkpad.
[14:05] <cyphermox> my screen isn't black, but that's because I have shim debugging enabled
[14:05] <davmor2> I have to select the grubx64.efi file, if it boots from the bootx64.efi it just locks up
[14:14] <shadeslayer> clivejo: ^^ you'll need to talk to the release team to get the frameworks approved
[14:15] <clivejo> I thought the FFe was approved?
[14:17] <cyphermox> davmor2: how do you select the grubx64.efi file??
[14:17] <cyphermox> do you mean you get dropped to the EFI Shell and then go boot?
[14:17] <davmor2> cyphermox: boot from file in efi
[14:17] <cyphermox> is that in a VM or in hardware?
[14:18] <cyphermox> I'm guessing Dell hardware?
[14:19] <davmor2> cyphermox: hardware, it's a temp thing, you just setup a connection call grub.efi and point it at the usb pendrive \EFI\boot\grubx64.efi save it and then boot from that
[14:20] <cyphermox> ok
[14:20] <cyphermox> alright, that confirms to be you can't boot the image at all
[14:21] <davmor2> \o/
[14:22] <cyphermox> ie. if you could by using bootx64.efi in some other weird way, it would mean I have two issues to deal with in shim rather than just one.
[14:24] <davmor2> cyphermox: by the way what changed between Thursday and now to break it all?
[14:27] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Yakkety Beta 2] has been marked as ready
[14:27] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop i386 [Yakkety Beta 2] has been marked as ready
[14:27] <cyphermox> davmor2: did the booting thing really only change on thursday? I expect it's broken since the last shim upload.
[14:28] <cyphermox> so, looks like since about 2016-08-08
[14:29] <davmor2> cyphermox: I had thursdays image installed on kvm and hardware with no monkeying about let me see if it is still on the server and test it
[14:30] <cyphermox> I have Sep 8 too I can give that a shot
[14:31] <cyphermox> otoh, even if that's the case, shim is clearly broken. the bug was clearly identified and is fixed upstream, etc.
[14:36] <acheronuk> clivejo: https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/1625392/comments/5
[14:36] <ubot5`> Ubuntu bug 1625392 in plasma-desktop (Ubuntu) "[FFe] KDE Frameworks 5.26.0 into the Yakkety Archive" [Undecided,Triaged]
[14:38] <acheronuk> so what else does the release team need?
[14:41] -queuebot:#ubuntu-release- Unapproved: python-pip (xenial-proposed/universe) [8.1.1-2ubuntu0.2 => 8.1.1-2ubuntu0.3] (no packageset)
[14:53] -queuebot:#ubuntu-release- Unapproved: flashcache (yakkety-proposed/universe) [3.1.3+git20150701-4 => 3.1.3+git20150701-4ubuntu1] (no packageset)
[14:54] -queuebot:#ubuntu-release- Unapproved: accepted flashcache [source] (yakkety-proposed) [3.1.3+git20150701-4ubuntu1]
[14:54] -queuebot:#ubuntu-release- Unapproved: kboot-installer (yakkety-proposed/main) [0.0.1ubuntu9 => 0.0.1ubuntu10] (core)
[15:16] <gQuigs> hi there, I think this bug https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1575614 is blocking a new network-manager from landing in xenial
[15:16] <ubot5`> Ubuntu bug 1575614 in network-manager (Ubuntu Xenial) "[SRU]Can't select secret key for TLS auth for 802.1X authentication" [Low,Fix committed]
[15:17] -queuebot:#ubuntu-release- Unapproved: gnome-chess (yakkety-proposed/universe) [1:3.21.90-1 => 1:3.22.0-1] (desktop-extra) (sync)
[15:17] -queuebot:#ubuntu-release- Unapproved: gnome-tetravex (yakkety-proposed/universe) [1:3.21.90-1 => 1:3.22.0-1] (desktop-extra) (sync)
[15:18] -queuebot:#ubuntu-release- Unapproved: quadrapassel (yakkety-proposed/universe) [1:3.21.90-1 => 1:3.22.0-1] (desktop-extra) (sync)
[15:20] <gQuigs> should that specific patch just be reverted?
[15:35] -queuebot:#ubuntu-release- Unapproved: libphonenumber (yakkety-proposed/universe) [7.1.0-4ubuntu1 => 7.1.0-5ubuntu1] (no packageset) (sync)
[15:38] -queuebot:#ubuntu-release- Unapproved: mediaplayer-app (yakkety-proposed/universe) [0.20.5+16.04.20160428-0ubuntu1 => 0.20.5+16.10.20160921-0ubuntu1] (no packageset) (sync)
[15:38] -queuebot:#ubuntu-release- Unapproved: ubuntu-keyboard (yakkety-proposed/universe) [0.100+16.10.20160818-0ubuntu1 => 0.100+16.10.20160921-0ubuntu1] (no packageset) (sync)
[15:40] -queuebot:#ubuntu-release- Unapproved: accepted mediaplayer-app [sync] (yakkety-proposed) [0.20.5+16.10.20160921-0ubuntu1]
[15:40] -queuebot:#ubuntu-release- Unapproved: bluez-qt (yakkety-proposed/universe) [5.24.0-0ubuntu2 => 5.26.0-0ubuntu1] (kubuntu)
[15:42] <wxl> we getting rebuilds?
[15:46] <ginggs> Would someone please approve the arch:amd64 and arch:all wine packages in yakkety NEW?
[15:48] <wxl> s/build/spin/
[15:56] <jderose> infinity: i didn't find any existing bug about this, but the Yakkety Server ISO is having troubles, doesn't find the cdrom/iso - https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1626622
[15:56] <ubot5`> Ubuntu bug 1626622 in debian-installer (Ubuntu) "yakkety server: fails to detect and mount CD-ROM" [Undecided,New]
[15:56] <wxl> oh jeez. this is going to be a fun day.
[15:56] <jderose> wxl: isn't every day a fun day? :P
[16:00] <wxl> jderose: oh yeah. it's extra special when you walk into work and the power's been down long enough to make the power supplies flip out >:(
[16:00] <wxl> s/power supply/ups/
[16:00] <wxl> meanwhile we have impending respins (supposedly)
[16:00] <wxl> every freaking package known to man seems to be broken XD
[16:00] <wxl> and now the server! aigh
[16:05] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (xenial-proposed/main) [4.4.0-39.59] (core, kernel)
[16:10] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (xenial-proposed) [4.4.0-39.59]
[16:11] <slangasek> jderose: that image shows as having the 4.8.0-11 kernel in the package pool; a rebuild of that image should fix it; I'm not sure if one is scheduled, checking before I kick one off
[16:12] <jderose> slangasek: cool, thanks! just wanted to make sure ya'll were aware of it at least, if you weren't already :)
[16:13] <nacc> so i sponsored an upload of a fix for python-django (1.8.7-1ubuntu7), i got an e-mail back saying it was 'waiting for approval', but i'm not sure where to look for it, and the link in the e-mail (https://launchpad.net/ubuntu/+source/python-django/1.8.7-1ubuntu7) doesn't seem to exist
[16:13] <slangasek> ok, no rebuild currently running, and no mention by infinity of a respin schedule in scrollback afaics, so I'll go ahead and kick off a rebuild now
[16:13] <slangasek> jderose: fwiw the image you just tested also has not been promoted to 'current'
[16:14] <slangasek> nacc: https://launchpad.net/ubuntu/yakkety/+queue
[16:14] <wxl> slangasek: there was some discussion about a respin yesterday but no particulars mentioned yet
[16:15] <jderose> slangasek: ah, i guess it hasn't. i was misled by the timestamps here - http://cdimages.ubuntu.com/ubuntu-server/daily/
[16:16] <nacc> slangasek: ah ha! i think i must have typo'd before, i did search unapproved before, thanks! so at this point, is it just timing due to the beta freeze? or what's the normal process?
[16:20] <slangasek> nacc: timing for beta freeze, yes; if you think this is a change that should land in beta (because it's somehow beta relevant), or you think it's particularly low risk despite being on the CD, ask the release team to let it through
[16:21] <nacc> slangasek: got it, thanks
[16:21] <nacc> jgrimm: --^
[16:24] <jgrimm> slangasek, nacc:  there is no pressing need for that fix in the beta.  low risk, but i'm not convinced worth your time vs getting beta out the door
[16:25] <slangasek> jgrimm, nacc: the queue has to be flushed at some point, and apw reminded me there's also a proposed-migration block. I've accepted it now
[16:26] -queuebot:#ubuntu-release- Unapproved: accepted python-django [source] (yakkety-proposed) [1.8.7-1ubuntu7]
[16:26] <jgrimm> slangasek, cool cool. thanks
[16:26] <nacc> slangasek: thanks
[16:28] -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)
[16:28] -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)
[16:28] -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)
[16:29] -queuebot:#ubuntu-release- Unapproved: libertine (yakkety-proposed/main) [1.4+16.10.20160908-0ubuntu1 => 1.4.1+16.10.20160914-0ubuntu1] (no packageset) (sync)
[16:33] <flocculant> infinity: just so you are aware, just talked with bluesabre (our tech lead and council chair) we are definitely NOT releasing this beta
[16:34] <flocculant> and he's marked the bug critical
[16:36] <apw> flocculant, could you drop the bug number in here next to that statement for the logs
[16:36] <flocculant> bug 1622303
[16:36] <ubot5`> bug 1622303 in light-locker (Ubuntu) "Fails to unlock/ resumes to black screen" [Critical,Confirmed] https://launchpad.net/bugs/1622303
[16:36] <flocculant> :)
[16:40] <flocculant> apw: one of those bugs I remember the number for currently and assume everyone knows exactly what I'm talking about :p
[16:42] -queuebot:#ubuntu-release- Unapproved: accepted cups [sync] (yakkety-proposed) [2.2.0-2]
[17:02] -queuebot:#ubuntu-release- Unapproved: accepted python-pbr [source] (yakkety-proposed) [1.10.0-0ubuntu1]
[17:06] -queuebot:#ubuntu-release- Builds: Ubuntu Server amd64 [Yakkety Beta 2] has been updated (20160922)
[17:06] -queuebot:#ubuntu-release- Builds: Ubuntu Server arm64 [Yakkety Beta 2] has been updated (20160922)
[17:06] -queuebot:#ubuntu-release- Builds: Ubuntu Server i386 [Yakkety Beta 2] has been updated (20160922)
[17:06] -queuebot:#ubuntu-release- Builds: Ubuntu Server powerpc [Yakkety Beta 2] has been updated (20160922)
[17:06] -queuebot:#ubuntu-release- Builds: Ubuntu Server ppc64el [Yakkety Beta 2] has been updated (20160922)
[17:06] -queuebot:#ubuntu-release- Builds: Ubuntu Server s390x [Yakkety Beta 2] has been updated (20160922)
[17:10] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Yakkety Beta 2] has been marked as ready
[17:10] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop i386 [Yakkety Beta 2] has been marked as ready
[17:10] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop powerpc [Yakkety Beta 2] has been marked as ready
[17:22] <slangasek> jderose: confirmed that the 20160922 ubuntu-server image has the correct kernel udebs in it; it has not been promoted yet to 'current', so smoketests are probably still running
[17:22] <jderose> slangasek: awesome, thank you very much!
[17:23] <jderose> slangasek: out of curiosity, how are these smoketests run? under QEMU, etc?
[17:23] <slangasek> jderose: ah, jibel would have the details
[17:23] <cyphermox> jderose: wanna test a fixed up shim (but unsigned, so it won't work with Secure Boot enabled)?
[17:24] <jderose> jibel: how are the smoketests run? also, is the code for them publicly available?
[17:24] <jderose> cyphermox: heck yeah i want to test it! :D
[17:24] <cyphermox> https://launchpad.net/~canonical-foundations/+archive/ubuntu/shim/+files/shim_0.9+1474479173.6c180c6-0ubuntu1~mtrudel1_amd64.deb
[17:24] <cyphermox> jderose: essentially the tests are run in VMs spun up with a custom test harness
[17:25] <jderose> cyphermox: ah, so a deb... what's the best way to remaster an iso to update just this package?
[17:25] <cyphermox> I would open it in file-roller and just go get the shimx64.efi file in /usr/lib/shim
[17:25] <cyphermox> then replace just that file in the iso image
[17:26] <jderose> cyphermox: okay, thanks. didn't know file-roller could do that. i've been using isomaster to add fallback.efi
[17:26] <cyphermox> jderose: the smoketests code is available, let me get you the link
[17:31] -queuebot:#ubuntu-release- Unapproved: accepted kbd [source] (xenial-proposed) [1.15.5-1ubuntu5]
[17:32] -queuebot:#ubuntu-release- Unapproved: accepted klibc [source] (xenial-proposed) [2.0.4-8ubuntu<IP_ADDRESS>]
[17:34] <cyphermox> jderose:  lp:ubuntu-test-cases/server
[17:35] <jderose> cyphermox: awesome, thanks! and i'll get to testing your shim build soon, have to finish up on other quick thing first
[17:36] -queuebot:#ubuntu-release- Unapproved: accepted update-notifier [source] (yakkety-proposed) [3.173]
[17:38] <slangasek> bdmurray, cyphermox: if we're switching to isc-dhcp in the initramfs, is fixing bug #1624014 in SRU worth doing as opposed to getting the isc-dhcp switch done?
[17:38] <ubot5`> bug 1624014 in klibc (Ubuntu Trusty) "Wrong bit set in klibc PXE dhcp/bootp flags" [High,In progress] https://launchpad.net/bugs/1624014
[17:38] <powersj> slangasek, I may be wrong, but the manifest for the pending iso appears to be the same as yesterdays. The result is the the tests won't run automatically.
[17:39] <lamont> cyphermox: maas ipv6 with yakkety proposed "works" for values of "works" that include "dies because the kernel overlay fs isn't writable either" -- unrelated to our changes.
[17:39] <lamont> http://paste.ubuntu.com/23216762/
[17:39] <cyphermox> slangasek: yes, bootp still goes through ipconfig if you set things up just right
[17:39]  * lamont still needs to find the actual bug #, but +1 from me to the various packages
[17:39] <bdmurray> slangasek: that's a follow up to a previous SRU so I think its worth doing right asap
[17:39] <cyphermox> (well, in truthfulness, dhcp too, again, if you set your command-line parameters just right)
[17:39] <slangasek> powersj: oh, that sounds like a buggy check, then, since either of the .list or the .manifest might change and warrant a re-test
[17:39] <slangasek> bdmurray: ack
[17:40] <slangasek> cyphermox: "just right" - you mean if you don't remove klibc entirely from your system? :)
[17:40] <cyphermox> that, but you also need to set ip= when booting
[17:40] <powersj> slangasek, I'll take that down as something to look into, for now do you want me to kick them off manually?
[17:40] <cyphermox> and use the weird format that klibc expects
[17:40] <slangasek> powersj: sounds good!
[17:45] <xnox> is there going to be a respin with -15 kernel, 476 d-i?
[17:45] <xnox> or shall the current server images with -14 kernel be tested?
[17:45] <xnox> (as in is -15 aimed for beta-2, or as a post-beta-2 update?)
[17:46] <xnox> i guess we need -15, because efi
[17:46] <xnox> sigh
[17:46] <lamont> cyphermox: when you have packges in xenial-proposed, I'll get further down the path I really care about.
[17:48] <jderose> cyphermox: quick question: so i need to copy shim.efi to /EFI/BOOT/BOOTx64.EFI?
[17:48] -queuebot:#ubuntu-release- Unapproved: accepted klibc [source] (trusty-proposed) [2.0.3-0ubuntu<IP_ADDRESS>]
[17:48] <cyphermox> jderose: yes. the file should actually be named shimx64.efi, and you want to copy it to EFI/BOOT/BOOTx64.EFI
[17:49] <bdmurray> slangasek: What will happen if I accept dkms into -proposed when there is one already? From the SRU report - "remove-package -y -m "moved to -updates" -s trusty-proposed -e <IP_ADDRESS>-1.1ubuntu<IP_ADDRESS> dkms"
[17:49] <jderose> cyphermox: gotcha, thanks. and in a production ISO, it would actually be shim.efi.signed that gets copied to this location, right?
[17:49] <cyphermox> yep
[17:50] <cyphermox> this time I just don't have it signed yet -- we're doing some testing before I ship it to MS so that we don't get something signed that we can't use because it's broken
[17:50] <jderose> cyphermox: right, understood
[17:52] <davmor2> cyphermox: how we looking?
[18:02] <jderose> cyphermox: hmm, so first test under qemu + ovfm: no hardware exception, but it's still going directly to Shell>, isn't booting the installer. have you been able to test this yet? if so, what's your experience been?
[18:02] <cyphermox> do you have the fallback in there as well?
[18:03] <cyphermox> you definitely don't want it to be included
[18:03] <jderose> cyphermox: no, i don't
[18:03] <cyphermox> I haven't exactly been testing that
[18:04] <jderose> cyphermox: i'll try a few qemu command permutations, see if i can coax it into worknig
[18:08] <davmor2> jderose: what version of Ubuntu are you on in Yakkety there is an updated OVFM that uses a separate vars file so you need to specify them both or it does crazy things :)
[18:09] <jderose> davmor2: right now i'm still using xenial for the host (which also requires a separate vars files or it does crazy things). i need to test under a yakkety host too, just in case that magically works :)
[18:11] <davmor2> jderose: no just making sure you were aware of the change, in xenial I was still using the old bios.bin and it worked fine but not in yakkety :)  So just double checking that to rule it out
[18:12] <cyphermox> that wouldn't break things this way
[18:13] <jderose> davmor2: yup, as it turns out i'm highly aware of that change because i had to work through it during xenial dev :D http://blog.system76.com/post/139138591598/howto-qemu-w-ubuntu-xenial-host-uefi-guest
[18:15] <davmor2> jderose: I wish I'd of seen that before I found it digging around in some fedora post in the end
[18:16] <davmor2> jderose: nice write up by the way :)
[18:16] <jderose> davmor2: yeah, still pretty difficult to find up-to-date and correct examples for this stuff. thanks!
[18:17] <cyphermox> jderose: you get dropped to the shell because the remastering is breaking the boot
[18:18] <davmor2> jderose: what happen if you use isomaster
[18:18] <jderose> cyphermox: ah, okay. btw, this first test i test using isomaster as i knew how to use it already, so that could be the problem. but do you expect it to break in the same way using file-roller?
[18:19] <cyphermox> file-roller is just to extract the shim from its deb package
[18:19] <jderose> cyphermox: ah, okay. is there something more correct than isomaster that i should try?
[18:21] <cyphermox> I'm not sure, I rarely have to do this
[18:21] <jderose> cyphermox: i'm in the same boat, except i've never had to do this :P
[18:22] <cyphermox> I have an old script that should more or less do the right thing, if I can find it again
[18:22] <jderose> infinity: O great master of the ISO... any recommendations on this? :)
[18:26] <cyphermox> jderose: there: http://paste.ubuntu.com/23216958/
[18:26] <cyphermox> to do this I copy everything off the CD image into a directory tree I can modify and go nuts
[18:26] <cyphermox> then run make_ubuntu_Iso.sh $dir  and it should make a pretty CD
[18:27] <jderose> cyphermox: awesome, thanks... trying it now
[18:27] <cyphermox> unsure if this will boot any better though, I recall there was something slightly wrong with it, but it mostly worked.
[18:27] <cyphermox> oh, you'll still be missing files
[18:29] <cyphermox> ah
[18:29] <cyphermox> you need xorriso and isolinux
[18:30] <cyphermox> then replace isohdpfx.bin with the full path from isolinux: /usr/lib/ISOLINUX/isohdpfx.bin
[18:30] <davmor2> trying here too
[18:32] <cyphermox> that big command in the script is basically taken from debian-cd after some copy-pasting the various bits and bobs
[18:34] <jderose> cyphermox: can you give me a quick invocation example for this script?
[18:36] <cyphermox> http://paste.ubuntu.com/23216990/
[18:37] <jderose> cyphermox: thanks!
[18:38] <cyphermox> heh, doesn't seem to work, but I think I know why, it's more embedded crap
[18:38] <jderose> cyphermox: so --squashfs isn't needed, it take it?
[18:38] <jderose> hehe
[18:38] <cyphermox> no
[18:38] <cyphermox> squashfs is for when I'm putting new stuff in the squashfs :)
[18:47] <cyphermox> ok, I think it's that pesky efi.img file under boot/grub :/
[18:48] <cyphermox> I was kind of expecting that was for the weird Mac EFI implementation though
[18:48] <jderose> cyphermox: is it using hard offsets to positions within the ISO or something like that?
[18:49] <cyphermox> (but since the CD now doesn't just kick me back to the boot selection but instead is stuck again at a "blank" screen with the shim version numbers, I think I'm hitting the old shim still)
[18:49] <jderose> all this is making me realize how strikingly little i know about how the ISO is structured, built, and works :)
[18:49] <cyphermox> jderose: efi.img is being written somwhere else to the disk in a small EFI partition just for that
[18:52] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (vivid-proposed/main) [3.19.0-70.78] (core, kernel)
[18:53] <jderose> cyphermox: i see boot/grub/efi.img, but are you saying it exists elsewhere also, mabye on a partition that file-roller doesn't understand how to extract?
[18:54] <cyphermox> no, that's not what I'm saying
[18:54] <cyphermox> that file is passed as a parameter to xorriso, and gets written to the final image as a separate partition
[18:55] <cyphermox> that definitely fixes it... the more you know...
[18:55] <cyphermox> fwiw to fix that I went in boot/grub, and used mcopy:
[18:56] <cyphermox> mcopy -i efi.img ../../EFI/BOOT/BOOTx64.EFI ::EFI/BOOT/BOOTx64.EFI
[18:56] <cyphermox> effectively putting the new shim that I had already copied to EFI/BOOT/BOOTx64.EFI into that efi.img file to replace the existing BOOTx64.EFI there.
[18:56] <jderose> okay, gotcha
[18:57] <cyphermox> I think when you run isomaster, it breaks things because it doesn't write that partition in the resulting image
[18:57] <slangasek> bdmurray: since old and new dkms binary package names are the same, accepting the new one should lead to launchpad superseding the old ones with no problems.  kernels are different and special
[18:58] <cyphermox> jderose: see, I think that's the part that "wasn't working" last I used this script to do weird stuff, and now it's figured out
[18:58] <cyphermox> that image now boots correctly in EFI and BIOS.
[19:02] <jderose> cyphermox: so when prompted by mcopy... do i want to o)verwrite, O)verright-all, or something else?
[19:02] <cyphermox> overwrite or overwrite-all should do the same, you're only copying one file :)
[19:04] <jderose> cyphermox: k, thanks. and the script here http://paste.ubuntu.com/23216958/ is still what i should use, or did you modify it since?
[19:10] <cyphermox> the only modification was the new path to isohdpfx.bin
[19:12] <jderose> cyphermox: er, where is this isohdpfx.bin file coming from, or what should the new path be?
[19:15] <jderose> er, never mind, think i figured it out
[19:20] <jderose> cyphermox: sweet, it's working for me under qemu + ovfm now! I'll test on physical uefi hardware shortly
[19:25] <cyphermox> jderose: great
[19:28] <jderose> cyphermox: so assuming the shim fix seems solid enough to justify getting it signed by MS, can that happen in time for 16.10? for me, at least i have a way to work around this issue for imaging mastering, so i'm all good. but i'm still curious
[19:30] <cyphermox> I pushed it to a PPA already, I'll file the paperwork so that it gets sent for signing
[20:07] -queuebot:#ubuntu-release- Unapproved: accepted cups-filters [source] (yakkety-proposed) [1.11.4-0ubuntu1]
[20:17] <flexiondotorg> It is looking like a Friday release for 16.10 beta now?
[20:18] <jderose> cyphermox: okay, finished sanity checking my customized iso on a boat load of UEFI hardware... all launched the installer pre-boot menu fine. two systems had issues booting into the full installer, but i think that's due to unrelated issues i'll have to track down later.
[20:19] <wxl> flexiondotorg: if we're not, someone's going to get choked.
[20:19] <jderose> cyphermox: but to the extent my customized iso is representative of a properly mastered iso with a fixed shim packaged, your fix seems solid
[20:20] <cyphermox> ok
[20:22] <flexiondotorg> wxl, OK, I'll make coffee and get some match sticks ;-)
[21:05] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Yakkety Beta 2] has been updated (20160922)
[21:05] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop i386 [Yakkety Beta 2] has been updated (20160922)
[21:13] -queuebot:#ubuntu-release- Unapproved: hplip (yakkety-proposed/main) [3.16.7+repack0-1 => 3.16.7+repack0-1ubuntu1] (desktop-core, ubuntu-server)
[21:14] <flexiondotorg> cyphermox, What was fixed in those new Ubuntu iso? Do flavours need to consider respinning?
[21:14] <cyphermox> I don't know what the difference it
[21:14] <cyphermox> *is
[21:14] <cyphermox> slangasek: ^
[21:15] <slangasek> cyphermox: that one is the respin against the current package pool
[21:15] <cyphermox> ok
[21:16] <flexiondotorg> slangasek, So Unity 8 stuff?
[21:16] <slangasek> that was the only reason *I* had for triggering that respin, and that was probably image-specific
[21:16] <slangasek> no
[21:16] <slangasek> time-of-image-build and ftp-mirror-skew stuff
[21:17] <flexiondotorg> slangasek, Thanks.
[21:31] <sakrecoer> do i understand right? no respin for flavours?
[21:34] <wxl> this respin thing is going to make me crazy
[21:35] <flexiondotorg> wxl I've missed some of the goings on today.
[21:35] <flexiondotorg> Can you catch myself and sakrecoer up on the status.
[21:35] <wxl> flexiondotorg: i've been here the whole time and still can't figure it out XD
[21:35] <flexiondotorg> llol
[21:35] <wxl> i've heard we should, we will, we won't, we might
[21:36] <wxl> i don't even know.
[21:36] <sakrecoer> me too, and i don't really get it either lol
[21:36] <flexiondotorg> So, Ubuntu MATE is good to go. For the record.
[21:36] <sakrecoer> we are too, but... not if there is a respin
[21:36] <sakrecoer> we=ubuntu studio sorry
[21:36] <flexiondotorg> Right, so you're asking because you can't afford to do the testing again, right?
[21:48] <wxl> we got a couple more tests to do
[21:49] <wxl> hey sakrecoer you might want to mark yourself as ready if you're good.
[21:57] <sakrecoer> ok, cheers wxl ! :)
[21:58] <wxl> ta :)
[22:02] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD amd64 [Yakkety Beta 2] has been marked as ready
[22:02] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD i386 [Yakkety Beta 2] has been marked as ready
[22:03] <sakrecoer> i'm off for now, thanks everyone! touching wood (my head) for everything to work out all good for everyone!
[22:03] <sakrecoer> o/
[22:17] -queuebot:#ubuntu-release- Unapproved: quadrapassel (yakkety-proposed/universe) [1:3.21.90-1 => 1:3.22.0-1] (desktop-extra) (sync)
[22:17] -queuebot:#ubuntu-release- Unapproved: tali (yakkety-proposed/universe) [1:3.21.90-1 => 1:3.22.0-1] (desktop-extra) (sync)
[22:24] -queuebot:#ubuntu-release- Builds: Ubuntu GNOME Desktop amd64 [Yakkety Beta 2] has been marked as ready
[22:24] -queuebot:#ubuntu-release- Builds: Ubuntu GNOME Desktop i386 [Yakkety Beta 2] has been marked as ready
[22:46] -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)
[22:46] -queuebot:#ubuntu-release- Unapproved: libphonenumber (yakkety-proposed/universe) [7.1.0-4ubuntu1 => 7.1.0-5ubuntu1] (no packageset) (sync)
[22:46] -queuebot:#ubuntu-release- Unapproved: libertine (yakkety-proposed/main) [1.4+16.10.20160908-0ubuntu1 => 1.4.1+16.10.20160914-0ubuntu1] (no packageset) (sync)
[22:46] -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)
[22:46] -queuebot:#ubuntu-release- Unapproved: ubuntu-keyboard (yakkety-proposed/universe) [0.100+16.10.20160818-0ubuntu1 => 0.100+16.10.20160921-0ubuntu1] (no packageset) (sync)
[22:46] -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)
[22:51] <mwhudson> can someone pretty please release docker from the xenial unapproved queue?
[22:57] <slangasek> powersj: wrt your follow-up on bug #1626622, can you also attach dmesg?
[22:57] <ubot5`> bug 1626622 in debian-installer (Ubuntu) "yakkety server: fails to detect and mount CD-ROM" [Critical,New] https://launchpad.net/bugs/1626622
[22:57] <slangasek> powersj: infinity and I are wondering if the remaining issue is related to the nls module issue that breaks fat partition mounting
[22:57] <slangasek> or if there's something else needing further investigation
[22:58] <slangasek> mwhudson: looking
[22:58] <powersj> slangasek, yeah I'll have to reproduce locally as those logs are from the automated run
[22:58] <mwhudson> slangasek: tia
[23:01] -queuebot:#ubuntu-release- Unapproved: accepted docker.io [source] (xenial-proposed) [1.12.1-0ubuntu12~16.04]
[23:05] <mwhudson> aaaaaaaaaaaaaaaaargh
[23:05] <mwhudson> slangasek: can you delete that again? :)
[23:05] <slangasek> well, yes, I can
[23:07] <slangasek> mwhudson: done (and make up your mind ;)
[23:09] <mwhudson> slangasek: ok, uploaded a new version, hopefully this one doesn't head straight into depwait
[23:19] -queuebot:#ubuntu-release- Unapproved: accepted openbabel [sync] (yakkety-proposed) [2.3.2+dfsg-2.4]
[23:26] <mwhudson> ok, *now* i've uploaded a new version
[23:26] -queuebot:#ubuntu-release- Unapproved: docker.io (xenial-proposed/universe) [1.12.1-0ubuntu7~16.04 => 1.12.1-0ubuntu12~16.04.1] (no packageset)
[23:36] <flexiondotorg> I've just upload ubuntu-mate-welcome 16.10.8. If someone could approve it please.
[23:36] -queuebot:#ubuntu-release- Unapproved: ubuntu-mate-welcome (yakkety-proposed/universe) [16.10.7 => 16.10.8] (ubuntu-mate)
[23:37] <flexiondotorg> The Ubuntu MATE have got a bit behind, this is a large collection of fixes and tweaks that has resulted from testing over recent days.
[23:37] <flexiondotorg> infinity, ^
[23:40] -queuebot:#ubuntu-release- Unapproved: nagios3 (yakkety-proposed/main) [3.5.1.dfsg-2.1ubuntu1 => 3.5.1.dfsg-2.1ubuntu2] (ubuntu-server)
[23:43] <powersj> https://paste.ubuntu.com/23218086/
[23:43] <powersj> slangasek, ^
[23:46] <nacc> doko: --^ the above nagios3 should fix the ftfbs
[23:47] <nacc> *ftbfs