[00:36] -queuebot:#ubuntu-release- Unapproved: accepted pulseaudio [source] (bionic-proposed) [1:11.1-1ubuntu7.4]
[01:15] -queuebot:#ubuntu-release- Unapproved: docopt (eoan-proposed/universe) [0.6.2-2ubuntu1 => 0.6.2-2.1] (no packageset) (sync)
[01:16] -queuebot:#ubuntu-release- Unapproved: accepted docopt [sync] (eoan-proposed) [0.6.2-2.1]
=== s8321414_ is now known as s8321414
[03:56] -queuebot:#ubuntu-release- Unapproved: openjdk-8 (eoan-proposed/universe) [8u232-b07-2ubuntu1 => 8u232-b09-0ubuntu1] (no packageset)
[04:02] -queuebot:#ubuntu-release- Unapproved: accepted openjdk-8 [source] (eoan-proposed) [8u232-b09-0ubuntu1]
[04:32] -queuebot:#ubuntu-release- Unapproved: wham-align (eoan-proposed/universe) [0.1.5-1 => 0.1.5-2] (no packageset) (sync)
[04:33] -queuebot:#ubuntu-release- Unapproved: accepted wham-align [sync] (eoan-proposed) [0.1.5-2]
[04:35] -queuebot:#ubuntu-release- New binary: wham-align [amd64] (eoan-proposed/universe) [0.1.5-2] (no packageset)
[04:35] -queuebot:#ubuntu-release- New binary: wham-align [i386] (eoan-proposed/universe) [0.1.5-2] (no packageset)
[05:25] -queuebot:#ubuntu-release- Unapproved: rsyslog (bionic-proposed/main) [8.32.0-1ubuntu4 => 8.32.0-1ubuntu4.1] (core)
[05:25] -queuebot:#ubuntu-release- Unapproved: rsyslog (disco-proposed/main) [8.32.0-1ubuntu7 => 8.32.0-1ubuntu7.1] (core)
[05:59] -queuebot:#ubuntu-release- Unapproved: openjdk-lts (eoan-proposed/main) [11.0.5+9-1ubuntu1 => 11.0.5+10-0ubuntu1] (core)
[06:27] <ginggs> please unblock wham-align's new binaries, this will allow bcbio to build, finally
[06:27] <ginggs> s/unblock/accept/
[06:39] <tdaitx> I would appreciate if someone could approve openjdk-lts in eoan
=== andrewc is now known as acloke
[07:29] <LocutusOfBorg> vorlon, we discussed it here yesterday and the day before
[07:30] <LocutusOfBorg> and it has been blocked until a respin was needed, and released after... was it a problem?
[07:40] <apw> infinity, the disco kernels are released
[08:31] -queuebot:#ubuntu-release- Unapproved: uim (eoan-proposed/universe) [1:1.8.8-5ubuntu1 => 1:1.8.8-6] (no packageset) (sync)
[08:32] -queuebot:#ubuntu-release- Unapproved: accepted uim [sync] (eoan-proposed) [1:1.8.8-6]
[08:33] -queuebot:#ubuntu-release- Unapproved: why3 (eoan-proposed/universe) [1.2.0-2ubuntu1 => 1.2.0-3ubuntu1] (no packageset)
[08:33] -queuebot:#ubuntu-release- Unapproved: accepted why3 [source] (eoan-proposed) [1.2.0-3ubuntu1]
[08:59] <bdmurray> jibel: I don't see any thing about zfs in the Release Notes for Eoan. Do you have plans to add it?
[09:13] <jibel> bdmurray, yes we'll do it with a link to the blog posts
[09:15] <bdmurray> jibel: will bug 1847628 be release noted too?
[09:15] <ubot5> bug 1847628 in ubiquity (Ubuntu) "When using swap in ZFS, system stops when you start using swap" [High,Incomplete] https://launchpad.net/bugs/1847628
[09:17] <jibel> bdmurray, yes, I can propose a fix but that's lot of re-test
[09:17] <jibel> let me propose something though and we'll see what we do
[09:45]  * cking notes that swap on a zvol is not a good idea
=== andrewc is now known as Guest50135
[10:18] -queuebot:#ubuntu-release- Unapproved: openstack-trove (eoan-proposed/universe) [1:12.0.0~rc1-0ubuntu3 => 1:12.0.0~rc1-0ubuntu4] (no packageset)
[10:19] -queuebot:#ubuntu-release- Unapproved: accepted openstack-trove [source] (eoan-proposed) [1:12.0.0~rc1-0ubuntu4]
[10:22] <doko> sil2100, infinity, xnox: do we have openjdk-lts on any image, or can we ship the security update directly in eoan?
[10:45] <sil2100> doko: I'll review it and accept to eoan-proposed at least
[10:46] <sil2100> Since it's not seeded on any images (only in supported), but it does built quite a long time
[10:47] -queuebot:#ubuntu-release- Unapproved: gnome-shell-extension-multi-monitors (eoan-proposed/universe) [18-1 => 19-1] (no packageset) (sync)
[10:48] -queuebot:#ubuntu-release- Unapproved: accepted gnome-shell-extension-multi-monitors [sync] (eoan-proposed) [19-1]
[10:54] -queuebot:#ubuntu-release- Unapproved: accepted openjdk-lts [source] (eoan-proposed) [11.0.5+10-0ubuntu1]
[11:39] <rbalint> sil2100, i'd like to update wslu in eoan, it is seeded only for the wsl image which is on cloud-images.u.c
[11:40] <rbalint> sil2100, the proposed packages is in https://launchpad.net/~rbalint/+archive/ubuntu/scratch/+packages
[11:41] <rbalint> sil2100, mostly but fixes, but also a little enhancement in the install
[11:42] <rbalint> sil2100, the reason for asking now is that i'd like to sru it soon following https://wiki.ubuntu.com/wslu-Updates
[11:48] -queuebot:#ubuntu-release- Unapproved: libdrm (bionic-proposed/main) [2.4.97-1ubuntu1~18.04.1 => 2.4.97-1ubuntu1~18.04.2] (core, xorg)
[11:57] -queuebot:#ubuntu-release- Unapproved: ubuntu-settings (eoan-proposed/main) [19.10.3 => 19.10.4] (ubuntu-desktop)
=== andrewc is now known as Guest93955
[12:33] <infinity> rbalint: If you can QA it reliably between now and tomorrow morning, sure.
[12:42] <sil2100> rbalint: please upload and I can review that
=== s8321414_ is now known as s8321414
[12:46] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-settings [source] (eoan-proposed) [19.10.4]
[12:48] -queuebot:#ubuntu-release- New: accepted dleyna-renderer [sync] (eoan-proposed) [0.6.0-1]
[12:48] -queuebot:#ubuntu-release- New: accepted wham-align [i386] (eoan-proposed) [0.1.5-2]
[12:48] -queuebot:#ubuntu-release- New: accepted wham-align [amd64] (eoan-proposed) [0.1.5-2]
[12:50] -queuebot:#ubuntu-release- New binary: dleyna-renderer [i386] (eoan-proposed/none) [0.6.0-1] (ubuntugnome)
[12:50] -queuebot:#ubuntu-release- New binary: dleyna-renderer [s390x] (eoan-proposed/none) [0.6.0-1] (ubuntugnome)
[12:50] -queuebot:#ubuntu-release- New binary: dleyna-renderer [ppc64el] (eoan-proposed/none) [0.6.0-1] (ubuntugnome)
[12:52] -queuebot:#ubuntu-release- New binary: dleyna-renderer [amd64] (eoan-proposed/none) [0.6.0-1] (ubuntugnome)
[12:52] -queuebot:#ubuntu-release- New binary: dleyna-renderer [armhf] (eoan-proposed/none) [0.6.0-1] (ubuntugnome)
[12:52] -queuebot:#ubuntu-release- New binary: dleyna-renderer [arm64] (eoan-proposed/none) [0.6.0-1] (ubuntugnome)
[12:54] <ahasenack> are bileto runs frozen because of the release?
[12:55] <Laney> nope
[12:55] -queuebot:#ubuntu-release- New: accepted dleyna-renderer [amd64] (eoan-proposed) [0.6.0-1]
[12:55] -queuebot:#ubuntu-release- New: accepted dleyna-renderer [armhf] (eoan-proposed) [0.6.0-1]
[12:55] -queuebot:#ubuntu-release- New: accepted dleyna-renderer [arm64] (eoan-proposed) [0.6.0-1]
[12:55] <Laney> you need a sil2100 to look into that
[12:56] <ahasenack> Laney: thx
[12:56] <ahasenack> sil2100: : https://bileto.ubuntu.com/#/ticket/3822 is "queued" since yesterday, can you take a quick look?
[12:56] -queuebot:#ubuntu-release- New: accepted dleyna-renderer [i386] (eoan-proposed) [0.6.0-1]
[12:56] -queuebot:#ubuntu-release- New: accepted dleyna-renderer [s390x] (eoan-proposed) [0.6.0-1]
[12:56] -queuebot:#ubuntu-release- New: accepted dleyna-renderer [ppc64el] (eoan-proposed) [0.6.0-1]
[13:01] <sil2100> ahasenack: ok, so I did notice some strangeness yesterday, I shall look into that once I have a momento
[13:01] <ahasenack> sil2100: cool. thanks
[13:08] -queuebot:#ubuntu-release- Unapproved: wslu (eoan-proposed/main) [2.3.0-1ubuntu1 => 2.3.2-0ubuntu1] (core)
[13:19] <xnox> https://paste.ubuntu.com/p/Vgx8fcf8Jv/
[13:20] <xnox> wrong
[13:20] <Laney> ❌
[13:20] <xnox> these two: https://paste.ubuntu.com/p/yHw2DXsQ3Z/
[13:20] <xnox> https://paste.ubuntu.com/p/Pm2XrvYTy6/
[13:20] <Laney> ✅
[13:21] <rbalint> infinity, sil2100, thanks, uploaded
[13:29] <sil2100> rbalint: ACK
[13:37] <sil2100> rbalint: looks good, a cosmetic thing I noticed was some whitespace/expanded-tab stuff in the patches, I guess!
[13:37] <sil2100> Approving
[13:38] -queuebot:#ubuntu-release- Unapproved: accepted wslu [source] (eoan-proposed) [2.3.2-0ubuntu1]
[14:05] -queuebot:#ubuntu-release- Unapproved: python-pyeclib (eoan-proposed/main) [1.5.0-1ubuntu5 => 1.5.0-1ubuntu6] (no packageset) (sync)
[14:06] -queuebot:#ubuntu-release- Unapproved: accepted python-pyeclib [sync] (eoan-proposed) [1.5.0-1ubuntu6]
[14:09] -queuebot:#ubuntu-release- Unapproved: ubiquity (eoan-proposed/main) [19.10.20 => 19.10.21] (core)
[14:09] <cyphermox> sil2100: ubiquity in ^
[14:12] <coreycb> Hi release team, I just uploaded a new version of python-pyeclib for eoan that fixes the current autopkgtest failure
[14:12] -queuebot:#ubuntu-release- Unapproved: python-pyeclib (eoan-proposed/main) [1.5.0-1ubuntu6 => 1.5.0-1ubuntu6] (no packageset)
[14:12] -queuebot:#ubuntu-release- Unapproved: accepted python-pyeclib [source] (eoan-proposed) [1.5.0-1ubuntu6]
[14:13] <handsome_feng> Sorry, could someone help to have a look at LP: #1848346, I think it's a release critical bug and I have no idea about this.
[14:13] <ubot5> Launchpad bug 1848346 in Ubuntu Kylin "Boot into black screen" [Critical,New] https://launchpad.net/bugs/1848346
[14:14] <cjwatson> coreycb: Don't both sync and upload something
[14:14] <cjwatson> The second is stuck
[14:15] <cjwatson> But uh hopefully the sync was correct?
[14:15] <coreycb> cjwatson: hmm I don't know if I did
[14:15] <cjwatson> Somebody did
[14:15] <cjwatson> https://launchpad.net/ubuntu/+source/python-pyeclib "Copied from ubuntu eoan in 3823 - 2019-10-16 by Corey Bryant"
[14:15] <RikMills> cyphermox: that ubiquity fixes the i386 nvidia issue that breaks steam I assume? just want to know so I can update that bug
[14:16] <coreycb> oh maybe I did. I was trying to use bileto but it was hanging over and over.
[14:16] <cjwatson> Identical changelog
[14:16] <coreycb> sorry
[14:16] <cjwatson> Yeah, bileto got there in the end apparently
[14:16] <cyphermox> RikMills: possibly, I'm not sure. xnox's change looks like it might
[14:16] <willcooke> handsome_feng, I might have seen something similar testing this morning.  For my machine it was a case of waiting for snapd to finish seeding and then it started
[14:16] <coreycb> cjwatson: they are the same then
[14:16] <cjwatson> RikMills: that's the theory (together with a debian-cd change), but needs testing
[14:16] <cjwatson> coreycb: cool
[14:17] <RikMills> cjwatson: thanks. I'll see how that goes then
[14:17] <cjwatson> RikMills: Does it affect Kubuntu as well?
[14:18] <cjwatson> The belief here was that only Ubuntu desktop was affected
[14:18] <cjwatson> (AIUI)
[14:18] <cjwatson> But maybe that was wrong
[14:18] <handsome_feng> willcooke, 100% dead here after that. :(
[14:18] <RikMills> cjwatson: yes, and ubuntu-mate
[14:19] <RikMills> lp: #1848001
[14:19] <ubot5> Launchpad bug 1848001 in steam (Ubuntu) "libnvidia-gl-435:i386 not installed from Ubiquity checkbox in 19.10 beta" [Undecided,Confirmed] https://launchpad.net/bugs/1848001
[14:19] <infinity> And budgie, I think.
[14:38] <jamespage> infinity: openstack have released today so coreycb,sahid and I will work to get it all done by EOD
[14:39] <jamespage> I don't believe we have anything that's seeded for a cloud-image or an ISO in the openstack package set
[14:40] -queuebot:#ubuntu-release- Unapproved: qr-tools (eoan-proposed/universe) [2.0~bzr33-1~build2 => 2.0~bzr33-2] (no packageset) (sync)
[14:41] -queuebot:#ubuntu-release- Unapproved: accepted qr-tools [sync] (eoan-proposed) [2.0~bzr33-2]
[14:43] <jamespage> however we do have seeded/in main packages which will need a release team ack
[14:43] <philroche> Hey all. RE Eoan cloud images release. Myself davidkrauser and patviafore from CPC team are running the cloud image release. Ping us (or cpc-help) if you have any Eoan cloud image release related questions/news/bugs.
[14:43] <jamespage> but these uploads should be version change only (or thereabouts)
[14:44] <tdaitx> sil2100: thanks for the openjdk-lts approval
[14:44] <philroche> Also please keep us in the loop should there be any respins required
[14:44] -queuebot:#ubuntu-release- Unapproved: rejected simplestreams [source] (xenial-proposed) [0.1.0~bzr426-0ubuntu1.4]
[14:52] -queuebot:#ubuntu-release- Unapproved: rejected ubiquity [source] (eoan-proposed) [19.10.21]
[14:52] <davidkrauser> We will also be running the HyperV Gallery desktop image releases, so please keep us in the loop for any desktop packages that trigger a respin, too.
[14:53] <sil2100> philroche: sure, right now we will still respin, and I guess the wslu package is still in eoan-proposed which might be relevant to you guys
[14:54] <philroche> sil2100: Thanks
[14:54] <sil2100> It's all a bit vague and confusing currently
[14:55] <vorlon> LocutusOfBorg: apologies, if you had discussed it (qrencode), there had been so much traffic after that it fell out of my lastlog
[14:56] <bdmurray> sil2100 means we are making progress there are just a few moving pieces.
[14:56] <sil2100> Yes
[14:56] <vorlon> LocutusOfBorg: as for it being released after a respin was needed... it hasn't though, qrencode 4.0.2-2 is sitting blocked in -proposed still
[14:58] <vorlon> LocutusOfBorg: well, I went back and looked and I still don't see any discussion from you in this channel about why the qrencode update is final-freeze appropriate
=== bdmurray_ is now known as bdmurray
[15:09] <LocutusOfBorg> vorlon, you are right, I was talking wrt qr-tools, not qrencode
[15:09] <jibel> infinity, ping me when there is something to review
[15:10] <xnox> cjwatson:  armhf+omap4:arm64 to support armhf expansions with arm64 multiarch =)))))
[15:10] <cjwatson> /ignore xnox
[15:13] -queuebot:#ubuntu-release- Unapproved: octavia (eoan-proposed/universe) [5.0.0~rc2-0ubuntu1 => 5.0.0-0ubuntu1] (no packageset)
[15:14] -queuebot:#ubuntu-release- Unapproved: accepted octavia [source] (eoan-proposed) [5.0.0-0ubuntu1]
[15:14] -queuebot:#ubuntu-release- Unapproved: networking-bagpipe (eoan-proposed/universe) [11.0.0~rc1-0ubuntu1 => 11.0.0-0ubuntu1] (no packageset)
[15:15] <LocutusOfBorg> in any case, I did while looking at the python qr library, and discovered that it was bringing a crash fix, minimal... it can be blocked, I don't care if it isn't in the iso, the other qr libraries are now ok, and we can live with a crash on eoan
[15:15] -queuebot:#ubuntu-release- Unapproved: accepted networking-bagpipe [source] (eoan-proposed) [11.0.0-0ubuntu1]
[15:15] -queuebot:#ubuntu-release- Unapproved: networking-odl (eoan-proposed/universe) [1:15.0.0~rc1-0ubuntu1 => 1:15.0.0-0ubuntu1] (no packageset)
[15:15] -queuebot:#ubuntu-release- Unapproved: networking-bgpvpn (eoan-proposed/universe) [11.0.0~rc1-0ubuntu1 => 11.0.0-0ubuntu1] (no packageset)
[15:16] -queuebot:#ubuntu-release- Unapproved: accepted networking-bgpvpn [source] (eoan-proposed) [11.0.0-0ubuntu1]
[15:16] -queuebot:#ubuntu-release- Unapproved: networking-ovn (eoan-proposed/universe) [7.0.0~rc1-0ubuntu2 => 7.0.0-0ubuntu1] (no packageset)
[15:16] -queuebot:#ubuntu-release- Unapproved: accepted networking-odl [source] (eoan-proposed) [1:15.0.0-0ubuntu1]
[15:17] -queuebot:#ubuntu-release- Unapproved: accepted networking-ovn [source] (eoan-proposed) [7.0.0-0ubuntu1]
[15:17] -queuebot:#ubuntu-release- Unapproved: networking-sfc (eoan-proposed/universe) [9.0.0~rc1-0ubuntu1 => 9.0.0-0ubuntu1] (no packageset)
[15:18] -queuebot:#ubuntu-release- Unapproved: accepted networking-sfc [source] (eoan-proposed) [9.0.0-0ubuntu1]
[15:19] -queuebot:#ubuntu-release- Unapproved: neutron-dynamic-routing (eoan-proposed/universe) [2:15.0.0~rc1-0ubuntu1 => 2:15.0.0-0ubuntu1] (no packageset)
[15:20] -queuebot:#ubuntu-release- Unapproved: accepted neutron-dynamic-routing [source] (eoan-proposed) [2:15.0.0-0ubuntu1]
[15:20] -queuebot:#ubuntu-release- Unapproved: neutron-vpnaas (eoan-proposed/main) [2:15.0.0~rc1-0ubuntu1 => 2:15.0.0-0ubuntu1] (openstack, ubuntu-server)
[15:20] -queuebot:#ubuntu-release- Unapproved: neutron-fwaas (eoan-proposed/main) [1:15.0.0~rc1-0ubuntu3 => 1:15.0.0-0ubuntu1] (openstack, ubuntu-server)
[15:21] -queuebot:#ubuntu-release- Unapproved: glance (eoan-proposed/main) [2:19.0.0~rc1-0ubuntu2 => 2:19.0.0-0ubuntu1] (openstack, ubuntu-server)
[15:22] -queuebot:#ubuntu-release- Unapproved: rejected python3.7 [source] (eoan-proposed) [3.7.5-1]
[15:22] <vorlon> doko: your python3.7 upload appears to have not been generated on Ubuntu, the Launchpad-Bugs header is missing from the .changes file.
[15:22] -queuebot:#ubuntu-release- Unapproved: cinder (eoan-proposed/main) [2:15.0.0~rc1-0ubuntu1 => 2:15.0.0-0ubuntu1] (openstack, ubuntu-server)
[15:22] -queuebot:#ubuntu-release- Unapproved: octavia-dashboard (eoan-proposed/universe) [4.0.0~rc1-0ubuntu1 => 4.0.0-0ubuntu1] (no packageset)
[15:23] -queuebot:#ubuntu-release- Unapproved: accepted octavia-dashboard [source] (eoan-proposed) [4.0.0-0ubuntu1]
[15:58] -queuebot:#ubuntu-release- Unapproved: accepted openscap [source] (bionic-proposed) [1.2.15-1ubuntu0.1]
[15:59] -queuebot:#ubuntu-release- Unapproved: accepted openscap [source] (xenial-proposed) [1.2.8-1ubuntu0.2]
[15:59] -queuebot:#ubuntu-release- Unapproved: unattended-upgrades (eoan-proposed/main) [1.14ubuntu1 => 1.14ubuntu1.1] (core)
[15:59] <rbalint> ^ only for sru after the release, to let me include the fix in other srus
[16:04] -queuebot:#ubuntu-release- Unapproved: keystone (eoan-proposed/main) [2:16.0.0~rc1-0ubuntu1 => 2:16.0.0-0ubuntu1] (openstack, ubuntu-server)
[16:05] -queuebot:#ubuntu-release- Unapproved: neutron (eoan-proposed/main) [2:15.0.0~rc1-0ubuntu1 => 2:15.0.0-0ubuntu1] (openstack, ubuntu-server)
[16:09] -queuebot:#ubuntu-release- Unapproved: nova (eoan-proposed/main) [2:20.0.0~rc1-0ubuntu3 => 2:20.0.0-0ubuntu1] (openstack, ubuntu-server)
[16:12] -queuebot:#ubuntu-release- Unapproved: swift (eoan-proposed/main) [2.22.0-0ubuntu2 => 2.23.0-0ubuntu1] (openstack)
[16:19] -queuebot:#ubuntu-release- Unapproved: zaqar (eoan-proposed/universe) [9.0.0~rc1-0ubuntu1 => 9.0.0-0ubuntu1] (no packageset)
[16:19] -queuebot:#ubuntu-release- Unapproved: accepted zaqar [source] (eoan-proposed) [9.0.0-0ubuntu1]
[16:20] <infinity> jibel: Check the zsys-swap branch in ubiquity git.
[16:20] -queuebot:#ubuntu-release- Unapproved: placement (eoan-proposed/universe) [2.0.0~rc1-0ubuntu2 => 2.0.0-0ubuntu1] (no packageset)
[16:21] -queuebot:#ubuntu-release- Unapproved: accepted placement [source] (eoan-proposed) [2.0.0-0ubuntu1]
[16:23] <jibel> infinity, ok
[16:23] -queuebot:#ubuntu-release- Unapproved: horizon (eoan-proposed/main) [3:16.0.0~rc1-0ubuntu1 => 3:16.0.0-0ubuntu1] (openstack, ubuntu-server)
[16:23] -queuebot:#ubuntu-release- Unapproved: senlin (eoan-proposed/universe) [8.0.0~rc1-0ubuntu2 => 8.0.0-0ubuntu1] (no packageset)
[16:24] -queuebot:#ubuntu-release- Unapproved: accepted senlin [source] (eoan-proposed) [8.0.0-0ubuntu1]
[16:26] -queuebot:#ubuntu-release- Unapproved: panko (eoan-proposed/universe) [7.0.0~rc1-0ubuntu1 => 7.0.0-0ubuntu1] (no packageset)
[16:26] -queuebot:#ubuntu-release- Unapproved: sahara (eoan-proposed/universe) [1:11.0.0~rc1-0ubuntu3 => 1:11.0.0-0ubuntu1] (openstack)
[16:26] -queuebot:#ubuntu-release- Unapproved: accepted panko [source] (eoan-proposed) [7.0.0-0ubuntu1]
[16:26] -queuebot:#ubuntu-release- Unapproved: openstack-trove (eoan-proposed/universe) [1:12.0.0~rc1-0ubuntu4 => 1:12.0.0-0ubuntu1] (no packageset)
[16:27] -queuebot:#ubuntu-release- Unapproved: accepted openstack-trove [source] (eoan-proposed) [1:12.0.0-0ubuntu1]
[16:28] -queuebot:#ubuntu-release- Unapproved: murano-agent (eoan-proposed/universe) [1:4.0.0~rc1-0ubuntu1 => 1:4.0.0-0ubuntu1] (no packageset)
[16:28] -queuebot:#ubuntu-release- Unapproved: accepted murano-agent [source] (eoan-proposed) [1:4.0.0-0ubuntu1]
[16:28] -queuebot:#ubuntu-release- Unapproved: murano (eoan-proposed/universe) [1:8.0.0~rc1-0ubuntu1 => 1:8.0.0-0ubuntu1] (openstack)
[16:29] -queuebot:#ubuntu-release- Unapproved: masakari-monitors (eoan-proposed/universe) [8.0.0~rc1-0ubuntu1 => 8.0.0-0ubuntu1] (no packageset)
[16:30] -queuebot:#ubuntu-release- Unapproved: accepted masakari-monitors [source] (eoan-proposed) [8.0.0-0ubuntu1]
[16:30] <doko> vorlon: which one?
[16:31] -queuebot:#ubuntu-release- Unapproved: mistral (eoan-proposed/universe) [9.0.0~rc1-0ubuntu1 => 9.0.0-0ubuntu1] (no packageset)
[16:31] -queuebot:#ubuntu-release- Unapproved: masakari (eoan-proposed/universe) [8.0.0~rc1-0ubuntu1 => 8.0.0-0ubuntu1] (no packageset)
[16:31] -queuebot:#ubuntu-release- Unapproved: accepted masakari [source] (eoan-proposed) [8.0.0-0ubuntu1]
[16:31] -queuebot:#ubuntu-release- Unapproved: accepted mistral [source] (eoan-proposed) [9.0.0-0ubuntu1]
[16:32] <jibel> infinity, first look, it seems fine. did you test it and if sop which setup?
[16:32] <jibel> so*
[16:33] -queuebot:#ubuntu-release- Unapproved: magnum (eoan-proposed/universe) [9.0.0~rc1-0ubuntu1 => 9.0.0-0ubuntu1] (no packageset)
[16:33] <infinity> jibel: We've tested both EFI and MBR.  Can you think of any things you'd want to do otherwise?
[16:33] -queuebot:#ubuntu-release- Unapproved: accepted magnum [source] (eoan-proposed) [9.0.0-0ubuntu1]
[16:33] -queuebot:#ubuntu-release- Unapproved: manila (eoan-proposed/universe) [1:9.0.0~rc1-0ubuntu2 => 1:9.0.0-0ubuntu1] (openstack)
[16:36] <jibel> infinity, no, I see some check missing to ensure we don't use the same number for different types of partition since you do a bpool - 1 for the swap but it was not there before, it's fine this way.
[16:36] -queuebot:#ubuntu-release- Unapproved: heat (eoan-proposed/main) [1:13.0.0~rc1-0ubuntu1 => 1:13.0.0-0ubuntu1] (openstack, ubuntu-server)
[16:37] -queuebot:#ubuntu-release- Unapproved: designate (eoan-proposed/main) [1:9.0.0~rc1-0ubuntu1 => 1:9.0.0-0ubuntu1] (openstack, ubuntu-server)
[16:39] -queuebot:#ubuntu-release- Unapproved: ceilometer (eoan-proposed/main) [1:13.0.0~rc1-0ubuntu1 => 1:13.0.0-0ubuntu1] (openstack, ubuntu-server)
[16:41] -queuebot:#ubuntu-release- Unapproved: barbican (eoan-proposed/main) [1:9.0.0~rc1-0ubuntu1 => 1:9.0.0-0ubuntu1] (openstack, ubuntu-server)
[16:42] -queuebot:#ubuntu-release- Unapproved: aodh (eoan-proposed/main) [9.0.0~rc1-0ubuntu1 => 9.0.0-0ubuntu1] (openstack, ubuntu-server)
[16:44] -queuebot:#ubuntu-release- Unapproved: ubiquity (eoan-proposed/main) [19.10.20 => 19.10.21] (core)
[16:45] -queuebot:#ubuntu-release- Unapproved: sahara-dashboard (eoan-proposed/universe) [11.0.0~rc1-0ubuntu1 => 11.0.0-0ubuntu1] (no packageset)
[16:47] -queuebot:#ubuntu-release- Unapproved: accepted sahara-dashboard [source] (eoan-proposed) [11.0.0-0ubuntu1]
[16:49] <bdmurray> vorlon: What was your concern with the shim-signed bugs?
[16:52] <Wimpress> https://bugs.launchpad.net/ubuntu-mate/+bug/1848001
[16:52] <ubot5> Launchpad bug 1848001 in steam (Ubuntu) "libnvidia-gl-435:i386 not installed from Ubiquity checkbox in 19.10 beta" [Undecided,Confirmed]
[16:52] <Wimpress> infinity: ^
[16:54] -queuebot:#ubuntu-release- Unapproved: accepted ubiquity [source] (eoan-proposed) [19.10.21]
[16:55] -queuebot:#ubuntu-release- Unapproved: accepted neutron-fwaas [source] (eoan-proposed) [1:15.0.0-0ubuntu1]
[16:55] -queuebot:#ubuntu-release- Unapproved: accepted neutron-vpnaas [source] (eoan-proposed) [2:15.0.0-0ubuntu1]
[16:57] -queuebot:#ubuntu-release- Unapproved: hugin (eoan-proposed/universe) [2019.0.0+dfsg-2 => 2019.0.0+dfsg-4] (kubuntu) (sync)
[16:58] -queuebot:#ubuntu-release- Unapproved: murano-dashboard (eoan-proposed/universe) [1:8.0.0~rc1-0ubuntu1 => 1:8.0.0-0ubuntu1] (openstack)
[17:00] -queuebot:#ubuntu-release- Unapproved: heat-dashboard (eoan-proposed/universe) [2.0.0~rc1-0ubuntu1 => 2.0.0-0ubuntu1] (no packageset)
[17:00] -queuebot:#ubuntu-release- Unapproved: accepted heat-dashboard [source] (eoan-proposed) [2.0.0-0ubuntu1]
[17:03] -queuebot:#ubuntu-release- Unapproved: accepted keystone [source] (eoan-proposed) [2:16.0.0-0ubuntu1]
[17:05] <sil2100> coreycb: hey! Looking at the openstack packages, at glance right now, and I see the po files for releasenotes have been dropped - wanted to make sure that's intentional?
[17:06] -queuebot:#ubuntu-release- Unapproved: designate-dashboard (eoan-proposed/universe) [9.0.0~rc1-0ubuntu1 => 9.0.0-0ubuntu1] (no packageset)
[17:06] -queuebot:#ubuntu-release- Unapproved: accepted designate-dashboard [source] (eoan-proposed) [9.0.0-0ubuntu1]
[17:11] <sil2100> I'll assume that it's all intentional, since I see similar changes for other packages as well
[17:11] <coreycb> sil2100: I think it's fine
[17:11] <coreycb> sil2100: some of them at least have just moved location
[17:13] <sil2100> coreycb: for example, http://launchpadlibrarian.net/446874990/glance_2%3A19.0.0~rc1-0ubuntu2_2%3A19.0.0-0ubuntu1.diff.gz <- looks like those just got removed
[17:13] <sil2100> releasenotes/source/locale/en_GB/LC_MESSAGES/releasenotes.po and releasenotes/source/locale/ja/LC_MESSAGES/releasenotes.po for instance
[17:16] <coreycb> sil2100: I'm not exactly sure why they removed those but it does match in the upstream glance release tarball.
[17:16] <sil2100> coreycb: ok, proceeding then o/
[17:16] <coreycb> sil2100: thanks very much
[17:17] -queuebot:#ubuntu-release- Unapproved: accepted glance [source] (eoan-proposed) [2:19.0.0-0ubuntu1]
[17:19] <doko> coreycb: are these packages on any images?
[17:20] <coreycb> doko: I'm not entirely sure how to check to be honest but jamesp mentioned earlier that I don't believe we have anything that's seeded for a cloud-image or an ISO in the openstack package set
[17:20] -queuebot:#ubuntu-release- Unapproved: accepted cinder [source] (eoan-proposed) [2:15.0.0-0ubuntu1]
[17:24] -queuebot:#ubuntu-release- Unapproved: accepted neutron [source] (eoan-proposed) [2:15.0.0-0ubuntu1]
[17:26] -queuebot:#ubuntu-release- Unapproved: accepted nova [source] (eoan-proposed) [2:20.0.0-0ubuntu1]
[17:28] -queuebot:#ubuntu-release- Unapproved: distro-info-data (eoan-proposed/main) [0.40ubuntu2 => 0.40ubuntu3] (core)
[17:29] <vorlon> doko: the python3.7/3.7.5-1ubuntu1 upload.  Bug is listed in the changelog, but not in the .changes file; so it'll need reuploaded (which I'll do if you don't)
[17:30] <vorlon> bdmurray: concern with the shim-signed bugs> well, jibel filed one of them, and I was asking for his help diagnosing since it probably requires a desktop install on nvidia hardware to reproduce
[17:30] <doko> vorlon: ok, re-uploading
[17:30] -queuebot:#ubuntu-release- Unapproved: watcher (eoan-proposed/universe) [1:3.0.0~rc1-0ubuntu1 => 1:3.0.0-0ubuntu1] (no packageset)
[17:30] <vorlon> bdmurray: and there's been a run of these bug reports with the same symptom in the past month, so it's probably a regression
[17:31] -queuebot:#ubuntu-release- Unapproved: accepted watcher [source] (eoan-proposed) [1:3.0.0-0ubuntu1]
[17:32] -queuebot:#ubuntu-release- Unapproved: accepted distro-info-data [source] (eoan-proposed) [0.40ubuntu3]
[17:32] <infinity> vorlon: Do you have any handle on what the bug is and/or how to fix it?  And are you considering it RC?  Cause we're running very short on time.
[17:33] <vorlon> infinity: nope
[17:33] <infinity> Was that two nopes or one?
[17:33] <vorlon> infinity: as many as you need
[17:33] <vorlon> 'yes nope'
[17:33] -queuebot:#ubuntu-release- Unapproved: accepted horizon [source] (eoan-proposed) [3:16.0.0-0ubuntu1]
[17:34] <infinity> vorlon: I appreciate the clarity in your communication.
[17:34] -queuebot:#ubuntu-release- Unapproved: accepted sahara [source] (eoan-proposed) [1:11.0.0-0ubuntu1]
[17:35] -queuebot:#ubuntu-release- Unapproved: accepted murano [source] (eoan-proposed) [1:8.0.0-0ubuntu1]
[17:35] <vorlon> infinity: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1848142 there's a non-zero exit from a shim-signed maintainer script; probably in a trigger; no output in the apt logs; the system successfully installed and booted and the nvidia module is loaded; but SecureBoot is disabled on the machine in question
[17:35] <ubot5> Launchpad bug 1848142 in shim-signed (Ubuntu) "package shim-signed 1.39+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1" [Undecided,New]
[17:36] -queuebot:#ubuntu-release- Unapproved: accepted manila [source] (eoan-proposed) [1:9.0.0-0ubuntu1]
[17:36] -queuebot:#ubuntu-release- Unapproved: python3.7 (eoan-proposed/main) [3.7.5~rc1-2 => 3.7.5-1ubuntu1] (core)
[17:36] -queuebot:#ubuntu-release- Unapproved: accepted designate [source] (eoan-proposed) [1:9.0.0-0ubuntu1]
[17:37] -queuebot:#ubuntu-release- Unapproved: accepted heat [source] (eoan-proposed) [1:13.0.0-0ubuntu1]
[17:37] <vorlon> (and it looks like SB is disabled via mok, given the combination of the SecureBoot efi variable and the kernel log)
[17:37] -queuebot:#ubuntu-release- Unapproved: rejected python3.7 [source] (eoan-proposed) [3.7.5-1ubuntu1]
[17:38] -queuebot:#ubuntu-release- Unapproved: accepted ceilometer [source] (eoan-proposed) [1:13.0.0-0ubuntu1]
[17:38] -queuebot:#ubuntu-release- Unapproved: accepted barbican [source] (eoan-proposed) [1:9.0.0-0ubuntu1]
[17:38] <cyphermox> vorlon: I think we'll want to check update-secureboot-policy first; with SB disabled it should just return 0
[17:38] <cyphermox> and well, it's what does the heavy lifting anyway
[17:39] -queuebot:#ubuntu-release- Unapproved: accepted aodh [source] (eoan-proposed) [9.0.0-0ubuntu1]
[17:40] -queuebot:#ubuntu-release- Unapproved: accepted murano-dashboard [source] (eoan-proposed) [1:8.0.0-0ubuntu1]
[17:53] <vorlon> Laney: there were other safe/opportunistic uploads in -proposed that could've been accepted, had it been communicated here that a respin was coming (six - but not the python-defaults doko was also after, which still has untriaged autopkgtest regressions)
[17:54] <Laney> vorlon: There's still time if you'd like to add more unblocks
[17:55] <doko> so not communicated?
[17:55] <vorlon> Laney: ok
[17:55] <doko> vorlon: then please accept the python3.7 sync, not the upload with the ubuntu diff
[17:55] <vorlon> doko: no
[17:55] <doko> ?
[17:56] <vorlon> the package needs to 1) build, 2) trigger autopkgtests, 3) be evaluated to see if there's a window for it to be included.  It has already missed the current window.
[17:56] <vorlon> it needs to be SRU-ready to be accepted now
[17:56] <cjwatson> What was the point of rebuilding six?
[17:56] <cjwatson> The changelog is, err, not communicative
[17:57] <vorlon> hmm quite
[17:57] <doko> six can be dropped. LocutusOfBorg claimed a rebuild was needed
[17:57] -queuebot:#ubuntu-release- Unapproved: vmware-nsx (eoan-proposed/universe) [14.0.0~b1~git2019062013.30eab6bb8-0ubuntu2 => 15.0.0~git2019101612.8364a82f3-0ubuntu1] (no packageset)
[17:57] <vorlon> dropping my unblock then
[17:58] <vorlon> and if I had seen that in the unapproved queue I would've rejected it
[17:58] -queuebot:#ubuntu-release- Unapproved: accepted vmware-nsx [source] (eoan-proposed) [15.0.0~git2019101612.8364a82f3-0ubuntu1]
[17:58] <infinity> vorlon: Yeah, I'd really like to know who accepted it.
[18:00] -queuebot:#ubuntu-release- Unapproved: accepted python3.7 [source] (eoan-proposed) [3.7.5-1ubuntu1]
[18:02] <doko> vorlon: then please do the same for python3-stdlib-extensions, not affecting 3.7, only 3.8
[18:03]  * vorlon nods
[18:03] <vorlon> reviewing
[18:04] <infinity> "not affecting 3.7", but it ships 3.7 packages...
[18:05] -queuebot:#ubuntu-release- Unapproved: rejected python3-stdlib-extensions [source] (eoan-proposed) [3.7.5-1]
[18:06] <doko> would be nice to look at the changes before commenting ...
[18:08] <infinity> doko: Sure, the changes don't affect the 3.7 packages, but there are 3.7 packages, which will have new versions, and said packages are seeded on images, so "not affecting 3.7" isn't helpful data right now. :P
[18:08] <cjwatson> Though perhaps the changelog shouldn't have said "Update 3.7 extensions and modules to 3.7.5 release" when 3.7 wasn't affected
[18:09] <sil2100> infinity: the swift upload is a bump from 2.22 to 2.23 - trying to determine if it has any features or just bug-fixes
[18:09] <doko> infinity: well, why not communicate that all images need rebuilding? or why not do a distro-info-data upload as a SRU ...
[18:10] <doko> cjwatson: agreed, a "(no changes)" affix wouldn't hurt
[18:11] <infinity> doko: You want me to tell you every time we're rebuilding images?
[18:11] <infinity> doko: Hey.  We're planning to rebuild images soon.
[18:11] <doko> infinity: yes, if that's the reason that packages are hold back
[18:12] <infinity> doko: Eh?  It was communicated that those python uploads would be done as SRUs.  Nothing's changed there.  There's nothing special about them that should change that.
[18:14] <infinity> doko: Sure, distro-info-data could have been an SRU, but it's a tiny package that tests quickly, is obviously reviewable and auditable by humans even without testing, and is almost certainly less prone to problem than a new python at the 0-hour.
[18:14] <doko> so we have an openjdl-lts upload which definitely takes longer to build than a python upload, and that has other criteria?
[18:15] <doko> sorry guys, but you reason to accept/reject need some kind of rationale
[18:15] <infinity> doko: "It's still in the queue" isn't a rejection.  It's that no one's reviewed it.
[18:16] <infinity> doko: If you mean accepted or rejected for release versus SRU, no one's promised that openjdk-lts will end up in the release pocket.
[18:16] <infinity> doko: But also, it's not on media.
[18:16] -queuebot:#ubuntu-release- Unapproved: trove-dashboard (eoan-proposed/universe) [13.0.0~rc1-0ubuntu1 => 13.0.0-0ubuntu1] (no packageset)
[18:17] <doko> no, it's not in the queue
[18:17] <infinity> doko: "it"?
[18:17] <doko> openjdk-lts
[18:17] -queuebot:#ubuntu-release- Unapproved: accepted trove-dashboard [source] (eoan-proposed) [13.0.0-0ubuntu1]
[18:17] <infinity> doko: I know, it's in proposed.  You were suggesting we've "rejected" python while "accepting" openjdk.  I've told you that "still in the queue" isn't a reject.
[18:18] <LocutusOfBorg> doko, six will migrate in some minutes
[18:18] <infinity> doko: Which was the state of python3.7 until Steve accepted it.
[18:18] <doko> infinity: what do you mean "in queue"?
[18:18] <doko> mea by ...
[18:18] <infinity> ...
[18:18] <LocutusOfBorg> and it wasn't  me claiming that... :)
[18:19] <doko> infinity: "in the unapproved queue"
[18:19] <infinity> Yes...
[18:19] -queuebot:#ubuntu-release- Unapproved: zvmcloudconnector (eoan-proposed/main) [2.0.0~b1~git2019062011.4fc9142-0ubuntu1 => 1:1.4.1-0ubuntu2] (ubuntu-server)
[18:20] <infinity> What are you suggesting we "rejected" that has your knickers in a twist about our process that you'd clearly do better if you were king of all releases?
[18:21] <infinity> Is it the python that Steve accepted for SRU, or the stdlib-extension which is still in the queue (but i assume he's reviewing it for the same)?
[18:21] <doko> infinity: please could you calm down and repeat your comment in a form which can be interpreted by non-canadian speakers?
[18:21] <infinity> doko: I'm quoting you, FFS.  You didn't understand what you said?
[18:21] <vorlon> doko: python3-stdlib-extensions had the same problem, launchpad bug field not in changes.  I've reuploaded it myself, with a build1 instead of ubuntu1 since that's more accurate, and will re-review shortly.
[18:21] <infinity> 12:15 < doko> sorry guys, but you reason to accept/reject need some kind of rationale
[18:22] <doko> vorlon: ta
[18:22] -queuebot:#ubuntu-release- Unapproved: rejected python3-stdlib-extensions [source] (eoan-proposed) [3.7.5-1ubuntu1]
[18:28] -queuebot:#ubuntu-release- Unapproved: vmware-nsx (eoan-proposed/universe) [15.0.0~git2019101612.8364a82f3-0ubuntu1 => 15.0.0~git2019101612.8364a82f3-0ubuntu2] (no packageset)
[18:29] -queuebot:#ubuntu-release- Unapproved: accepted vmware-nsx [source] (eoan-proposed) [15.0.0~git2019101612.8364a82f3-0ubuntu2]
[18:30] -queuebot:#ubuntu-release- Unapproved: python3-stdlib-extensions (eoan-proposed/main) [3.7.5~rc1-1 => 3.7.5-1build1] (core)
[18:40] <cjwatson> I've done most of a process-removals run
[18:42] -queuebot:#ubuntu-release- Unapproved: accepted swift [source] (eoan-proposed) [2.23.0-0ubuntu1]
[18:43] <sil2100> cjwatson: thanks o/
[18:44] <sil2100> ew, epoch addition to zvmcloudconnector
[18:50] <sil2100> coreycb: hm, the version change to zvmcloudconnector feels weird - so in other words, we already had 1.4.1, but now we have a 'new upstream release' that's 1.4.1 just with an epoch?
[18:50] <sil2100> coreycb: I mean, shouldn't it be something like 1:1.4.2 or something like that if it's supposed to be a new upstream release?
[18:51] <coreycb> sil2100: yes it's very weird but we got ourselves into a bad spot with that and doing git snapshots this cycle
[18:55] <sil2100> coreycb: yes, but what I mean is, the changelog mentions 'New upstream release for OpenStack Train', but version-wise, besides the epoch (which is a debian-package version thing, not upstream related), the current version is the same as what we had previously
[18:56] <sil2100> coreycb: but this is a new upstream release, right? Or is it a 'revert' back to the 1.4.1 that was there previously?
[18:58] <wxl> what are we planning on respinning for ubiquity?
[18:59] <wxl> err what are we trying to solve XD
[19:02] <sil2100> wxl: the most important thing is zfs swap-handling, switching it to using a swap partition instead of a zvol for swap
[19:02] <sil2100> LP: #1847628
[19:02] <ubot5> Launchpad bug 1847628 in ubiquity (Ubuntu) "When using swap in ZFS, system stops when you start using swap" [High,Triaged] https://launchpad.net/bugs/1847628
[19:02] <wxl> sil2100: is that the only thing? if so, lubuntu doesn't need a respin.
[19:05] <sil2100> wxl: there's one more change in ubiquity regarding the package installation, but I guess lubuntu uses calamares, right? Anyway, infinity probably has a better handle on what has been let into the archives
[19:06] <sil2100> We did allow some other seeded bits into release while we were at it, and since all images need to be in sync with the archive when we snapshot, there might be something that might have affected lubuntu images
[19:06] <wxl> sil2100: yeah that's right, it uses calamares, so it shouldn't be relevan.
[19:06] <wxl> fair enough
[19:06] <wxl> it's good to know what to look for of course :)
[19:12] <vorlon> cjwatson: process-removals> hmm I had been abstaining on account of the impact python2 removals had been having on autopkgtests
[19:13] <doko> well, it's a lost battle for eoan, and it will get worse for f
[19:14] <vorlon> it wasn't a lost battle; we had gotten to a reasonably steady-state.  Now we are likely to see a number of new autopkgtest regressions only during SRU
[19:15] <doko> that's not true. the only thing you know is what is failing with the current state
[19:16] <vorlon> how is that different from what I said?
[19:16] <doko> you don't have any means to refer to that for any eoan SRU
[19:17] <vorlon> I don't know what point you're trying to make.  The archive is the baseline against which SRUs are measured.  Removing more packages, day before release, means the baseline has moved but we haven't re-tested
[19:17] <vorlon> that means we're going to be dealing with fallout during SRUs, which we otherwise wouldn't have been
[19:19] <doko> well, if we need to have an eoan test rebuild, then it shouldnt show any more regresssions? compared to what?
[19:20] -queuebot:#ubuntu-release- Unapproved: accepted python3-stdlib-extensions [source] (eoan-proposed) [3.7.5-1build1]
[19:20] <doko> but anyway, that's not related to the eoan, don't let#s disturb the eoan release party
[19:21] <Wimpress> wxl: and also for seeded nvidia drivers.
[19:46] -queuebot:#ubuntu-release- Unapproved: unity-control-center (eoan-proposed/universe) [15.04.0+19.04.20190209-0ubuntu5 => 15.04.0+19.10.20190921-0ubuntu1] (mythbuntu, ubuntukylin)
[19:53] <vorlon> Laney, infinity: python-defaults would be releasable now (with a skiptest of the two remaining armhf autopkgtests which I'm confident will pass but are currently stuck in a non-empty queue).  But I don't know whether the window has passed for accepting additional seeded packages
[19:54] <vorlon> oh, it evidently hasn't, since distro-info-data is still waiting for tests also
[19:57] <vorlon> Laney, infinity: ^^ the armhf tests are reasonable to skip for distro-info-data IMHO; I don't know what the critical chain is for respins, but I guess we at least need a ubiquity somewhere along there
[19:59] <vorlon> oh, that's ubiquity 19.10.21 which is already in proposed; and we should definitely not block on *its* armhf tests when we build no armhf images that use it
[19:59] <coreycb> hi release team, I've re-uploaded zvmcloudconnector with an updated changelog per sil2100's comments above
[20:00] -queuebot:#ubuntu-release- Unapproved: zvmcloudconnector (eoan-proposed/main) [2.0.0~b1~git2019062011.4fc9142-0ubuntu1 => 1:1.4.1-0ubuntu2] (ubuntu-server)
[20:01] -queuebot:#ubuntu-release- Unapproved: rejected zvmcloudconnector [source] (eoan-proposed) [1:1.4.1-0ubuntu2]
[20:01] <vorlon> Laney, infinity: I've skiptested ubiquity and distro-info-data which were only waiting for armhf test results.  I don't see any other pending unblocks.
[20:03] <vorlon> coreycb: bump epoch> is Debian on the same page wrt introducing an epoch?  Or are you comfortable having to manage this package indefinitely as being out of sync with Debian?  because introducing an epoch downstream of Debian is messy
[20:04] <coreycb> vorlon: Let me check, I didn't realize they had a package for this
[20:06] <vorlon> coreycb: even if they hadn't had one yet (which they do), an Ubuntu-specific epoch is still messy.  The other convention here would be to version it as 2.0.0~b1~git2019062011.4fc9142.really.1.4.1-0ubuntu2
[20:07] <coreycb> vorlon: ok. I hadn't considered that. I can see how that would be useful for not introducing an epoch.
[20:15] <mwhudson> +really is ugly but at least it goes away, epochs are forever :)
[20:15] <tsimonq2> infinity: Dibs on Focal's wiki.
[20:51] <coreycb> vorlon: I uploaded a new version of zvmcloudconnector based on what's in debian experimental but with tests enabled
[20:53] <coreycb> vorlon: urgh I need to update the version
[20:53] <coreycb> have to step out though
[20:54] -queuebot:#ubuntu-release- Unapproved: rejected pyjwt [source] (eoan-proposed) [1.7.0-2ubuntu1]
[20:55] -queuebot:#ubuntu-release- Unapproved: rejected zvmcloudconnector [source] (eoan-proposed) [1:1.4.1-0ubuntu2]
[20:56] -queuebot:#ubuntu-release- Unapproved: accepted unattended-upgrades [source] (eoan-proposed) [1.14ubuntu1.1]
[20:57] <seb128> the community people maintaining unity would probably appreciate if the unity-control-center from the queue is accepted before relase, it was part of a keybinding gsettings transition to move their own schemas that landed in septembre
[20:57] <seb128> but for some reason the bileto copy for that one failed and that went un-noticed since bileto stated it was copied with success
[20:57] <vorlon> seb128: looking
[20:57] <seb128> vorlon, thx
[20:58] <seb128> I just saw that a no change rebuild was uploaded since and that changelog entry is being dropped
[20:58] <seb128> that shouldn't be a problem but I can fix it if you prefer
[20:58] <seb128> vorlon, https://launchpad.net/ubuntu/+source/unity-settings-daemon/15.04.1+19.10.20190921-0ubuntu1 is the counterpart in the backend
[20:59] <vorlon> seb128: I'm guessing it was rejected because it collided with a no-change rebuild in the archive; I believe bileto is supposed to signal that error condition
[20:59] <seb128> vorlon, https://bileto.ubuntu.com/log/3812/publish/1/info/
[20:59] <seb128> is the publish log I had in my firefox history
[21:00] <seb128> unsure if we have data to figure out why that claims that the copy succeded when it didn't?
[21:00] -queuebot:#ubuntu-release- Unapproved: accepted unity-control-center [source] (eoan-proposed) [15.04.0+19.10.20190921-0ubuntu1]
[21:01] <vorlon> seb128: right; the date on the publish log is later than 15.04.0+19.04.20190209-0ubuntu5 so it probably was built, then the no-change rebuild happened, then the silo was published, and by policy I think we're supposed to refuse because of the changelog mismatch.  But the log certainly doesn't show this
[21:02] <seb128> right
[21:03] <seb128> vorlon, thx for the review!
[21:05] <seb128> vorlon, the bug received the SRU boilerplate, the archive is already locked for release including universe/unseeded packages?
[21:05] <seb128> ah, it's seeded on kylin and mythubuntu
[21:05] <seb128> ignore that
[21:06] <vorlon> seb128: I sent the boilerplate in case it didn't get tested etc in time
[21:06] <seb128> fair enough
[21:07] <vorlon> I didn't see it seeded on images fwiw
[21:10] <seb128> my comment is based on what the bot stated when the upload hit the queue
[21:13]  * vorlon nods
[21:26] <infinity> vorlon: Thanks for the skiptest on ubiquity while we were dinnering.
[21:26] <vorlon> n/p
[21:27] <infinity> A second set of eyes on excuses would be appreciated, but all I see that we're waiting to migrate are d-i-d and ubiquity, both of which have actually migrated, britney's just not caught up to reality.
[21:29] <infinity> Ahh, and python-defaults, same story (migrated, but britney slow)
[21:30]  * infinity checks bzr history to see if you snuck anything else in.
[21:31] <infinity> Alright, all the unblocks today have migrated.  Huzzah.
[21:32] <infinity> No more unblocks for seeded packages.
[21:57] -queuebot:#ubuntu-release- Builds: Ubuntu Base amd64 [Eoan Final] has been updated (20191016)
[21:57] -queuebot:#ubuntu-release- Builds: Ubuntu Base arm64 [Eoan Final] has been updated (20191016)
[21:57] -queuebot:#ubuntu-release- Builds: Ubuntu Base armhf [Eoan Final] has been updated (20191016)
[21:57] -queuebot:#ubuntu-release- Builds: Ubuntu Base i386 [Eoan Final] has been updated (20191016)
[21:57] -queuebot:#ubuntu-release- Builds: Ubuntu Base ppc64el [Eoan Final] has been updated (20191016)
[21:57] -queuebot:#ubuntu-release- Builds: Ubuntu Base s390x [Eoan Final] has been updated (20191016)
[22:02] <cjwatson> vorlon: I think the set of things I removed was likely to be mostly unproblematic, but apologies if not
[22:02] <cjwatson> They looked generally pretty leaf
[22:02] <cjwatson> (But it would definitely be nice if reverse-depends could tell us about this sort of thing)
[22:03] <cjwatson> Somebody did mention the autopkgtest issue in London, but it was after I was already mostly done :-/
[22:06] -queuebot:#ubuntu-release- Builds: Ubuntu Server amd64 [Eoan Final] has been updated (20191016)
[22:06] -queuebot:#ubuntu-release- Builds: Ubuntu Server arm64 [Eoan Final] has been updated (20191016)
[22:06] -queuebot:#ubuntu-release- Builds: Ubuntu Server ppc64el [Eoan Final] has been updated (20191016)
[22:06] -queuebot:#ubuntu-release- Builds: Ubuntu Server s390x [Eoan Final] has been updated (20191016)
[22:09] <vorlon> cjwatson: I thought tumbleweed had said reverse-depends support for checking test deps had landed, but I don't see it in the git repo or archive
[22:12] <vorlon> ah, it's shown via 'reverse-depends -a source'
[22:13] <vorlon> (not in eoan yet, only in git)
[22:13] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Eoan Final] has been updated (20191016)
[22:14] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Eoan Final] has been updated (20191016)
[22:14] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop amd64 [Eoan Final] has been updated (20191016)
=== guiverc2 is now known as guiverc
[22:16] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Eoan Final] has been updated (20191016)
[22:17]  * Wimpress waits patiently
[22:23] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Eoan Final] has been updated (20191016.5)
[22:23] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Eoan Final] has been updated (20191016)
[22:24] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD amd64 [Eoan Final] has been updated (20191016)
[22:26] -queuebot:#ubuntu-release- Unapproved: zvmcloudconnector (eoan-proposed/main) [2.0.0~b1~git2019062011.4fc9142-0ubuntu1 => 2.0.0~b1~git2019062011.4fc9142.really.1.4.1-0ubuntu2] (ubuntu-server)
[22:27] <coreycb> I think that's better ^ Thanks for the advice :)
[22:28] -queuebot:#ubuntu-release- Builds: Ubuntu Server arm64+raspi3 [Eoan Final] has been updated (20191016)
[22:28] -queuebot:#ubuntu-release- Builds: Ubuntu Server armhf+raspi3 [Eoan Final] has been updated (20191016)
[22:50] <Wimpress> ZFS install now creates a dedicate swap partition.
[23:06] <infinity> I should hope so, or I did all that for nothing. :)
[23:11] <mwhudson> 20191016.5
[23:11] <mwhudson> that's a sign of a busy day
[23:11] <infinity> mwhudson: It's a sign of testing debian-cd changes in production because that's the easiest way. :/
[23:11] <infinity> But also a busy day, yes.
[23:11] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity amd64 [Eoan Final] has been updated (20191016)
[23:11] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity arm64 [Eoan Final] has been updated (20191016)
[23:11] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity ppc64el [Eoan Final] has been updated (20191016)
[23:11] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity s390x [Eoan Final] has been updated (20191016)
[23:16] <Wimpress> Laney xnox Nice work on the nvidia i386 pool. All good here now.
[23:16] <infinity> Wimpress: That would be me.  But thanks!
[23:16]  * Wimpress hangs head in shame
[23:16] <infinity> Also, WTF why are lubuntu livefses suddenly failing to build? :(
[23:17] <Wimpress> Thanks infinity
[23:22] <ogra> Setting up lubuntu-grub-theme (19.10.3) ...
[23:22] <ogra> dpkg: error processing package lubuntu-grub-theme (--configure):
[23:22] <ogra>  installed lubuntu-grub-theme package post-installation script subprocess returned error exit status 1
[23:22] <ogra> infinity, ^^
[23:22] <ogra> thats why
[23:23] <infinity> ogra: I mean, yes, I can read.  I was trying to figure out why. :P
[23:23] <ogra> he
[23:23] <ogra> h
[23:23] <infinity> And "why" is because that package was added to their desktop task 9 hours ago.
[23:23] <infinity> tsimonq2: What have you done? :P
[23:23] <ogra> lovely !
[23:24] <infinity> tsimonq2: And can I just undo it?
[23:25] <popeytesting> 20191016.5 takes a long time to finish becoming "ready" - boot leaves me at 4 dots a long time, and once on desktop systemd-analyze blame says not ready for ages
[23:25] <popey> https://usercontent.irccloud-cdn.com/file/SN9cVD14/IMG_20191017_002426.jpg
[23:26] <popeytesting> I also have booted a usb stick I had lying around from a couple of days ago (last time I did a live stream) and it's much quicker to get to desktop
[23:27] <popeytesting> ^ that photo is 20191016.5 after 8 minutes
[23:27] <ogra> are you offline ?
[23:27] <popeytesting> yes
[23:27] <popeytesting> i was with previous usb too and it was way quicker
[23:27] <ogra> it seems the only running process is timesyncd
[23:27] <infinity> popeytesting: https://bugs.launchpad.net/ubuntukylin/+bug/1848346
[23:27] <ubot5> Launchpad bug 1848346 in Ubuntu Kylin "Boot into black screen" [Medium,New]
[23:27] <ogra> trying to set your clock from the network
[23:28] <infinity> Oh, or timesyncd if you're offline.
[23:28] <infinity> So maybe not that bug. :P
[23:28] <popeytesting> not sure it's that, no
[23:28] <infinity> ogra: But do you have any insight into people complaining that snappy's been off the rails for the last few days?
[23:28] <ogra> nope, havent heard anything
[23:28] <infinity> (off the rails == excessive CPU usage and slow boot times)
[23:29] <ogra> (but i'm less active there nowadays ... )
[23:29] <ogra> i'd expect some forum outcry though ... that i'd have seen
[23:29] <ogra> but there was nothing
[23:29] <popeytesting> I am not seeing high cpu on this fwiw
[23:29] <guiverc> popeytesting, this may be completely wrong, but I noted 1848333  (lp) wifi slow booting on lubu/xub
[23:29] <popeytesting> core i7 / 16GB / SSD
[23:30] <ogra> snapd is also not in the list on popeytesting's screenshot ...
[23:30] <popeytesting> i haven't attached to wifi at all, and no cable connected
[23:30] <wxl> yeah i was going to mention that http://launchpad.net/bugs/1848333
[23:30] <ubot5> Launchpad bug 1848333 in linux (Ubuntu) "wifi problem delays boot in live mode" [Undecided,Confirmed]
[23:30] <ogra> just the repairtimer but thats waiting
[23:30] <wxl> i had heard from others about problems with post-install boots, too, but nothing consistent
[23:31] <infinity> ogra: Yeah, I know, his bug is likely not the snappy one, I noted that already.
[23:31] <ogra> well, if there is a snapd one, ijohnson is surely still up and active (but not here)
[23:32] <infinity> ogra: Honestly, it's too late to beg for rollbacks if core's gone wonky anyway, I'm not rerolling ISOs unless something dire comes up.  Just irked that I didn't really hear about it until today (like everything on release week, right?)
[23:33] <ogra> heh, yeah ... well, i havent heard anything really
[23:33] <popeytesting> me either
[23:34] <popeytesting> put laptop online to let the jobs finish...
[23:34] <popey> https://usercontent.irccloud-cdn.com/file/UQ0YEeo4/IMG_20191017_003435.jpg
[23:35] <ogra> looks okayish ... apart from the 14min wait :P
[23:36] <wxl> i'm perplexed about the lubuntu-grub-theme thing
[23:36] <ogra> missing an || true in the postinst ?
[23:36] <wxl> should be this https://phab.lubuntu.me/rARTc7b5bed2ff91d1c410cd75328fb4431d69f40a1c#change-mvbFMsoVdp76
[23:36] <ogra> (grub itself seems to show the same error but it seems to be not fatal there)
[23:37] <ogra> Setting up grub-pc (2.04-1ubuntu12) ...
[23:37] <ogra> Creating config file /etc/default/grub with new version
[23:37] <ogra> grub-probe: error: cannot find a device for / (is /dev mounted?).
[23:37] <ogra> grub-probe: error: cannot find a device for /boot (is /dev mounted?).
[23:37] <wxl> it doesn't seem to be hitting the case wildcard
[23:37] <ogra> grub-probe: error: cannot find a device for /boot/grub (is /dev mounted?).
[23:37] <ogra> Setting up libreoffice-style-colibre (1:6.3.2-0ubuntu2) ...
[23:37] <ogra> same thing
[23:38] <wxl> oh that's fun
[23:38] <infinity> I mean, it's a chroot.
[23:39] <infinity> You can't update-grub in a chroot that doesn't have grub configured to boot anything. :P
[23:39] <wxl> thing is, though, it's been there for a while now, no?
[23:39] <infinity> But also, the seeds were updated without updating the metapackages.
[23:39] <infinity> wxl: A "while" being 9 hours?
[23:39] <wxl> 19.10.2
[23:39] <infinity> wxl: Simon added it to the desktop task TODAY.
[23:39] <wxl> ahhhh k sigh
[23:40] <infinity> wxl: And I'm inclined to just revert that to move on with the release.
[23:40] <wxl> seems that there's not going to be an easily solution otherwise
[23:40] <wxl> s/il//
[23:41] <ogra> well, ubquity runs update-grub anyway ... the easy fix would be to make sure its just skipped in chroot ...
[23:41] <ogra> *ubiquity
[23:41] <infinity> wxl: I mean, there are other solutions, like making update-grub's failure non-fatal in the postinst, but any solution other than "revert Simon's commit" also implies a package upload and migration (and, in fact, two packages, cause lubuntu-meta should be uploaded to match the seeds)
[23:41] <ogra> yeah ...
[23:42] <wxl> ogra: well, we're not using ubiquity but point taken :)
[23:42] <ogra> "your installer" then :)
[23:43] <wxl> i guess my feeling is that if you're anxious to release, it's not worth holding things up by
[23:44] <wxl> so i'd advise reverting away
[23:44] <infinity> wxl: I'm anxious to release in about 11.5 hours, give or take.  Work backwards from there if you want to keep iterating.
[23:44] <wxl> okie dokie
[23:44] <infinity> wxl: But yeah, I don't think day-before-release is the ideal time for "oops, we forgot to seed a package".
[23:44] <wxl> i know....... i'd like to say i can take the blame for it, but... nope :)
[23:45] <infinity> Ach well.  If you're +1 on the simple revert, I'll JFDI and spin your image so it can get tested.
[23:45] <wxl> yeah just do it. i'll make simon grovel for getting the fix in if we get to that XD
[23:47] <infinity> Alright, revert pushed, third try on building an ISO...
[23:49] <popeytesting> ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]g
[23:49] <popeytesting> y9999999999999999999999999999999999999999999 q
[23:49] <infinity> popeytesting: I agree.
[23:49] <popeytesting> ============================================================
[23:50] <popeytesting> gah
[23:50] <popey> https://usercontent.irccloud-cdn.com/file/2zN8cimT/IMG_20191017_004911_Bokeh.jpg
[23:50] <popeytesting> Ubuntu Release Cat was being a Cat
[23:51]  * guiverc thinks popey fell asleep on his keyboard
[23:51] <infinity> That creature looks perfectly angelic, I can't believe you're trying to blame him.
[23:51] <ogra> say meow from me !
[23:52] <wxl> it's a fossa!
[23:53] <infinity> popeytesting: Can you do me a favour and do a slightly urgent CFT on the latest batch of images.  We may have some timezone-impaired flavours that will need help with coverage.
[23:54] <infinity> popeytesting: For most, it should just be smoketesting that we didn't break them with the respin, for people with zfs, they should be sure to test it still does what it says on the tin, for people with nvidia hardware and testing kubuntu, budgie, mate, or ubuntu, they should check and see if a bunch of i386 junk got pulled in with the nvidia drivers.
[23:54] <infinity> (Which it should do)
[23:55] <popeytesting> I can indeed!
[23:55] <infinity> popeytesting: Ta.
[23:55] <popeytesting> np
[23:56]  * ogra sadly needs to go bedwards (customer calls in the morning) ... good luck guys !
[23:56] <infinity> popeytesting: Any bug that doesn't seem sets-computer-on-fire levels of important is definitely not RC at this point, but if someone finds an ISO that legit doesn't do things like boot or insall an OS, we'd like to know. :P
[23:57] <popeytesting> http://iso.qa.ubuntu.com/qatracker/milestones/407/builds
[23:57] <popeytesting> that's where to point folks, right?
[23:57] <popeytesting> gonna write up a discourse thing and share it abouts
[23:58] <infinity> popeytesting: Yarp.  And for those who seem to be integer-reading impaired and love testing images from 3 days ago, point out that serials >= 20191016 are what they're after.
[23:58] <popeytesting> roger roger
[23:59] <infinity> popeytesting: <3
[23:59] <Wimpress> ZFS installs completed on BIOS, UEFI (no SecureBoot) and UEFI (with SecureBoot).
[23:59] <Wimpress> Nice one infinity, all good ^
[23:59] <infinity> Wimpress: Neat, that's one more test case than we tried.