[00:04] <tsimonq2> 0-day SRU-eligible menu-cache is coming in.
[00:04] -queuebot:#ubuntu-release- Unapproved: menu-cache (artful-proposed/universe) [1.0.2-3 => 1.0.2-3ubuntu0.17.10.1] (no packageset)
[01:04] <tsimonq2> Aaand that should be the last 0-day SRU for now...
[01:05] -queuebot:#ubuntu-release- Unapproved: ktexteditor (artful-proposed/universe) [5.38.0-0ubuntu1 => 5.38.0-0ubuntu1.1] (kubuntu)
[01:22] -queuebot:#ubuntu-release- Unapproved: cloud-init (xenial-proposed/main) [17.1-18-gd4f70470-0ubuntu1~16.04.1 => 17.1-18-gd4f70470-0ubuntu1~16.04.2] (edubuntu, ubuntu-cloud, ubuntu-server)
[01:23] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop amd64 [Artful Final] has been marked as ready
[01:26] -queuebot:#ubuntu-release- Unapproved: cloud-init (zesty-proposed/main) [17.1-18-gd4f70470-0ubuntu1~17.04.1 => 17.1-18-gd4f70470-0ubuntu1~17.04.2] (edubuntu, ubuntu-cloud, ubuntu-server)
[02:36] -queuebot:#ubuntu-release- Unapproved: xdg-utils (artful-proposed/main) [1.1.1-1ubuntu2 => 1.1.1-1ubuntu3] (kubuntu, ubuntu-desktop)
[02:44] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop i386 [Artful Final] has been marked as ready
[03:14] -queuebot:#ubuntu-release- Builds: Lubuntu Alternate amd64 [Artful Final] has been marked as ready
[03:39] -queuebot:#ubuntu-release- Builds: Lubuntu Alternate i386 [Artful Final] has been marked as ready
[05:05] <valorie> hi folks, I've notice that upgrade test cases are now offered on the iso.qa site which is cool
[05:06] <valorie> however, LTS upgrades should not be there until BB, correct?
[05:06] <valorie> I don't see any way to disable that for Kubuntu
[05:20] <infinity> valorie: Just ignore the LTS upgrade test case, IMO.
[05:21] <infinity> valorie: I mean, it's not invalid to run it (as it'll give an indication of what will go wrong with 16.04 -> 18.04), but indeed, doesn't point to anything that needs fixing for 17.10
[05:21] <valorie> ok
[05:23] <slangasek> upgrade from 16.04 -> 17.10 matters because 17.04 goes EOL 3 months from now
[05:24] <slangasek> of course, any bugs found can be SRUed and are thus not release-critical
[05:24] <valorie> true that
[05:24] <infinity> Oh er, yes, also that.
[05:33] <valorie> ya talked me into it
[05:33] <valorie> I needed to burn a 16.04.3 iso USB anyway
[05:34] <acheronuk> hmmm. did not realise update manager could be persuaded to do a LTS -> dev version of a few releases higher
[05:36] <slangasek> it can, but bdmurray was doing some work on it this cycle, so let me check if the test cases document the actual procedure
[05:37] <slangasek> that appears to be bdmurray's current text, yes
[05:39] <acheronuk> will do-release-upgrade do the same I wonder?
[05:39] <slangasek> given the same options, yes
[05:39] <acheronuk> we don't have update-manager by default
[05:40] <acheronuk> ok
[05:40] <slangasek> oh? how are kubuntu upgrades done nowadays?
[05:43] <acheronuk> discover used to offer them, but that function got ripped out by upstream without anyone mentioning the fact, so at the moment it's a work-around with do-release-upgrade
[05:44] <acheronuk> discover in Xenial still works ok to trigger upgrades
[05:44] <acheronuk> we need to sort something for future updates though
[05:45] <acheronuk> lubuntu going to Qt means they will want a Qt based upgrade path, so going to try to collaborate with the and maybe budgie to get a solution we can share
[05:46] <infinity> A Qt port of update-manager should be "trivial".  And would be nice to share a common codebase for all but the presentation layer.
[05:47] <slangasek> I thought there was one previously... isn't that why there's a package called 'update-manager-kde'?
[05:48] <infinity> Oh, indeed.  That one might have been slightly more kde-specific and less Qt-generic, but shouldn't be hard to clean it up.
[05:48] <infinity> Yeah, it uses python3-pykde4, not pyqt.
[05:50] <acheronuk> indeed. I think discover package manager being able to do it made that stuff get neglected, putting us in a slight spot now
[05:51] <valorie> acheronuk: perhaps we could fix that for now, and then talk to Aleix about integrating it back into Discover
[05:51] <infinity> OTOH, I'm not keen on two things spinning their wheels looking for updates (discover and u-m for you, gnome-software and u-m for us), but I feel like update-notifier/update-manager really fill the niche better, and we should just collectively agree to turn off all automated checking stuff in the heavier package managers.
[05:51] <valorie> although since it's now cross-platform, dunno
[05:52] <acheronuk> valorie: well, as far as I can see, most of the original code discover used for release upgrade triggering is still in Muon. so might be easier to fix it up in that
[05:52] <acheronuk> or both
[05:53] <valorie> cool
[05:53] <valorie> whatever works
[05:54] <valorie> Discover has features that Muon will never have, like the KDE store
[05:54] <valorie> but I still prefer package managers over software stores
[05:54] <valorie> 16.04.3 proceeds apace
[05:55] <infinity> I really like the clean "this is just for upgrades, here's what I'm doing, here's the changelogs" no fuss presentation of update-manager.
[05:55] <infinity> It's about as close as a GUI can get to 'apt-get dist-upgrade'.
[05:56] <infinity> Most heavier package managers and *shudder* stores seem to make the whole daily/weekly update experience feel clunky and opaque.
[05:56] <valorie> indeed
[05:56] <valorie> more unixy
[05:56] <acheronuk> infinity: indeed
[05:57] <valorie> glad to hear I'm not the only stores-hater
[05:57] <acheronuk> apart from testing, I can't recall the last time I did updates with a package manager/store
[05:57] <valorie> same here
[05:57] <valorie> up-arrow is easier and faster
[05:58] <acheronuk> :) Xenial offers me a UK keyboard by default ;)
[05:58] <valorie> my gosh, already installed
[05:58] <infinity> Yeah, cyphermox found that bug.
[05:58] <infinity> We'll fix it for 18.04.
[05:59] <infinity> On the other hand, who wants an icky UK keyboard? :)
[06:00] <infinity> I'll eat my words the day I find a need for a ¬ key.
[06:01] <acheronuk> history has handed us some weird differences we now have to cope with
[06:01] <infinity> It's a shame that latinish countries couldn't settle on One True Layout 20 or 30 years ago.
[06:02] <infinity> Heck, even Japan uses us101 (with very different keycaps and deadkeys galore, but still a us101 layout), but noooo, not Europe. ;)
[06:02] <infinity> (*cough*azerty*cough*qwertz*cough*)
[06:04] <infinity> I guess that's us104 now.  I'm showing my age.
[06:04] <infinity> I still refuse to admit the three new keys exist.
[06:04] <acheronuk> lol
[06:05] <acheronuk> what time are we looking at a release? late afternoon UK time?
[06:05] <infinity> Mid-afternoon seems likely.
[06:05] <valorie> updating is soooo much slower than a new install
[06:06] <infinity> I need to clean up a bit of code, wait for some mirror love, dot some Ts and cross dome Is, but it's mostly just a waiting game.
[06:06] <infinity> s/dome/some/
[06:06] <acheronuk> ok. understood
[06:26] <LocutusOfBorg> folks, quick question
[06:26] <LocutusOfBorg> I fixed sambamba with an ldc fix
[06:26] <LocutusOfBorg> am I in time?
[06:27] <LocutusOfBorg> ldc is ready to upload, checked that didn't break ABI and tilix still works
[06:27] <LocutusOfBorg> https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+sourcepub/8363180/+listing-archive-extra
[06:27] <LocutusOfBorg> here the patch
[06:27] <infinity> LocutusOfBorg: ldc is on the budgie ISOs, so nope, no can do.  But we can 0-day SRU it.
[06:27] <LocutusOfBorg> I mean here ->> https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+sourcepub/8371725/+listing-archive-extra
[06:28] <LocutusOfBorg> infinity, the problem is that sambamba won't reach release then
[06:28] <LocutusOfBorg> you will move it to artful+1, right?
[06:28] <infinity> LocutusOfBorg: sambamba hasn't been in any release yet, I'm not fussed about it not making artful.
[06:29] <infinity> LocutusOfBorg: So, yeah, if this is really only affecting sambamba, best to just hold off and fix it all in BB.
[06:29] <LocutusOfBorg> me neither, I'm just pointing out a fix that few hours ago has been developed by upstream
[06:29] <acheronuk> Checking for a new Ubuntu release
[06:29] <acheronuk> Upgrades to the development release are only
[06:29] <acheronuk> available from the latest supported release.
[06:29] <infinity> LocutusOfBorg: Right.  And yay.  But "too late". :)
[06:29] <acheronuk> in Xenial
[06:29] <LocutusOfBorg> please have a look, it fixes some assertions, not sure how much they might be bad
[06:30] <infinity> acheronuk: Yeah, the "test LTS upgrades before a new LTS exists" path might be one of the ones that needs meta-release to be mocked locally.  Worth asking bdmurray for his current understanding of that, as we had a dozen conversations about it, and my brain is mush.
[06:30] <LocutusOfBorg> but no problem, better keep safe
[06:30] <LocutusOfBorg> thanks!
[06:30] <infinity> acheronuk: And, of course, "that case needs to be mocked" is a different copout that we should perhaps write a wrapper tool or a new d-r-u option to do for you.  Dunno.
[06:30] <acheronuk> infinity: this is what I thought, but gave it a try anyway
[06:31] <infinity> LocutusOfBorg: it's not so much about keeping safe as it is image/archive consistency.  If I let a new ldc in, I'd have to respin budgie and force them to revalidate their ISOs 6 hours before release. :)
[06:32] <acheronuk> I'll go back to testing ISOs, and come back to that later if I have time
[06:32] <LocutusOfBorg> infinity, I perfectly understand that
[06:32] <LocutusOfBorg> this is why I uploaded in my ppa and not in the archive
[06:32] <LocutusOfBorg> better keep it for 18.04
[06:32]  * infinity nods.
[06:32] <infinity> At least it's nice to know there's a fix coming.
[06:32]  * LocutusOfBorg in the meanwhile debian will upload the patch too
[06:48] <flocculant> infinity: a bit random - but do you know what timezones bdmurray and Michael Hudson-Doyle (and this one's irc nick) are please :)
[06:49] <infinity> flocculant: Pacific US for bdmurray, NZ for mwhudson.
[06:49] <flocculant> infinity: thanks - I'll try and catch them then :)
[06:53] <flocculant> oh easy - both idling in -quality
[06:54] <acheronuk> infinity: so presumably I would need do a small amount of hackery on update manager's check script to read a locally modified http://changelogs.ubuntu.com/meta-release-lts
[06:54] <acheronuk> giving artful as a valid next LTS
[06:56] <infinity> acheronuk: Basically, yeah.
[06:57] <infinity> acheronuk: Or meta-release-lts-development for -d
[06:58] <acheronuk> ok. can try that later if I have time
[06:58] <Asus-LUB> How many hours left? (The countdown?) :D
[06:59] <infinity> Asus-LUB: More than 2, less than 12.
[07:00] -queuebot:#ubuntu-release- Unapproved: percona-xtradb-cluster-5.6 (artful-proposed/universe) [5.6.34-26.19-0ubuntu3 => 5.6.34-26.19-0ubuntu4] (no packageset)
[07:00] -queuebot:#ubuntu-release- Unapproved: accepted percona-xtradb-cluster-5.6 [source] (artful-proposed) [5.6.34-26.19-0ubuntu4]
[07:01] <sil2100> jibel: hey! You working on the remaining desktop iso-testing?
[07:02] <jibel> sil2100, yes I am
[07:02] <jibel> should be done by noon
[07:02] <jibel> (my time)
[07:02] <jibel> ~3h
[07:02] <sil2100> \o/
[07:03] <sil2100> It's hiiigh noon
[07:06] <flocculant> sil2100: please use wet trout instead of guns :p
[07:06] -queuebot:#ubuntu-release- Builds: Netboot amd64 [Artful Final] has been marked as ready
[07:09] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop amd64 [Artful Final] has been marked as ready
[07:09] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop i386 [Artful Final] has been marked as ready
[07:11] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Artful Final] has been marked as ready
[07:11] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop i386 [Artful Final] has been marked as ready
[07:49] -queuebot:#ubuntu-release- Unapproved: dmucs (artful-proposed/universe) [0.6.1-2.1 => 0.6.1-3] (no packageset) (sync)
[07:50] -queuebot:#ubuntu-release- Unapproved: accepted dmucs [sync] (artful-proposed) [0.6.1-3]
[07:54] -queuebot:#ubuntu-release- Unapproved: doxia-sitetools (artful-proposed/universe) [1.7.4-2 => 1.7.5-1] (no packageset) (sync)
[07:54] -queuebot:#ubuntu-release- Unapproved: accepted doxia-sitetools [sync] (artful-proposed) [1.7.5-1]
[08:29] <jibel> sil2100, I think Ubuntu Desktop is fine. I'm reviewing the bugs and the release notes for desktop
[08:40] <sil2100> jibel: thanks!
[08:40] <sil2100> infinity: ^
[08:46] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Artful Final] has been marked as ready
[08:46] <Laney> wee
[08:48] <infinity> Laney: I feel like needs an 'h' in it, or it means something entirely different in en_GB
[08:48] <infinity> And I'm not enjoying the mental image.
[08:50] <Laney> Now you're getting an idea of how much I love release day
[08:55] <jibel> sil2100, checking netboot mini.iso and pxe for sanity and it should be all from me
[08:56] <jibel> 32bit
[09:00] <sil2100> Sweet
[09:01] <acheronuk> must get sorted for artful :S https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1447144
[09:02] <acheronuk> I mean for 18.04
[09:04] <sil2100> infinity, jibel, flexiondotorg: I did all the basic tests for MATE i386 - I can't test the screenreader as I don't have everything configured for sound in the VM (still using kvm directly)
[09:04] <sil2100> I'd say it's all good, should we mark MATE as ready?
[09:04] <sil2100> flexiondotorg: ^ ?
[09:04] <jibel> sil2100, sound in a vm should just work
[09:07] <jamespage> o/ morning release team
[09:08] <jamespage> quick q - I have a high priority SRU for openvswitch to work  (https://bugs.launchpad.net/bugs/1723480)
[09:08] <sil2100> Let me try tweaking my commandline
[09:08] <jamespage> that's causing service disruption in prod deployments :(
[09:08] <jamespage> however I need to clear the FTBFS in artful - can I part the artful updates in the UNAPPROVED queue for zero-day SRU?
[09:09] <jamespage> that would include a point release (https://bugs.launchpad.net/bugs/1724622)
[09:09] <jamespage> the fix for the test failure (https://bugs.launchpad.net/bugs/1722799)
[09:09] <jamespage> and https://bugs.launchpad.net/bugs/1723480
[09:09] <jamespage> part/park
[09:09]  * jamespage needs more coffee
[09:10] <infinity> jamespage: If you want your fix out quickly, I wouldn't tie it up with the point release if I were you.
[09:11] <infinity> jamespage: I'd just do the FTBFS fix and the config fix, turn it around quickly, then followup with the point release.
[09:11] <jamespage> infinity: ok thats a good point - I'll rebase it on 2.8.0 and do a followup
[09:12] <infinity> jamespage: Those two small fixed should be easy to turn around in a matter of hours with high confidence, which is likely what you're after here.
[09:12] <infinity> s/fixed/fixes/
[09:17] <jamespage> infinity: ack
[09:17] <jamespage> working that now
[09:22] -queuebot:#ubuntu-release- Builds: Netboot i386 [Artful Final] has been marked as ready
[09:37] <sil2100> hmmm
[09:38] <didrocks> this is when sil2100 should say "HOLD ON!" :)
[09:39] <sil2100> Kubuntu installer on i386 crashed with a python traceback when I tried checking the 'format' checkbox on a newly created partition
[09:40] <sil2100> It's reproducible for me
[09:40] <flexiondotorg> sil2100: I'll mark them ready now.
[09:40] <sil2100> flexiondotorg: thanks!
[09:41] <infinity> sil2100: I feel like that wouldn't be kubuntu-specific, nor i386-specific.
[09:41] <sil2100> It's a crash in the kde frontend of ubiquity
[09:41] <infinity> Okay, not i386-specific. :P
[09:41] <sil2100> So I guess it's only visible on Kubuntu
[09:41] <infinity> Either way, it's too late, so there are no bugs.
[09:41] <infinity> LA LA LA.
[09:41] <infinity> I CAN'T HEAR YOU.
[09:42] <sil2100> In PartitionModel.py at one place they're trying to execute .toBool() on an int apparently
[09:42] <sil2100> Right
[09:42] <sil2100> RIGHT
[09:42]  * sil2100 clears out the #ubuntu-release backlog
[09:42] <infinity> toBool or not toBool.
[09:42] <sil2100> Nobody saw anything, nothing to see here, move along
[09:42] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Artful Final] has been marked as ready
[09:42] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop i386 [Artful Final] has been marked as ready
[09:43] <infinity> I think nusakan is ready for the final mirror push.  Just need the OK from IS.
[09:43]  * didrocks is hearding loud music, so can't read
[09:43] <infinity> Then we do the long waiting game while we see if mirrors have picked up the changes.
[09:43] <jibel> sil2100, bug 1724058
[09:43] <sil2100> o/
[09:44] <sil2100> \o/
[09:48] <sil2100> jibel: thanks!
[09:53] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Artful Final] has been marked as ready
[09:53] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop i386 [Artful Final] has been marked as ready
[09:54] <bluesabre> Xubuntu's ready to roll :)
[09:56] <sil2100> woot
[09:56] <sil2100> \o/
[09:58] <acheronuk> & Kubuntu
[09:58]  * acheronuk waits for the bot
[09:58] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Artful Final] has been marked as ready
[09:58] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop i386 [Artful Final] has been marked as ready
[09:59] <acheronuk> :)
[10:01] <sil2100> Uh oh my i386 installation just finished ;)
[10:06] <sil2100> infinity: I guess I'll mark ubuntustudio as ready
[10:06] <sil2100> Since all the tests are done
[10:07] -queuebot:#ubuntu-release- Unapproved: openvswitch (artful-proposed/main) [2.8.0-0ubuntu1 => 2.8.0-0ubuntu2] (ubuntu-server)
[10:07] -queuebot:#ubuntu-release- Unapproved: openvswitch (zesty-proposed/main) [2.6.1-0ubuntu5.1 => 2.6.1-0ubuntu5.2] (ubuntu-server)
[10:07] -queuebot:#ubuntu-release- Unapproved: openvswitch (xenial-proposed/main) [2.5.2-0ubuntu0.16.04.2 => 2.5.2-0ubuntu0.16.04.3] (ubuntu-server)
[10:08] <sil2100> infinity: should we also mark subiquity as ready? I see mwhudson did all the tests and they're green
[10:08] <infinity> sil2100: Yeah.
[10:08] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD amd64 [Artful Final] has been marked as ready
[10:08] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD i386 [Artful Final] has been marked as ready
[10:08] <sil2100> Marking
[10:09] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity amd64 [Artful Final] has been marked as ready
[10:13] <jamespage> infinity: as discussed ^^ three ovs uploads with minimal patch for speed!
[10:16] <infinity> jamespage: Are you sure it's managed as a dpkg conffile now?
[10:17] <xnox> infinity, s390x is good too.
[10:17] <jamespage> infinity: I am - http://paste.ubuntu.com/25771470/
[10:17] <infinity> jamespage: Kay, then mangling it is very much evil indeed. ;)
[10:18] <jamespage> infinity: (output from dpkg-query --showformat='${Conffiles}\n' --show openvswitch-switch)
[10:18] <infinity> jamespage: When did it become a conffile?
[10:18] <jamespage> infinity: yeah I think that goes back to the dawn of time for that package
[10:18] <jamespage> (mangling)
[10:18] -queuebot:#ubuntu-release- Unapproved: accepted openvswitch [source] (artful-proposed) [2.8.0-0ubuntu2]
[10:19] <jamespage> infinity: 2.3.1-0ubuntu1 in vivid
[10:19] <jamespage> infinity: by me - I missed the mangling part
[10:20] <infinity> jamespage: Ouch.
[10:21] -queuebot:#ubuntu-release- Unapproved: accepted openvswitch [source] (zesty-proposed) [2.6.1-0ubuntu5.2]
[10:22] <jamespage> infinity: that's kinda what elmo said to me
[10:23] <infinity> jamespage: Was he waving a stick when he said it?
[10:23] -queuebot:#ubuntu-release- Unapproved: accepted openvswitch [source] (xenial-proposed) [2.5.2-0ubuntu0.16.04.3]
[10:24] <jamespage> infinity: maybe :)
[10:24] <jamespage> infinity: that behaviour causes a double restart issue in openstack deployments; the package upgrade is expected to restart the daemons
[10:25] <jamespage> infinity: however we have charms that manage that file for dpdk support; they then re-assert the templated state after the package upgrade, which triggers another restart...
[10:25] <jamespage> infinity: and an ovs restart does cause a minor blip in the data plane for the network...
[10:26] <jamespage> that's next of my list of things to see if we can fix/minimize
[11:17] <flocculant> infinity: don't know if you'll be done before I'm back later, but https://xubuntu.org/news/xubuntu-17-10-release is our release doodah if I'm not
[11:20] <infinity> flocculant: Tell the ReleaseNotes wiki. :)
[11:20] <flocculant> oh ok :D
[11:21] <infinity> flocculant: (Or tell your users by mailing an announce in a couple of hours)
[11:22] <infinity> flocculant: I stopped linking to flavour release announcements in the Ubuntu announcement years ago, cause it's just painful.
[11:22] <infinity> flocculant: See, eg: https://lists.ubuntu.com/archives/ubuntu-announce/2017-April/000220.html
[11:22] <flocculant> infinity: oh right, can understand that :) leaving wiki to point where it does then
[11:38] -queuebot:#ubuntu-release- Builds: Ubuntu Base amd64 [Artful Final] has been marked as ready
[11:38] -queuebot:#ubuntu-release- Builds: Ubuntu Base arm64 [Artful Final] has been marked as ready
[11:38] -queuebot:#ubuntu-release- Builds: Ubuntu Base armhf [Artful Final] has been marked as ready
[11:38] -queuebot:#ubuntu-release- Builds: Ubuntu Base i386 [Artful Final] has been marked as ready
[11:38] -queuebot:#ubuntu-release- Builds: Ubuntu Base ppc64el [Artful Final] has been marked as ready
[11:38] -queuebot:#ubuntu-release- Builds: Ubuntu Base s390x [Artful Final] has been marked as ready
[11:38] -queuebot:#ubuntu-release- Builds: Ubuntu Server amd64 [Artful Final] has been marked as ready
[11:38] -queuebot:#ubuntu-release- Builds: Ubuntu Server arm64 [Artful Final] has been marked as ready
[11:38] -queuebot:#ubuntu-release- Builds: Ubuntu Server armhf+raspi2 [Artful Final] has been marked as ready
[11:38] -queuebot:#ubuntu-release- Builds: Ubuntu Server i386 [Artful Final] has been marked as ready
[11:38] -queuebot:#ubuntu-release- Builds: Ubuntu Server ppc64el [Artful Final] has been marked as ready
[11:38] -queuebot:#ubuntu-release- Builds: Ubuntu Server s390x [Artful Final] has been marked as ready
[11:45] <infinity> jamespage: Oh hey, openvswitch isn't on any media.  If you're lucky and these tests finish soon, that artful upload might squeak into the release pocket before I close the archive.
[11:45] <jamespage> infinity: ack - I'll work with fnordahl on testing now
[11:46]  * infinity disabled the auto-accept bot.
[12:00] -queuebot:#ubuntu-release- Unapproved: accepted xdg-utils [source] (artful-proposed) [1.1.1-1ubuntu3]
[12:08] <slashd> sil2100, good day ;), do you have a moment to approve lshw in the trusty upload queue ? LP: #1471983. Thanks
[12:53] <sil2100> slashd: hey! Let me take care of that in a minute
[12:54] <slashd> sil2100, thanks
[12:54] <sil2100> (17.10 release-day today, but I'm basically done)
[12:54] <slashd> sil2100, right busy day
[12:54] <sil2100> (infinity is taking care of the final announcements)
[12:55] <flexiondotorg> OK, then I'll get the Ubuntu MATE release notes posted then :-)
[13:05] <sil2100> I just noticed
[13:06] <sil2100> We're not releasing lubuntu-next for the release?
[13:06] <sil2100> I remember we had it for Final Beta
[13:07] <acheronuk> tsimonq2: ^^
[13:07] <infinity> sil2100: As a general rule, we don't 'release' preview products like that.  They're not supportable.
[13:07] <infinity> When they switch, then yay.
[13:07] <infinity> (was the same story with kubuntu versus kubuntu-active)
[13:07] <sil2100> Ah, ok
[13:08] <tsimonq2> Yep.
[13:08] <infinity> It was a mistake to have it in beta-2 probably, but also who cares.
[13:08] <tsimonq2> (I expected this)
[13:08] <tsimonq2> infinity: *shrug*
[13:09] <sil2100> infinity: ok, updated releasenotes links, but wiki-page doesn't want to refresh those for me
[13:09] <sil2100> I saved the changes but the wiki just wants to keep showing the old ones
[13:09] <sil2100> Oh well
[13:09] <infinity> Doesn't look saved to me.
[13:09] <infinity> wiki harder?
[13:10] <mdeslaur> Congrats!
[13:10] <tsimonq2> :D
[13:10] <sil2100> infinity: if you press 'edit' you should see the changes
[13:11] <sil2100> Not sure why it's not showing!
[13:11] <ogra_> can i upload to BB yet ?
[13:11] <didrocks> \o/
[13:11]  * sil2100 yells at the wiki
[13:11] <ogra_> (just had to ask the obligatory question :) )
[13:12] <infinity> ogra_: We have no name, vacation time.
[13:12] <sil2100> https://wiki.ubuntu.com/ArtfulAardvark/ReleaseNotes?action=recall&rev=71 <- why wiki why
[13:12] <ogra_> infinity, except in CE (where i work now) :(
[13:12] <sil2100> infinity: ok, it's there now
[13:12] <tsimonq2> infinity: Can it be Big Bat, pretty plleeeaaassseee? :P
[13:12] <sil2100> Anyway, yay \o/
[13:12] <ogra_> you distro guys get all the free vacations !
[13:13] <infinity> sil2100: Ahh, cache seems to have timed out for me, seeing that rev now.
[13:13] <ogra_> ... oh ... and congrats everoyne indeed !
[13:13] <infinity> tsimonq2: You can see my vote cleverly encoded in the release announcement.
[13:13] <jibel> congrats everyone!
[13:13] <sil2100> Yeah, the main one is updated now too, yelling helped
[13:14] <tsimonq2> infinity: Excellent.
[13:17] <didrocks> sil2100: does yelling support transactional two-phase commit? :)
[13:17] <ogra_> only if you yell twice i think
[13:17] <sil2100> I think it was yellin that helped
[13:17] <didrocks> oh right
[13:17] <didrocks> ;)
[13:17] <ogra_> :)
[13:17] <sil2100> The second thing was just removing a line, pfff, I don't count that as an action
[13:19] <sil2100> ;)
[13:22] -queuebot:#ubuntu-release- Builds: 52 entries have been added, updated or disabled
[13:22] <tsimonq2> infinity: ftr I call dibs on creating the wiki pages for BB once we have a codename (like the past several releases)
[13:23] <infinity> tsimonq2: I've already got the ReleaseSchedule done, but you can do the rest, sure.
[13:23] <infinity> https://wiki.ubuntu.com/BBSeries/ReleaseSchedule
[13:28] <tsimonq2> I saw that, cool.
[13:29]  * acheronuk +1 for 'Big Bat'
[13:29] <apw> slashd, this lshw thing ... do you have somethign in hand which triggers the crash ?  as that fix looks supect at best
[13:30] <infinity> apw: Literally all of lshw is suspect.
[13:30] <infinity> At least this time it's crashing itself instead of the kernel.
[13:32] <slashd> apw, I don't have a USB-3 drive myself to test, but I have tested with a user that has one .. so when a USB 3.0 is connected to the system, if you ran lshw it segfault. The fix has been SRU'd on Wily in the past, but never made its way to Trusty. I have a user that will be able to test the -proposed pkg as well
[13:33] <apw> slashd, that fix just looks plain wrong by the spec, the upstream fix is differnt, and also wrong
[13:33] <apw> to my eye.  that field is nominally unsigned as far as i can see, so loading into a signed value and comparing > 0 seems wrong
[13:33] <apw> slashd, is suspect the real bug is that that length is > len, that the overall inquirey data was truncated
[13:34] <apw> slashd, and the real fix, would be to load it into a u_int8_t _len; if (_len > (len - 4) { _len = len - 4; }
[13:34] <apw> slashd, would stop the crash
[13:36] <slashd> apw, , upstream commit "7b57987bb21d8c178c9beba1f5a574eb0af18e54" is changing from char to uint8_t as you suggest
[13:36] <apw> slashd, right and then doing if (_len > 0), which has exactly 0 meaning
[13:36] <apw> so i don't believe their fix fixes it
[13:38] <slashd> apw, right make sense, what do you suggest ? drop the patch for now ? and we'll work with upstream to fix this for good.
[13:41] <apw> if you have someone who can test, we could ask them to test what seems like the real fix and see
[13:41] <slashd> apw, I have someone to test, otherwise I can find a USB 3.0 and do the test on my own
[13:42] <apw> ack
[13:42] <slashd> apw, tks
[13:42] <LocutusOfBorg> can I be the first one to ask... when will BB open?
[13:42] <apw> slashd, i assume my theory is clear enough to write a patch for
[13:42]  * LocutusOfBorg is jocking
[13:42] <slashd> apw, it is
[13:42] <apw> LocutusOfBorg, some time after we have a name :)
[13:42] <LocutusOfBorg> :)
[13:43] <LocutusOfBorg> apw, I have one name
[13:43] <infinity> LocutusOfBorg: You weren't the first to ask, thus the joke fell flat.
[13:43] <apw> i have three, but none of them start with B
[13:43] <LocutusOfBorg> seriosly? lol
[13:43] <LocutusOfBorg> apw, http://www.bbc.co.uk/news/technology-18922629
[13:43] <infinity> 07:11 < ogra_> can i upload to BB yet ?
[13:43] <infinity> 07:42 < LocutusOfBorg> can I be the first one to ask... when will BB open?
[13:43] <LocutusOfBorg> sad!
[13:43] <infinity> 31 minutes late to the party.
[13:43] <ogra_> hahaha !
[13:43] <ogra_> \o/
[13:43] <LocutusOfBorg> I was eating some food :/
[13:44] <ogra_> i win
[13:44] <LocutusOfBorg> lets try again for 18.04
[13:44] <LocutusOfBorg> :)
[13:44] <ogra_> :)
[13:44] <LocutusOfBorg> seriously, congrats infinity! take your well deserved rest you all
[13:53] <acheronuk> thank you all (r'team) for this release :D (and you patience)
[13:53] <acheronuk> *your
[13:55] <doko> tsimonq2: you did the last debhelper merge, do you want to prepare one for the b-series?
[13:56] <LocutusOfBorg> doko, can I also prepare something?
[13:56] <LocutusOfBorg> automake merge
[13:57] <doko> sure
[13:58] <ddstreet> apw re: _len > 0 has no meaning for unsigned, that is wrong, it does have meaning
[13:58] <ddstreet> it's checking if the serial number string length is non-zero
[13:58] <ddstreet> slashd ^
[13:59]  * infinity decides it's time for naps.
[13:59] <ddstreet> apw you're right that it should be a unsigned, not char, though
[13:59] <ddstreet> but that is a separate upstream patch, that should be sru'ed separately from this bugfix
[14:00] <sil2100> infinity: goodnight!
[14:01] <apw> ddstreet, a point, though why is 0 invalid to the string contstuctor
[14:02] <ddstreet> apw 0 means there is no serial number string
[14:02] <ddstreet> it's not about being valid/invalid to the string() call
[14:02] <apw> ddstreet, ok that makes sense, so if it was u_int8_t it would be ok
[14:02] <ddstreet> yeah
[14:02] <apw> will you resubmit it ?
[14:02] <ddstreet> sure
[14:03] <ddstreet> and we will open a new bug to sru the other upstream patch, to char->uint8_t
[14:03] <ddstreet> make sure that gets into t/x/y/z where needed
[14:03] <LocutusOfBorg> doko, https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+sourcepub/8373959/+listing-archive-extra
[14:03] <LocutusOfBorg> I used artful as target for obvious reasons
[14:03] <slashd> ddstreet, apw so basically doing this : http://pastebin.ubuntu.com/25772721/
[14:04] <ddstreet> apw i think it's still in upload queue? https://launchpad.net/ubuntu/trusty/+queue?queue_state=1&queue_text=lshw
[14:04] <slashd> apw, can you reject it ? or you want us to overwrite ?
[14:04] <apw> i can reject it yes
[14:05] <slashd> apw, thanks
[14:06] -queuebot:#ubuntu-release- Unapproved: rejected lshw [source] (trusty-proposed) [02.16-2ubuntu1.4]
[14:06] <tsimonq2> doko: Yes, I can take care of it
[14:09] -queuebot:#ubuntu-release- Unapproved: accepted gtk+3.0 [source] (artful-proposed) [3.22.24-0ubuntu2]
[14:17] <apw> jbicha, the fix for sane-backends has that been validated as the bug commentary seem to indicate a Provises: is not sufficient
[14:25] <jbicha> apw: the bug commentary says trying to install 'libsane' currently will not work since important stuff depends on libsane1 which is uninstallable with zesty's libsane
[14:26] <jbicha> the commentators didn't try out the proposed artful package because it's not in -proposed yet ;)
[14:27] <jbicha> I don't have a scanner to test the bug fix for sure, but I think PeterPall will help us verify on real hardware
[14:31] <jbicha> I did discuss the issue with Simple Scan maintainer robert_ancell who thought my proposed change looked ok
[14:48] <apw> jbicha, okies
[14:49] -queuebot:#ubuntu-release- Unapproved: accepted sane-backends [source] (artful-proposed) [1.0.27-1~experimental2ubuntu2]
[14:56] -queuebot:#ubuntu-release- Unapproved: accepted ktexteditor [source] (artful-proposed) [5.38.0-0ubuntu1.1]
[15:05] -queuebot:#ubuntu-release- Unapproved: accepted menu-cache [source] (artful-proposed) [1.0.2-3ubuntu0.17.10.1]
[15:16] <LocutusOfBorg> tomorrow the number of google searches for "how to hide the application panel in gnome shell" will rise a lot
[15:17]  * LocutusOfBorg goes in extensions.gnome.org
[15:25] <mgedmin> so are y'all waiting for mirrors to sync before you update http://changelogs.ubuntu.com/meta-release?
[15:25] <ddstreet> sil2100 can you promote initramfs-tools to -updates for lp #1712491 (for trusty and xenial) if you have time?
[15:30] <pinnerup> Does anyone know who authored the Latin motto in the topic? I'm pretty sure it has an error in it.
[15:31] <mgedmin> https://tutorials.ubuntu.com/tutorial/tutorial-upgrading-ubuntu-desktop#0 still links to the release notes for 17.04
[15:33] <jbicha> bdmurray: do you usually handle the meta-release ?
[15:34] <bdmurray> jbicha: yes
[15:35] <apw> pinnerup, i am sure whoever it was reads here regularly enough, that would could just propose your correction; though there is every possibility the error is intended and sarcasm
[15:35] <cjwatson> pinnerup: slangasek, I think.  what's the error?
[15:36] <bdmurray> I'll be updating the meta-release file in a bit after checking for any last minute upgrade issues. However, if you use the -d switch with do-release-upgrade it'll be exactly the same as if I did update the meta-release file.
[15:37] <jbicha> thanks :)
[15:37] <pinnerup> cjwatson: "melior" is an adjectuve that should congruate with "malum", that is, it should be in the neuter ("melius").
[15:37] <cjwatson> pinnerup: also https://irclogs.ubuntu.com/2014/02/06/%23ubuntu-release.html#t18:55
[15:38] <cjwatson> that sounds like a plausible correction but I will leave it to slangasek
[15:39] <pinnerup> s/adjectuve/adjective/
[15:59] -queuebot:#ubuntu-release- Unapproved: lshw (xenial-proposed/main) [02.17-1.1ubuntu3.2 => 02.17-1.1ubuntu3.3] (core)
[16:01] -queuebot:#ubuntu-release- Unapproved: lshw (trusty-proposed/main) [02.16-2ubuntu1.3 => 02.16-2ubuntu1.4] (core)
[16:01] <ddstreet> bdmurray can you promote initramfs-tools to -updates for lp #1712491 (for trusty and xenial) if you have time?
[16:02] <ddstreet> apw can you review the new uploads for lp #1471983?  in the trusty and xenial upload queues
[16:23] <acheronuk> no update to the meta yet? http://changelogs.ubuntu.com/meta-release
[16:24] <nacc> acheronuk: bdmurray said he'd do it in a bit
[16:24] <nacc> acheronuk: after he checked for any last minute upgrade issues
[16:24] <acheronuk> nacc: okay :)
[16:33] <slangasek> pinnerup: thanks, I was unaware melior declined in this way :)
[16:59] <bdmurray> meta-release updated
[17:07] <acheronuk> :)
[17:26] <pinnerup> slangasek: No problem; comparatives always decline like that :)
[18:12] -queuebot:#ubuntu-release- Unapproved: accepted cloud-init [source] (zesty-proposed) [17.1-18-gd4f70470-0ubuntu1~17.04.2]
[18:15] -queuebot:#ubuntu-release- Unapproved: accepted cloud-init [source] (xenial-proposed) [17.1-18-gd4f70470-0ubuntu1~16.04.2]
[20:08] <teward> if i wanted to get a 0-day update for nginx (literally a minor version bump just to get some bugfixes in), I should target the version numbering for Artful and not presume for B-series, right?
[20:08] <teward> s/0-day //
[20:09] <infinity> teward: If it's an SRU, treat it as an SRU.
[20:09] <infinity> Because it's an SRU.
[20:09] <infinity> When you upload to tautology club...
[20:12] <teward> yep
[20:12] <teward> infinity: i meant with the version scheming where you could have multiple versions of the same package within multiple releases
[20:12] <teward> since there's no B-series and therefore no 'newer' version issue, i'm assuming just handle it as a standard SRU
[20:13] <teward> B-series 18.04 is gonna jump to Mainline during development for nginx anyways, so... :P
[20:13] <teward> (post-release stable nginx release, anyone?  :P)
[20:18] -queuebot:#ubuntu-release- Unapproved: apport (artful-proposed/main) [2.20.7-0ubuntu3 => 2.20.7-0ubuntu3.1] (core)
[20:22] -queuebot:#ubuntu-release- Unapproved: nginx (artful-proposed/main) [1.12.1-0ubuntu2 => 1.12.2-0ubuntu1] (ubuntu-server)
[20:24] <teward> infinity: remind me because it's unclear, do I need to subscribe the SRU team to the bug or no?
[20:24] <teward> *is tired and forgot things xD*
[20:25] <infinity> teward: If it's referenced in the changelog, we can find it.
[20:25] <teward> cool cool :)
[20:26] <teward> *goes back to beating his head against code*
[20:29] <infinity> teward: I wish everyone's bugfix point releases looked like that.
[20:29] <teward> infinity: heh.  Well, nginx is pretty darned smart about it :)
[20:29] <teward> now, 1.13.x, that's its own beast.
[20:30] <infinity> Those crazy Russians.
[20:30] <teward> you get feature changes, AND bug fixes, and it's a hodgepodge and a huge damned mess xD
[20:30] <teward> but you're right.
[20:30] <teward> these bugfix point releases are pretty nice.  And ultimately are very specific about what issues were fixed.
[20:30] <teward> They're good with security pointreleases that way too
[20:31] <teward> it's not a *critical* bugfix except that HTTP/2 request client body corruption thing, but as i'm doing some PPA updates I said "Screw it while i'm here let's SRU!" :p
[20:32] <infinity> teward: "[ Testcase ] none" is pretty unacceptable for an SRU.
[20:33] <teward> infinity: you're right.  I'm trying to find test cases.
[20:33] <infinity> teward: There needs to be some way you intend to demonstrate that this update it no less bad than the package already in artful and, ideally, better.
[20:33] <teward> their redmine is evil.
[20:33] <teward> give me a minute, i'll find one.  Feel free to NACK until I update.
[20:33] <teward> (I"m juggling 15 tasks at once)
[20:34] <teward> trac* is evil
[20:35] <teward> infinity: it'd be nice if people gave links to the individual trac issue tickets >.<
[20:35] <teward> i'll have to get back to you; NACK it for now.
[20:37] -queuebot:#ubuntu-release- Unapproved: accepted linux-firmware [source] (xenial-proposed) [1.157.13]
[20:38] <infinity> bdmurray: Yo.
[20:38] <infinity> bdmurray: Does raw_input_char return when char_count is hit, or a CR?
[20:39]  * infinity looks.
[20:42] <teward> infinity: just outright NACK it, I'll deal with this when 18.04's repos open.  CBA to hunt through mercurial upstream to try and find which tickets were addressed (it's messy as all hell)
[20:43] <teward> (really hate mercurial repositories...)
[20:44] <teward> (their merge of the fixes ended up merging in 1.13.x commits so the entire revision tree is messed and I can't find the specific bugfixes or test cases)
[20:44] -queuebot:#ubuntu-release- Unapproved: rejected nginx [source] (artful-proposed) [1.12.2-0ubuntu1]
[20:45] <infinity> bdmurray: As I read this, when there are >10 choices, I can't pick a single-char choice. :)
[20:45] <infinity> bdmurray: IOW, the cute trick here of allowing user input without a carriage return is just something that needs to go away if people need multi-char options.
[20:47] <apw> infinity, or they need to just start at 10 or be 01
[20:48] <infinity> apw: Well, yes.  But nothing in the code enforces that.
[20:48] <infinity> Also, ick.
[20:48] <apw> no indeed, i think you would have to type ' 1' or '1 ' and let the strip do its thing, but ugg
[20:49] <infinity> And the strip doesn't remove \n
[20:49] <infinity> Which is extra gross.
[20:49] <infinity> Actually, doesn't seem to strip much of anything.
[20:50] <infinity> Oh, no.
[20:50] <infinity> That's my test thing being crap.
[20:50] <apw> strip does do newlines right ?
[20:50] <apw> but just making it a type and hit return thing seems much more sensible
[20:51] <infinity> So, yes.  The strip works.
[20:51] <infinity> But it's weird to be inconsistent for 1-char and 2-char responses.
[20:52] <infinity> And worse, inconsistent depending on number of choices.
[20:52] <infinity> So if you have 5, then 9, then 12, then 3...
[20:52] <apw> yep
[20:52] <infinity> You get used to "I can type one char and it works", and then that third option...
[20:53] <apw> it seems too random to me, concur
[20:56] -queuebot:#ubuntu-release- Unapproved: rejected apport [source] (artful-proposed) [2.20.7-0ubuntu3.1]
[22:32] -queuebot:#ubuntu-release- Unapproved: accepted mdadm [source] (zesty-proposed) [3.4-4ubuntu0.1]
[22:34] -queuebot:#ubuntu-release- Unapproved: accepted mdadm [source] (xenial-proposed) [3.3-2ubuntu7.5]
[22:37] -queuebot:#ubuntu-release- Unapproved: rejected livecd-rootfs [source] (xenial-proposed) [2.408.19]
[22:38] -queuebot:#ubuntu-release- Unapproved: accepted lmbench [source] (zesty-proposed) [3.0-a9-1.3ubuntu0.1]
[22:41] -queuebot:#ubuntu-release- Unapproved: accepted lmbench [source] (xenial-proposed) [3.0-a9-1.1ubuntu0.1]
[22:43] -queuebot:#ubuntu-release- Unapproved: accepted audit [source] (zesty-proposed) [1:2.6.6-1ubuntu1.1]
[22:44] -queuebot:#ubuntu-release- Unapproved: accepted audit [source] (xenial-proposed) [1:2.4.5-1ubuntu2.1]
[22:52] <bashfulrobot> Quick question, did the final iso's include the patch for the WPA hack?
[22:53] <bashfulrobot> Once I'm back at a computer I can check though.
[22:58] <tsimonq2> bashfulrobot: Yes.
[23:03] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (xenial-proposed) [2.408.20]
[23:10] <bashfulrobot> Thanks
[23:11] <bashfulrobot> Tsimonq2^^
[23:32] -queuebot:#ubuntu-release- Unapproved: accepted iptstate [source] (xenial-proposed) [2.2.5-1ubuntu0.1]
[23:37] -queuebot:#ubuntu-release- Unapproved: accepted lshw [source] (xenial-proposed) [02.17-1.1ubuntu3.3]