[00:00] <cyphermox> ack
[00:00] <infinity> cyphermox: Unless you really feel like documenting every bug fixed since wily.
[00:00] <cyphermox> not especially
[00:00] <infinity> ;)
[00:00] <cyphermox> I want to be able to use my computer to test tomorrow
[00:00] <flexiondotorg> cyphermox, jderose Doing an OEM install. Ubiquity doesn't prompt to join WiFi networks. So proceeds without a connection.
[00:00] <cyphermox> and you might want LP to not decide I'm evil and never respond to me ever again
[00:00] <jderose> flexiondotorg: hmm, that was working just a week or so ago
[00:00] <cyphermox> flexiondotorg: you should see nm-applet
[00:01]  * infinity crashes.
[00:01] <flexiondotorg> The applet is there.
[00:01] <flexiondotorg> And works.
[00:01] <flexiondotorg> However, Ubiquity itself no longer prompts for join a wireless network.
[00:02] <flexiondotorg> When wifi is available.
[00:04] <cyphermox> d'oh
[00:05] <cyphermox> I should unxz that image before I write it shouldn't I? :)
[00:05] <cyphermox> flexiondotorg: I don't know that oem-config ever did
[00:07] <flexiondotorg> cyphermox, Yeah, it did. Both during the initial install and also in after it had been prepared.
[00:08] <flexiondotorg> VirtualBox has a regression.
[00:09] <jderose> cyphermox: it definitely used to prompt you to join the wifi network, although it was broken in 15.10. but it was working in 16.04 not that long ago (it was at most 2 weeks ago when i last tested)
[00:09] <flexiondotorg> Had this in 14.10 where the graphics are screwed in the guest and you have to switch tty and back to correct the corruption.
[00:09] <cyphermox> ok well then oem-config has been broken this way since before wily, not critical enough to scramble to fix and respin the images
[00:10] <cyphermox> jderose: weird
[00:10] <cyphermox> I tried looking into this, since at some point the applet was missing too
[00:10] <cyphermox> but all indicates it *should* work
[00:10] <jderose> cyphermox: yeah, i think you had it 100% fixed. but sounds like something might have changed
[00:10] <flexiondotorg> oem-config wifi worked in wily and in xenial, as jderose said, just a couple of weeks back.
[00:10] <cyphermox> maybe I have some weird ordering issue in the panels for OEM that I didn't notice
[00:11] <cyphermox> jderose: I didn't change anything relevant for the network prompts there.
[00:11] <flexiondotorg> The new a11y indicator has been introduced since.
[00:13] <cyphermox> flexiondotorg: well, I distinctly recall you guys mentioning that wifi prompts didn't work when we were preparing wily.
[00:14] <jderose> flexiondotorg: grub-install fails with nvme drives in BIOS mode on 14.04.4 also... so longstanding bug, not a regression
[00:14] <cyphermox> if things started working again, and then started not working again, it sounds like it wasn't my conscious doing :)
[00:15] <cyphermox> jderose: possible we didn't add nvme in grub-installer until after the .4 release
[00:15] <cyphermox> well
[00:15] <cyphermox> in fact either way it would not work since it doesn't work in xenial
[00:20] <cyphermox> slangasek: armhf+raspi2 looks good.
[00:21] <flexiondotorg> cyphermox, wifi prompts do not work in any install mode right now :-(
[00:22] <flexiondotorg> cyphermox, What jderose and I reported in Wily was that there was no network indicator in oem-config after the prepare had been done.
[00:22] <cyphermox> oh, nmcli dev must report all your wifis are wireds?
[00:23] <flexiondotorg> Maybe. How can I confirm that?
[00:23] <slangasek> run 'nmcli dev'
[00:26] <flexiondotorg> OK, preparing next test machine. Will do that.
[00:27] <flexiondotorg> So those last minute VirtualBox changes are busted.
[00:30] <flexiondotorg> nmcli dev is correctly reporting wifi devices.
[00:30] <flexiondotorg> Like I say, the network indicator works. I can manually join a wifi network. The issue is that Ubiquity is no longer prompting to do so.
[00:34] <flexiondotorg> cyphermox, ^^^
[00:35] <cyphermox> yeah, I see
[00:37] <flexiondotorg> jderose, ack the nvme testing. Thanks.
[00:43] <flexiondotorg> jderose https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1572793
[00:43] <ubot5`> Launchpad bug 1572793 in ubiquity (Ubuntu) "Ubiquity no longer prompts to join available WiFi networks" [Undecided,New]
[00:50] <cyphermox> ugh
[00:53] <cyphermox> flexiondotorg: I fail.
[00:53] <cyphermox> not sure why it's doing that, I'll have a look.
[00:53] <cyphermox> can you file a bug?
[00:53] <flexiondotorg> Oh, OK. I thought you were saying you couldn't reproduce for a moment :-)
[00:57] <Kamilion> lost the ability to fully shutdown or reboot in virtualbox.
[00:58] <Kamilion> (from the lubuntu64 livemedia)
[00:59] <cyphermox> flexiondotorg: nah, something is clearly broken
[01:11] <flexiondotorg> OK, I've done what testing I can. Tracker updated. Night. Or morning ;-)
[01:39] <tsimonq2> cyphermox: you guys need anything else that I can help with?
[01:39] <tsimonq2> cyphermox: for release tomorroe
[01:39] <tsimonq2> cyphermox: *tomorrow
[01:39] <cyphermox> test any image you'd like.
[01:40] <cyphermox> report findings on iso.qa.ubuntu.com, as usual :)
[01:40] <cyphermox> (and open bugs when you see some)
[01:43] <tsimonq2> alright
[01:43] <tsimonq2> that's all?
[01:44] <cyphermox> yeah
[01:47] <tsimonq2> cool :)
[02:27] <darkxst> can someone approve that ^, so I can re-spin
[02:34] <cyphermox> slangasek: ^ if you're still around
[03:01] <slangasek> darkxst, cyphermox: looking
[03:03] <slangasek> darkxst: why such a late seed change?  and doesn't this imply you'll have an extra session type now on the image that needs validated for release?
[03:04] <slangasek> (package accepted into -proposed for building, but not unblocking into xenial yet to give you time to reconsider / demand I comply :)
[03:05] <darkxst> slangasek, the fallback to X11 is broken on some systems, and yes a "wayland" session will show up
[03:07] <slangasek> "fallback to X11" - without this package, aren't you currently using X11 on all systems?
[03:07] <darkxst> we will still call the "wayland" session experimental though
[03:07] <darkxst> gdm tries to start on wayland first
[03:07] <darkxst> when that fails it should use X11
[03:07] <slangasek> so "experimental" but used by default? :)
[03:08] <darkxst> the user (login) session is experimental
[03:09] <darkxst> that would need to be manually selected when logging in
[03:10] <slangasek> alright, well, it doesn't sound to me like a change that is going to improve users' experience overall, but it's certainly your call - unblock hint added as well
[03:10] <darkxst> gdm running on wayland is well supported, but I could also force that off in the config
[03:10] <slangasek> so feel free to respin when it lands in xenial
[03:12] <darkxst> well landing at a blank screen at boot is not a great experience
[03:29] <Kamilion> well, I'll certainly jump on that, darkxst, I've been meaning to try wayland on as many bare metal boxes as I can, and that seems like a good opportunity
[03:38] <mwhudson> hm go 1.6.2...
[03:38] <mwhudson> nothing very urgent looking though, could just sru after release
[04:04] <darkxst> hmm actually I might revert that and just patch gdm conf instead
[04:08] <darkxst> slangasek, are you able to reject the -meta upload?
[04:10] <slangasek> darkxst: it's already accepted so can't be rejected, but can be removed
[04:10] <slangasek> assuming it hasn't already published to xenial, let me see
[04:11] <slangasek> darkxst: ah yeah, it's already published to xenial.  Sorry, was expediting to not hold up your respins
[04:13] <slangasek> darkxst: so, if you want to revert you need another meta upload
[04:36] <slangasek> darkxst: ^^ is there also an ubuntu-gnome-meta revert coming?
[04:36] <darkxst> slangasek, yes uploading now
[04:37] <slangasek> ok
[04:39] <slangasek> darkxst: both accepted and unblocked
[04:39] <darkxst> slangasek, thanks
[05:01] <cyphermox> moar coffeee
[05:33] <slangasek> ogra_: looks like the arm64 build doesn't want to pull from multiverse
[05:52] <slangasek> cyphermox: failed xubuntu test case; am I doing something wrong with my setup? https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1572842
[05:52] <ubot5`> Launchpad bug 1572842 in ubiquity (Ubuntu) "xubuntu 16.04 image does not give auto-resize option on 8GB disk" [Undecided,New]
[05:59] <cyphermox> isn't 8gb slightly too small?
[06:00] <cyphermox> come to think of it, for xubuntu it should be fine I think
[06:00] <slangasek> well, that's what I don't knowv
[06:00] <slangasek> I looked at actual usage, and it seemed it should have been enough space
[06:01] <cyphermox> you may be able to tell from running ubiquity --debug; at some point you'll see ubiquity SUBST the free_space templates, and you'd have the size there
[06:01] <cyphermox> it does seem like it should be plenty though
[06:01] <slangasek> mmm
[06:02] <slangasek> I'll just make the disk a bit bigger and retry
[06:02] <cyphermox> I also can boot up a xubuntu vm with the same conditions and try it
[06:03] <cyphermox> need to zsync that image first
[06:05] <cyphermox> ENOTENOUGHPOWEROUTLETSHERE
[06:10] <apw> cyphermox, bigger battery required ...
[06:10] <cyphermox> yeah, battery replacements for old spare laptops
[06:10] <cyphermox> well, old testing laptops I guess
[06:14] <slangasek> cyphermox: same problem reproduced with 10G disk
[06:14] <cyphermox> ok
[06:14] <cyphermox> wow, this release is terrible for the installer
[06:22] <cyphermox> I'm starting the ppc64el netboot test, and finishing the others I have been running, and then logging off
[06:27] <slangasek> cyphermox: ok I had resized the disk to 10GB but realize that there was still a swap partition in the middle of that.  Blew that away, resized the original partition up to fill the disk, and now I have the auto-resize option
[06:31] <cyphermox> ah?
[06:32] <cyphermox> why would it matter that it's a swap?
[06:32] <cyphermox> oh wait, we do explicitly swapon them now..
[06:32] <cyphermox> no, that wouldn't matter either
[06:33] <cyphermox> slangasek: please leave the bug open, I wonder if it's not that we don't deal with the swap correctly for resizing
[06:34] <slangasek> cyphermox: well, I expect it makes a difference because it means it can't make space for the new OS just by carving up the existing install partition
[06:34] <cyphermox> right
[06:35] <slangasek> cyphermox: also, just dropped another comment on the bug - spectacular failures
[06:35] <slangasek> so I'm going to consider this a failure and move on
[06:35] <cyphermox> yeah
[06:36] <cyphermox> slangasek: is it too late to save the exact crash message?
[06:39] <slangasek> cyphermox: yes.  the crash message was self-explanatory to me, it was an "out of space" error, and the partition table confirmed this
[06:40] <darkxst> trusty -> xenial upgrade for Ubuntu GNOME seems to have dpkg diverts in place still
[06:40] <darkxst> diverted by libgbm1-lts-wily to: /usr/lib/x86_64-linux-gnu/old.libgbm.so.1.0.0
[06:41] <slangasek> darkxst: please file a bug against xorg-lts-transitional tjaalton ^^
[06:41] <cyphermox> slangasek: right, but you said crash, so I'm curious where it crashed exactly, but I can just find out after rest.
[06:41] <darkxst> ok
[06:47] <tjaalton> I don't see where that divert comes from..
[06:47] <tjaalton> ah
[06:47] <tjaalton> now I do
[06:50] <pitti> Good morning
[06:51] <pitti> iso testing time! :-)
[06:51] <slangasek> tjaalton: yeah, so the new package in xenial will need to un-divert :/
[06:51] <tjaalton> sure
[06:52] <cyphermox> pitti: good morning
[06:52] <darkxst> there is also the gbm drm driver diverted
[06:52] <darkxst> bug 1572855
[06:52] <ubot5`> bug 1572855 in xorg-lts-transitional (Ubuntu) "libgbm.so.1: cannot open shared object file" [Undecided,New] https://launchpad.net/bugs/1572855
[06:52] <tjaalton> yep
[06:53] <tjaalton> I guess this has been carried over to newer lts stacks for no reason
[06:53] <tjaalton> anyway
[06:53] <slangasek> xnox: your mainframes netbooting ok?
[06:59] <cyphermox> slangasek: was the ppc netboot test you?
[06:59] <slangasek> cyphermox: no
[07:00] <slangasek> cyphermox: tracker says user 'sqldatapoo'
[07:00] <cyphermox> yeah, I just hadn't look far enough
[07:00] <slangasek> no idea if the described system is one that this is expected to work on
[07:01] <pitti> I find it a bit confusing that we still have these "ubuntu core" tarballs; seems this got overloaded quite a lot by now
[07:08] <cyphermox> slangasek: if we really care lots I'll try to boot my G5 again in the morning
[07:09] <slangasek> cyphermox: surely that's a matter for the powerpc community to care about... sooner than the day before release
[07:09] <cyphermox> of course
[07:09] <cyphermox> but I wouldn't mind upgrading that system anyway
[07:40]  * cyphermox -> sleep; back in ~4-5 hours
[07:48] <tjaalton> ^ tested
[07:50] <slangasek> tjaalton: the postinst->postinst.in logic /should/ be done in the build target, not in the clean target; it's valid to call build on the unpacked source without first running clean.  But LP builds call clean so this is ok.  But the maintscript logic worries me a bit; why do you have to do the dpkg-divert query, is it not guaranteed that the package which owns the divert is the same one currently
[07:50] <slangasek> running?
[07:51] <tjaalton> slangasek: copied it from a similar case when it removed xrandr diverts
[07:51] <slangasek> that it was copied doesn't make me feel better about it ;)
[07:51] <tjaalton> hear that
[07:52] <tjaalton> maybe for scriptability
[07:55] <slangasek> tjaalton: so if this were me, this would be the entirety of the postinst.in: http://paste.ubuntu.com/15960926/
[07:55] <pitti> WTF
[07:55] <pitti> ubuntu desktop/i386 with OEM still seems broken
[07:56] <slangasek> tjaalton: this way, each package only removes its own divert
[07:56] <tjaalton> slangasek: ok I can do that
[07:56] <slangasek> tjaalton: cool; I'll reject the previous one, please test the above
[07:56] <tjaalton> crap, need another victim machine :)
[07:56] <slangasek> heh
[07:57] <tjaalton> or I'll just add manual diverts of course
[07:58] <slangasek> pitti: but on the bright side, there are no i386 OEMs?
[07:58] <pitti> heh, yes
[07:58] <pitti> well, we might still respin that one, there aren't too many test cases yse
[07:58] <pitti> yet
[07:58] <pitti> or we ignore this indeed
[07:59] <slangasek> pitti: is it broken in a way that's fixable without source uploads that touch every image?
[07:59] <pitti> slangasek: yes, this looks like the mirror desync again
[07:59] <slangasek> ok
[07:59] <pitti> live system has ubiquity 2.21.63, pool/ still has 2.21.59
[07:59] <pitti> i. e. prodding that mirror and rebuilding just that iso should fix it
[07:59] <pitti> infinity, cjwatson ^
[08:00] <pitti> updated bug 1572436
[08:00] <ubot5`> bug 1572436 in Ubuntu CD Images ""Prepare for OEM install" icon and oem-config-prepare missing on Ubuntu desktop i386" [High,Confirmed] https://launchpad.net/bugs/1572436
[08:01] <pitti> and pool/ being out of date for ubiquity probably also means out-of-date-ness for other debs
[08:01] <pitti> and we are shipping a binary which we don't ship a source for
[08:01] <slangasek> mmm, would this impact all i386 images?
[08:01] <pitti> let's hope not
[08:02] <pitti> I don't think it's arch specific
[08:02] <pitti> yesterday we had that on the amd64 image, and the current one is good
[08:02] <pitti> file-roller xenial-desktop-i386.iso and checkign the version in pool/main/u/ubiquity/ is a quick test that doesn't even need installation
[08:03] <slangasek> or checking the .list files
[08:03] <pitti> indeed
[08:03] <pitti> hm, hang on
[08:04] <pitti> .disk/info says 20160419
[08:04] <pitti> I just downloaded this an hour ago..
[08:04] <slangasek> from the wrong url?
[08:04] <pitti> http://cdimage.ubuntu.com/cdimage/daily-live/current/
[08:04] <pitti> well, who knows, rsyncing again
[08:05] <pitti> (oh the joys of mirror rotation :) )
[08:05] <jibel> pitti, I'm retriggering the job that makes the copy.
[08:05] <pitti> jibel: how do you mean?
[08:05] <jibel> pitti, the copy between pending and current didn't happen
[08:05] <jibel> the node crashed during the nighrt
[08:05] <pitti> oh
[08:06] <pitti> http://cdimage.ubuntu.com/cdimage/daily-live/current/ looks okay
[08:06] <pitti> so maybe that actually updated in the last hour after I downloaded, or it's only one mirror that is affected?
[08:06] <slangasek> or it's a problem that affected only your rsync endpoint, not the http endpoint?
[08:06] <jibel> pitti, it should be now, I did it 5 minutes ago
[08:06] <slangasek> ah, heh
[08:06] <pitti> aah
[08:07] <pitti> ok, .disk/info is current now, and so is pool/, sorry for the noise
[08:07] <pitti> retest o'clock
[08:11] <tjaalton> slangasek: ^ there you go. btw, debuild -S runs clean, so the package itself comes with the .postinst's so there should be no way to not have them :)
[08:12] <slangasek> tjaalton: except the postinst is supposed to be different on each arch - anyway, that's not a blocker
[08:12] <tjaalton> oh indeed, hehe
[08:12] <Laney> hi
[08:14] <flexiondotorg> pitti, How did that i386 issue manifest? Ubuntu MATE i386 images were some of the last made, I tested them last night. No issues with oem mode.
[08:15] <pitti> flexiondotorg: yes, you'd notice because OEM mode is broken
[08:15] <flexiondotorg> pitti, Thanks.
[08:15] <pitti> that was an issue on a lot of images yesterday, and was supposed to be fixed; so I just fell into that "old image" trap
[08:16] <infinity> pitti: WTF?  I did a hard ftpsync before building anything.
[08:17] <pitti> infinity: yes, it wasn't the internal mirror after all, just a cdimage mirror being out of date (see above, jibel fixed it)
[08:17] <infinity> Oh, you were looking at current, not the dated dirs
[08:17] <pitti> yes, my daily rsync scripts do that
[08:18] <pitti> all good on the current image
[08:22] <Laney> tjaalton: Did you see the llvm-3.8/i386 FTBFS?
[08:23] <tjaalton> Laney: yes, and uploaded a new version
[08:24] <Laney> tjaalton: Ahhhhh, in the queue.
[08:24] <Laney> Um
[08:24] <pitti> infinity: does it make sense to manually test ubuntu core? (on some less common arches like arm64 or ppc64el), or do we have some automagic for that?
[08:25] <Laney> Can't you just disable the relevant tests?
[08:25] <Laney> Or are they the only ones?
[08:25] <infinity> pitti: I do a quick run across all arches, it's a 2 minute affair.
[08:25] <pitti> infinity: yeah, I thought the same, nice thing to do while watching ubiquity install :) ok, I'll leave this to you then
[08:25]  * pitti would need more like 3 minutes per arch, not 2 minutes for everything
[08:31] <cjwatson> pitti: *phew*
[08:31] <pitti> cjwatson: *phew*² indeed
[08:32] <flexiondotorg> I was testing last night. Not sure if you guys have seen the backlog.
[08:32] <cjwatson> infinity: We could do the cloudfront uploads now, right?
[08:33] <flexiondotorg> The VirtualBox updates that were included yesterday are a bit busted. Has a regression that reintroduces video corruption.
[08:33] <flexiondotorg> Requires switching ttys to restore a usable display.
[08:34] <infinity> cjwatson: Yup.  I was just going to run officeward, but if you want to relay the info to IS while I walk, yay.
[08:34] <cjwatson> infinity: Will do.  Presumably just the pre-published ones?
[08:34] <infinity> cjwatson: No, they want everything, I believe.
[08:34] <cjwatson> flexiondotorg: That should be fixable in SRU, I guess.
[08:34] <flexiondotorg> Ubiquity no longer prompts to join wifi networks - https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1572793
[08:34] <ubot5`> Launchpad bug 1572793 in ubiquity (Ubuntu) "Ubiquity no longer prompts to join available WiFi networks" [Undecided,Confirmed]
[08:35] <flexiondotorg> cjwatson, Yes, except installs right now on VirtualBox appear broken.
[08:35] <cjwatson> flexiondotorg: Right, sure, but the virtualisation host is usually easily updatable to SRUs.
[08:35] <flexiondotorg> The install is fine, but on first boot video is completely screwed.
[08:35] <cjwatson> (once they exist)
[08:35] <mapreri> they ask me if you could accept a last-minute sync of virtualbox, changing nothing from the current version in debian but the version (maintainer uploaded both in debian and ubuntu for fear of hitting dinstall last night and not having the upload done to ubuntu)
[08:35] <flexiondotorg> pitti, I confirm the swap issue is totally fixed :-D
[08:36] <infinity> virtualbox isn't seeded, if someone had a magic fix, I'd take it.  Otherwise, meh.
[08:36] <infinity> The "not seeded" part also means that an SRU with magically fix it.
[08:36] <flexiondotorg> infinity, Kernel modules.
[08:36] <infinity> flexiondotorg: The kernel modules builtin to the Ubuntu kernel didn't change.
[08:37] <infinity> flexiondotorg: Only the dkms packages did.
[08:37] <mapreri> "an SRU with magically fix it" s/with/will/ ?
[08:37] <infinity> flexiondotorg: So, if your image was fine N days ago and broke recently, it's all the unseeded packages being pulled in later.
[08:37] <pitti> flexiondotorg: yay
[08:37] <infinity> mapreri: Will, yes.
[08:37] <mapreri> infinity: do you mean an SRU will magically be accepted?
[08:37] <flexiondotorg> infinity, Something changed. Has worked fine throughout 16.04 cycle until image built yesterday.
[08:37] <mapreri> if so, guess I'll tell him "just wait tomorrow"
[08:37] <infinity> mapreri: No, I mean an SRU that fixes it would DTRT, since the images aren't broken, it's packages pulled during install.
[08:38] <infinity> flexiondotorg: Again, it's not the *image*, though, it's the archive.
[08:38] <infinity> flexiondotorg: It's the drivers being installed from the archive at install.
[08:38] <infinity> flexiondotorg: Installing without network probably wouldn't reproduce the bug.
[08:38] <mapreri> ok.  i'll forward the NACK.  To me it seems crazy anyway bugging for only a version change :)  ta.
[08:38] <infinity> flexiondotorg: And, thus, an SRU post-release would also fix it.
[08:39] <flexiondotorg> infinity, So I install from the current image, without network connected, and the video is corrupt in VirtualBox.
[08:39] <rbasak> infinity: I'm assuming the MySQL 5.7 upstream update will need to be a 0-day at this stage? In which case, probably the security pocket?
[08:40] <infinity> flexiondotorg: Then that can't be virtualbox's (the package) fault, since it's not anywhere near your ISO.
[08:40] <infinity> rbasak: Coordinate with the security team, yes.
[08:40] <rbasak> OK
[08:41] <flexiondotorg> infinity, I see linux-firmware-nonfree is no longer in the xenial archive.
[08:41] <flexiondotorg> Is that intentional?
[08:42] <Laney> https://bugs.launchpad.net/ubuntu/+source/linux-firmware-nonfree/+bug/1513589 Yes.
[08:42] <ubot5`> Launchpad bug 1513589 in linux-firmware-nonfree (Ubuntu Xenial) "linux-firmware-nonfree should be removed from Xenial" [Undecided,Fix released]
[08:44] <flexiondotorg> infinity, Thanks. I'll need to request an update to Ubuntu MATE Welcome.
[08:51] <davmor2> cyphermox: you about?
[08:51] <davmor2> infinity: wizard is missing the connect to wifi page
[08:52] <infinity> davmor2: Reported a few times over the last day.
[08:53] <davmor2> infinity: I'm wondering if it is the update to 1.93 changes that broke it
[08:53] <infinity> flexiondotorg: Respinning for MATE welcome alone is probably not reasonable at this stage, unless it's completely busted.
[08:53] <infinity> flexiondotorg: As for your vbox woes, what's the host machine?  Is that also up to date xenial?  I can see it perhaps having broken on the host side.
[08:54] <davmor2> infinity: network-manager that is :)
[08:54] <ogra_> slangasek, infinity http://paste.ubuntu.com/15961377/ does that look sane ?
[08:54] <Laney> oh god an ogra_ diff
[08:54] <ogra_> lol
[08:54] <flexiondotorg> infinity, Not to respin the image. Just a package upload. Is that OK?
[08:55] <infinity> flexiondotorg: Only as an SRU.
[08:55] <infinity> flexiondotorg: Images should match the release pocket.
[08:56] <infinity> ogra_: Probably not.
[08:56] <flexiondotorg> infinity, So I should not file an package update in the usual way?
[08:57] <ogra_> infinity, well, how else do i get multiverse into a dedicated chroot then ?
[08:57] <Laney> flexiondotorg: Do an SRU in the usual way
[08:57] <flexiondotorg> Laney, Never done one before.
[08:57] <Laney> Then reading https://wiki.ubuntu.com/StableReleaseUpdates#Procedure is in your future. :)
[08:57]  * ogra_ grumbles about last minute landing that make everything explode
[08:57] <ogra_> *landings
[08:58] <cjwatson> pot, kettle, ... :-)
[08:58] <infinity> ogra_: That didn't "make everything explode", you were building from a PPA before. :P
[08:58] <ogra_> infinity, well, i''m naggibng the kernel team since 6 weeks about the rpi kernel that was stuck in proposed
[08:58]  * flexiondotorg is already reading about SRU
[08:59] <ogra_> especially to avoid shuch crap
[08:59] <infinity> ogra_: http://paste.ubuntu.com/15961413/
[08:59] <infinity> ogra_: That's probably what you want.
[08:59] <ogra_> infinity, that wont work
[08:59] <infinity> Because?
[08:59] <ogra_> because there is adedicated chroot freshly debootstrapped
[09:00] <ogra_> will a plain debootstrap call pick up COMPONENTS= ?
[09:00] <infinity> ogra_: Which you use the previous sources.list for.
[09:00] <infinity> ogra_:       cp -a chroot/etc/apt/* chroot-device/etc/apt/
[09:00] <ogra_> oh, wait ... i think i'm copying /etc/apt
[09:00] <infinity> ogra_: So, yes, it'll work.
[09:00] <ogra_> yeah :)
[09:00] <ogra_> thanks !
[09:00] <infinity> ogra_: If it didn't work, you wouldn't have a kernel either (since debootstrap only uses main, and your kernel is universe)
[09:01] <ogra_> indeed
[09:04] <jibel> anyone know if the wifi page has been removed from ubiquity on purpose?
[09:04] <jibel> cyphermox, ^
[09:04] <jibel> cf bug 1572793
[09:04] <ubot5`> bug 1572793 in ubiquity (Ubuntu) "Ubiquity no longer prompts to join available WiFi networks" [Undecided,Confirmed] https://launchpad.net/bugs/1572793
[09:05] <jibel> nevermind, I scrolled up
[09:05] <ogra_> cjwatson, i assume i can land your livecd-rootfs change alongside ?
[09:06] <cjwatson> ogra_: yes
[09:06] <cjwatson> that was "I never want to see that particular mistake again"
[09:07] <ogra_> heh
[09:09] <pitti> o_O what happened to 2.407?
[09:10] <ogra_> dch -i ... seemingly ...
[09:10]  * ogra_ sighs
[09:11] <Laney> :)
[09:11] <ogra_> should i re-upload ?
[09:11] <ogra_> ok
[09:11] <infinity> And rename that tag. :P
[09:12] <infinity> Well, delete that tag.
[09:12] <Laney> Tag the taggy tag
[09:13]  * ogra_ notes he cant win ... i spent nightshifts the last weeks making sure everything is fine and snappy builds rock solid ... to avoid exactly these last minute hacks ... :((((((
[09:18] <ogra_> sigh
[09:18] <ogra_> ssh: Could not resolve hostname bazaar.launchpad.net: Name or service not known
[09:20] <cjwatson> I swear we haven't decommissioned it
[09:20] <ogra_> haha
[09:25] <davmor2> infinity, jibel: so the wifi page doesn't show in standard setup or in the End User setup in oem mode so I assume we need a fix for this right?
[09:26] <davmor2> pitti: on a good news side of things No swap space error dialogue \o/
[09:26] <infinity> davmor2: Not a fix in the sense of an ISO respin.  AFAIK, the nm-applet still works, so you can configure there instead.
[09:27] <Laney> Sounds like a release note + SRU
[09:27] <pitti> i. e. fix for 16.04.1?
[09:27] <pitti> sucks a bit, but meh
[09:27] <infinity> Sucks less than delaying the release for a day for it.
[09:28] <infinity> (a day or more, since no one's quite sure what the bug is yet)
[09:29] <flexiondotorg> Laney, Can an SRU be a point release "upgrade" or should it just be a patch to the existing version?
[09:30] <infinity> flexiondotorg: I'm not sure I understand that question.
[09:31] <flexiondotorg> ubuntu-mate-welcome is currently 16.04.9. I've pushed and change and built it in a PPA as 16.04.10
[09:31] <flexiondotorg> Can the SRU introduce the newer version?
[09:32] <Laney> Yes
[09:34] <flexiondotorg> Laney, ty
[09:36] <cjwatson> yofel: can nepomuk-widgets be removed?  it seems to have a bunch of uninstallables
[09:36] <yofel> cjwatson: kill it
[09:37] <cjwatson> yofel: awesome, thanks.  is it superseded by something I can log in the removal message?
[09:37] <yofel> nepomuk itself was obsoleted by baloo, so nothing should be using nepomuk-* anymore
[09:37] <cjwatson> ok
[09:37] <cjwatson> yofel: how about declarative-plasmoids?
[09:37] <davmor2> infinity: might be a secondary issue with wifi on oem mode just reinstalling to check on it
[09:38] <yofel> cjwatson: "Depends: kdeworkspace-bin", that's kde4 and can go too
[09:39]  * cjwatson nukes
[09:40] <cjwatson> yofel: startactive too?  I think that's the last of the KDE-specific all-arch uninstallables
[09:41] <yofel> cjwatson: yes, can go too
[09:42] <cjwatson> done
[09:48] <flexiondotorg> Laney, infinity Does this look like what you'd expect? https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-welcome/+bug/1572931
[09:48] <ubot5`> Launchpad bug 1572931 in ubuntu-mate-welcome (Ubuntu) "SRU: ubuntu-mate-welcome 16.04.10 bug fix [dsc attached]" [Undecided,New]
[09:51] <Laney> flexiondotorg: Sure, although I think you should apply some imagination to the regression potential section :)
[09:51] <flexiondotorg> Laney, it's accurate :-)
[09:51] <Laney> Yeah right
[09:51] <flexiondotorg> So, I should also subscribe the sru verification team?
[09:52] <Laney> No
[09:52] <Laney> Nominate to xenial, then upload or subscribe sponsors
[09:52] <flexiondotorg> Sponsors subscribed.
[09:53] <flexiondotorg> Laney, Do I nominate xenial using tags?
[09:56] <Laney> No, there's a link for it below the list of bug tasks
[09:56] <Laney> But if you can't see it then don't bother
[09:57] <flexiondotorg> Laney, I don't see bug tasks :-(
[09:59] <Laney> k
[09:59] <Laney> I don't remember what permissions it needed
[10:02] <cjwatson> yofel: oh, one more, how about sentinella?
[10:02] <cjwatson> cf. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797942
[10:02] <ubot5`> Debian bug 797942 in src:sentinella "sentinella: build-depends on obsolete kdebase-workspace-dev" [Serious,Open]
[10:02] <cjwatson> maybe I should demote that one to -proposed since there seems at least some chance that it might be fixed at some point, and it's synced from Debian
[10:03] <cjwatson> yeah, I've argued myself into that, done
[10:04] <davmor2> infinity, jibel: yeap confirmed second oem install and I have no wifi for the end user http://people.canonical.com/~davmor2/desktop-screenshots/wifi-broken.png
[10:04] <davmor2> I need to reboot the end user session to get working wifi
[10:05] <flexiondotorg> infinity, Using different 16.04 host, which is fully updated. Installing a VirtualBox guest I have no video corruption :-)
[10:05] <apw> davmor2, "reboot the user session" means logout/in again ?
[10:06] <flexiondotorg> infinity, Looks like you're right about host/guest mismatch.
[10:06] <davmor2> apw: no means reboot the machine
[10:06] <apw> davmor2, what what wifi driver is that using?
[10:07] <davmor2> apw: 1 second
[10:09] <davmor2> apw: Intel Corporation Centrino Wireless-N 2200 (rev c4)
[10:10] <davmor2> apw: it works in the installer, let me see what happens if I enable it in oem user and enable it in enduser setup too
[10:10] <apw> davmor2, nothing eosteric then, i would be a bit supprised broken kernel side ... /me looks sideways at network-manager
[10:12] <Laney> darkxst: can haz testing?
[10:13] <darkxst> Laney, if you mean on QA tracker, there was a late respin with a minor gdm change
[10:14] <seb128> Laney, darkxst, I'm downloading a i386 GNOME iso for testing
[10:15] <Laney> darkxst: OK, so you don't need to fully test everything then
[10:18] <darkxst> Laney, I am pretty happy with 20.1 results for amd64, but yeh we are lacking for i386
[10:18] <ginggs_> flexiondotorg: i nominated your ubuntu-mate-welcome bug for xenial
[10:19] <flexiondotorg> ginggs_, Thank you :-)
[10:23] <flexiondotorg> pitti, I confirm https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1572863
[10:23] <ubot5`> Launchpad bug 1572863 in language-selector (Ubuntu) "no "incomplete language support" note in offline xenial install" [Undecided,Confirmed]
[10:24] <pitti> flexiondotorg: seb128 told me that there were some deliberate changes there; so this might actually just be an outdated test description
[10:24] <flexiondotorg> OK.
[10:24] <pitti> I didn't check whether I got spell checking in LibO, I just ran check-language-support and got two handfuls of missing packages
[10:25] <seb128> pitti, well, didrocks' changes inted was to have full support on the iso for the main languages afaik
[10:25] <seb128> like opening language-selector shouldn't display you the  incomplete dialog
[10:25] <seb128> if that's not the case then there is a bug
[10:27] <Laney> pitti: Did you do some componenty stuff for xorg-lts-transitional? http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#xorg-lts-transitional needs some fixing up
[10:27] <pitti> seb128: ok, I'll reinstall that scenario again and check this
[10:28] <seb128> pitti, https://lists.ubuntu.com/archives/ubuntu-devel/2015-December/039028.html has the details
[10:28] <pitti> Laney: they all got seeded, so I promoted them into main; I  guess for the universe packages those metapackags need unseeding?
[10:28] <seb128> "1. Install full language support for those shipped on xenial image. It
[10:28] <seb128> means that opening "language selector" won't request any additional
[10:28] <seb128> package to install[1]."
[10:28] <seb128> pitti, ^
[10:28] <seb128> so yeah that was the intend
[10:29] <seb128> unsure if that's working as expected or if we have a bug though
[10:29] <pitti> just started a new VM test install, ETA 3 mins
[10:29] <tjaalton> Laney: no, can't disable just some tests and filing a bug report just to fix a FTBFS is unnecessary paperwork I think
[10:29] <pitti> (installing onto tmpfs is  fun!)
[10:30] <davmor2> Okay so I am in oem mode right now and I see available Networks so it is fine there. Moving onto End user setup environment
[10:30] <seb128> darkxst, is the GNOME iso supposed to boot to a "get me started" screen with any obvious installer link/icon?
[10:30] <pitti> tjaalton: so I suppose the bits in http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#xorg-lts-transitional need unseeding?
[10:31] <Laney> tjaalton: Not if you want to SRU it it isn't.k
[10:32] <tjaalton> Laney: there is #1564156 already, should it be on every changelog entry?
[10:32] <davmor2> Wifi networks are available in end user creation page
[10:32] <tjaalton> pitti: where did all that come from..
[10:32] <pitti> tjaalton: not sure, I suppose someone seeded the transitional metapackages into main wholesale without realizing that some drivers are in universe?
[10:33] <tjaalton> pitti: oh, then yes drop those
[10:34] <apw> tjaalton, there are two on that list that look odd ... the two libegl1-....-dbg ones depend on a non -dbg one in xenial ... is that rght ?
[10:35] <tjaalton> apw: mesa doesn't build separate -dbg packages anymore
[10:35] <apw> tjaalton, ack thanks, ignore me then :)
[10:35] <davmor2> Bingo Nothing in the end user desktop session, seb128 I assume that means it's actually some config getting screwed up by oem-config setup thingy right?
[10:35] <Laney> pitti: Looks like the "!" stuff doesn't work that way
[10:36] <seb128> davmor2, having the logs would help to know
[10:36] <Laney> pitti: Are you fixing it? It needs to specify the binaries individually
[10:36] <pitti> Laney: haven't started looking yet, still figuring out an install bug
[10:36] <tjaalton> apw: this was best I could figure out to make sure the lts dbg packages get replaced
[10:36] <davmor2> seb128: yeap I just did another fresh install to figure out at exactly what point it broke
[10:36] <tjaalton> than not depend on anything
[10:36] <davmor2> seb128: I'm triggering the bugs now
[10:36] <pitti> seb128: done, started language-selector, getting the "incomplete language support" dialog
[10:37] <apw> tjaalton, right ... happy enough ... noticed the oddity so just wanted to make sure it was intended, which it is
[10:37] <seb128> pitti, k, so bug :-(
[10:37] <pitti> seb128: however
[10:37] <seb128> suck
[10:37] <seb128> which packages are missing?
[10:37] <pitti> seb128: looking more closely, this only affects the English stuff and some -de-at and -de-ch
[10:37] <seb128> ah
[10:37] <seb128> you didn't pick proper de?
[10:37] <tjaalton> apw: yeah, actually an empty depends would've worked just the same.. and is used for libopenvg-*
[10:37] <seb128> oh
[10:37] <seb128> you mean it lacks some de-at- and de-ch variants
[10:38] <pitti> seb128: I do have -de-de actually
[10:38] <pitti> so, it's actually fine
[10:38] <seb128> k, gotchat
[10:38] <seb128> so it might work with -it or -fr
[10:38] <pitti> seb128: I suppose you'll also get the -en-gb stuff for fr or it
[10:38] <pitti> but that's ok -- we really don't need to show a notification for those
[10:38] <Laney> pitti: OK, looking here then
[10:38] <seb128> right
[10:39] <seb128> why does it want -en-gb on a de or fr install?
[10:39] <davmor2> seb128: because en-gb is the most awesome language variant in the world obviously ;)
[10:39] <seb128> rrrright ;-)
[10:40] <davmor2> seb128: I'm sensing sarcasm in that rrrrright :D
[10:40] <flexiondotorg> infinity, Have you started syncing the release images to the mirrors?
[10:41] <seb128> you are seeing things... ;-)
[10:41] <pitti> seb128: well, we also enable an English keyboard by default :)
[10:41] <pitti> seb128: bug 1572863 updated, thanks for the heads-up
[10:41] <ubot5`> bug 1572863 in language-selector (Ubuntu) "no "incomplete language support" note in offline xenial install" [Undecided,Won't fix] https://launchpad.net/bugs/1572863
[10:42] <seb128> pitti, thanks
[10:43] <seb128> pitti, the english keyboard is actually needed to get e.g ctrl-C to work on non latin locales
[10:43] <seb128> so there is a valid reason
[10:48] <davmor2> seb128: bug 1572956
[10:48] <ubot5`> bug 1572956 in network-manager (Ubuntu) "Oem install end user has no wifi" [Undecided,New] https://launchpad.net/bugs/1572956
[10:48] <davmor2> seb128: not sure if the logs will lie because I had to enable wifi to send the bug report
[10:51] <seb128> davmor2, how did you enable wifi and at what time in that log?
[10:51] <pitti> RAOF, infinity: do you see any reason to actually keep http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#dovecot? ubuntu4 reverts ubuntu3, so IMHO we should just remove that from -proposed
[10:52] <davmor2> seb128: you have to reboot to enable it
[10:52] <infinity> pitti: We're just going to toss it into y-proposed.
[10:52] <pitti> there is no net change
[10:52] <seb128> davmor2, there is onlye one boot in https://launchpadlibrarian.net/254822439/WifiSyslog.txt
[10:52] <infinity> pitti: Mostly to avoid versions going backwards and being confusing.
[10:52] <seb128> davmor2, is that the first or the reboot?
[10:52] <infinity> pitti: But yes, no net chage.
[10:53] <davmor2> seb128: probably the reboot, the oem end user session is launched from the oem enduser installer so the boot stuff for that would be in other logs I guess
[10:54] <seb128> davmor2, could you collect those logs then?
[10:54] <davmor2> seb128: no idea what or where they would be but I can have a dig around
[10:55] <seb128> davmor2, some people on this channel can probably help you
[10:57] <pitti> Laney: I think you need to look at xenial, not trusty, for the components
[10:57] <pitti> Laney: e. g. xserver-xorg-video-mach64 was demoted in xenial only
[10:57] <pitti> so the transitional must be in universe, too
[11:01] <pitti> ^ no heart attack, please; this is SRU material
[11:01] <pitti> (0-day, or N-day for low N)
[11:01] <davmor2> seb128: syslog I attached shows some stuff from both oem and dave as users where it changes from oem to dave there are some warnings around network-manager that don't seem to be further down which I assume is after reboot, will keep digging though
[11:02] <Laney> pitti: Hm, then maybe I need to look at the *Depends* and not the package itself
[11:07] <seb128> davmor2, yeah, I think you got the right log, unsure about the issue though, maybe cyphermox has a better clue
[11:07] <seb128> Apr 21 11:28:18 oem-Lenovo-IdeaPad-Y580 NetworkManager[887]: <info>  [1461234498.2955] (21710752) ... get_connections (managed=false): return empty list.
[11:07] <seb128> that looks wrong though
[11:08] <seb128> hum, though it's doing that as well on the working boot..
[11:08] <Laney> pitti: Re-running
[11:15] <Laney> pitti: https://paste.ubuntu.com/15963110/ ?
[11:21] <Laney> (pushed anyway)
[11:21] <Laney> (so wait for the *next* c-m run please)
[11:52] <ogra_> Setting up linux-firmware-raspi2 (1.20151118+b70b451-0ubuntu1) ...
[11:52] <ogra_> cp: cannot create regular file '/boot/firmware/bootcode.bin': No such file or directory
[11:52] <ogra_> dpkg: error processing package linux-firmware-raspi2 (--configure):
[11:52] <ogra_>  subprocess installed post-installation script returned error exit status 1
[11:52] <ogra_> Setting up linux-image-raspi2 (4.4.0.1009.9) ...
[11:52] <ogra_> Errors were encountered while processing:
[11:52] <ogra_>  linux-firmware-raspi2
[11:52]  * ogra_ curses loudly 
[11:52] <ogra_> apw, ^^^
[11:56] <ogra_> what the hell is /boot/firmware even ...
[11:58] <infinity> ogra_: The package always had that, that's not new.  I'm guessing you weren't using it before?
[11:58] <infinity> ogra_: /boot/firmware is a vfat mountpoint, evidently.
[11:59] <ogra_> infinity, the package was not accessible for me until yesterday late evening (the final snappy images were built yesterday monring)
[12:00] <ogra_> (i'm just trying to rebuild the mess now, after that package was stuck 6 weeks in proposed)
[12:01] <ogra_> apw, ppisati ^^^ can you fix that ?
[12:02] <apw> ogra_, its where the firmware has to be i am told
[12:03] <apw> is that _not_ true ?
[12:03] <infinity> ogra_: "not accessible"?  rasperrypi2-firmware has been in the archive for months, we just renamed it.
[12:03] <ogra_> apw, havging a hardcoded mountpoint check in the postinst makes the package uninstallable in chroots
[12:03] <apw> infinity, we did change how the copy was done but still copied to there
[12:03] <apw> ogra_, it has a do_chroot check round it
[12:03] <infinity> ischroot, even.
[12:03] <infinity> What it doesn't do is create the dir.
[12:04] <infinity> Cause it's meant to be there, in theory.
[12:04] <ogra_> ok,. i'll hack that into livecd-rootfs then
[12:04] <ogra_> but the package needs fixing too
[12:04] <infinity> Fixing to do what?
[12:04] <ogra_> create the dir
[12:04] <infinity> Maybe.
[12:05] <ogra_> (i have no clue what that dir is supposed to do ... we definitely dont use it in snappy)
[12:05] <apw> then we might want to stop copyuing things into it ...
[12:05] <apw> ppisati, ^^^^^^
[12:05] <ogra_> (and couldnt, since the gadget would over-mount something )
[12:05] <infinity> If you "don't use it", then why are you installing that package?
[12:05] <infinity> Given that its entire purpose it to install that boot-related firmware.
[12:05] <infinity> It doesn't seem to have any runtime firmware.
[12:05] <ogra_> infinity, i need whats in /lib/firmware ... which is supposedly the wlan fFW for the pi3
[12:06] <ogra_> which is the whole purpose of me using that package
[12:06] <ogra_> (and video stuff for the pi2 toop afaik)
[12:07] <ogra_> err ...
[12:07] <infinity> Nothing there looks like wifi firmware to me.
[12:07] <ogra_> so looking at the package there is nothing if the stuff we had in the former pi2 firmware package
[12:07] <ogra_> *of the
[12:07] <ogra_> where is that gone ?
[12:07] <infinity> It's *identical* to the previous rpi2 firmware package.
[12:08] <infinity> Unless you mean some package you had in some PPA, which we weren't aware of.
[12:08] <infinity> In which case, thanks for telling us about it.
[12:09] <ogra_> infinity, all i ever did was copy package packagfes that were supposed to go to the archive from the kernel team to the snappy PPA
[12:09] <rbasak> xnox: hey, edit conflicts in the release notes. Did you pay attention to my lock?
[12:09] <pitti> Laney: thanks, shoudl have updated by now; http://people.canonical.com/~ubuntu-archive/component-mismatches.txt looks a little thin, though? or did you already demote some lot?
[12:09] <xnox> rbasak, i have and i have cancelled my edit
[12:09] <Laney> pitti: Needed some more Extra-Excludes
[12:09] <pitti> Laney: like, shouldn't at least -mach be in there?
[12:10] <infinity> pitti: Need another run after some more changes I made.
[12:10] <xnox> rbasak, and re-did mine after yours...
[12:10] <ogra_> anyway ... i'll drop the firmware package and pray tha the snappy images will at least boot with the new packages ...
[12:10] <pitti> ah
[12:10] <xnox> rbasak, is everything good or did we loose thigns?
[12:10] <Laney> germinate is hard
[12:10] <pitti> ok, let's give this another cycle then
[12:10] <ogra_> i really diont get why that stuff has to land one day before release
[12:10] <pitti> Laney: thanks
[12:10] <infinity> ogra_: I guess your complaint is with Paolo then?  apw and I were only working with what was in the archive.
[12:10] <infinity> ogra_: And nothing "landed" before release, except a package rename.
[12:10] <rbasak> xnox: everything I wnated is still there. Can you check yours? Then I'll clear the markers.
[12:10] <infinity> ogra_: Well, not for rpi2.
[12:10] <ogra_> infinity, well, again ,... the rpi package was sitting in -proposed for weeks
[12:11] <xnox> rbasak, my stuff is good
[12:11] <infinity> ogra_: A new kernel was.  The old kernel and firmware had been in the release pocket for months.
[12:11] <ogra_> and i was poking about it since at kleast 4 weeks
[12:11] <infinity> ogra_: I know, because I was building images with it.
[12:11] <rbasak> xnox: OK I'll clear the markers. I have another change to make, too.
[12:11] <xnox> rbasak, imho it should be fine for multiple people to edit non-conflicting sections wikimedia stile.
[12:11] <ogra_> all snappy images were built and tested yesterday ... everyone who could work on them is off today, i'm just trying to cover the fallout here now
[12:11] <infinity> ogra_: You had a *long* time to test that firmware package in the release pocket and tell us it was wrong.
[12:12] <infinity> "Published on 2016-02-12"
[12:12] <infinity> https://launchpad.net/ubuntu/+source/raspberrypi2-firmware/+publishinghistory
[12:12] <ogra_> i'm, talking about the kernel
[12:13] <infinity> ogra_: Again, there was an older kernel in the release pocket too, just not the latest rebase.
[12:13] <infinity> ogra_: Waiting on the latest to test things isn't helpful.
[12:13] <ogra_> infinity, yes, that old kernel is in our snappy release today
[12:13] <ogra_> we havent build rpi from the PPA for at least 6 weeks
[12:13] <infinity> ogra_: Anyhow, you were complaining about firmware, not kernels, I'm saying the firmware has been in this state for months and no one thought to tell us it might be wrong.
[12:13] <ogra_> (dragonboard was the only one having a PPA kernel til yesterday)
[12:18] <rbasak> jamespage, jcastro, teward: right now new package version notes for server packages in the Xenial release notes are split between "Updated Packages" and "Ubuntu Server" - pretty inconsistent. How should we resolve this?
[12:19] <infinity> rbasak: Please.
[12:20] <rbasak> Yeah but how? Move updated server packages to the update packages section? Or pull server updated packages out of the updated package section?
[12:20] <rbasak> Maybe the former?
[12:20] <infinity> rbasak: Traditionally, we put server/desktop bits in their own sections.
[12:20] <infinity> rbasak: And the "updated packages" section is for core stuff like kernel, systemd, whatever.
[12:20] <rbasak> infinity: OK. I'll move the server stuff down.
[12:21] <infinity> Frankly, most updates don't need to be documented anyway.
[12:21]  * rbasak wonders if LXD is an updated package.
[12:21] <Odd_Bloke> rbasak: I think we definitely want something in there about the bridge changes.
[12:22] <infinity> It's only worth documenting if it's either a big press release bullet point ("Yay, juju2 is awesome" -- Fictional User), or if it's something people need to pay attention to ("New MySQL, watch for config breakage")
[12:22] <rbasak> Yeah, but people seem to want to document the New Shiny in the release notes.
[12:22] <rbasak> Odd_Bloke: do you mind writing that up please?
[12:22] <jcastro> rbasak: you can copy our stuff into Server, that's fine, don't really feel strongly one way or the other
[12:22] <infinity> rbasak: Yup, there's a section for shiny, just limit it to things that seem legitimately shiny.  Like "apache bumped from 2.2.7 to 2.2.32" is not shiny, for instance.
[12:22] <jcastro> it's a major release that doesn't support upgrades though
[12:23] <Odd_Bloke> rbasak: I would prefer it if stgraber or someone else on the lxd team did, as I don't think I have a full grasp of it. :)
[12:23] <jcastro> well, let me rephrase, upgrading from 1->2 is non-trivial
[12:23] <stgraber> Odd_Bloke: boarding a plain in 2 minutes so won't be able to help much with that, sorry :)
[12:24] <Odd_Bloke> stgraber: How convenient. ;)
[12:24] <stgraber> Odd_Bloke: I did tweak the "shiny" LXD paragraph earlier, I guess the bridge stuff should go separately in upgrade notes or something
[12:24] <stgraber> Odd_Bloke: basically telling people to read their screen :)
[12:24] <Odd_Bloke> stgraber: :)
[12:24] <stgraber> we do show a pretty clear warning telling them exactly what's going on and what to do about it
[12:25] <rbasak> OK, server stuff moved down. I decided LXD was "server" and moved it down too.
[12:25] <rbasak> I put everything at the bottom. Feel free to edit the order.
[12:25] <stgraber> Odd_Bloke: which boils down to, run "sudo dpkg-reconfigure -p medium lxd" and answer the questions
[12:25] <rbasak> Is mvo not around? There's bug 1554121 which I think should probably be noted
[12:25] <ubot5`> bug 1554121 in Release Notes for Ubuntu "unattended-upgrades defaults to installing security updates" [Undecided,New] https://launchpad.net/bugs/1554121
[12:25] <infinity> rbasak: Works for me.  In my mind, virt/pseudo-virt (qemu, xen, lxc, lxd) should be "core", but our corproate structure disagrees with me. :)
[12:26]  * stgraber diappears for 2-3 hours
[12:26] <stgraber> *disappears too
[12:27] <Odd_Bloke> https://twitter.com/ubuntu/status/723112408437284864 *facepalm*
[12:31] <rbasak> infinity: opinion on unattended-upgrades note? I'd like to also say what users should do to disable it but I don't know what that is exactly.
[12:31] <rbasak> bug 831487 suggests that it should be purgeable but germinate-output suggests otherwise to me.
[12:31] <ubot5`> bug 831487 in software-properties (Ubuntu Xenial) "Dependency on package unattended-upgrades on Ubuntu Server" [High,Fix released] https://launchpad.net/bugs/831487
[12:32] <flexiondotorg> Odd_Bloke, Everytime :-)
[12:35] <ppisati> ogra_: infinity: apw: that's the raspi2 firmware from my ppa, i think it was never used to build a snappy | ubuntu img before
[12:36] <ogra_> ppisati, yes, i falsely assimed it had firmware in it ... not bootloaders ...
[12:36] <ogra_> i uploaded a new livecd-rootfs to archive and PPA and will do another testbuild
[12:36]  * ogra_ hopes these kernels will at least still boot on snappy
[12:36] <flexiondotorg> http://www.omgubuntu.co.uk/2016/04/ubuntu-16-04-download-new-features
[12:37]  * ogra_ wishes creating a snappy image wouldnt be a multi hour process with all the manual snap uploads ... then downloading them again from the store ... yadda yadda .... 
[12:38] <infinity> rbasak: You can change the preferences.  I'm not sure that telling people how to reduce their security is a thing that belongs in release notes, though.
[12:38] <ogra_> ppisati, so if thats only bootloader stuff, wghere do i actually find the driver related firmware files for the raspberries ?
[12:39] <flexiondotorg> infinity, How goes the sync? ETA?
[12:39] <ppisati> ogra_: which one?
[12:40] <infinity> flexiondotorg: It's in progress.  ETA is in the next hour or so.
[12:40] <ogra_> ppisati, wlan for pi3 ... videocore stuff for both ?
[12:40] <ppisati> ogra_: i think we never packaged those
[12:40] <infinity> pitti: Are you mangling overrides?
[12:40] <ogra_> hmm, k
[12:40] <flexiondotorg> infinity, ty
[12:40] <infinity> pitti: If not, I'll take a lock on it, so we don't stomp on each other.
[12:40] <ppisati> ogra_: the wifi driver for thr pi3
[12:40] <ppisati> let me think
[12:40] <pitti> infinity: not ATM, I was waiting for c-m to update, which apparently happened now
[12:40] <pitti> infinity: ack
[12:40] <ogra_> ppisati, i remember we dug up the firmware file together
[12:41] <ogra_> some weeks ago
[12:41] <ogra_> ppisati, brcmfmac43430-sdio.txt and brcmfmac43430-sdio.bin iirc
[12:44] <flexiondotorg> ogra_, Those firmware we updated recently.
[12:44] <ogra_> flexiondotorg, in the archive ? (if so, in which package)
[12:45] <flexiondotorg> ogra_, From the Raspberry Pi Foundation.
[12:45] <flexiondotorg> ogra_, https://git.launchpad.net/ubuntu-pi-flavour-maker/tree/firmware
[12:45] <flexiondotorg> I'm an "insider"
[12:45] <flexiondotorg> Make the wifi much more reliable.
[12:45] <ogra_> flexiondotorg, right, i'm talking about the archive ... the snappy images need to use everything form the archive now
[12:45] <flexiondotorg> ogra_, OK.
[12:46] <infinity> ogra_: We can SRU firmware fixes post-release, we'll sort this out.
[12:46] <flexiondotorg> When the 16.04 release madness is behind us. I'd like to catch up with you on the Pi stuff.
[12:47] <ogra_> infinity, yeah, i'm more scared that something doesnt boot now since these kernel packages didnt see any testing in the snappy world before ...
[12:47] <ogra_> the build should at least besorted though :)
[12:47] <ogra_> (one would hope :P )
[12:54] <infinity> ogra_: changelog formatting is hard?
[12:55] <ogra_> hmm ?
[12:55] <infinity> +  * drop linux-firmware-raspi2, it does not actually contain driver
[12:55] <infinity> +  firmware but bootloaders (and fails to install if its target dir
[12:55] <infinity> +  is missing).
[12:56] <ogra_> whats wrnmg with that ?
[12:56] <infinity> "firmware" and "is" should be aligned with "drop"?
[12:56] <ogra_> oh
[12:58]  * ogra_ wonders why thats not automatic for him ... i only used dch ...
[13:02] <ogra_> infinity, reject then, i have a new upload ready
[13:08] <infinity> ogra_: Alright, after this, all new livecd-rootfs are SRUs.
[13:08] <ogra_> ok
[13:11] <infinity> slangasek: ^-- Committed the packageset changes, if anyone has any comments on things needing to be changed, we can do it post-release.
[13:12] <de-facto> hmm what does this mean?
[13:13] <ogra_> how big is main now ? are we down to three digits ?
[13:13] <infinity> It's still pretty big.
[13:14] <infinity> -rw-r--r-- 1 lp_publish lp_publish 1410686 Oct 22 12:48 wily/main/source/Sources.gz
[13:14] <ogra_> heh ... 7me likes how s390x and ppc64el take less than 10mins for snappy images
[13:14] <infinity> -rw-r--r-- 1 lp_publish lp_publish 1102679 Apr 21 13:12 xenial/main/source/Sources.gz
[13:15] <ogra_> hmm, still a bit
[13:15] <ogra_> i thought it would be more significant though
[13:42] <cyphermox> good morning
[13:43] <g4z> good afternoon
[13:46] <tjaalton> editing release notes to mention the llvm issue on skylake
[13:56]  * flexiondotorg sat in the back of the car. infinity are we nearly there yet?
[13:57]  * ogra_ hands flexiondotorg an icecream cone
[13:57]  * flexiondotorg rubs icecream into the upholstery out of boredom ;-)
[13:57] <ogra_> !
[13:57] <ogra_> infinity, hurry up ... he is making a mess !
[13:59] <tjaalton> Laney: I've reuploaded llvm to include the previous changelog entry in .changes
[14:01] <Laney> tjaalton: thanks
[14:01] <Laney> I saw that
[14:02] <Laney> pitti: ^^^ maybe if you're free you could review that for a 0-ish-day?
[14:02] <nearffxx> wtf guys
[14:02] <nearffxx> when it will be released?
[14:02] <teward> nearffxx: not helping
[14:02] <ogra_> sigh ... having to download something from cdimage on release day is like punishment :P
[14:02] <teward> nearffxx: it will be released when it's ready to be released - you need patience
[14:02] <g4z> lol... very helpful nearffxx :D
[14:03] <cjwatson> (I'll make this channel moderated for the time being if need be; if you don't want that then please don't hassle us)
[14:03] <pitti> Laney, tjaalton: is that actually an useful SRU? it sounds like something that should be stashed into git for the next real SRU?
[14:04] <tjaalton> pitti: yes it's useful, read the entry on https://wiki.ubuntu.com/XenialXerus/ReleaseNotes :)
[14:04] <pitti> it sounds like an update people would get for zero effect and nonzero risk
[14:04] <tjaalton> https://wiki.ubuntu.com/XenialXerus/ReleaseNotes#A6th_gen_Intel_Core_CPU.27s_and_llvmpipe_software_rasterizer
[14:05] <tjaalton> allows installing certain type of systems and then not fall over when logging in the first time
[14:05] <nearffxx> what's the status of the building machine?
[14:06] <rbasak> tjaalton: does that mean live mode won't work? Do we need to note that?
[14:06] <pitti> tjaalton: ah, understood; was confused because the changelog doesn't refer to anything, but I missed the version already in -proposed
[14:06] <tjaalton> rbasak: right, I'll add that
[14:06] <rbasak> Thanks :)
[14:07] <tjaalton> rbasak: also, the apache merge fail earlier; it was due to me just copying debian/ from the then-current package on top of git, so a file removal didn't show, duh..
[14:08] <rbasak> tjaalton: np, it's sorted now. And handily with this being an LTS we can drop the conffile removal in the first upload of the new cycle.
[14:15]  * flexiondotorg starts poking soggy wafer into the CD player ;-)
[14:16] <jderose> infinity: slangasek: tjaalton: so i was going to wait for the new llvm-toolchain-3.8 package to at least hit proposed before i added instructions on working around the problem to the release notes, but now i'm thinking i should just add the instructions now even though i can't yet test it in real life. what do ya'll think?
[14:16] <tjaalton> jderose: I'm writing them now, you can edit the grammar etc to your liking once I'm donw :)
[14:16] <tjaalton> *done
[14:16] <jdstrand> fyi, click-reviewers-tools uploaded (it is in universe). it is fine for release or as 0-day
[14:17] <jderose> tjaalton: ah, thanks! you beat me to it :)
[14:17] <jderose> tjaalton: but seems that builds haven't started yet for 2ubuntu3? https://launchpad.net/ubuntu/+source/llvm-toolchain-3.8
[14:17] <willcooke> tjaalton, are you still editing the release notes?
[14:18] <willcooke> I can wait, just askin'
[14:18] <willcooke> oh, just read the backlog - looks like yes you are
[14:18] <teward> jderose: it looks to me like they're running now?  https://launchpad.net/ubuntu/+source/llvm-toolchain-3.8/1:3.8-2ubuntu3
[14:19] <jderose> teward: ah, yup, i didn't notice the "latest uploads" link
[14:26] <tjaalton> willcooke: done now
[14:26] <tjaalton> jderose: it got rejected once, will take some time
[14:27] <flocculant> willcooke: if you're going to edit could you add https://xubuntu.org/news/xubuntu-16-04-release to the Official Flavours for me - pretty please :)
[14:32] <xnox> flocculant, willcooke - ok
[14:33] <xnox> flocculant, willcooke - done
[14:33] <flocculant> thanks xnox :)
[14:35] <flexiondotorg> willcooke, xnox Please can you add https://ubuntu-mate.org/blog/ubuntu-mate-xenial-final-release/ to the Official Flavours for me - pretty please :)
[14:35] <flocculant> pffft - copycat there :p
[14:35] <knome> flocculant, but our URL is shorter ;)
[14:36] <flexiondotorg> flocculant, :-)
[14:36] <flocculant> :)
[14:36] <flexiondotorg> knome, But mine is longer ;)
[14:36] <knome> TMI
[14:39] <ogra_>  ..... 44,1KB/s  ETA 18m 21s
[14:39] <ogra_> *sniff*
[14:39] <ogra_> (downloading kernel snaps from cdimage to push them to the store)
[14:40] <yofel> willcooke, xnox: on that topic: please also add https://kubuntu.org/news/￼kubuntu-16-04-lts-release-anouncement/ please :)
[14:40] <flocculant> ogra_: nice ... at least it's KB/s one day last week for some reason I was pushed to get more than B/s ...
[14:40] <ogra_> ppisati, FYI, dragon and pi2 kernels are good on snappy
[14:40] <ogra_> flocculant, wow, thats bitter
[14:41] <xnox> yofel, there is utf-8 things in your url for me.
[14:41] <xnox> yofel, can you paste it again?
[14:41] <ogra_> i usually get a few M, but it is release day :)
[14:41] <flocculant> :)
[14:41] <yofel> meh
[14:42] <yofel> xnox: https://kubuntu.org/news/kubuntu-16-04-lts-release-anouncement
[14:44] <Laney> →←
[14:45] <Phuket> whats the diff between this channel and ubuntu-release-party
[14:45] <Phuket> fewer beverages?
[14:45] <ppisati> ogra_: \o/
[14:45] <balloons> if you have to ask, you belong in ubuntu-release-party
[14:45] <balloons> :-)
[14:45] <Phuket> well they said join this one so i had to ask.
[14:45] <leftyfb> they shouldn't have said that
[14:57] <hggdh> Phuket: who is "they"?
[14:58] <teward> hggdh: i'll fill you in off channel
[14:58] <hggdh> k
[15:00] <pitti> ah, that "ubuntu-distro-info: Distribution data outdated." time again
[15:00] <infinity> Yeah, I've already told mine that Xenial releases a week from now. :P
[15:03] <Mez> infinity: your what ? (I just joined and irclogs isn't up to date yet!)
[15:05] <xnox> apw, https://launchpadlibrarian.net/254865980/buildlog_ubuntu-xenial-ppc64el.p7zip_9.20.1~dfsg.1-5_BUILDING.txt.gz
[15:09] <pitti> davmor2, infinity: a bit sad to realize that the ubiquity wifi bug can be fixed with literally flipping one bit..
[15:10] <davmor2> pitti: possibly not mine bug though right unless you and cyphermox had a conversation I knew nothing about :)
[15:11] <cyphermox> nah, just the panels stuff
[15:11] <davmor2> pitti: see I find the interesting bugs ;)
[15:12] <cyphermox> davmor2 means bug 1572956
[15:12] <ubot5`> bug 1572956 in network-manager (Ubuntu) "Oem install end user has no wifi" [Undecided,New] https://launchpad.net/bugs/1572956
[15:12] <pitti> yeah, I know
[15:12] <cyphermox> (which I'm working on now)
[15:12] <pitti> this wasn't really meant to start a serious conversation
[15:12] <cyphermox> ok
[15:22] <cjwatson> Getting images onto the CDN is taking somewhat longer than expected, but we're getting there.
[15:28] <doko> is the release notes page now frozen?
[15:29] <rbasak> Not for me.
[15:29] <rbasak> I did have issues with it appearing immutable a few times over the last day or two though.
[15:30] <doko> ahh, works on reload
[15:30] <cjwatson> moin behaves a bit dodgily sometimes
[15:30]  * nacc noticed issues primarily with the login service -- it would show me as not logged in at first, but on refresh it would show me was logged in
[15:30] <rbasak> Sometimes I "log in" and it immediately things I'm not.
[15:30] <rbasak> nacc: snap :)
[15:31] <nacc> rbasak: :)
[15:31] <rbasak> Also, thinks. My fingers seem to prefer thing.
[15:33] <doko> barry, renamed the Python section from Python 3.5 to Python 3. do we know of more images without Python2 installed?
[15:47] <barry> doko: yes, it should be off of cloud and touch, but it's not actually off of desktop because of samba :(
[15:48] <doko> ouch, so we didn't change that ...
[15:48] <barry> doko: desktop team overruled me
[15:48] <doko> no comment
[15:49] <doko> and server has openstack and 2 ... ok, so I'll change that to cloud and touch
[15:49] <barry> doko: i thought we did remove it from server
[15:49] <barry> i guess it came back :(
[15:50] <doko> smoser, is python2 on the server images?
[15:51] <smoser> doko, no. http://paste.ubuntu.com/15967494/
[15:52] <barry> sweet
[15:53] <doko> ok, re-adding
[15:56]  * willcooke has a UOS session planned for SMB Py2 etc etc 
[16:13] <infinity> wxl: So... I see no ppc testing for you guys.  Did you not want to release those?
[16:15] <Laney> wxl: please to mark as ready?
[16:15] <Laney> and, no ppc testing?
[16:19] <teward> flexiondotorg: you pinged?
[16:19] <teward> (elsewhere)
[16:19] <flexiondotorg> teward, Laney and infinity are asking about PPC and marking images ready.
[16:19] <teward> AFAIK that's wxl's territory
[16:19] <teward> I've never touched the PPC stuff for any release
[16:20] <teward> or any variant therein
[16:20] <teward> sorry!
[16:20] <flexiondotorg> OK, just know you're active in Lubuntu.
[16:20] <Odd_Bloke> infinity: I assume we are go on cloud images?
[16:20] <infinity> Odd_Bloke: Go for it!
[16:20] <Odd_Bloke> *pushes buttons*
[16:20] <Odd_Bloke> *pulls levers*
[16:20] <Odd_Bloke> *looks busy*
[16:20] <Laney> you sysadmin you
[16:20] <teward> flexiondotorg: indeed, moreso because phillw and wxl poke me with alternate image thingies, and that issue on the 15.10 RPi images I discovered, but other than that, not as much with testing :P
[16:20]  * teward returns to lurk mode
[16:20] <phillw> ppc has been teted for lubuntu.. just still trying to get the tester to use the tracker!!!
[16:21] <phillw> *tested
[16:22] <Laney> phillw: Mmmkay, I'll mark it as ready then
[16:23] <knome> hooray
[16:23] <phillw> Laney: thanks
[16:24] <teward> yay, now I can bust my head against nginx from Debian >.<
[16:24] <infinity> @pilot out
[16:24] <infinity> DERP!
[16:24] <stgraber> infinity: enjoy the drinks! :)
[16:24] <olli|> hooray
[16:24] <olli|> congrats guys
[16:24] <teward> infinity: i think you need this... *hands infinity some drinks* ... and then sleep :)
[16:24] <teward> thanks to all thougH!
[16:24] <Odd_Bloke> infinity: \o/
[16:25]  * olli| wonders what his tap with the release-team is this cycle
[16:25] <Laney> EPARSE
[16:25] <Odd_Bloke> s/tap/tab/ ?
[16:27] <olli|> tab
[16:28] <olli|> this was in reference to "We accept payment in cash, check or beerta" and some ... discussions this week
[16:29] <davmor2> olli|: don't worry about the release-team tab, wait till you get QA's
[16:29] <pitti> congrats everyone!
[16:30] <jcastro> nice work everyone, congratulations!
[16:30]  * pitti goes to grab some ice cream for celebrations :)
[16:31] <flexiondotorg> infinity, Thank you for everything you've done for Ubuntu MATE!
[16:31] <flexiondotorg> popey, Thank you for everything you've done for Ubuntu MATE!
[16:31] <flexiondotorg> cjwatson, Thank you for everything you've done for Ubuntu MATE!
[16:31] <flexiondotorg> dholbach, Thank you for everything you've done for Ubuntu MATE!
[16:31] <flexiondotorg> didrocks, Thank you for everything you've done for Ubuntu MATE!
[16:31] <flexiondotorg> Laney, Thank you for everything you've done for Ubuntu MATE!
[16:31] <tgm4883> Who has access to the release notes wiki?
[16:32] <flexiondotorg> sil2100, Thank you for everything you've done for Ubuntu MATE!
[16:32] <flexiondotorg> Trevinho, Thank you for everything you've done for Ubuntu MATE!
[16:32] <flexiondotorg> pitti, Thank you for everything you've done for Ubuntu MATE!
[16:32] <flexiondotorg> cyphermox, Thank you for everything you've done for Ubuntu MATE!
[16:32] <popey> are you drunk?
[16:32] <popey> :)
[16:32] <flexiondotorg> mhall119, Thank you for everything you've done for Ubuntu MATE!
[16:32] <flexiondotorg> ogra_, Thank you for everything you've done for Ubuntu MATE!
[16:32] <flexiondotorg> seb128, Thank you for everything you've done for Ubuntu MATE!
[16:32] <flexiondotorg> bregma, Thank you for everything you've done for Ubuntu MATE!
[16:32] <cyphermox> flexiondotorg: you're not going to do through all the uploaders are you?
[16:32] <flexiondotorg> Mirv, Thank you for everything you've done for Ubuntu MATE!
[16:32] <barry> so, cjwatson, when does yakkity yak open?
[16:32] <flexiondotorg> willcooke, Thank you for everything you've done for Ubuntu MATE!
[16:32]  * rbasak hands flexiondotorg a compression algorithm :)
[16:33] <tgm4883> willcooke: xnox can one of you add http://www.mythbuntu.org/home/news/mythbuntu1604released to the release notes?
[16:33] <teward> lol rbasak
[16:33] <flexiondotorg> https://ubuntu-mate.org/blog/ubuntu-mate-xenial-final-release/
[16:33] <popey> heh
[16:33] <ogra_> flexiondotorg, dude ! thank *you* for doing it ... we're all just little gears in a machine you drive ;)
[16:34] <\9> rbasak: <flexiondotorg> \x1f\x8b\x08\x00\xfe\x00\x19W\x02\xff\xcbO/J\x8c\xd7Q\x08\xc9H\xcc\xcbV\xa8\xcc/UH\xcb/RH-K-\xaa,\xc9\xc8\xccK\x07\t\xa9\x97\xa5*\xa4\xe4\xe7\xa5\x82\xa5B\x93J\xf3JJ\x15|\x1dC\\\x15\x018\xb8b4<\x00\x00\x00
[16:34] <\9> :v
[16:34] <Mirv> flexiondotorg: you're welcome! :)
[16:34] <Mirv> flexiondotorg: +1 on ogra's comment :)
[16:34] <\9> also, congratulations everyone
[16:35] <cholcombe> \o/
[16:35] <cyphermox> \9, can we call you "tab"? ;)
[16:35] <\9> heh
[16:36] <Dataforce> Does http://changelogs.ubuntu.com/meta-release-lts update later then? :)
[16:36] <knome> some of us are little rocks on the gears you drive too
[16:36] <knome> :Ð
[16:36] <ogra_> haha
[16:37] <ogra_> Dataforce, lts only gets switched at the .1 release
[16:37] <Dataforce> ogra_: I see - what about http://changelogs.ubuntu.com/meta-release?
[16:37] <nearffxx_> https://kubuntu.org/news/%EF%BF%BCkubuntu-16-04-lts-release-anouncement/
[16:37] <Odd_Bloke> Unless you're looking at `distro-info --lts`, then xenial has been the LTS since midnight. :p
[16:43] <davmor2> popey: flexiondotorg is only tiddly he starts with IIIIIIi LLLLLLuvv you when he gets drunk
[16:44] <yofel> thanks to the release team and everyone else for all the work over the last half year :)
[16:45] <rbasak> yofel, sgclark: thank you for your patience and work with the MySQL switch. Sorry again that it landed so late.
[16:46] <rbasak> And jamespage too.
[16:46] <sgclark> np
[16:46] <jamespage> ;)
[16:46] <rbasak> I should have put out a call for testing when it landed in xenial-proposed really. It was sat there longer than we expected :-/
[16:51] <tgm4883> flexiondotorg: Do you have the raspberrypi-dev package on a PPA for 16.04 somewhere? I had been using yours for wily stuff, but I can't find a xenial version
[16:53] <phillw> tgm4883: there is an RC for both MATE and Lubuntu at http://phillw.net/isos/pi2/
[16:54] <tgm4883> phillw: actually, just found what I was looking for. raspberrypi-firmware
[16:54] <phillw> kk
[16:55] <tgm4883> I need it in my building PPA for some openmax support
[16:57] <wxl> ok ok i'm here
[16:58] <wxl> infinity: i think we're confident enough to release ppc at this point, at least if flexiondotorg is willing to release mate :). i'll mark it ready in one sec.
[16:58] <Trevinho> flexiondotorg: no worries, it was easy!you guys did the most. ☺️
[16:59] <Trevinho> Trevinho: thank you for the contributions
[17:00] <davmor2> Congratulations all
[17:01] <wxl> oh
[17:01] <wxl> heh
[17:01] <wxl> nevermind already done XD
[17:09] <bladernr> Hey, I just wanted to verfiy something... the 16.04 images on releases.ubuntu.com are dated yesterday.  Are those the official GA ISOs or are there newer spins coming to the web shortly?
[17:10] <bladernr> the torrent and zsync files are all dated today, but the ISOs themselves are dated 4/20
[17:16] <bladernr> ummm anyone?
[17:16] <bladernr> stgraber: infinity cjwatson ?
[17:17] <Odd_Bloke> bladernr: I suspect they are all in a pub by now. :)
[17:17] <bladernr> Odd_Bloke: yeah, probably :/ but I need the official GA bits for test work, so we're gated on that question. heh...
[17:17] <Odd_Bloke> bladernr: I don't have the answer for you, I'm afraid.
[17:18] <bladernr> Odd_Bloke: no worries
[17:18] <Odd_Bloke> slangasek: You, presumably, aren't drinking yet; do you have an answer?
[17:18] <slangasek> Odd_Bloke: not drinking yet? you wound me, sir
[17:18] <nacc> heh
[17:18] <slangasek> Odd_Bloke: I am deep in scrollback at the moment, one second
[17:21] <rcj> bladernr, if you use a torrent link and check the result against the SHA256SUMS[.gpg] then you should be fine
[17:21] <willcooke> tgm4883, done
[17:21] <rcj> just a guess
[17:24] <slangasek> cjwatson: sentinella> but if it's in sync and the current version will never work without a change, we can drop it and resync it later and keep -proposed nice and clean... :)
[17:24] <slangasek> Laney, pitti: so what did happen with the xorg-lts-transitional stuff?  I see there were changes made to the seeds and I saw emails about c-m flapping, but this was all clean yesterday when I was done with it
[17:26] <slangasek> infinity1: raspberrypi2-firmware was renamed to linux-firmware-raspi2? wat?  the contents weren't linux firmware...
[17:27] <Odd_Bloke> slangasek: Heh, you weren't kidding about being deep in scrollback.
[17:28] <slangasek> bladernr: so what's the concern with torrent/zsync files?  Just the timestamps on them?
[17:39] <slangasek> bladernr: right, the torrent files are only generated when the images are published.  The images are built before they're tested for release, and the testing takes a while.  timestamp differences are expected
[17:39] <slangasek> Odd_Bloke: hurray I survived
[17:39] <slangasek> infinity1, cjwatson, Laney, pitti, apw, xnox: congrats on the lovely release
[17:40] <LocutusOfBorg> <3
[17:41] <DiamondSword> http://releases.ubuntu.com/xenial/ << here the desktop is last modified date is 20th of April. it says 16.04 is out on the front page. should I download the iso which it is stable(?) or download the torrent file becasue its last modified date is 21st ?
[17:42] <LocutusOfBorg> [   ] ubuntu-16.04-desktop-amd64.metalink    21-Apr-2016 10:00   43K  Ubuntu 16.04 Final Beta (Xenial Xerus)
[17:42] <LocutusOfBorg> please s/Beta//
[17:42] <DiamondSword> beta? isn't this stable version?
[17:42] <slangasek> DiamondSword: I literally just answered that question.  The timestamps are the date the image was created, which happens *before* the testing, which is not instantaneous.  Timestamp differences are expected.
[17:43] <slangasek> LocutusOfBorg: where do you see that?
[17:43] <DiamondSword> slangasek, so the iso is fine you say?
[17:43] <slangasek> DiamondSword: yes.
[17:43] <DiamondSword> thank you for the 16.04 :)
[17:43] <DiamondSword> congratz!
[17:43] <DiamondSword> I like the "X"
[17:44] <LocutusOfBorg> http://releases.ubuntu.com/16.04/
[17:44] <LocutusOfBorg> slangasek, ^^^ :)
[17:44] <slangasek> LocutusOfBorg: thanks.  Fixed, dunno how long the mirror push will take
[17:44] <LocutusOfBorg> thanks
[17:46] <Laney> Hey slangasek
[17:46] <Laney> There were some c-m problems on britney
[17:46] <slangasek> Laney: ah, ok
[17:46] <Laney> and cjwatson said that the "!" stuff doesn't work and don't ever use it
[17:46] <slangasek> hah
[17:46] <Laney> so I expanded the problem out into the positive sense
[17:46] <Laney> and then good things were good
[17:46] <slangasek> except it totally did work for c-m
[17:46] <slangasek> and it was used in trusty
[17:46] <slangasek> it was only p-m that didn't like it :)
[17:46] <LocutusOfBorg> and now I start the question for libpng16 transition, do you have any ETA for the next archive opening? no asking about the auto import, but somewhen before it :)
[17:47] <Laney> Bottom line was that things were in main that shouldn't be in main
[17:47] <Laney> and now it is time for pub
[17:47] <Laney> tata
[17:48] <slangasek> Laney: enjoy :)
[17:50] <Laney> :)
[17:51] <slangasek> Laney: btw (async), do you know why juju-core didn't make it through unapproved automatically (and from there into release)? did the bot stop working?
[17:51] <cjwatson> bladernr: images are always dated a bit old, they have to be tested after they're built.
[17:51] <cjwatson> oh yeah, I see that above.
[17:52] <bladernr> cjwatson: ok, I just needed to verify that the 4/20 dated ones were GA and not just a case of "haven't synced yet"
[17:52] <bladernr> cjwatson: thanks
[17:52] <slangasek> bladernr: they don't get published to releases.ubuntu.com until they're golden
[17:53] <bladernr> slangasek: ack, just crossing the t's and dotting the lower-case j's
[17:53] <bladernr> thanks both of you
[17:54] <Kamilion> wow, people are really worried about an off-by-one date 'error'... That makes me happy (that people are paying attention)
[17:56] <Basstard`> It was actually meant to be released yesterday but.. 4/20 happened.
[17:58] <Kamilion> yeah, I know, I was here all day instead of Golden Gate Park.
[17:59] <DiamondSword> you should put a downloads counter on the main page, people are very excited about this release :)
[18:25] <tjaalton> are relnotes for "official" features only, or whatever someone with the community hat feels is worth mentioning?-)
[18:26] <tjaalton> and by official I mean supported
[18:26] <tjaalton> ..by C.
[18:30] <slangasek> tjaalton: if it's a feature present in the distro, and you think it's worth mentioning, then we should at least consider it for the release notes... doesn't have to be just features that Canonical thought to trumpet :)
[18:34] <tjaalton> slangasek: ok, well I'm pondering if freeipa 4.3.1 should be mentioned or if I'll just blog about it. supports replication too for the first time on debian/ubuntu
[18:36] <slangasek> tjaalton: ah, a vanity release note ;-)  I think freeipa is awesome and important to certain users, but it's in universe/unseeded and one update among many
[18:36] <slangasek> but a blog sounds perfect to me
[18:37] <tjaalton> yeah, and a ml post to freeipa-users@, that'll do
[18:38] <Pici> sorry to bug, but we're getting a lot of users saying that they're not being prompted to upgrade.  http://changelogs.ubuntu.com/meta-release looks like it doesn't advertize xenial.. is this just a mirror/cdn issue or??
[18:40] <slangasek> bdmurray: ^^ is that something you have control over?
[18:41] <Odd_Bloke> I thought we didn't prompt to upgrade until .1?
[18:41] <slangasek> Odd_Bloke: we don't prompt LTS users to upgrade until .1.  wily users should get the prompt
[18:41] <Odd_Bloke> Oh, right.
[18:41] <tgm4883> Odd_Bloke: I think we do for 15.10 -> 16.04
[18:41] <nacc> Odd_Bloke: that would be meta-release-lts
[18:42] <Odd_Bloke> That makes a lot of sense now I engage brain. ^_^
[18:42] <slangasek> Odd_Bloke, rcj, gaughen: I see the release notes call https://cloud-images.ubuntu.com/releases/16.04/release/ "Ubuntu Cloud Server".  Is that how you want them labelled?
[18:42] <slangasek> Garçon de nuages Ubuntu
[18:43] <Odd_Bloke> I would prefer "Best Ubuntu".
[18:43] <Odd_Bloke> "Ubuntu Cloud Server" does sound weird though.
[18:44] <Odd_Bloke> gaughen: Probably one for you/Udi: ^
[18:45] <slangasek> suggestions:
[18:45] <slangasek> Ubuntu Servers on Ice
[18:45] <slangasek> Ubuntu in the Sky With Diamonds
[18:46] <slangasek> Ubuntu Cloud, Purple Rain Commemorative Edition
[18:46] <gaughen> can't we just say Ubuntu Cloud?
[18:46] <Odd_Bloke> Do You Want To Build A(n Ubuntu) Server
[18:47] <gaughen> although I do like the commemorative edition
[18:47] <gaughen> thanks for that Odd_Bloke, now I have that frozen song stuck in my head AGAIN
[18:47] <Odd_Bloke> Ubuntu Cloud: This Time It's Cirrus
[18:47] <gaughen> sigh
[18:49] <rcj> We're clearly marketing wizards.  "Ubuntu cloud images"?  Seems to fit nicely with cloud-images.ubuntu.com.
[18:50] <pitti> clearly the hardest part of the release :)
[18:52] <rcj> pitti, oh we're still releasing cloud images
[18:52] <balloons> naming is everything
[18:54] <Kamilion> now if we could only get some licensing wizards to tell me how many trademarks I'm supposed to be removing
[19:01] <Pici> Can anyone besides bdmurray take a look at the meta-release thing?
[19:20] <bdmurray> Pici: I'll do it shortly
[19:21] <Pici> bdmurray: thanks :)
[19:21] <slangasek> gaughen: yes, we can certainly say that.  Done!
[19:21] <slangasek> gaughen: 'Ubuntu Cloudy with a chance of eatballs'
[19:21] <slangasek> Meatballs
[19:21] <slangasek> that was the final answer, right?
[19:28]  * balloons sings 'sunshine, lollipops and rainbows, everything that's wonderful is sure to come your way . . .' ♪ ♪
[19:29] <bdmurray> Pici: should be set, feel free to double check
[19:29] <Pici> bdmurray: already got confirmation from impatient users in #ubuntu  thanks again :)
[20:56] <daniele_> Hi guys, yesterday I just installed the daily build of ubuntu, and now I typed "apt-get upgrade" it only installed tzdata
[20:56] <daniele_> I'm on the final version now?
[20:56] <daniele_> is there any difference?
[20:57] <Kamilion> I only got some cups-filters and an upgrade to nginx-common & nginx-extras
[20:57] <Kamilion> oh, yeah, I got the tzdata update as well, almost missed that
[20:57] <daniele_> Kamilion: thanks
[20:58] <pmatulis> when does cloud-images.u.c get updated?
[20:58] <Kamilion> daniele_: I don't see anything else really, http://puu.sh/oqVGc/569d0a7af6.jpg
[20:59] <Kamilion> daniele_: don't forget to apt autoremove to clean up any old kernels, but I had this installed for a while, if yours was from yesterday you probably don't have any old ones to remove :)
[21:00] <Kamilion> pmatulis: there was some traffic here about an hour ago of people talking about pushing the cloud images
[21:00] <Kamilion> pmatulis: I assume they take some amount of time to publish and sync
[21:09] <pmatulis> Kamilion: k
[21:10] <Laney> slangasek: At a guess, it was after the script was turned off (which was about the same time we put a $world block on)
[21:11] <slangasek> Laney: k
[21:41] <slangasek> pitti: fyi, bug #1573240 reported already against the initscripts SRU.  I did test a wily->xenial upgrade with the new initscripts enabled, so I don't know why that didn't pick this up if it's really a breaks/pre-deps loop
[21:41] <ubot5`> bug 1573240 in sysvinit (Ubuntu) "package initscripts 2.88dsf-59.2ubuntu2.1 failed to install/upgrade: pre-dependency problem - not installing initscripts" [Critical,New] https://launchpad.net/bugs/1573240
[23:06] <infinity1> slangasek: The bot was disabled and the britney hint changed to "block all" to prevent anything happening as we neared final release.
[23:06] <infinity1> slangasek: That said, despite release announcements, we've still not closed the archive, nor have we opened a new one, so if there's a valid argument for juju-core squeezing in, go for it.
[23:07] <slangasek> infinity1: right; that seemed to happen somewhat early, the juju-core upload was yesterday?
[23:07] <infinity1> slangasek: Eh?  I see one 4 hours ago.
[23:07] <infinity1> slangasek: Or was there one well before that?
[23:07] <slangasek> infinity1: that's the /reupload/ after Laney rejected my earlier one that got stuck yesterday without me noticing
[23:07] <slangasek> the reupload for SRU, with bug ref
[23:08] <slangasek> anyway, I'm not going to try to sneak it into the release pocket today, it can go via SRU
[23:08] <slangasek> the difference between beta4 and beta5 being in the release pocket is negligible, neither is 2.0final
[23:08] <Laney> Ah, an earlier one, sorry
[23:09] <Laney> Then if it wasn't held because of seeding, it'll have been because it's in a packageset
[23:09] <infinity1> slangasek: Neither is final, though the control file changes seem important?  Or was juju2 not a thing long enough for it to matter?
[23:10] <slangasek> infinity1: it was only in a ppa
[23:10] <slangasek> Laney: packageset> that seems buggy behavior by the bot, then?
[23:11] <slangasek> anyway here's what queuebot actually said
[23:11] <slangasek> Unapproved: juju-core (xenial-proposed/main) [2.0~beta4-0ubuntu2 => 2.0~beta5-0ubuntu1] (ubuntu-server)
[23:11] <slangasek> so yeah, it is seeded, duh - just not on images
[23:11] <slangasek> my mistake
[23:12] <infinity1> slangasek: That upload has added git vomit too.  Yay.
[23:12] <infinity1> I really wish -i -I were default for dpkg-buildpackage.
[23:12] <slangasek> infinity1: it's in the upstream tarball so wouldn't change anything
[23:12] <infinity1> Oh.
[23:12] <infinity1> Gross.
[23:12] <slangasek> ;)
[23:13] <Laney> make distcheck, people
[23:14] <Laney> slangasek: I think that *is* "(packagesets)" FWIW
[23:15] <slangasek> hohum
[23:15] <Laney> It's intentional, haven't thought about whether it's correct though
[23:15] <infinity> It's intentional and correct.
[23:16] <infinity> Packages in packagesets shouldn't sail through during a freeze period without review.
[23:16] <Laney> I suppose the idea is that somebody actively cares about this thing and so it should be up for extra scrutiny
[23:16] <infinity> (There is a whitelist for some that have been granted sailing privileges, like some touch stuff)
[23:16] <slangasek> packageset just means it's been marked as having a particular uploader acl; it doesn't mean it's part of an image
[23:16] <slangasek> or product, or whatever
[23:17] <infinity> No, true.  It should probably actually match more closely what LP uses for supported fields.
[23:18] <infinity> Which juju-core wouldn't be caught in because it's in universe.
[23:18] <infinity> Though it shouldn't be.
[23:18] <infinity> Cause this whole "we support it but the uploaders don't want to admit to it" thing is silly.
[23:19] <infinity> I'll twiddle it to match in that direction next time.  I thikn that makes more sense.
[23:19] <infinity> Since "supported" implies "we need to review that your upload is sane because we're agreeing to fix it after release if it's not".
[23:20] <infinity> slangasek: Sound reasonable to you?
[23:20] <slangasek> infinity: nah, juju-core (source) is in main, so it's right in this case that it /was/ caught, via seeds if not packagesets
[23:21] <infinity> (That said, projects like juju should stop skipping the queue and get in server supported)
[23:21] <infinity> Oh, I'm looking at "juju-core".
[23:21] <infinity> The binary.
[23:21] <slangasek> the overlooked non-autoapproval was my fault and nothing to do with the bot config.  But I do agree with your proposed bot change
[23:22] <infinity> So, yes.   juju-2.0 is 5y supported, so absolutely should be stopped.
[23:22] <infinity> Bot change on the todo anyway, I agree that random packageset created for a universe PPU is none of my business to stop uploads for.
[23:25] <infinity> So, we've had a few clean publisher runs in a row.
[23:25] <infinity> If that juju's an SRU, I'm closing xenial.
[23:26] <infinity> And there it goes.
[23:28] <slangasek> \o/
[23:49] <doko> is there an expected release date for 16.04.1?
[23:49] <doko> slangasek, infinity: ^^^
[23:54] <slangasek> doko: estimated 3 months after .0, so "late July" (as I was corrected yesterday)
[23:54] <slangasek> I don't know if infinity has put a target date on a calendar yet?
[23:56] <doko> ta