[07:59] <tsimonq2> infinity: could you (or someone with the permissions) please approve the libfm SRU ( bug 1562764 ) and once that lands in xenial-updates, do a respin of the Lubuntu 16.04.1 image?
[09:55] <davmor2> Hey guys can someone add upgrades to the iso tracker please, making a start on netboot
[10:40] <sakrecoer> Hi, where can i find the schedule for dot releases? i've found this: https://wiki.ubuntu.com/XenialXerus/ReleaseSchedule however, it doesn't announce for when 16.04.2 release is scheduled..
[10:50] <apw> sakrecoer, likely an exact date has not yet been determined for 16.04.2, but it will be approximatly 6 moths from now
[10:53] <sakrecoer> apw: thank you! :) so, a good way to stay informed is to check /XenialXerus/ReleaseSchedule regularily?
[10:57] <apw> sakrecoer, i would expect to see it being put in provisionally quite soon, once the current one is out of the way
[11:02] <davmor2> Guys I'm having major issues with netboot detecting usb and networking in kvm I'm going to try on hardware but I assume it will be a real issue so just a heads up
[11:22] <rbasak> sakrecoer: you can subscribe to release schedule wiki page changes if you want.
[11:25] <flocculant> infinity: do you know the download links on 16.04.1 are wrong? and no upgrade tests for it either
[11:28] <davmor2> infinity: netboot iso's for xenial are fubar, I get error while running 'modprobe -v usb-storage'  and then get No network interfaces on kvm and hardware
[11:28] <sakrecoer> thank you rbasak! :)
[11:29] <davmor2> flocculant: hey dude how's life
[11:29] <flocculant> just emptied the kitchen of 3 buzzing hornets
[11:29] <flocculant> everything is just great now :D
[11:38] <davmor2> cyphermox: one for you to look at too dude :) I'm using mini.iso from http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/installer-amd64/current/images/netboot/mini.iso
[12:40] <coreycb> hello, can an archive admin please promote python-aodhclient and python-monascaclient to main? this will help get some of our openstack packages out of dependency waits.
[12:41] <coreycb> here are the accompanying MIR bugs: bug 1552415 and bug 1590836
[12:43] <coreycb> we also have packages blocked by MIR bug 1552415 if we could get a review of that.  thanks!
[12:44] <coreycb> bah, first 2 bugs above should have been 1590836 and bug 1586069
[14:08] <davmor2> infinity, cyphermox: just tried server cd amd64 on kvm and got the same issue so there is a definite issue with the debian installer
[14:26] <davmor2> infinity, cyphermox: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1604441
[14:55] <infinity> davmor2: ORLY?
[14:57] <jderose> infinity: so no new RC ISOs yet, sans proposed?
[14:57] <infinity> jderose: Waiting on verification of a dhclient bug, so I can squeeze that in the respin.
[14:58] <infinity> jderose: Also looking at davmor2's claim that d-i is FUBAR.
[14:58] <infinity> jderose: And was sick and in bed all morning. :/
[14:58] <jderose> infinity: gotcha, thanks. i'm just anxious to get testing :)
[14:58] <jderose> ah bummer, sorry to hear your sick. bad timing for that
[14:58] <infinity> jderose: Like I said in my mail, don't let any of that stop you from testing!
[14:59] <infinity> jderose: You find bugs in the current daily, we fix them for the respin (maybe).  If you wait to test, nothing wil get fixed before release.
[14:59] <jderose> already tested the crap out of yesterdays, now just need to do the same minus proposed
[14:59] <infinity> Heh.
[14:59] <infinity> jderose: Kay.  Verdict?
[15:00] <jderose> infinity: this was the only thing I found - https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1604173
[15:01] <infinity> jderose: Kay, and that's upgrade-only, so not ISO critical.  But should definitely be looked at.
[15:01] <jderose> yeah true, can be fixed post ISO. plus, it's just slightly annoying, not a deal breaker by any means
[15:03] <jderose> infinity: so there are d-i problems that were found? i mean, i'm assuming FOOBAR might not be code for "works perfectly in every way" :P
[15:04] <infinity> jderose: Yeah, I'm grabbing a mini.iso and server.iso to confirm right now.  Maybe I'm crazy, maybe davmor2 is.
[15:04] <infinity> Hotel wifi isn't being my bestest friend today, though.
[15:05] <jderose> infinity: gotcha. for what it's worth, i didn't find any problems with the server ISO (although we only test amd64, don't test i386)
[15:05] <infinity> He claimed amd64 was bust, so...
[15:05] <infinity> I'm considering blaming him instead. :P
[15:07] <jderose> infinity: guess it could be something unique to the mini ISO. that's also something we don't test
[15:08] <infinity> He claimed mini and server were both broken.
[15:08] <infinity> davmor2: Can you confirm exact versions you tested, and what qemu cmdline you use to reproduce your woes?
[15:08] <infinity> davmor2: We seem to have conflicting reports of awesomeness. ;)
[15:11] <infinity> davmor2: FWIW, a simple "kvm -m 2G -hda disk.img.server -cdrom mini.iso" worked fine here and got me a network.
[15:11] <davmor2> infinity: http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/installer-amd64/current/images/netboot/mini.iso and http://cdimages.ubuntu.com/ubuntu-server/xenial/daily/current/
[15:12] <infinity> davmor2: "current" links don't fill me with confidence of versions being correct. :)
[15:12] <davmor2> infinity: command I use is kvm -m 2048 -vga qxl -cpu host --soundhw ac97 -cdrom Downloads/xenial-server-amd64.iso -hda kvm-images/ubuntu20hda.qcow2 -pflash kvm-images/bios.fd and replace the xenial-server-amd64 with mini.iso
[15:13] <davmor2> infinity: also I tested netboot on hardware
[15:13] <davmor2> same issue
[15:13]  * infinity tries your CLI.
[15:13] <davmor2> infinity: you'll need uefi in play
[15:13] <davmor2> maybe that is the cause
[15:14] <infinity> Oh, "bios.fd" is actually not a BIOS? :P
[15:14] <davmor2> I aslo have secureboot enabled on both kvm and hardware
[15:14] <jderose> davmor2: that could be. BIOS mode installs were fine for me, but i didn't test UEFI server installs
[15:15] <infinity> Might be easier for me to just reboot and play, then.  I never got around to setting up kvm with SB with Microsoft keys.
[15:15] <davmor2> infinity: bios.fd is the uefi file I pull from downloading uefi package that I can't remember the name of
[15:16] <infinity> /usr/share/qemu/OVMF.fd ?
[15:16] <davmor2> infinity: that's the one
[15:16] <infinity> Do you have the MS keys in your keyring?
[15:17] <davmor2> no it's /usr/share/ovmf/OVMF.FD iirc
[15:17] <jderose> infinity: yeah, i use the files from the ovmf package. but there is some trickiness using xenial or newer as the host, at least in my experience - http://blog.system76.com/post/139138591598/howto-qemu-w-ubuntu-xenial-host-uefi-guest
[15:17] <infinity> Same file. :)
[15:17] <davmor2> infinity: I do and I set it against shim
[15:17] <jderose> davmor2: so you're only hitting an issue with secure boot is enabled?
[15:18] <davmor2> jderose: let me turn it off and see
[15:18] <jderose> (i've still never gotten around to playing with secure boot with qemu, probably should at some point)
[15:20] <infinity> I'll have to bounce and look once this ISO is down.  A dmesg from the failing install would be good.
[15:20] <infinity> I'm guessing it might be refusing to validate module sigs or something, but I can't quite fathom WHY that would be.
[15:21] <davmor2> so with uefi only it gets past the issue so it is just secureboot
[15:21] <davmor2> let me double check it on hardware though
[15:22] <infinity> davmor2: Definitely want dmesg from the failed systems, then.
[15:23] <infinity> It's almost certainly our module sig validation patches in play, but they should be happy.
[15:23] <infinity> Hrm.  Unless the build system accidentally strips the sigs off the modules or something awful.
[15:23] <infinity> Will poke in 20m. :P
[15:23]  * infinity kicks the WiFi.
[15:24] <apw> davmor2, yeah can we get some dmesg output or something in the failing mode ...
[15:26] <davmor2> sorry was confirming with no secureboot on hw I get screwy gfx but it gets to networking now
[15:32] <apw> infinity, or whats in the udebs arn't signed
[15:32] <davmor2> apw, infinity: not the best d-i installer in the universe if I disable secureboot http://people.canonical.com/~davmor2/desktop-screenshots/screwy-gfx.jpg
[15:32] <apw> i assume the netboot uses udebs
[15:33] <infinity> apw: Indeed.
[15:34] <jderose> davmor2: i see the problem, the screen is too glossy! :P
[15:34] <davmor2> apw, infinity: any clues as to how to get dmesg of a system that has no usb or networking?
[15:35] <apw> infinity, ok picked random udeb ... they seem signed ... ~Module signature appended~
[15:35] <infinity> Paraphrase the bits that talk about loading the modules?
[15:35] <infinity> davmor2: How do I enable SB and inject MS's key in OVMF?
[15:37] <davmor2> infinity: see pm
[15:39] <xnox> davmor2, one should be able to run qemu kvm with uefi in serial mode, and then esentially $ cat /var/log/syslog should generate all the output in your terminal on the host....
[15:39] <xnox> pipe to pastebinit or some such
[16:06] <davmor2> apw, infinity: http://paste.ubuntu.com/20051421/ http://paste.ubuntu.com/20051642/  I'll try and dig out a /var/log/dmesg too but I couldn't find one so that is just the command dmesg and syslog
[16:06] <davmor2> xnox: mount the hd and wrote it there in the end ;)
[16:08] <infinity> [    0.000000] Secure boot enabled
[16:08] <infinity> Jul 19 15:44:31 hw-detect: modprobe: ERROR: could not insert 'usb_storage': Required key not available
[16:08] <infinity> Huh.
[16:11] <apw> infinity, do you have shell, if so you could check what keys are in the keyring
[16:11] <infinity> apw: I will shortly.  That was from davmor2's paste up there.  I'll get to where he is in a few minutes.
[16:12] <davmor2> apw: I have shell open now if you tell me what to do I can do it
[16:13] <rtg> apw, didn't we have trouble with time of day impacting these keys once upon a time ?
[16:15] <apw> rtg, we had cases where if the first byte was 0 that they didn't work, so randomly, but that one looks long enough
[16:16] <rtg> apw, I was just thinking of the absolute platform time predated the MS cert, then it might cause issues
[16:16] <rtg> s/of/if/
[16:17] <rtg> hmm, RTC time: 15:44:21, date: 07/19/16
[16:17]  * xnox thought we explicitely fixed secureboot stuff to ignore time
[16:17] <xnox> are udebs signed, or just debs?
[16:17] <infinity> Yeah, my VM here has a sane time, that's not the issue.
[16:17] <rtg> xnox, keyrings are somewhat independent of secureboot
[16:18] <rtg> xnox, just .ko's
[16:18] <apw> xnox, i opened up block-modules and one i picked in there had some kind of signature appended
[16:18] <davmor2> I'll update the bug to say it is just secure boot
[16:21] <davmor2> apw, infinity: this is the bug I'm using feel free to swap it all about https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1604441 as it most likely isn't d-i now
[16:30] <infinity> Found the bug.
[16:30] <infinity> Spinning up test fix.
[16:31] <davmor2> infinity: yay \o/
[16:31] <rtg> in d-i ?
[16:31] <infinity> Yeah.
[16:31] <infinity> rtg: We miiiiight be stripping modules.
[16:31] <infinity> DERP.
[16:31] <rtg> doh!
[16:32] <davmor2> To quote Muttley Shuggin' fashin' shuggin' fashin' dick dastardly
[16:33] <infinity> Lobbing a test build at my PPA.
[16:34] <slangasek> tsimonq2: hi, did you happen to see the email I sent asking about lubuntu image sizes?  16.04.1 around the corner and everything's still reporting as 'oversized'
[16:34] <davmor2> infinity: but yay for iso testing
[16:38] <xnox> davmor2, well, we kept using old kernel with all d-i builds, so this is first d-i build with new kernel...
[17:03] <infinity> davmor2: http://ppa.launchpad.net/adconrad/ppa/ubuntu/dists/xenial/main/installer-amd64/20101020ubuntu451.4~ppa1/images/netboot/mini.iso
[17:03] <infinity> davmor2: Testing locally too.
[17:06] <davmor2> infinity: downloading
[17:08] <infinity> davmor2: Seems to get past that hump for me at least.
[17:08]  * infinity uploads.
[17:11] <infinity> pitti: ^-- Review, please.  The i386 image size bump is to match yakkety (for my peace of mind, and also because the slightly fatter modules didn't fit anymore :P)
[17:11] <wxl> infinity: just curious on the eta of that respin for trusty.
[17:12] <infinity> wxl: trusty?  It's still dailies...
[17:12] <infinity> wxl: Did you mean xenial?
[17:12] <wxl> infinity: derp. yes.
[17:12] <infinity> wxl: Once this d-i change lands, I'll rebuild the world.
[17:12] <infinity> wxl: So, likely an hour or two?
[17:12] <infinity> slangasek: Or if you'd like to take my d-i upload?
[17:13]  * infinity will self-review in 5m.
[17:13] <wxl> k cool. thx for your hard work infinity :)
[17:15] <pitti> infinity: done
[17:16] <xnox> infinity, is 5m as per bdmurray guidelines "long enough time pass i cannot even remember i did this"
[17:16] <infinity> xnox: Heh.
[17:16]  * xnox wants whatever infinity is drinking
[17:16] <infinity> xnox: Nothing, sadly.  Too sick to.
[17:17] <xnox> =(
[17:17] <xnox> oh.
[17:17] <rtg> infinity, 'Strop stripping modules' ?
[17:17] <infinity> rtg: Oh, close enough.
[17:18] <infinity> The best bit is that I've put that in three changelogs and pitti reviewed it, and no one noticed.
[17:18] <infinity> rtg: So, we'll just hone our stripping a bit.
[17:18] <infinity> With a strop.
[17:18] <pitti> Strop stipping?
[17:18] <rtg> razor sharp :)
[17:19] <xnox> Enterprise class engineering =)
[17:19] <infinity> The engineering bit was right.
[17:19] <infinity> It was the technical documentation that wasn't.
[17:19] <infinity> I'm okay with that.
[17:21] <infinity> Tempted to upload trusty with the same typo, just for consistency.
[17:21] <infinity> And lolz.
[17:22] <jderose> infinity: hehe :P
[17:23] <infinity> davmor2: I assume you got a successful install out of that?  I'm still mid-install on hotel WiFi, but at least all the module loading bits were good.
[17:59] <davmor2> infinity: sorry food got called, installing now
[17:59] <davmor2> install has an ip address and is downloading files \o/
[18:00] <davmor2> infinity: ^
[18:01] <davmor2> infinity: I'll continue with this install and confirm no further issues but I'm passed the point of failure previously
[18:36] <davmor2> infinity: I now have a booting desktop so I would say that is fixed I'll comment on the bug for pitti it'll be a pain in the arse to test the sru way so we'll stick with what we've done :)
[18:36] <pitti> davmor2: "test the sru way" hm? context?
[18:37] <davmor2> pitti: it's the debian installer how do you install it from proposed for a cd image?
[18:37] <infinity> davmor2: I'm testing "the SRU way" right now (as in, downloading the proper mini.iso)
[18:37] <infinity> But it should be identical to the PPA one I pointed you at.
[18:37] <pitti> davmor2: hm, I only know that for netboot
[18:38] <pitti> oh, we build mini.iso too, not just netboot images?
[18:38] <infinity> We do.  Which is much simpler to test for this case.
[18:39] <infinity> And yes, the mini.iso in proposed is also correct, as expected.
[18:39] <infinity> So, I'd call that v-done.
[18:39] <davmor2> pitti: I've tested infinity's build which works fine and I have a booting desktop
[18:40] <infinity> pitti: Cool with sru-releasing that now?
[18:40] <pitti> infinity: sure, it can't possibly break running systems
[18:41] <infinity> It could, if I try really hard.
[18:41] <infinity> Maybe with an embedded worm that turns every installer into an attacker.
[18:41] <infinity> Which, ironically, would require me fixing this bug first, since we couldn't load network drivers. :P
[18:44]  * infinity waits patiently for pitti's releasy magic.
[18:45] <davmor2> infinity: so if I grab the proposed server image that should have the fix right?
[18:50] <davmor2> apparently not :(
[18:52] <davmor2> infinity: seriously strop stripping modules ;)
[18:53] <infinity> :P
[18:53] <jderose> hehe
[18:53] <infinity> There is no new server image yet, that'll be built once the new d-i is in updates.
[18:53] <infinity> pitti: Did we miscommunicate?  Am I releasing that, or are you?  (or did you and LP is lagging?)
[18:56] <infinity> pitti: Right, assuming miscommunication and releasing myself. :)
[19:15] <rharper> hi, could someone let the curtin bzr399 package into proposed to replace the older 389?
[19:22] <infinity> rharper: The one with only 1/4 bugs tested and verified?
[19:22] <slangasek> infinity: he's asking for an overwrite of -proposed, not a release to -updates
[19:23] <infinity> Oh, trusty.
[19:23] <infinity> Nevermind.
[19:23] <infinity> I was looking at 399 already being in xenial.
[19:24] <rharper> slangasek: thanks for translating what I had in my mind  to the correct phrasing
[19:37] <infinity> pitti: Can you roll up some trusty langpacks in the next week?
[20:09] <jderose> infinity: are new respins in progress yet, or are you still waiting other packages?
[20:09] <infinity> jderose: Almost ready to start.  Another 10m or so before I start pushing buttons.
[20:09] <infinity> (Waiting on the publisher to finish)
[20:09] <jderose> infinity: awesome
[20:20] <xnox> so hot in the uk at the moment
[20:38] <infinity> jderose: Respinaroo is respinnering.
[20:38] <infinity> jderose: Do me a favour and poke a bunch of flavour leads to get their poop in a group?  After battling a clod all day and bugs all evening, I'm done. :P
[20:39] <jderose> infinity: respinerrific!
[20:39] <infinity> s/clod/cold/
[20:39] <jderose> infinity: hehe, well i could give it a try i guess, but that feels out of my jurisdiction :P
[20:39] <infinity> Jurisdictions are fuzzy.
[20:40] <jderose> true, true
[20:55] <bdmurray> is there a reason the xorg lts-xenial stack is still in proposed?
[20:57] <slangasek> infinity: ^^ ?
[20:58] <infinity> bdmurray: Because I'm waiting for Timo and friends to tell me it's awesome and tested.
[20:58] <bdmurray> infinity: Is there a timeline for that?
[20:58] <slangasek> ah, and also this is lts-xenial for trusty, so zero impact on 16.04.1
[20:59] <infinity> bdmurray: This week or early next, ideally, so dailies can stop using proposed.
[20:59] <infinity> bdmurray: I'll poke them some tomorrow.
[20:59] <infinity> slangasek: Right.
[23:40] <tsimonq2> slangasek: it is oversized (we still aim for CD size) and it's an issue that I don't think we will be able to address in time for 16.04.1
[23:44]  * tsimonq2 tests to see if the bug fix got in the daily image
[23:44] <tsimonq2> s/daily/16.04.1/
[23:54] <tsimonq2> infinity: ping, it's urgent, Lubuntu has no Alternate images: http://cdimage.ubuntu.com/lubuntu/daily/20160718/ http://cdimage.ubuntu.com/lubuntu/daily/20160719/
[23:54] <tsimonq2> infinity: those sirectories are empty
[23:54] <tsimonq2> *directories
[23:54] <tsimonq2> infinity: what's going on here?
[23:55] <tsimonq2> whoever else is on the release team as well, am I not seeing this correctly?
[23:55] <wxl> tsimonq2: did you check if other flavors/images are affected?
[23:56] <tsimonq2> wxl: let me see
[23:56] <wxl> i do know there was some sort of d-i image that was getting fixed
[23:56] <wxl> might want to check server specifically
[23:56] <jderose> infinity: furious round of testing with the latest RC ISOs at System76... no issues found. so shiny, so chrome.
[23:56] <tsimonq2> alright
[23:57] <tsimonq2> wxl, infinity: Ubuntu Server is NOT affected, this is only a Lubuntu Alternate image issue
[23:57] <wxl> tsimonq2: do you see any problem with any other image at all?
[23:57] <tsimonq2> checking