[01:34] -queuebot:#ubuntu-release- Unapproved: squashfs-tools (bionic-proposed/main) [1:4.3-6ubuntu0.18.04.1 => 1:4.3-6ubuntu0.18.04.2] (core) === stgraber is now known as stgraber_ === stgraber_ is now known as stgraber [05:21] -queuebot:#ubuntu-release- Unapproved: ceph (hirsute-proposed/main) [16.2.1-0ubuntu0.21.04.1 => 16.2.4-0ubuntu0.21.04.1] (ubuntu-desktop, ubuntu-server) [06:17] morning - the ceph upload above for hirsute ^^ is another set of security updates to complement the ones already in the queue for focal and groovy [06:17] the 16.2.1 release in proposed has completed verification yesterday and today (https://bugs.launchpad.net/bugs/1925322) [06:18] Launchpad bug 1925322 in ceph (Ubuntu Hirsute) "[SRU] ceph 16.2.1" [High, Fix Committed] [06:18] so is ready to be released [07:22] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-release-upgrader [source] (hirsute-proposed) [1:21.04.12] === guiverc2 is now known as guiverc [07:37] -queuebot:#ubuntu-release- New: accepted ubuntu-wsl-integration [amd64] (impish-proposed) [0.31.1] [07:37] -queuebot:#ubuntu-release- New: accepted ubuntu-wsl-integration [arm64] (impish-proposed) [0.31.1] [08:42] hey - an invalid change to nfs-ganesha was proposed to groovy and hirsute as part of resolving functiolnal and build failures in focal+, there is a new upload in unapproved for both that reverts the change (as well as picking up the rest of the proposed fixes) since 14 May; given that the bug target was invalid for Groovy and Hirsute, I've removed those series from the original bug (can re-add if necessary, and mark invalid maybe?) but would [08:42] appreciate getting those accepted into proposed so I can work my way through verifying that the nfs-ganesha package now works as expected :) [08:57] -queuebot:#ubuntu-release- New: accepted gnome-photos [amd64] (impish-proposed) [3.38.0-3] [08:57] -queuebot:#ubuntu-release- New: accepted gnome-photos [armhf] (impish-proposed) [3.38.0-3] [08:57] -queuebot:#ubuntu-release- New: accepted gnome-photos [riscv64] (impish-proposed) [3.38.0-3] [08:57] -queuebot:#ubuntu-release- New: accepted php-http-interop-http-factory-tests [amd64] (impish-proposed) [0.9.0-1build1] [08:57] -queuebot:#ubuntu-release- New: accepted gnome-photos [arm64] (impish-proposed) [3.38.0-3] [08:57] -queuebot:#ubuntu-release- New: accepted gnome-photos [s390x] (impish-proposed) [3.38.0-3] [08:57] -queuebot:#ubuntu-release- New: accepted gnome-photos [ppc64el] (impish-proposed) [3.38.0-3] [10:00] -queuebot:#ubuntu-release- Unapproved: konversation (focal-proposed/universe) [1.7.5-3ubuntu2 => 1.7.5-3ubuntu2.20.04.1] (kubuntu) [10:01] -queuebot:#ubuntu-release- Unapproved: konversation (groovy-proposed/universe) [1.7.5-3ubuntu2 => 1.7.5-3ubuntu2.20.10.1] (kubuntu) [10:02] -queuebot:#ubuntu-release- Unapproved: konversation (hirsute-proposed/universe) [20.12.3-0ubuntu1 => 20.12.3-0ubuntu1.1] (kubuntu) [10:03] sil2100: ^^ SRU's to take care of the move of #kubuntu etc to libera.chat [10:04] o/ On it in a bit! [10:05] ty :) [10:06] -queuebot:#ubuntu-release- Unapproved: accepted konversation [source] (hirsute-proposed) [20.12.3-0ubuntu1.1] [10:07] -queuebot:#ubuntu-release- Unapproved: accepted konversation [source] (groovy-proposed) [1.7.5-3ubuntu2.20.10.1] [10:14] RikMills: ok, so I accepted groovy and hirsute already, but I guess I see in groovy and focal that the port seems to be 8001 instead of 6697 [10:14] I mean, that was the value for the previous versions already, but in hirsute+ I see it was the correct 6697 [10:14] Is that a problem? Or does that need to be modified as well? [10:16] sil2100: I noticed as well and pondered. then decide to keep the change as minimal as possible. libera works with the 8001 (I did test), but it's just not ssl [10:17] If you think it desirable to make the switch then I could do that [10:19] though I would think that would/could be a separate bug [10:24] sil2100: actually, the older .cpp code does not have a 'server.setSSLEnabled(true)' option, so I am not 100% sure switching the port there in the code would work ok [10:24] so for now in the interests of a prompt fix, I would say go with what we have [10:37] Ok! [10:37] -queuebot:#ubuntu-release- Unapproved: accepted konversation [source] (focal-proposed) [1.7.5-3ubuntu2.20.04.1] [10:42] sil2100: thanks. the 7 days starting today is great [10:44] -queuebot:#ubuntu-release- New source: ubuntu-wsl-oobe (impish-proposed/primary) [0.1.16] [10:50] -queuebot:#ubuntu-release- Unapproved: pulseaudio (hirsute-proposed/main) [1:14.2-1ubuntu1 => 1:14.2-2ubuntu1.1] (core, i386-whitelist) [11:10] -queuebot:#ubuntu-release- Unapproved: rejected livecd-rootfs [source] (focal-proposed) [2.664.22] [11:21] -queuebot:#ubuntu-release- Unapproved: accepted ubiquity [source] (focal-proposed) [20.04.15.12] [11:37] should a test marked as flaky be interpreted as a regression even if test dependencies fail to install? see debos [11:44] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (groovy-proposed) [2.694.6] [11:48] -queuebot:#ubuntu-release- Unapproved: rejected pulseaudio [source] (hirsute-proposed) [1:14.2-2ubuntu1.1] [11:49] -queuebot:#ubuntu-release- Unapproved: pulseaudio (hirsute-proposed/main) [1:14.2-1ubuntu1 => 1:14.2-1ubuntu2] (core, i386-whitelist) [11:51] -queuebot:#ubuntu-release- Unapproved: pulseaudio (focal-proposed/main) [1:13.99.1-1ubuntu3.10 => 1:13.99.1-1ubuntu3.11] (desktop-core, i386-whitelist, ubuntu-server) [11:55] -queuebot:#ubuntu-release- Unapproved: alsa-ucm-conf (focal-proposed/main) [1.2.2-1ubuntu0.7 => 1.2.2-1ubuntu0.8] (no packageset) [11:57] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (focal-proposed) [2.664.23] [11:57] -queuebot:#ubuntu-release- New: accepted ubuntu-wsl-oobe [source] (impish-proposed) [0.1.16] [12:04] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (bionic-proposed) [2.525.54] [13:05] sil2100, thanks for the SRUs of AD. There is also golang 1.16 in NEW for focal. The only diff with impish is the version of debhelper [13:51] jibel: o/ [13:53] -queuebot:#ubuntu-release- New: accepted llvm-toolchain-12 [amd64] (focal-proposed) [1:12.0.0-3ubuntu1~20.04.1] [13:53] -queuebot:#ubuntu-release- New: accepted llvm-toolchain-12 [armhf] (focal-proposed) [1:12.0.0-3ubuntu1~20.04.1] [13:53] -queuebot:#ubuntu-release- New: accepted llvm-toolchain-12 [ppc64el] (focal-proposed) [1:12.0.0-3ubuntu1~20.04.1] [13:53] -queuebot:#ubuntu-release- New: accepted llvm-toolchain-12 [arm64] (focal-proposed) [1:12.0.0-3ubuntu1~20.04.1] [13:53] -queuebot:#ubuntu-release- New: accepted llvm-toolchain-12 [s390x] (focal-proposed) [1:12.0.0-3ubuntu1~20.04.1] [13:53] -queuebot:#ubuntu-release- New: accepted llvm-toolchain-12 [i386] (focal-proposed) [1:12.0.0-3ubuntu1~20.04.1] [13:54] jibel: ok, looks sane [13:55] -queuebot:#ubuntu-release- New: accepted golang-1.16 [source] (focal-proposed) [1.16.2-0ubuntu1~20.04] [13:56] sil2100, Thanks [14:03] -queuebot:#ubuntu-release- New binary: ubuntu-wsl-oobe [amd64] (impish-proposed/universe) [0.1.17] (no packageset) [14:04] -queuebot:#ubuntu-release- New binary: ubuntu-wsl-oobe [arm64] (impish-proposed/universe) [0.1.17] (no packageset) [14:07] -queuebot:#ubuntu-release- New binary: golang-1.16 [s390x] (focal-proposed/universe) [1.16.2-0ubuntu1~20.04] (no packageset) [14:08] seb128: ubuntu-wsl-oobe ^ FYI [14:10] -queuebot:#ubuntu-release- New binary: golang-1.16 [ppc64el] (focal-proposed/universe) [1.16.2-0ubuntu1~20.04] (no packageset) [14:16] -queuebot:#ubuntu-release- New binary: golang-1.16 [amd64] (focal-proposed/universe) [1.16.2-0ubuntu1~20.04] (no packageset) [14:17] -queuebot:#ubuntu-release- New binary: golang-1.16 [armhf] (focal-proposed/universe) [1.16.2-0ubuntu1~20.04] (no packageset) [14:18] -queuebot:#ubuntu-release- New binary: golang-1.16 [arm64] (focal-proposed/universe) [1.16.2-0ubuntu1~20.04] (no packageset) [14:23] didrocks, ack [14:27] In Launchpad, the precise distro_series is still listed as "active". However, it doesn't appear in apt any more at http://archive.ubuntu.com/ubuntu/dists/. [14:27] This is breaking git-ubuntu, which uses the active series list from Launchpad to decide what apt suites exist. [14:27] Did someone move precise to old-releases recently? [14:27] If so, shouldn't the Launchpad series be changed to match? [14:30] ubuntu-archive: ^ [14:30] In [7]: lp.load('https://api.launchpad.net/devel/ubuntu/precise').status [14:30] Out[7]: 'Supported' [14:36] -queuebot:#ubuntu-release- New: accepted ubuntu-wsl-oobe [amd64] (impish-proposed) [0.1.17] [14:36] -queuebot:#ubuntu-release- New: accepted ubuntu-wsl-oobe [arm64] (impish-proposed) [0.1.17] [14:38] cjwatson, ^ [14:38] It's not really up to us, this is all in https://wiki.ubuntu.com/EndOfLifeProcess [14:39] If somebody only did like half the process, then maybe they shouldn't have done that ;-) [14:39] But whoever it was didn't consult with us [14:41] I think this is one of those things that has got worse since infinity stopped handling it :-( [14:41] But it *should* pretty much all be documented [14:42] Incidentally, I wondered if I might have the appropriate button (not that I'd press it without an ack from someone appropriate), but I couldn't find an API method. And https://launchpad.net/ubuntu/precise gives me OOPS-3a6747846d18659364851cc558f00bfa. [14:42] Oh, the status property is just "writeable". [14:47] -queuebot:#ubuntu-release- New: accepted golang-1.16 [amd64] (focal-proposed) [1.16.2-0ubuntu1~20.04] [14:48] -queuebot:#ubuntu-release- New: accepted golang-1.16 [armhf] (focal-proposed) [1.16.2-0ubuntu1~20.04] [14:48] -queuebot:#ubuntu-release- New: accepted golang-1.16 [s390x] (focal-proposed) [1.16.2-0ubuntu1~20.04] [14:48] -queuebot:#ubuntu-release- New: accepted golang-1.16 [arm64] (focal-proposed) [1.16.2-0ubuntu1~20.04] [14:48] -queuebot:#ubuntu-release- New: accepted golang-1.16 [ppc64el] (focal-proposed) [1.16.2-0ubuntu1~20.04] [14:50] https://wiki.canonical.com/InformationInfrastructure/OSA/LPHowTo/ObsoleteDistroSeries needs to be followed before doing that [14:51] Normally IIRC it involves getting acks from various people first though [14:51] Bugs in that form are likely pretty much negative priority since it's pretty rarely used :) [14:52] I wonder what I can easily do in git-ubuntu instead. [14:52] Hardcode "don't touch precise" I suppose :) [14:53] juliank: so where we are at with grub2 in bionic? cause we are currently failing testing of kernels that kind of have to go out this week. and [14:53] we fail our adt-testing, cause we fail to reboot into new kernels sometimes. [14:53] xnox: bionic was good always [14:53] juliank: hm...... not what I see. [14:53] let me check again [14:54] juliank: have you removed grubaa64.efi from \efi\boot\ path? [14:54] xnox: let me finish my 1:1 [14:58] ok [14:58] juliank: so stuff like this is not nice at the moment https://autopkgtest.ubuntu.com/packages/d/dahdi-linux/bionic/arm64 [14:58] which is indicative that we fail to reboot our bionic cloud images. [14:59] i guess a rebuilt new bionic cloud image (from fresh) may fix it, as grub2.04 will be in all the places. [14:59] xnox: Yes, we can't reboot because qemu is crashing [14:59] xnox: Not sure if same issue [14:59] xnox: What I meant is I had no concerns about the bionic update [15:00] right, but to test bionic kernel SRUs we must reboot into the new kernel. [15:02] ie. https://people.canonical.com/~kernel/status/adt-matrix/bionic-linux-meta-snapdragon.html [15:03] we have like half a dozen kernels that are missing adt testing on arm64 for bionic. [15:05] xnox: but that dahdi things looks like kernel bug, not grub bug, and the grub update we are doing is for the conffile change [15:05] xnox: so it should already use 2.04 [15:06] xnox: and qemu crashes, I'm not sure if related, but see https://portal.admin.canonical.com/C131118/ [15:11] xnox: ah but not all end with "Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000005" [15:11] juliank: should i retrigger them all to get fresher results? and failure rates? [15:13] xnox: all I can say is that from the grub side, all releases already _are_ on 2.04 [15:13] xnox: And the autopkgtest image is built daily with a dist-upgrade [15:14] horum [15:15] xnox: but there are build failures of those images I can dig into more [15:15] juliank: we have a bad cloud then. i thought that arm64 cloud is on [15:15] the cloud-archive [15:15] aka qemu from later series.... that should be fixed up [15:17] xnox: i have no idea, hence opened rt ticket [15:17] :D [15:17] python-flake8 is having issues in focal-proposed: https://bugs.launchpad.net/ubuntu/+source/python-flake8/+bug/1929841 [15:17] Launchpad bug 1929841 in python-flake8 (Ubuntu) "python3-flake8 dependency issues in focal-proposed" [Undecided, New] [15:17] xnox: I can confirm that our autopkgtest images on bos01 were last built on may 5 for bionic, and may 6 for xenial, and have failed to build since then [15:18] xnox: on bos02, all images are current [15:19] I gave arnatious a ping about that in MM ^ (he's not in here) [15:19] xnox: so I guess bos01 is a bit weird [15:20] xnox: which is also where canonistack is where I got the crash :D [15:21] xnox: wondering if I can copy images between cliuds :D [15:22] juliank: you can download image and upload it again. [15:22] juliank: there is bos02 for arm64 too? can you take out bos01 out of autopkgtest cloud; then i retrigger all the tests; and then we can see if they will all work. [15:22] blocking building new kernels for all series, starting like next week. [15:23] juliank: if we think only bos01 is affected. [15:23] cpaelzer is not here yet. [15:23] xnox: one second [15:26] xnox: please retry now [15:26] juliank: ok. [15:29] juliank: loading them up [15:30] xnox: I think the dahdi-linux you linked never passed before, fwiw [15:30] juliank: sure, but we want to see that we booted with the target kernel we asked; and attempt the test; to see in the logs that we have at least tried to run it against the new kernel. [15:30] otherwise the kernel team automation says "you didn't even give it a chance" [15:31] heh [15:31] the kernel team's adt-matrix is more strict then pure britney [15:35] sil2100: hi, I wonder if we should consider reverting the changes for this: 1883175 [15:35] bug 1883175 [15:36] https://pad.lv/1883175 [15:36] xnox: I might have to move your tests into the huge queues, given the number [15:37] :- [15:37] :-( [15:37] juliank: it's just _some_ kernels [15:37] xnox: atm it's ok either way :) [15:37] juliank: i need to improve kernel's team tooling to kind of like call the retry-autopkgtest stuff and/or like share flags for it. [15:38] Note that we operate at 12 out of of 36 workers now [15:38] it's going to be slow [15:39] juliank: as long as we get results.... [15:39] it's weekend soon, so :D [15:39] coreycb: hah! paride just poked about this on -devel, I'll be removing the SRU from -proposed after my meeting (soon) [15:40] also US is out on Monday, so :D:D [15:40] UK too [15:40] coreycb: I think it's fine to revert the change later on [15:40] We can fill up the queues like mad people [15:40] sil2100: awesome! ty, I should have checked over there. [15:40] xnox: fascinating [15:40] xnox: /me also needs to do a week of digital detox next week [16:11] juliank: so stock bionic arm64 images have grub in removable path ; and in ubuntu path and that's it. [16:11] juliank: i guess they must update both paths, do they? [16:11] xnox: yes, they do [16:12] juliank: great. [16:12] xnox: bionic made extra-removable the default, changing the option from --force-extra-removable to --no-extra-removable [16:12] well sometime between xenial and bionic :D [16:12] great. [16:15] xnox: we can also fix that in xenial autopkgtest image by setting --force-extra-removable option there for those ESM things [16:16] I need to go eat dinner any minute now, though, and eod [16:16] I'm sooo tired [16:16] Maybe it's hay fever :D [16:22] maybe it's covid [16:22] =/ just in case. test? [16:24] juliank: such a xenial image fix would be nice in adt; but also for our xenial arm64 images too which we still need to build "the last one" [16:25] and the xenial aws image we build [16:25] arm64 [16:38] xnox: nah, it's not unnormal for me to be half dead between 4 and 8 pm [16:39] xnox: yeah we could set the right debconf in final xenial image too [16:52] -queuebot:#ubuntu-release- Unapproved: systemd (groovy-proposed/main) [246.6-1ubuntu1.3 => 246.6-1ubuntu1.4] (core, i386-whitelist) [16:56] -queuebot:#ubuntu-release- Unapproved: systemd (focal-proposed/main) [245.4-4ubuntu3.6 => 245.4-4ubuntu3.7] (core, i386-whitelist) [16:57] -queuebot:#ubuntu-release- Unapproved: systemd (bionic-proposed/main) [237-3ubuntu10.47 => 237-3ubuntu10.48] (core) [17:54] -queuebot:#ubuntu-release- Unapproved: systemd (hirsute-proposed/main) [247.3-3ubuntu3 => 247.3-3ubuntu3.1] (core, i386-whitelist) [20:02] -queuebot:#ubuntu-release- Unapproved: neutron (focal-proposed/main) [2:16.3.1-0ubuntu1.1 => 2:16.3.2-0ubuntu2] (openstack, ubuntu-server) === ossurayynot is now known as tonyyarusso [20:16] -queuebot:#ubuntu-release- Unapproved: update-manager (hirsute-proposed/main) [1:21.04.10 => 1:21.04.11] (core) [20:22] hello SRU team, we have a high impact bug for neutron in the focal queue if someone can take a look. [20:24] coreycb: I'm your huckelberry [20:24] your bad typing one but still [20:28] -queuebot:#ubuntu-release- Unapproved: rejected neutron [source] (focal-proposed) [2:16.3.2-0ubuntu1] [20:33] -queuebot:#ubuntu-release- Unapproved: update-manager (groovy-proposed/main) [1:20.10.6 => 1:20.10.7] (core) [20:35] SRU Team: Still waiting on an ack for bug 1928146. [20:35] Bug 1928146 in nvidia-modprobe (Ubuntu Hirsute) "Please SRU nvidia-modprobe 465.24" [High, Fix Committed] https://launchpad.net/bugs/1928146 [20:36] -queuebot:#ubuntu-release- Unapproved: accepted neutron [source] (focal-proposed) [2:16.3.2-0ubuntu2] [20:38] xnox: sorry, the bos01 workers restarted, I now disabled them in mojo [20:40] xnox: i think dahdi-linux looked better now [20:40] I'm off until the monday after next week [20:52] bdmurray: lol thank you [20:53] -queuebot:#ubuntu-release- Unapproved: update-manager (focal-proposed/main) [1:20.04.10.7 => 1:20.04.10.8] (core) [21:23] -queuebot:#ubuntu-release- Unapproved: update-manager (bionic-proposed/main) [1:18.04.11.13 => 1:18.04.11.14] (core) [22:44] juliank: yes, but not everywhere. [22:45] so over at https://autopkgtest.ubuntu.com/packages/d/dahdi-linux/bionic/arm64 [22:45] the linux-meta/4.15.0.144.131 result is bad, and not because the module failed to build.