[00:45] britney block in place, waiting for some reports to go empty so I'm sure that my view of the archive is stable. [00:45] * slangasek nods [01:57] I trust that by 20.04, emoji font uploads will be considered release blockers. [01:58] But why? :P [01:58] I think lolcat should be a release blocker, but it doesn't seem to be, despite all my efforts. ;) [02:03] -queuebot:#ubuntu-release- Unapproved: gr-fosphor (bionic-proposed/universe) [3.7.0.2.7b6b996-2 => 3.7.0.2.7b6b996-3] (no packageset) (sync) [02:04] -queuebot:#ubuntu-release- Unapproved: accepted gr-fosphor [sync] (bionic-proposed) [3.7.0.2.7b6b996-3] [02:26] World respinning, off to bed. [02:35] I thought you'd just go ahead with an Ubuntu version of 'lolcat' [02:36] -queuebot:#ubuntu-release- Builds: Ubuntu Base amd64 [Bionic Final] has been updated (20180425) [02:36] -queuebot:#ubuntu-release- Builds: Ubuntu Base arm64 [Bionic Final] has been updated (20180425) [02:36] -queuebot:#ubuntu-release- Builds: Ubuntu Base armhf [Bionic Final] has been updated (20180425) [02:36] -queuebot:#ubuntu-release- Builds: Ubuntu Base i386 [Bionic Final] has been updated (20180425) [02:36] Ukikie: I was told "no deltas allowed" :P [02:36] I have skittles-barf you can use instead, tsimonq2. [02:36] Aha, I see. [02:36] -queuebot:#ubuntu-release- Builds: Ubuntu Base ppc64el [Bionic Final] has been updated (20180425) [02:36] -queuebot:#ubuntu-release- Builds: Ubuntu Base s390x [Bionic Final] has been updated (20180425) [02:36] Ukikie: Hah. [02:37] -queuebot:#ubuntu-release- Builds: Lubuntu Alternate amd64 [Bionic Final] has been updated (20180425) [02:37] -queuebot:#ubuntu-release- Builds: Lubuntu Alternate i386 [Bionic Final] has been updated (20180425) [02:40] tsimonq2: http://paste.openstack.org/show/1nJeawNVJYw1TlG8R9PR cat foo | skittles-barf [02:47] 08:57:02 PM < Odd_Bloke> I trust that by 20.04, emoji font uploads will be considered release blockers. [02:47] 08:58:02 PM < tsimonq2> But why? :P [02:47] grrrrrrrrr [02:48] * tsimonq2 highlighted text then middle clicked [02:54] -queuebot:#ubuntu-release- Builds: Ubuntu Server amd64 [Bionic Final] has been updated (20180425) [02:54] -queuebot:#ubuntu-release- Builds: Ubuntu Server arm64 [Bionic Final] has been updated (20180425) [02:54] -queuebot:#ubuntu-release- Builds: Ubuntu Server ppc64el [Bionic Final] has been updated (20180425) [02:54] -queuebot:#ubuntu-release- Builds: Ubuntu Server s390x [Bionic Final] has been updated (20180425) [02:57] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop amd64 [Bionic Final] has been updated (20180425) [02:57] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop i386 [Bionic Final] has been updated (20180425) [03:04] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Bionic Final] has been updated (20180425) [03:04] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Bionic Final] has been updated (20180425) [03:04] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop i386 [Bionic Final] has been updated (20180425) [03:05] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Bionic Final] has been updated (20180425) [03:05] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop i386 [Bionic Final] has been updated (20180425) [03:08] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop amd64 [Bionic Final] has been updated (20180425) [03:08] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop i386 [Bionic Final] has been updated (20180425) [03:11] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Bionic Final] has been updated (20180425) [03:11] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Bionic Final] has been updated (20180425) [03:11] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop i386 [Bionic Final] has been updated (20180425) [03:11] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop i386 [Bionic Final] has been updated (20180425) [03:15] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD amd64 [Bionic Final] has been updated (20180425) [03:15] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD i386 [Bionic Final] has been updated (20180425) [03:21] -queuebot:#ubuntu-release- Builds: Ubuntu Server armhf+raspi2 [Bionic Final] has been updated (20180425) === sergiusens_ is now known as sergiusens [03:50] infinity: which one? [03:53] LocutusOfBorg: slangasek: I patched ceph to replace that javah call with an additional flag to javac, it has worked locally in an existing chroot from a failed chroot, so I uploaded to a ppa to check if the fix works on a clean environment [03:54] * from a failed build [03:54] tdaitx: ok. let me know when you have something for uploading [03:55] please unblock gcc-6, the gcc-6-cross and gcc-6-cross-ports packages are already in the release pocket [03:56] doko: you going to fix that rails sync? [03:56] doko: unblocking [03:56] slangasek: I didn't look after infinity's upload [03:57] doko: well, it's still broken [03:57] sure, I can have a look [04:03] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity amd64 [Bionic Final] has been updated (20180425) [04:42] infinity: ah, linux-libc-dev [04:45] infinity: not sure how to fix that, apw? [04:47] tjaalton: you'll need to change the packaging to build-depend on something actually built from linux-oem's source package. b-d on linux-libc-dev is convenient to use for this for linux-signed, doesn't work for -oem. what does linux-signed-azure do? [04:47] I see e.g. linux-headers-4.15.0-1008-azure [04:47] so I guess there's probably some toggle in the generic kernel packaging to support this [04:53] okay, I'll have a look [05:16] -queuebot:#ubuntu-release- Unapproved: libplist (bionic-proposed/main) [2.0.0-2 => 2.0.0-2ubuntu1] (kubuntu, ubuntu-desktop) [05:26] -queuebot:#ubuntu-release- Unapproved: rejected libplist [source] (bionic-proposed) [2.0.0-2ubuntu1] [05:36] -queuebot:#ubuntu-release- Unapproved: libplist (bionic-proposed/main) [2.0.0-2 => 2.0.0-2ubuntu1] (kubuntu, ubuntu-desktop) [05:36] libplist, a FTBFS to make you hate compilers. and cpus. and numbers. [05:41] doko: did you have any further thoughts around google-perftools, since your upload seems not to have fixed the ppc64el ftbfs? [05:41] everybody implements this himself instead of using intrinsics ... https://gcc.gnu.org/onlinedocs/gcc/Other-Builtins.html [05:43] slangasek: no, didn't look yet. it's the configury now failing. it's fixed in unstable, tested in ppa:doko/toolchain. but would need a proper merge, or cherry pick [05:45] doko: yes, I ignored the intrinsics because I'm byteswapping an unaligned buffer, so it wasn't obvious to me that memcpy() + __builtin_bswap64() is better than a manual byteswap. is it? [05:46] I haven't checked ... [05:51] slangasek: I'll port 21456eb0acdcf from -signed-azure.. [05:51] to support using the headers pkg [06:05] uh [06:06] linux-headers-4.15.0-1004-oem (>= 4.15.0-1004.6), [06:06] that's not going to work either [06:07] -queuebot:#ubuntu-release- Unapproved: pyxdg (bionic-proposed/main) [0.25-4 => 0.25-4ubuntu1] (core) [06:11] wondering if we should ignore the autopkg test failure for python-redis on i386 [06:11] doko: vs removing all redis things on i386? [06:11] tjaalton: does it work if you use 4.15.0-1004.5+signed1 as your changelog version number instead? [06:13] slangasek: sure, would be an option as well [06:13] but doesn't help with newly synced packages [06:13] filing a Debian issue [06:13] slangasek: oh, yes. I thought that version was bogus :P [06:15] which the script created [06:15] :) [06:18] -queuebot:#ubuntu-release- Unapproved: linux-signed-oem (bionic-proposed/universe) [4.15.0-1004.5 => 4.15.0-1004.5+signed1] (kernel) [06:19] doko: btw, I fixed tomcat8 to work with jre8.. https://pastebin.com/EnVh7K8v [06:19] libphonenumber built when given back [06:20] doko: tdb also [06:21] yeah, can't give all the packages back on armhf and arm64, because the test rebuilds are not yet finished there [06:22] and random nightly/daily builds are considered to be more important [06:22] sure. I tried to reproduce the tdb failure on the porterbox and couldn't [06:22] there's something wrong if you only have 2-5 test rebuilds running at at time [06:22] hmm, so there's a patch in BTS for the first db5.3 failure, but then it also complains about java version numbers [06:27] tjaalton: is this an upstream fix? btw, should tomcat8.0 be removed? [06:29] doko: no, I made that. yes tomcat8.0 can be removed, there's a bug open and u-a subscribed [06:29] looking [06:29] had a chat with coty sutherland, I'll ask if this is upstreamable [06:30] or at least part of it [06:31] -queuebot:#ubuntu-release- Unapproved: accepted linux-signed-oem [source] (bionic-proposed) [4.15.0-1004.5+signed1] [06:31] tjaalton: resteasy still b-d on it [06:31] bug 1717998 [06:31] bug 1717998 in tomcat8.0 (Ubuntu) "Please remove tomcat8.0 before 18.04 releases" [High,Triaged] https://launchpad.net/bugs/1717998 [06:31] oh [06:31] resteasy3.0? [06:32] yes, opened a task for that one as well [06:33] no rdeps [06:33] well, that's another one to sort.. there aren't other consumers in the distro for resteasy other than dogtag [06:33] but it can't work with 3.1 [06:34] oops, removed too early [06:35] but dogtag doesn't depend on it [06:35] tomcat8.0? [06:35] I think the build-dep can be fixed back to tomcat8 [06:35] for resteasy? [06:35] thing is either src:resteasy would need to be reverted to 3.0.19 or resteasy3.0 left in the archive [06:36] there's a bug about that too [06:36] which I can't find [06:36] bug 1682149 [06:36] bug 1682149 in dogtag-pki (Ubuntu) "dogtag-pki stops working with resteasy newer than 3.0.19-2" [Undecided,Confirmed] https://launchpad.net/bugs/1682149 [06:41] resteasy ftbfs [06:41] with tomcat8 [06:41] ? [06:42] linux-signed-oem failed too [06:42] Downloading http://ftpmaster.internal/ubuntu/dists/bionic-proposed/universe/signed/linux-oem-amd64/4.15.0-1004.5/SHA256SUMS ... not found [06:44] tjaalton: because it's in main. tralala [06:45] ahaha [06:45] tjaalton: so reasteasy3.0 succeeds to build. so we can live with the resteasy removal [06:46] -queuebot:#ubuntu-release- Unapproved: db5.3 (bionic-proposed/main) [5.3.28-13.1 => 5.3.28-13.1ubuntu1] (core) [06:46] doko: you mean tomcat8.0 removal? [06:47] tjaalton: probably because it was initially accepted into main and then demoted? I can hack around this by temporarily promoting linux-headers-4.15.0-1004-oem to main, let you build, and then we can re-demote it if that's where it's supposed to be. As for fixing the location of the signed files on disk, that may simply involve pepo surgery, but I'll leave that for someone else to figure out [06:47] during UK daytime [06:47] tjaalton: anyway, linux-headers-4.15.0-1004-oem overridden to main, watch for that to take effect then retry the build [06:49] slangasek: yeah we discussed this with infinity briefly, perhaps main is the right target since it's going to be supported until either -generic or -hwe takes over [06:49] tjaalton: yes [06:58] slangasek, I got the cmake issue [06:59] the cmake part is correct, javah is ignored now, so wrt cmake the archive is correct [06:59] the problem is: ceph still uses manually Java_JAVAH_EXECUTABLE, so this needs to change on ceph side [07:00] I changed it to "Java_JAVAC_EXECUTABLE -h" but I presume your "-h" was just to make it show the help :p [07:00] https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+build/14794722 [07:00] if this one is good, I'll upload mostly as-is [07:00] * LocutusOfBorg afk for some time today [07:11] Laney, seb128 hi, I get bug 1766811 with latest ubuntu desktop image [07:11] bug 1766811 in ubiquity (Ubuntu Bionic) "ubiquity crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.DBus.Error.UnknownMethod: No such interface '(null)' on object at path /org/gnome/SessionManager" [Critical,New] https://launchpad.net/bugs/1766811 [07:12] doko: huh, I could've sworn src:resteasy was at version 3.1.. [07:17] jibel, when did that start? with the ubiquity update? [07:17] seb128, today with latest build [07:18] jibel, but you didn't have the issue yesterday when you tried .11 locally built? [07:19] seb128, I couldn't test that because there was another crash that we reverted just before this point [07:20] jibel, is the issue in the live session or in ubiquity-dm? [07:20] seb128, live session, I'm testing the ubiquity-only mode now [07:21] k, that makes sense, that codepath is not supposed to be used in -dm [07:21] jibel, do you know what other packages changed between the isos? [07:22] I don't see anything that could create that pb in the ubiquity diff, but maybe it's just some side effect we didn't think of [07:22] seb128, http://paste.ubuntu.com/p/FYx3J7NGsZ/ [07:22] thx [07:23] gnome-shell [07:23] it's puzzling [07:23] the code does [07:23] if gnome_session: [07:23] manager = session.get_object('org.gnome.SessionManager', [07:23] '/org/gnome/SessionManager') [07:23] manager.RequestReboot() [07:23] so it's using dbus to talk directly to gnome-session [07:24] which gives [07:24] No such interface '(null)' on object at path /org/gnome/SessionManager [07:25] seb128, it only happens from the live session [07:25] k, makes sense [07:25] there is no gnome-session in ubiquity-dm [07:25] so it doesn't try to do that call there [07:27] I'm syncing the pending iso [08:16] -queuebot:#ubuntu-release- Unapproved: google-perftools (bionic-proposed/main) [2.5-2.2ubuntu2 => 2.5-2.2ubuntu3] (ubuntu-server) [08:41] -queuebot:#ubuntu-release- Unapproved: libvirt (artful-proposed/main) [3.6.0-1ubuntu6.5 => 3.6.0-1ubuntu6.6] (ubuntu-server, virt) [08:41] -queuebot:#ubuntu-release- Unapproved: libvirt (xenial-proposed/main) [1.3.1-1ubuntu10.21 => 1.3.1-1ubuntu10.22] (ubuntu-server, virt) [09:30] slangasek: For better or worse, LP currently hardcodes main for the signing custom upload there, so we shouldn't do ftpmaster surgery to move the files around. [10:20] -queuebot:#ubuntu-release- Unapproved: ubiquity (bionic-proposed/main) [18.04.11 => 18.04.12] (core) [10:25] respins for that ubiquity ^^^? [10:26] really? that's taking "last minute" to the extreme! [10:32] Yeah [10:32] It's a bit of a serious thing [10:41] fossfreedom_: if it causes restart to fail at the end of installation, then users may assume that installation failed, or do some unsafe method of restart [10:41] + it look bad [10:43] hmm ... then sounds like nobody is sleeping tonight to complete the retesting [10:44] mostly it just looks bad [10:49] yeah [10:50] I'm getting a weak signal that some 16.04 LTS users (one source, claiming plural) would be getting offer to 18.04 LTS upgrade without -d switch or anything, but so far unable to get any direct source (and unable to reproduce). just mentioning if the noise would happen to become louder. [10:51] probably just people really messing with -d [10:53] it's also impossible to get the message really through that supported upgrading starts around 18.04.1 [10:55] -queuebot:#ubuntu-release- Unapproved: accepted ubiquity [source] (bionic-proposed) [18.04.12] [11:01] -queuebot:#ubuntu-release- Unapproved: accepted fonts-noto-color-emoji [source] (bionic-proposed) [0~20180424-0ubuntu1] [11:02] -queuebot:#ubuntu-release- Unapproved: accepted db5.3 [source] (bionic-proposed) [5.3.28-13.1ubuntu1] [11:02] -queuebot:#ubuntu-release- Unapproved: accepted libplist [source] (bionic-proposed) [2.0.0-2ubuntu1] [11:02] -queuebot:#ubuntu-release- Unapproved: accepted google-perftools [source] (bionic-proposed) [2.5-2.2ubuntu3] [11:02] -queuebot:#ubuntu-release- Unapproved: accepted pyxdg [source] (bionic-proposed) [0.25-4ubuntu1] [11:05] fossfreedom_: Feel free to find a release when we didn't respin day before release :) [11:15] -queuebot:#ubuntu-release- Unapproved: flash-kernel (bionic-proposed/main) [3.90ubuntu2 => 3.90ubuntu3] (core) [11:17] -queuebot:#ubuntu-release- Unapproved: accepted flash-kernel [source] (bionic-proposed) [3.90ubuntu3] [11:22] -queuebot:#ubuntu-release- Unapproved: caja (bionic-proposed/universe) [1.20.2-3ubuntu1 => 1.20.2-4ubuntu1] (ubuntu-mate, ubuntukylin, xubuntu) [11:23] -queuebot:#ubuntu-release- Unapproved: marco (bionic-proposed/universe) [1.20.1-1 => 1.20.1-2ubuntu1] (ubuntu-mate) [11:23] -queuebot:#ubuntu-release- Unapproved: mate-control-center (bionic-proposed/universe) [1.20.2-1 => 1.20.2-2ubuntu1] (ubuntu-mate) [11:27] why do I still see the old ghc 8.0.2-10 package in bionic? [11:28] the source package [11:31] laney@nightingale> GET http://archive.ubuntu.com/ubuntu/dists/bionic/universe/source/Sources.xz | xzcat | grep-dctrl -S -sPackage,Version -X ghc ~ [11:31] Package: ghc [11:31] Version: 8.0.2-11 [11:31] no [11:32] apt-cache showsrc shows it [11:32] and: [11:32] $ reverse-depends -b src:llvm-toolchain-3.7 [11:32] Reverse-Build-Depends [11:32] ===================== [11:32] * ghc (for llvm-3.7) [11:33] doko: reverse-depends is a 3rd party service that's often out of date. [11:33] $ apt-cache showsrc ghc | grep ^Version: [11:33] Version: 8.0.2-11 [11:34] not here [11:34] apw: that would prove the existance ... [11:35] ... of? [11:35] * apw sees -11 [11:35] was this in -proposed at some time? [11:36] you sure you don't have artful in sources.list or something? [11:36] hmm, so here we go with llvm-3.7 :-/ [11:37] doko: ... what? [11:38] -11 build-deps on llvm-3.7 too (on arm*) [11:38] we have to keep it [11:38] doko: -11 indeed build-depends on llvm-3.7. Not sure why you thought that meant -10 was still around. [11:39] right, so unstable's version b-ds on -3.9, but no time for a Haskell transition now :) [11:48] -queuebot:#ubuntu-release- Unapproved: pluma (bionic-proposed/universe) [1.20.1-2ubuntu1 => 1.20.1-3ubuntu1] (ubuntu-mate, ubuntukylin) [11:48] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896864 can we bad-test python-redis for the release? [11:48] Debian bug 896864 in src:python-redis "python-redis autopkg test failures on i386" [Important,Open] === sergiusens_ is now known as sergiusens [12:20] apw, infinity - the most relevant bit got copied into the bug description [12:20] https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1766727 [12:20] Ubuntu bug 1766727 in linux (Ubuntu) "initramfs-tools exception during pm.DoInstall with do-release-upgrade from 16.04 to 18.04 " [Undecided,Confirmed] [12:20] upgrade.log if you want to read it non-wrapped, skip to the end of said file === Kamilion|ZNC is now known as Kamilion [12:25] -queuebot:#ubuntu-release- Unapproved: gcc-snapshot (bionic-proposed/universe) [1:20180322-1ubuntu1 => 1:20180425-1ubuntu1] (no packageset) [12:25] -queuebot:#ubuntu-release- Unapproved: accepted gcc-snapshot [source] (bionic-proposed) [1:20180425-1ubuntu1] [12:31] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (trusty-proposed/main) [3.13.0-146.195] (core, kernel) [12:32] infinity, fyi https://bugs.launchpad.net/ubuntu/+source/netcfg/+bug/1757078 [12:32] Ubuntu bug 1757078 in netcfg (Ubuntu) "DNS setting is not reflected in netplan yaml file when domain name isempty string" [Critical,Confirmed] [12:43] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (trusty-proposed) [3.13.0-146.195] [12:46] apw, infinity https://paste.ubuntu.com/p/tHqNpPQDhb/ [12:51] -queuebot:#ubuntu-release- Unapproved: accepted mate-control-center [source] (bionic-proposed) [1.20.2-2ubuntu1] [12:52] -queuebot:#ubuntu-release- Unapproved: accepted marco [source] (bionic-proposed) [1.20.1-2ubuntu1] [12:53] -queuebot:#ubuntu-release- Unapproved: accepted pluma [source] (bionic-proposed) [1.20.1-3ubuntu1] [12:54] -queuebot:#ubuntu-release- Unapproved: accepted caja [source] (bionic-proposed) [1.20.2-4ubuntu1] [13:07] -queuebot:#ubuntu-release- Unapproved: netcfg (bionic-proposed/main) [1.142ubuntu6 => 1.142ubuntu7] (core) [13:11] -queuebot:#ubuntu-release- Unapproved: accepted netcfg [source] (bionic-proposed) [1.142ubuntu7] [13:31] -queuebot:#ubuntu-release- Unapproved: pypeg2 (bionic-proposed/universe) [2.15.2-1 => 2.15.2-2] (no packageset) (sync) [13:32] -queuebot:#ubuntu-release- Unapproved: accepted pypeg2 [sync] (bionic-proposed) [2.15.2-2] [13:37] -queuebot:#ubuntu-release- Unapproved: installation-guide (bionic-proposed/main) [20160121ubuntu3 => 20160121ubuntu4] (core) [13:41] -queuebot:#ubuntu-release- Unapproved: adonthell (bionic-proposed/universe) [0.3.6-1build1 => 0.3.7-1] (no packageset) (sync) [13:41] -queuebot:#ubuntu-release- Unapproved: accepted adonthell [sync] (bionic-proposed) [0.3.7-1] [13:52] hi release team, bug 1750121 for neutron-dynamic-routing basically causes BGP to become unusable after reboot. very minimal patch and very minimal reverse dependencies involved. can i upload to bionic? [13:52] bug 1750121 in neutron-dynamic-routing (Ubuntu Bionic) "Dynamic routing: adding speaker to agent fails" [High,Triaged] https://launchpad.net/bugs/1750121 [13:53] -queuebot:#ubuntu-release- Unapproved: eom (bionic-proposed/universe) [1.20.0-1 => 1.20.0-2ubuntu1] (ubuntu-mate, ubuntukylin) [13:55] -queuebot:#ubuntu-release- Unapproved: mate-panel (bionic-proposed/universe) [1.20.1-2ubuntu1 => 1.20.1-3ubuntu1] (ubuntu-mate) [14:13] -queuebot:#ubuntu-release- Unapproved: accepted installation-guide [source] (bionic-proposed) [20160121ubuntu4] [14:17] -queuebot:#ubuntu-release- Unapproved: accepted eom [source] (bionic-proposed) [1.20.0-2ubuntu1] [14:17] -queuebot:#ubuntu-release- Unapproved: accepted mate-panel [source] (bionic-proposed) [1.20.1-3ubuntu1] [14:27] -queuebot:#ubuntu-release- New binary: linux-signed-oem [amd64] (bionic-proposed/main) [4.15.0-1004.5+signed1] (kernel) [14:28] slangasek: c-icap/1:0.4.4-1 autopkg test on amd64 now fails the same way as on s390x (Ignored failure) [14:29] tjaalton, slangasek: linux-signed-oem given back and successfully built [14:29] cool [14:36] -queuebot:#ubuntu-release- Unapproved: linux-base (xenial-proposed/main) [4.0ubuntu1 => 4.5ubuntu1~16.04.1] (core) [15:04] when do you plan to respin an image? [15:07] infinity: mind if i upload neutron-dynamic-routing to bionic? re: msg above [15:08] jibel: Very soon. Working on one more bug. [15:17] okay, I'll take a break and come back later in the evening then [15:33] cjwatson: no surgery- ack [15:34] cjwatson: so the kernel should also not look in universe [15:34] Agreed [15:41] infinity, sil2100, apw: do you know who accepted libplist, db5.3, pyxdg? These are all targeted for SRU but the bugs don't seem to be marked as SRUs [15:41] slangasek, i do not [15:43] -queuebot:#ubuntu-release- New: accepted linux-signed-oem [amd64] (bionic-proposed) [4.15.0-1004.5+signed1] [15:45] Not me [15:48] apw: fyi https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766916 [15:48] Ubuntu bug 1766916 in linux (Ubuntu) "secureboot signing code looks for signed artifacts by component, should always be in main" [Undecided,New] [15:48] slangasek, aware of that, which kernel was exhibiting it? linux-oem ? [15:49] apw: it was, yes [15:51] slangasek, so that one is resolved by its promotion [15:54] apw: yes [16:02] -queuebot:#ubuntu-release- Unapproved: s390-tools (bionic-proposed/main) [2.3.0-0ubuntu2 => 2.3.0-0ubuntu3] (core) [16:06] * sil2100 should have checked that before approving === pietroalbini_ is now known as pietroalbini [16:15] -queuebot:#ubuntu-release- Unapproved: s390-tools (bionic-proposed/main) [2.3.0-0ubuntu2 => 2.3.0-0ubuntu3] (core) === hc_ is now known as Guest59296 [16:18] -queuebot:#ubuntu-release- Unapproved: rejected s390-tools [source] (bionic-proposed) [2.3.0-0ubuntu3] [16:18] -queuebot:#ubuntu-release- Unapproved: accepted s390-tools [source] (bionic-proposed) [2.3.0-0ubuntu3] [16:21] -queuebot:#ubuntu-release- New binary: linux-signed-hwe-edge [amd64] (xenial-proposed/main) [4.15.0-20.21~16.04.1] (kernel) [16:21] -queuebot:#ubuntu-release- New binary: linux-signed-hwe-edge [ppc64el] (xenial-proposed/main) [4.15.0-20.21~16.04.1] (kernel) [16:37] -queuebot:#ubuntu-release- Unapproved: linux-base (xenial-proposed/main) [4.0ubuntu1 => 4.5ubuntu1~16.04.1] (core) [16:37] -queuebot:#ubuntu-release- Unapproved: linux-base (xenial-proposed/main) [4.0ubuntu1 => 4.5ubuntu1~16.04.1] (core) [16:39] infinity: Are we calling this next respin a *final* final? [16:39] tsimonq2: Friggin' better be. [16:40] -queuebot:#ubuntu-release- Unapproved: rejected linux-base [source] (xenial-proposed) [4.5ubuntu1~16.04.1] [16:40] -queuebot:#ubuntu-release- Unapproved: rejected linux-base [source] (xenial-proposed) [4.5ubuntu1~16.04.1] [16:41] infinity: I'm confirming that someone isn't crying wolf here, but there's a super slim chance Kubuntu might need something snuck in. If not in the final, as a 0 day SRU. [16:42] * tsimonq2 isn't particularly pleased about it.. [16:42] tsimonq2: if 0 day SRU is even an option for whatever it is, then that's your only option [16:42] slangasek: Alright. [16:42] tsimonq2: anything that doesn't scream "this needs to be in the ISO" doesn't need to be in the ISO [16:43] * tsimonq2 continues trying to confirm the severity of the problem. [16:43] slangasek: You're probably right, but I need to cover my bases here. [16:43] tjaalton: linux-oem has all the bits in the archive now and it appears tests are running [16:44] could installation-guide please be unblocked? AFAICT it's in main but only seeded in supported-installer-common, it does not land on any CD [16:44] cyphermox: looking [16:45] unblocked [16:45] ta [16:46] -queuebot:#ubuntu-release- Unapproved: accepted linux-base [source] (xenial-proposed) [4.5ubuntu1~16.04.1] [16:47] -queuebot:#ubuntu-release- Unapproved: linux-meta (bionic-proposed/main) [4.15.0.20.22 => 4.15.0.20.23] (core, kernel) [16:49] slangasek: yeah, I'll pay attention to those [16:49] should actually show more green this time [16:50] -queuebot:#ubuntu-release- Unapproved: accepted linux-meta [source] (bionic-proposed) [4.15.0.20.23] [16:50] slangasek: You are right. src:powerdevil will get an upload to Bionic tonight that I'd argue needs to be a 0 day SRU. [16:50] I don't have access to my machine with my GPG privkey atm, so unless acheronuk snipes it, we're talking 8ish PM Central. [16:52] -queuebot:#ubuntu-release- Unapproved: debian-installer (bionic-proposed/main) [20101020ubuntu541 => 20101020ubuntu542] (core) [16:52] -queuebot:#ubuntu-release- Unapproved: accepted debian-installer [source] (bionic-proposed) [20101020ubuntu542] [16:53] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe-edge [amd64] (xenial-proposed) [4.15.0-20.21~16.04.1] [16:53] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe-edge [ppc64el] (xenial-proposed) [4.15.0-20.21~16.04.1] [16:57] infinity, sil2100, apw, Laney: anyone reviewing unseeded things in -proposed? Should I be looking at this? [16:57] slangasek: The bot's still doing unseeded. [16:57] infinity: they're not being unblocked into the release pocket [16:58] you froze the whole archive, I believe? [16:58] slangasek: Oh, *in* proposed. I was doing a mass unblock of stuff from the last 24h, but if you wanted to fish through old things to see if something magically fixed itself, go nuts. [16:59] -queuebot:#ubuntu-release- Unapproved: linux-meta-raspi2 (bionic-proposed/universe) [4.15.0.1010.8 => 4.15.0.1010.9] (kernel) [16:59] infinity: "were doing" - so you already have this in progress? since I'm seeing stuff that's blocked and not seeded e.g. adonthell [16:59] slangasek: Yeah, I'm on it. [16:59] infinity: ok. yeah I wasn't going to fish the old stuff [17:00] infinity, Wimpress: and what's the deal with the various mate packages? I don't see any discussion here about them, they're clearly not on track to be SRUs, and they're not unblocked so they're not looking good for inclusion in an imminent respin [17:01] slangasek: They're being unblocked. [17:01] ok [17:02] infinity: eom mate-panel caja marco mate-control-center pluma? is that a complete list for mate? [17:13] -queuebot:#ubuntu-release- Unapproved: build-essential (bionic-proposed/main) [12.4ubuntu1 => 12.5ubuntu1] (core) [17:14] infinity Thanks [17:15] Travelling right now, so appreciate you unblocking the MATE packages [17:16] -queuebot:#ubuntu-release- Unapproved: a7xpg (bionic-proposed/universe) [0.11.dfsg1-9.1 => 0.11.dfsg1-10] (no packageset) [17:16] -queuebot:#ubuntu-release- Unapproved: ii-esu (bionic-proposed/universe) [1.0a.dfsg1-7build1 => 1.0a.dfsg1-8] (no packageset) [17:16] -queuebot:#ubuntu-release- Unapproved: parsec47 (bionic-proposed/universe) [0.2.dfsg1-8 => 0.2.dfsg1-9] (no packageset) [17:16] -queuebot:#ubuntu-release- Unapproved: tatan (bionic-proposed/universe) [1.0.dfsg1-7 => 1.0.dfsg1-8] (no packageset) [17:16] -queuebot:#ubuntu-release- Unapproved: gunroar (bionic-proposed/universe) [0.15.dfsg1-8build1 => 0.15.dfsg1-9] (no packageset) [17:16] -queuebot:#ubuntu-release- Unapproved: projectl (bionic-proposed/universe) [1.001.dfsg1-8build1 => 1.001.dfsg1-9] (no packageset) [17:16] -queuebot:#ubuntu-release- Unapproved: mu-cade (bionic-proposed/universe) [0.11.dfsg1-11 => 0.11.dfsg1-12] (no packageset) [17:16] -queuebot:#ubuntu-release- Unapproved: titanion (bionic-proposed/universe) [0.3.dfsg1-6build1 => 0.3.dfsg1-7] (no packageset) [17:16] slangasek That list looks correct [17:16] doko: build-essential is seeded in the images. What is this? [17:16] really? [17:16] mehh [17:17] -queuebot:#ubuntu-release- Unapproved: accepted a7xpg [source] (bionic-proposed) [0.11.dfsg1-10] [17:17] -queuebot:#ubuntu-release- Unapproved: accepted ii-esu [source] (bionic-proposed) [1.0a.dfsg1-8] [17:17] -queuebot:#ubuntu-release- Unapproved: accepted parsec47 [source] (bionic-proposed) [0.2.dfsg1-9] [17:17] -queuebot:#ubuntu-release- Unapproved: accepted tatan [source] (bionic-proposed) [1.0.dfsg1-8] [17:17] -queuebot:#ubuntu-release- Unapproved: accepted gunroar [source] (bionic-proposed) [0.15.dfsg1-9] [17:17] -queuebot:#ubuntu-release- Unapproved: accepted projectl [source] (bionic-proposed) [1.001.dfsg1-9] [17:17] -queuebot:#ubuntu-release- Unapproved: accepted mu-cade [source] (bionic-proposed) [0.11.dfsg1-12] [17:17] -queuebot:#ubuntu-release- Unapproved: accepted titanion [source] (bionic-proposed) [0.3.dfsg1-7] [17:17] I'll do that as a SRU then [17:17] why does it need SRUed? [17:18] -queuebot:#ubuntu-release- Unapproved: rejected build-essential [source] (bionic-proposed) [12.5ubuntu1] [17:18] missed to build the cross packages for amd64 and i386 [17:31] -queuebot:#ubuntu-release- Builds: Netboot amd64 [Bionic Final] has been updated (20101020ubuntu542) [17:31] -queuebot:#ubuntu-release- Builds: Netboot arm64 [Bionic Final] has been updated (20101020ubuntu542) [17:31] -queuebot:#ubuntu-release- Builds: Netboot armhf [Bionic Final] has been updated (20101020ubuntu542) [17:31] -queuebot:#ubuntu-release- Builds: Netboot i386 [Bionic Final] has been updated (20101020ubuntu542) [17:31] -queuebot:#ubuntu-release- Builds: Netboot ppc64el [Bionic Final] has been updated (20101020ubuntu542) [17:31] -queuebot:#ubuntu-release- Builds: Netboot s390x [Bionic Final] has been updated (20101020ubuntu542) [17:31] -queuebot:#ubuntu-release- Unapproved: linux-meta-raspi2 (bionic-proposed/universe) [4.15.0.1010.8 => 4.15.0.1010.9] (kernel) [17:34] -queuebot:#ubuntu-release- Unapproved: rejected linux-meta-raspi2 [source] (bionic-proposed) [4.15.0.1010.9] [17:34] -queuebot:#ubuntu-release- Unapproved: accepted linux-meta-raspi2 [source] (bionic-proposed) [4.15.0.1010.9] [17:39] Hi jbicha and all: Thank you for (automatically?) syncing hugo 0.40-1, though it actually introduced a bug that was fixed in the 0.40.1 release today. I have just uploaded hugo_0.40.1-1 to Debian, though it will be some hours yet before it got processed by dinstall and got picked up by Launchpad. [17:42] But yes, if hugo 0.40.1-1 arrives before Bionic's release, it would be nice to get it in. (Hugo's main author got bitten by the "shortcode vs .Content corner cases" bug himself.) See https://gohugo.io/news/0.40.1-relnotes/ [17:42] Thanks again! [17:44] infinity: do I understand correctly based on the recent accepts that you're respinning everything? for those following along, what triggered this? [17:44] slangasek: We have one last ubiquity fix we're mulling over. If we decide to land that, I think I'll accept doko's build-essential from rejected and let it pass too. [17:45] slangasek: Respinning the world is triggered by previous ubiquity anyway. But testing one final reboot fix. [17:47] slangasek, infinity: I'll be uploading a fix for bug 1764848 shortly. [17:47] bug 1764848 in openssl (Ubuntu Bionic) "Upgrade to ca-certificates to 20180409 causes ca-certificates.crt to be removed if duplicate certs found" [High,In progress] https://launchpad.net/bugs/1764848 [17:50] infinity: last ubiquity fix being EFI? [17:52] doko: how about building tomcat with jdk8 for now and fixing the issues with jre8 in sru? This patch is getting bigger and I'd like to send it upstream first [17:53] cyphermox: Expand on that statement? [17:54] infinity: what is the last ubiquity fix you're mulling over? [17:54] -queuebot:#ubuntu-release- Unapproved: lxd (xenial-backports/main) [2.21-0ubuntu3~16.04.1 => 2.21-0ubuntu3~16.04.2] (edubuntu, ubuntu-server) [17:55] cyphermox: Papering over the longstanding Plymouth reboot issue. [17:55] ok [17:55] cyphermox: But what did you mean? [17:56] I mean fixing crash at the end of install when you don't have an EFI system partition [17:56] cyphermox: I'm not familiar with that one. [17:56] -queuebot:#ubuntu-release- Unapproved: accepted lxd [source] (xenial-backports) [2.21-0ubuntu3~16.04.2] [17:56] infinity: anybody working on the plymouth one right now? [17:57] cyphermox: xnox is, if he stops talking about it at some point [17:57] cyphermox: Yes. [17:57] ok [17:57] lol [17:57] cyphermox: Your bug. Does it have a bug? Does it have a fix? [17:58] filing the bug, fix for now may be to revert a change in partman-efi we did a few weeks ago [17:59] OTOH it won't so much "fix" things as give users an apportunity to go back to partitioning and add what's missing [17:59] -queuebot:#ubuntu-release- Unapproved: openssl (bionic-proposed/main) [1.1.0g-2ubuntu3 => 1.1.0g-2ubuntu4] (core) [18:00] cyphermox: Allowing them to fix things seems better than crashing. What was the actual intent? To yell at them? [18:01] cyphermox: Anyhow, proposed fix ASAP, please. [18:01] the original issue was the message is confusing for everyone, so it was dropped, but it's meant to catch EFI installs being attempted where there is no ESP created [18:07] cyphermox: So, why did this cause things to crash? [18:08] -queuebot:#ubuntu-release- New: accepted golang-1.10-race-detector-runtime [amd64] (artful-backports) [0.0+svn285455-0ubuntu1~17.10.1] [18:08] -queuebot:#ubuntu-release- Unapproved: lxd (artful-backports/main) [2.21-0ubuntu3~17.10.1 => 2.21-0ubuntu3~17.10.2] (edubuntu, ubuntu-server) [18:08] -queuebot:#ubuntu-release- Unapproved: casper (bionic-proposed/main) [1.393 => 1.394] (desktop-core, ubuntu-server) [18:08] -queuebot:#ubuntu-release- New: accepted golang-1.10-race-detector-runtime [amd64] (xenial-backports) [0.0+svn285455-0ubuntu1~16.04.1] [18:08] -queuebot:#ubuntu-release- New: accepted golang-1.9-race-detector-runtime [amd64] (xenial-backports) [0.0+svn285455-0ubuntu1~16.04.1] [18:11] cyphermox: nack on reverting partman-efi. [18:11] -queuebot:#ubuntu-release- Unapproved: accepted lxd [source] (artful-backports) [2.21-0ubuntu3~17.10.2] [18:11] infinity: ^^ [18:11] this needs to be fixed properly by enforcing ESP before we proceed with the install [18:11] *not* by restoring that terrible dialog [18:12] Right, that sounds like a code change too large to review and land confidently. [18:12] and that we were discussing it today doesn to make it critical for GA [18:12] Can we just avoid the installer crashing? [18:12] no [18:12] it crashes in grub-installer [18:12] Excellent. [18:12] "crashes" [18:12] Well job. [18:13] 🧔 [18:13] infinity: this is a longstanding existing bug that has resulted in multiple bug reports on shim-signed over multiple cycles. It's not 18.04.0 critical. [18:13] slangasek: Check. [18:14] Then this last trivial fix is the end of (seeded) bionic [18:15] slangasek: linux-azure is no longer blocked by our bug [18:16] tjaalton: do we need that for the release, or could that be done in a SRU? [18:20] -queuebot:#ubuntu-release- Unapproved: accepted casper [source] (bionic-proposed) [1.394] [18:22] -queuebot:#ubuntu-release- New binary: build-essential [amd64] (bionic-proposed/main) [12.5ubuntu1] (core) [18:23] -queuebot:#ubuntu-release- Unapproved: accepted openssl [source] (bionic-proposed) [1.1.0g-2ubuntu4] [18:24] -queuebot:#ubuntu-release- New: accepted build-essential [amd64] (bionic-proposed) [12.5ubuntu1] [18:24] infinity: are you planning to skip tests for linux-meta so it doesn't take all day? [18:24] slangasek: Yes. [18:25] https://salsa.debian.org/debian/ca-certificates/commit/1bc87e0b41a04551a93d4e784e158b044c18792a [18:26] infinity: ack [18:26] bdmurray: Actually, after a talk with Laney, we're going to revert https://salsa.debian.org/debian/ca-certificates/commit/1bc87e0b41a04551a93d4e784e158b044c18792a instead. [18:28] infinity: when the dust settles I'd like to understand why that s390-tools upload was needed [18:31] infinity: openssl upstream is making the same change pretty much [18:31] additionally the debian-devel thread leads me to believe other packages might have switched to openssl rehash https://lists.debian.org/debian-devel/2018/04/msg00058.html [18:31] bdmurray: According to..? [18:32] https://github.com/openssl/openssl/issues/6083 [18:32] openssl bug 6083 in openssl "return codes for duplicate certificates differs between c_rehash and openssl rehash" (comments: 0) [Open] [18:32] bug 6083 in Mozilla Firefox "Double-clicking Firefox shortcut in Quick launch gives profile selection" [Undecided,Invalid] https://launchpad.net/bugs/6083 [18:34] bdmurray: Hah, approved 12m ago. Nice. [18:34] bdmurray: Alright, pretend this conversation didn't happen. :) [18:37] doko: it's better to have something not breaking in the release, breaks upgrades too [18:40] but upgrade issues can always be solved as 0-day SRU, and these packages are not on any images, correct? [18:41] infinity: does the fact that the automated tests for the subiquity server image are broken and failing to promote impact the ability to publish for release? [18:42] (doesn't stop us from testing and reporting results on iso.qa, just means it won't be 'current') [18:42] slangasek: Not as long as someone registers some manual tests. [18:42] slangasek: correct, not in any image [18:42] and in universe [18:42] slangasek: The current links mean exactly diddly to the publishing process. [18:43] infinity: ok. andreas is working on fixing the test (it needs to know location of vmlinuz on disk in order to do a non-booting check of sb signatures), but needs someone to be able to land the utah change [18:43] 0-day sru to build against jdk8 would work for me [18:44] -queuebot:#ubuntu-release- Unapproved: node-vue-resource (bionic-proposed/universe) [1.3.4-1ubuntu1 => 1.3.4+dfsg-1] (no packageset) (sync) [18:44] jibel: ^^ ah, looks like you have utah access, could you look at https://code.launchpad.net/~ahasenack/utah/live-server-kernel-path-1766947/+merge/344342 ? [18:44] Not in images and in universe is certainly doable right now, too. [18:44] -queuebot:#ubuntu-release- Unapproved: accepted node-vue-resource [sync] (bionic-proposed) [1.3.4+dfsg-1] [18:45] jibel: the fact that this change will be incorrect for releases < bionic is ignorable since server-live is not in xenial and we won't respin for artful [18:47] -queuebot:#ubuntu-release- New binary: node-vue-resource [amd64] (bionic-proposed/universe) [1.3.4+dfsg-1] (no packageset) [18:49] -queuebot:#ubuntu-release- New: accepted node-vue-resource [amd64] (bionic-proposed) [1.3.4+dfsg-1] [18:54] rbalint: \o/ all the D games back in [18:56] -queuebot:#ubuntu-release- Unapproved: modglue (bionic-proposed/universe) [1.19-0ubuntu4 => 1.19-0ubuntu5] (no packageset) [18:58] -queuebot:#ubuntu-release- Unapproved: accepted modglue [source] (bionic-proposed) [1.19-0ubuntu5] [18:59] -queuebot:#ubuntu-release- Unapproved: gnome-gmail (bionic-proposed/universe) [2.5.4-2 => 2.5.4-3] (no packageset) (sync) [19:00] -queuebot:#ubuntu-release- Unapproved: accepted gnome-gmail [sync] (bionic-proposed) [2.5.4-3] [19:02] infinity - what we actually respinning for? [19:02] slangasek: plars gave a review. Your comment above about releases < bionic addresses his comment, correct? [19:02] flocculant: ubiquity, and misc. [19:03] ahasenack: yes. commented on MP. [19:03] infinity: okey doke - thanks :) [19:03] slangasek: plars thanks! ok, who can merge? plars? [19:03] ahasenack: ah, didn't see the conversation here. Even if it was, I'd rather go back and do a quick cleanup later than block things over something like that, but not even an issue it seems. I already gave my +1 [19:04] plars: could you land it? since we cannot [19:04] doko: i was wondering how much time should i spend testing them before upload :-) [19:04] ahasenack: I top approved it, not sure if they have an autolander for this, do you know? if not I can just merge by hand [19:05] let me look at some old ones [19:05] I don't see a bot [19:06] bzr log also only shows actual people committing and merging [19:07] ahasenack: pushed [19:09] infinity: I changed the release notes, but if you plan on doing flavor announcement paragraphs in your announcement, Lubuntu's will be at https://lubuntu.me/bionic-released/ [19:10] -queuebot:#ubuntu-release- Unapproved: jargoninformatique (bionic-proposed/universe) [1.3.6-0ubuntu6 => 1.3.6-0ubuntu7] (no packageset) [19:10] plars: plars thanks [19:10] tsimonq2: I do not. [19:10] plars: now I need a build in this ppa I guess: https://launchpad.net/~canonical-platform-qa-jenkins/+archive/ubuntu/canonical-platform-qa-jenkins-prod [19:10] tsimonq2: It'll look like the xenial release announce: https://lists.ubuntu.com/archives/ubuntu-announce/2016-April/000207.html [19:10] https://launchpad.net/~canonical-platform-qa-jenkins/+archive/ubuntu/canonical-platform-qa-jenkins-staging has it too [19:10] checking recipes [19:10] infinity: OK. Just thought I'd explicitly mention it, just in case. [19:11] -queuebot:#ubuntu-release- Unapproved: accepted jargoninformatique [source] (bionic-proposed) [1.3.6-0ubuntu7] [19:11] https://code.launchpad.net/~canonical-platform-qa-jenkins/+recipe/utah-staging and https://code.launchpad.net/~canonical-platform-qa-jenkins/+recipe/utah-production [19:11] plars: do you have perms to kick either recipe? ^ === fossfree- is now known as fossfreedom [19:12] ahasenack: looks like I do. Do you have a preference? which one are you set up to use right now? [19:12] jenkins uses the prod one [19:12] plars: we can of course try staging first [19:12] just checking the current ver, if it's what we had in trunk before [19:13] yeah, ppa has r1123, our merge became r1124 [19:13] ahasenack: for a change like that, it doesn't seem bad to go straight to production if that helps you [19:13] it does [19:13] also, staging only builds for xenial for some reason, I wonder if it's even used [19:14] they are both built daily anyway [19:14] I've triggered them both [19:14] plars: after this I'll need a manual jenkins run of the failed job :) https://platform-qa-jenkins.ubuntu.com/view/server/job/ubuntu-bionic-live-server-amd64-iso-static-validation/79/ [19:14] after the builds finish, of course [19:14] plars: thx [19:14] indeed, they are daily. We are just anticipating things [19:15] ahasenack: sure, np [19:16] ahasenack: as luck would have it, I even have access to that jenkins [19:16] haha :) [19:16] I logged in, and I can just see [19:21] ahasenack: it built, but that job doesn't seem to update utah... looking around to see if they have something for that already, but do you know per chance? [19:21] plars: the ppas are not done yet [19:22] https://launchpad.net/~canonical-platform-qa-jenkins/+archive/ubuntu/canonical-platform-qa-jenkins-prod/+packages [19:22] plars: the job adds that ppa [19:22] now it's done [19:22] let me check in my container [19:22] * ahasenack apt updates [19:23] yeah, new version visible, at least in bionic. I don't know what release is in that jenkins node [19:23] but all are built [19:24] plars: can you see the actual script that jenkins is running? There is no add-apt-repository or apt-update call? [19:24] ahasenack: I found info for venonat, updating it now [19:25] are you having to login to do it? [19:25] or using jenkins' script execution perhaps? [19:25] ahasenack: we could probably do it through jenkins too, but shortest path [19:25] sure [19:26] and this way I could easily see which ppa it was using too (prod) [19:26] nice [19:26] matches the code I was looking at, good to know [19:28] ahasenack: well it seemed to fail for a different reason now at least? [19:28] checking [19:29] hm, it's looking for that file in another test [19:29] ./utah/isotest/data/file_list_subiquity:casper/vmlinuz.efi [19:29] :/ [19:30] yeah [19:30] just a sec [19:30] should have grepped before [19:33] plars: https://code.launchpad.net/~ahasenack/utah/one-more-vmlinuz-rename-1766947/+merge/344346 [19:35] infinity: is there a draft up for the 18.04 release announcement, so that the product teams can have input on wording? [19:36] slangasek: Nope, feel free to do that based on a copy/waste of 16.04, if you like and aim me at it. [19:39] infinity: https://wiki.ubuntu.com/BionicBeaver/ReleaseAnnouncement [19:40] infinity: I didn't see any follow-up on list of UbuntuKylin's statement of 5y LTS? [19:45] slangasek: Ahh, balls. I forgot to do that. They're still 3y in the Packages file and that's, IMO, correct, but I suppose we should have a formal debate with them about it before we close the archive. :/ [19:45] k [19:45] tsimonq2: speaking of which, clock's ticking on lubuntu-next supported fields [19:46] slangasek: Indeed. [19:46] oh, is that going to be released, or should I grab one of the dailys to continue playing with it? [19:47] -queuebot:#ubuntu-release- Unapproved: debian-installer (bionic-proposed/main) [20101020ubuntu542 => 20101020ubuntu543] (core) [19:47] Kamilion: it is not going to be released. but currently the archive says the packages are LTS-supported, which is false. [19:47] SYN/ACK. [19:48] bdmurray: sil2100: missed my SRU day today. I can do tomorrow instead though, assuming you'll be busy with the release anyway? [19:49] infinity: why the d-i respin for openssl vs. putting that in as 0-day SRU? [19:49] slangasek: To make d-i not be built against things that no longer exist in the archive. [19:49] I mean, apparently openssl has already landed, but [19:50] AIUI openssl is only an upgrade issue. [19:50] ahasenack: success! [19:50] hoorray [19:50] #82 [19:50]