[01:11] ddstreet: Hm, that systemd upload appears to drop a bunch of changes from the existing cosmic-proposed package? [01:17] ddstreet: Specifically, the fixes for bug #1799364, LP: #1804584, LP: #1804603, LP: #1804864, LP: #1805358 [01:17] bug 1799364 in systemd (Ubuntu Bionic) "The wlan/bt hotkey doesn't work for all Dell Latitude and Precision computers" [Medium,New] https://launchpad.net/bugs/1799364 [01:17] Launchpad bug 1804584 in systemd (Ubuntu Bionic) "LG screen reported as being a Goldstar one" [Undecided,New] https://launchpad.net/bugs/1804584 [01:17] Launchpad bug 1804603 in systemd (Ubuntu Disco) "systemd-tmpfiles-setup.service fails on btrfs" [Undecided,Fix released] https://launchpad.net/bugs/1804603 [01:17] Launchpad bug 1804864 in systemd (Ubuntu Cosmic) "autopkgtest regression TEST-22-TMPFILES are not executable" [Undecided,Fix released] https://launchpad.net/bugs/1804864 [01:17] Launchpad bug 1805358 in systemd (Ubuntu Bionic) "autopkgtest boot-and-services fails on many architectures very often since systemd/239-7ubuntu12" [Undecided,New] https://launchpad.net/bugs/1805358 [01:20] ddstreet: Likewise, the bionic upload appears to drop a bunch of changes? [08:39] apw, yes I need an hint too :/ force-badtest virtualbox-ext-pack/all/i386 #relies on non-existing virtualbox binary on i386 [08:39] good morning btw :) [08:47] infinity, will 18.04.2 use hwe package? The daily image is still using 4.15 kernel [08:47] I mean the desktop one [09:13] ypwong, the 18.04.2 point release desktop images would be expected to be using the hwe kernel [09:41] -queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (bionic-proposed/main) [4.15.0-45.48] (core, kernel) [09:41] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (bionic-proposed/main) [4.15.0-45.48] (core, kernel) [09:42] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (bionic-proposed) [4.15.0-45.48] [09:42] -queuebot:#ubuntu-release- New: accepted linux-signed [ppc64el] (bionic-proposed) [4.15.0-45.48] [09:56] -queuebot:#ubuntu-release- Unapproved: snapd (xenial-proposed/main) [2.37 => 2.37.1] (desktop-core, ubuntu-server) [09:59] there's a lot of /unknown results atm, I think one of the cloud regions is woeful so I've disabled it [10:00] -queuebot:#ubuntu-release- Unapproved: snapd (bionic-proposed/main) [2.37+18.04 => 2.37.1+18.04] (desktop-core, ubuntu-server) [10:01] -queuebot:#ubuntu-release- Unapproved: snapd (cosmic-proposed/main) [2.37+18.10 => 2.37.1+18.10] (desktop-core, ubuntu-server) [10:02] -queuebot:#ubuntu-release- Unapproved: snapd (trusty-proposed/universe) [2.37~14.04 => 2.37.1~14.04] (no packageset) [10:03] and I'm too lazy to click all those buttons so I'll just retry all failed arm64 :> [10:18] * apw looks at snapd ^ [10:30] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (cosmic-proposed) [2.37.1+18.10] [10:31] RAOF you're comparing against the last pre-security systemd release; I didn't drop the changes, the last (security) systemd release did [10:31] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (bionic-proposed) [2.37.1+18.04] [10:31] if you compare against the current systemd in -updates you should see the correct diff, with just my changes added [10:32] RAOF that is not unusual when security releases supercede something in -proposed [10:32] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (xenial-proposed) [2.37.1] [10:33] RAOF let me know if you have any other q about the uploads [10:34] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (trusty-proposed) [2.37.1~14.04] [10:40] rbasak if you're sru approver today, can you approve the b/c systemd uploads, please, when you get a chance [10:54] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [amd64] (xenial-proposed/main) [4.15.0-45.48~16.04.1] (kernel) [10:54] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [ppc64el] (xenial-proposed/main) [4.15.0-45.48~16.04.1] (kernel) [11:12] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [amd64] (xenial-proposed) [4.15.0-45.48~16.04.1] [11:12] -queuebot:#ubuntu-release- New binary: erlang-erlware-commons [amd64] (disco-proposed/universe) [1.3.1+dfsg-2] (no packageset) [11:12] -queuebot:#ubuntu-release- New binary: erlang-erlware-commons [ppc64el] (disco-proposed/universe) [1.3.1+dfsg-2] (no packageset) [11:12] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [ppc64el] (xenial-proposed) [4.15.0-45.48~16.04.1] [11:12] -queuebot:#ubuntu-release- New binary: erlang-erlware-commons [s390x] (disco-proposed/universe) [1.3.1+dfsg-2] (no packageset) [11:12] -queuebot:#ubuntu-release- New binary: erlang-erlware-commons [i386] (disco-proposed/universe) [1.3.1+dfsg-2] (no packageset) [11:13] -queuebot:#ubuntu-release- New binary: progress-linux [amd64] (disco-proposed/universe) [20181201-3] (no packageset) [11:23] -queuebot:#ubuntu-release- New binary: erlang-erlware-commons [arm64] (disco-proposed/universe) [1.3.1+dfsg-2] (no packageset) [11:26] -queuebot:#ubuntu-release- New binary: erlang-erlware-commons [armhf] (disco-proposed/universe) [1.3.1+dfsg-2] (no packageset) [12:03] rbasak, if you're sru approver today, could you please approve the upload of libmemcached for C/B/X/T (LP: #1573594) [12:03] Launchpad bug 1573594 in libmemcached (Ubuntu Cosmic) "Missing null termination in PROTOCOL_BINARY_CMD_SASL_LIST_MECHS response handling" [Medium,In progress] https://launchpad.net/bugs/1573594 [12:06] ddstreet, joalif: added to my list. I'll see how far I get today. [12:06] rbasak, thanks! === philroche_ is now known as philroche [13:52] -queuebot:#ubuntu-release- Unapproved: libidn (bionic-proposed/main) [1.33-2.1ubuntu1 => 1.33-2.1ubuntu1.1] (core) === chrisccoulson_ is now known as chrisccoulson [14:10] sil2100: thanks! (xtensor hint) [14:17] hello AA I need an hint too :/ force-badtest virtualbox-ext-pack/all/i386 #relies on non-existing virtualbox binary on i386 [14:18] plllllllllllllllllease ^^ === jdstrand_ is now known as jdstrand [14:32] ginggs: yw! [14:32] LocutusOfBorg: looking o/ [14:33] ta [14:33] sil2100, basically, there is no vbox anymore on i386, so the testsuite needs a permanent hint [14:33] upstream stopped supporting it with 6.0 release [14:34] good for them [14:34] ugh [14:35] wait, I don't mean guest [14:35] I mean vbox as *host* [14:36] in fact, the ext-pack regression was the reason for me discovering that :D [14:36] so, for the first time a regression has been useful :) [14:36] would a member of the sru team be able to look at https://bugs.launchpad.net/ubuntu/bionic/+source/ceph/+bug/1813582 please - that bug is impacting on bionic openstack deploys (for a subset of services) [14:36] Ubuntu bug 1813582 in ceph (Ubuntu Bionic) "Update to 12.2.8 leads to SIGSEGV Segmentation fault in python3-rados" [High,In progress] [14:50] hey rbasak, do you have some time to review the stuff we have as desktop-team in SRU queue, mostly shell relateded stuff though (mutter, g-s, g-c-c, g-s-d and related upower) [14:51] anyone know why bionic dailies still don't use HWE packages (kernel + xorg stack)? [14:52] Trevinho: adding to my list, but it seems unlikely I'll get to it, sorry. [14:53] could someone binNEW review the bionic/fwupdate SRU, it's going to miss .2 otherwise (https://launchpad.net/ubuntu/bionic/+queue?queue_state=0&queue_text=) [14:54] -queuebot:#ubuntu-release- New: accepted erlang-erlware-commons [amd64] (disco-proposed) [1.3.1+dfsg-2] [14:54] -queuebot:#ubuntu-release- New: accepted erlang-erlware-commons [armhf] (disco-proposed) [1.3.1+dfsg-2] [14:54] -queuebot:#ubuntu-release- New: accepted erlang-erlware-commons [ppc64el] (disco-proposed) [1.3.1+dfsg-2] [14:54] -queuebot:#ubuntu-release- New: accepted progress-linux [amd64] (disco-proposed) [20181201-3] [14:54] -queuebot:#ubuntu-release- New: accepted erlang-erlware-commons [arm64] (disco-proposed) [1.3.1+dfsg-2] [14:54] -queuebot:#ubuntu-release- New: accepted erlang-erlware-commons [s390x] (disco-proposed) [1.3.1+dfsg-2] [14:54] -queuebot:#ubuntu-release- New: accepted erlang-erlware-commons [i386] (disco-proposed) [1.3.1+dfsg-2] [14:56] rbasak: ok, that's fine... In case please pass the wort to others in the SRU team please [14:56] Trevinho: sure but that happens automatically...there's a queue :-) [14:56] (though unfortunately lately every item in the queue seems to be a mega-feature-review) [14:59] yeah, indeed, I see the point our stuff isn't the smallest either :-P [15:49] bos01's supposed to be fixed [15:49] will start up 1× instance to see if it works [15:52] it's aliiiivvvveeeee [16:41] -queuebot:#ubuntu-release- New: accepted fwupdate [amd64] (bionic-proposed) [12-3bionic1] [16:41] -queuebot:#ubuntu-release- New: accepted fwupdate [armhf] (bionic-proposed) [12-3bionic1] [16:41] -queuebot:#ubuntu-release- New: accepted fwupdate [arm64] (bionic-proposed) [12-3bionic1] [16:41] -queuebot:#ubuntu-release- New: accepted fwupdate [i386] (bionic-proposed) [12-3bionic1] [16:42] Hi sil2100, looks like it's that time again, we sorted the cloud-init disco intermittent build failure per ftbs and have queued cloud-init 18.5-21-g8ee294d5 for Xenial Bionic and Cosmic per SRU process bug https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1813346. [16:42] Ubuntu bug 1813346 in cloud-init (Ubuntu) "sru cloud-init (18.4.0 update to 18.5-21-g8ee294d5) Xenial, Bionic, Cosmic" [Undecided,New] [16:43] if there is time today, we'd like to reject the queued cloud-init 18.5-17 upload requests, in favor of 18.5-21 I that would be great. [16:46] seb128, i assume you know that those signing templates won't do anything [16:47] blackboxsw: hey! Thanks, I'll reject the old ones but not sure if I'll have the cycles to do the review today (I'll try) - if not, I'll do them first thing tomorrow morning as I have my SRU shift then [16:48] sil2100: excellent. thanks much! [16:49] -queuebot:#ubuntu-release- Unapproved: rejected cloud-init [source] (cosmic-proposed) [18.5-17-gd1a2fe73-0ubuntu1~18.10.1] [16:49] -queuebot:#ubuntu-release- Unapproved: rejected cloud-init [source] (bionic-proposed) [18.5-17-gd1a2fe73-0ubuntu1~18.04.1] [16:57] Hi, it would be great if a release team member could consider https://code.launchpad.net/~paelzer/britney/hints-ubuntu-mask-livecd-rootfs-disco/+merge/362475 to unblock a few things blocked by livecd-rootfs [16:58] doko: python-numpy showing some autopkgtest regressions from the usual suspects, any thoughts? [17:00] vorlon: not my biggest priority for now, however I was trying to give back all the astro stuff for now [17:00] there was some entanglement with scikit and a ftbfs matplotlib2 which is now resolved in -proposed, so the remaining astro stuff should now build [17:17] vorlon, thanks for kicking it out [17:17] I spent two full days trying to fix it [17:17] and *nothing* :/ even with upstream patches [17:18] I hope they will have a new release out soon, and I pinged today to backport the patch to 2.3.x branch [17:20] LocutusOfBorg: for kicking which out? [17:41] cpaelzer: done [18:00] vorlon, for kicking matplotlib2 :) [18:00] I would have kicked sphinx too, to let matplotlib2 migrate :p [18:03] apw, the fwupdate bionic SRU? I don't know much about that SRU, just that Mario pinged to get it unblocked [18:15] LocutusOfBorg: ah, sure thing [18:25] LocutusOfBorg: (I added that vbox hint if anything) [18:28] sil2100, ❤ [18:41] apw, sorry, I forgot we have a boinc-virtualbox on i386... I uploaded boinc to stop providing it... can you please do the magic? (remove boinc-virtualbox on i386) [18:41] I also opened a debian bug [18:42] https://bugs.debian.org/920944 [18:42] Error: debian bug 920944 not found [19:40] Laney, juliank: were either of you involved in the rollout of the new ssl certificate on autopkgtest.ubuntu.com? [20:22] vorlon: not me [20:22] k [20:23] timestamps on the files coincide with a login from Laney on wendigo [20:23] and the new ssl certificate was missing its certificate chain so I had to do surgery [20:28] Laney: I think 'juju set autopkgtest-web ssl-cert="$(cat autopkgtest.ubuntu.com.crt autopkgtest.ubuntu.com_chain.crt)" ssl-key="$(cat *.key)"' is the right modification and matches the impementation in autopkgtest-cloud/deployment/deploy.sh (namely, cat *.crt). Should this be documented on https://wiki.ubuntu.com/ProposedMigration/AutopkgtestInfrastructure#Production_deployment_from_wendigo ? [21:43] python-defaults (2.7.15-3 to 2.7.15-4) in proposed for 11 days [21:43] Waiting [21:43] dds/2.9.0-6: arm64, armhf [21:43] django-maintenancemode/0.11.2-3: amd64, arm64, i386 [21:43] openslide-python/1.1.1-4: amd64, arm64, s390x [21:44] python-lzma/0.5.3-4: amd64, arm64, armhf, i386, s390x [21:44] sphinxcontrib-restbuilder/0.2-2: amd64, arm64, i386, s390x [21:44] svgwrite/1.2.1-1.1: arm64 [21:44] vorlon, Laney: are you giving all these tests back which are marked as running, but are not? [21:45] doko: no (it doesn't require admin privs to do so; if someone had done it you would see them in the queue again) [21:45] although [21:45] I did give ack openslide-python [21:45] back [21:45] but only with a python3-defaults trigger, not python-defaults [21:45] well, just trying to address the ones I didn't mention above [21:47] anyway, EOD [21:51] thanks vorlon [21:56] actually, I thought you merged https://code.launchpad.net/~paelzer/britney/hints-ubuntu-mask-livecd-rootfs-disco/+merge/362475 but it is still waiting [21:57] vorlon: might I ask what is "done" ? [21:57] cpaelzer: hmm oops, there was a push conflict; fixing [21:58] cpaelzer: now done [21:59] thanks again [21:59] I'm going to be dreaming of migrating packages ... [21:59] cu [23:04] -queuebot:#ubuntu-release- Unapproved: accepted libidn [source] (bionic-proposed) [1.33-2.1ubuntu1.1] [23:05] vorlon: ah, thx [23:06] I tested with openssl s_cert and firefox, both worked for me, sorry for missing that (please document) [23:06] doko: all of which ones? it's not expected to happen, so it's not a case of randomly retrying them imho, but something to be investigated [23:07] s/s_cert/s_client/ [23:18] doko: unless you mean those ones that I think were missed when the surgery was done. if so, feel free to retry those yourself, yes.