[00:07] -queuebot:#ubuntu-release- Packageset: Removed extra-cmake-modules from i386-whitelist in plucky [01:45] -queuebot:#ubuntu-release- Unapproved: containerd-app (jammy-proposed/universe) [1.7.12-0ubuntu2~22.04.1 => 1.7.19-0ubuntu1~22.04.1] (no packageset) [01:47] -queuebot:#ubuntu-release- Unapproved: containerd-app (focal-proposed/universe) [1.7.12-0ubuntu2~20.04.1 => 1.7.19-0ubuntu1~20.04.1] (no packageset) [05:26] -queuebot:#ubuntu-release- New binary: rust-version-ranges [arm64] (plucky-proposed/none) [0.1.0-1] (no packageset) [05:26] -queuebot:#ubuntu-release- New binary: rust-version-ranges [ppc64el] (plucky-proposed/none) [0.1.0-1] (no packageset) [05:26] -queuebot:#ubuntu-release- New binary: rust-version-ranges [armhf] (plucky-proposed/none) [0.1.0-1] (no packageset) [05:26] -queuebot:#ubuntu-release- New binary: rust-version-ranges [s390x] (plucky-proposed/none) [0.1.0-1] (no packageset) [05:27] -queuebot:#ubuntu-release- New binary: glosstex [arm64] (plucky-proposed/none) [0.4.dfsg.1-4.1] (no packageset) [05:27] -queuebot:#ubuntu-release- New binary: glosstex [ppc64el] (plucky-proposed/none) [0.4.dfsg.1-4.1] (no packageset) [05:27] -queuebot:#ubuntu-release- New binary: glosstex [armhf] (plucky-proposed/none) [0.4.dfsg.1-4.1] (no packageset) [05:27] -queuebot:#ubuntu-release- New binary: glosstex [s390x] (plucky-proposed/none) [0.4.dfsg.1-4.1] (no packageset) [05:35] -queuebot:#ubuntu-release- New binary: pyvicare [amd64] (plucky-proposed/none) [2.32.0-1] (no packageset) [05:35] -queuebot:#ubuntu-release- New binary: rust-version-ranges [amd64] (plucky-proposed/none) [0.1.0-1] (no packageset) [05:36] -queuebot:#ubuntu-release- New binary: glosstex [amd64] (plucky-proposed/none) [0.4.dfsg.1-4.1] (no packageset) [06:34] -queuebot:#ubuntu-release- New binary: rust-version-ranges [riscv64] (plucky-proposed/universe) [0.1.0-1] (no packageset) [06:42] -queuebot:#ubuntu-release- New binary: glosstex [riscv64] (plucky-proposed/universe) [0.4.dfsg.1-4.1] (no packageset) [07:12] -queuebot:#ubuntu-release- New: accepted glosstex [amd64] (plucky-proposed) [0.4.dfsg.1-4.1] [07:12] -queuebot:#ubuntu-release- New: accepted glosstex [armhf] (plucky-proposed) [0.4.dfsg.1-4.1] [07:12] -queuebot:#ubuntu-release- New: accepted glosstex [riscv64] (plucky-proposed) [0.4.dfsg.1-4.1] [07:12] -queuebot:#ubuntu-release- New: accepted mysql-8.4 [source] (plucky-proposed) [8.4.3-0ubuntu1] [07:12] -queuebot:#ubuntu-release- New: accepted rust-version-ranges [amd64] (plucky-proposed) [0.1.0-1] [07:12] -queuebot:#ubuntu-release- New: accepted rust-version-ranges [armhf] (plucky-proposed) [0.1.0-1] [07:12] -queuebot:#ubuntu-release- New: accepted rust-version-ranges [riscv64] (plucky-proposed) [0.1.0-1] [07:12] -queuebot:#ubuntu-release- New: accepted glosstex [arm64] (plucky-proposed) [0.4.dfsg.1-4.1] [07:12] -queuebot:#ubuntu-release- New: accepted glosstex [s390x] (plucky-proposed) [0.4.dfsg.1-4.1] [07:12] -queuebot:#ubuntu-release- New: accepted rust-version-ranges [arm64] (plucky-proposed) [0.1.0-1] [07:12] -queuebot:#ubuntu-release- New: accepted rust-version-ranges [s390x] (plucky-proposed) [0.1.0-1] [07:12] -queuebot:#ubuntu-release- New: accepted glosstex [ppc64el] (plucky-proposed) [0.4.dfsg.1-4.1] [07:12] -queuebot:#ubuntu-release- New: accepted rust-version-ranges [ppc64el] (plucky-proposed) [0.1.0-1] [07:12] -queuebot:#ubuntu-release- New: accepted pyvicare [amd64] (plucky-proposed) [2.32.0-1] [07:14] sru-team: can we move forward with https://bugs.launchpad.net/ubuntu/+source/containerd-app/+bug/2065423 please? this blocks the public cloud team from releasing EKS Noble images [07:14] -ubottu:#ubuntu-release- Launchpad bug 2065423 in docker.io-app (Ubuntu Noble) "Update AppArmor template to allow confined runc to kill containers" [Undecided, Fix Committed] [07:23] -queuebot:#ubuntu-release- New binary: mysql-8.4 [armhf] (plucky-proposed/none) [8.4.3-0ubuntu1] (no packageset) [07:26] toabctl: lp2040461 is unverified [07:34] tjaalton, what needs to be verified? noble is verified and I don't see what other series is affected. [07:44] this bug isn't [07:45] and it's more than just containerd-app, the whole container stack [07:53] -queuebot:#ubuntu-release- New: accepted linux-firmware-nvidia-tegra [arm64] (noble-proposed) [36.4.0-20240912212859-0ubuntu1~24.04] [07:54] -queuebot:#ubuntu-release- New: accepted linux-firmware-nvidia-tegra [arm64] (jammy-proposed) [36.4.0-20240912212859-0ubuntu1~22.04] [07:59] and it's only 6d old [09:41] -queuebot:#ubuntu-release- New binary: mysql-8.4 [s390x] (plucky-proposed/universe) [8.4.3-0ubuntu1] (no packageset) [09:45] ubuntu-archive can somebody reject the fwupd-efi builds in plucky? We want to try copying in the fwupd-efi builds from the build PPA instead like we did in https://launchpad.net/ubuntu/+source/fwupd-efi/1:1.4-1 - as we just signed those [09:45] CC mkukri ^ [09:46] Launchpad rejects copies while the existing builds are in unpublished state but looking back at that build it works once they are rejected [09:47] juliank, rejected [09:47] -queuebot:#ubuntu-release- Unapproved: rejected fwupd-efi [amd64] (plucky-proposed) [1:1.7-1] [09:47] Also I guess we could tweak tooling now to auto-accept fwupd-efi; there's no need to block them, signing doesn't happen in the archive anymore - then we can binary copy them to the build PPA for signing as an inverse solution :) [09:47] -queuebot:#ubuntu-release- Unapproved: rejected fwupd-efi [armhf] (plucky-proposed) [1:1.7-1] [09:47] -queuebot:#ubuntu-release- Unapproved: rejected fwupd-efi [arm64] (plucky-proposed) [1:1.7-1] [09:47] -queuebot:#ubuntu-release- Unapproved: rejected fwupd-efi [riscv64] (plucky-proposed) [1:1.7-1] [09:47] apw: thanks [09:49] Let's see what it says for the copy-package now [09:50] I guess I gotta wait for the publisher run [10:37] -queuebot:#ubuntu-release- New binary: mysql-8.4 [ppc64el] (plucky-proposed/universe) [8.4.3-0ubuntu1] (no packageset) [10:48] -queuebot:#ubuntu-release- New binary: mysql-8.4 [amd64] (plucky-proposed/universe) [8.4.3-0ubuntu1] (no packageset) [10:50] -queuebot:#ubuntu-release- New source: mofed-modules-24.10 (plucky-proposed/primary) [24.10.0.7.0.0+ds1-0ubuntu1] [10:57] -queuebot:#ubuntu-release- Unapproved: nvidia-tegra-defaults (oracular-proposed/universe) [1.3 => 1.4~24.10] (no packageset) [11:14] -queuebot:#ubuntu-release- New binary: mysql-8.4 [arm64] (plucky-proposed/universe) [8.4.3-0ubuntu1] (no packageset) [13:19] apw: OK that did not help, I think we need to reject the source too and then that gets copied back in and doesn't conflict [13:20] Still easier than redoing the signing :D [13:22] juliank, was it copied into the signing pipeline from the archive copy? [13:22] apw: yeah, source copy from ubuntu to ubuntu-uefi-team/build [13:23] juliank, so i would expect you to be able to copy back over it, if it never built [13:23] what does it say when you did it. [13:24] apw: fwupd-efi 1:1.7-1 in plucky (same version has unpublished binaries in the destination archive for Plucky, please wait for them to be published before copying) [13:24] 1:1.4-1 we seemingly rejected at the source package level too [13:24] Looking at https://launchpad.net/ubuntu/+source/fwupd-efi/1%3A1.4-1/+publishinghistory [13:25] For 1:1.6-1 we failed to figure out what we did there, but I think this should work now [13:25] I don't see a difference otherwise in state between the 1.4 and 1.7 binaries [13:26] right, but 1:1.7-1 has already been accepted [13:26] so rejecting it has no meaning. [13:27] apw: oh I meant remove it :D [13:27] Then it will copy the same artefact back into the archive and it should stop complaining about having unpublished binaries [13:27] we routinely copy in sources already published in the destination to trigger builds [13:28] In an optimal world we'd have the auto syncer sync fwupd-efi directly to the build PPA I suppose [13:28] so i don't think it should care [13:28] Removal requested on 2023-03-10. [13:28] Deleted on 2023-03-10 by Steve Langasek [13:28] Removed in favor of sync from signing ppa [13:28] All I can say is that this seemed to work [13:28] ok, will do that and we can see if it helps. [13:28] I think ultimately there is a bug in Launchpad where it considers rejected binaries as waiting for approval [13:29] Whereas to trigger a build is different because there is no build it waits for approval of [13:31] that sounds believable. [13:31] removed. [13:32] apw: thanks, and it accepted my copy now [13:32] * apw gives launchpad the side-eyes [13:37] juliank, given fwupd-efi comes from debian and contains no ubuntu signing, why can that not just drop into proposed directly [13:37] then you could copy that wiht binaries into the signing pipeline and add a coresponding -signed [13:38] and then only copy in the -signed. [13:42] apw: that works too, I think [13:42] apw: Kind of needs an auto-accept bot [13:42] Because all signing tarballs still land in unapproved and it builds them [13:43] But we don't actually sign anymore or rather reject the signed binaries with the old archive key automatically [13:43] So having the binaries go through unapproved is just unnecessary work [13:43] juliank, we moved to a "generate" model for all of our signed packages [13:43] to avoid this very issue. and the signing pipeline understands this model. [13:44] apw: how does that work? [13:45] juliank, rather than foo producing the signing tarball, we have a third (middle) package which consume foo and produces the custom-binary upload, and signed consumes that in the normal way [13:45] and signing knows that generate is only needed through the signing pipeline, and not published out the end. [13:46] foo -> foo-generate -> foo-signed [13:46] hmm [13:47] I'd love if the tooling could generate the generate package itself from the Vcs :D [13:47] (and the signed package fwiw) [13:47] juliank, we have something to do that too; modelled on the signed-template support [13:48] So you upload fwupd-efi, it builds fwupd-efi-generate from git recipe and then fwupd-signed [13:48] We need that :D [13:48] juliank, if you look at our -generate packages they are "ancillary" packages built from the signed [13:50] apw: I see [13:50] apw: But they don't get generated automagically if you upload signed, do they? [13:51] I was wondering what launchpad does if you just stuff multiple .dsc into a single changes file [13:51] juliank, not magically no, the signed source carries the information to make them, and our bot does the rest. [13:52] This would be super helpful for grub (and fwupd-efi if less regularly :D) [13:52] We really need to align this closer [13:52] juliank, lets talk in our coffee meeting, and i can help make that happen [13:53] ack [14:44] -queuebot:#ubuntu-release- New sync: klevernotes (plucky-proposed/primary) [1.1.0-1] === dviererbe1 is now known as dviererbe === fuseteam1 is now known as fuseteam [14:56] -queuebot:#ubuntu-release- New: accepted 0ad [amd64] (oracular-proposed) [0.0.26-6ubuntu0.24.10.1] [14:56] -queuebot:#ubuntu-release- New: accepted 0ad [armhf] (oracular-proposed) [0.0.26-6ubuntu0.24.10.1] [14:56] -queuebot:#ubuntu-release- New: accepted 0ad [arm64] (oracular-proposed) [0.0.26-6ubuntu0.24.10.1] [16:00] -queuebot:#ubuntu-release- Unapproved: python-cepces (oracular-proposed/universe) [0.3.7-0ubuntu1 => 0.3.7-0ubuntu1.24.10.1] (no packageset) [16:07] -queuebot:#ubuntu-release- Unapproved: python-cepces (noble-proposed/universe) [0.3.7-0ubuntu1 => 0.3.7-0ubuntu1.24.04.1] (no packageset) [16:18] -queuebot:#ubuntu-release- Unapproved: packagekit (oracular-proposed/main) [1.3.0-1 => 1.3.0-1ubuntu1] (core) [16:18] -queuebot:#ubuntu-release- Unapproved: rejected packagekit [source] (oracular-proposed) [1.3.0-1ubuntu1] [16:18] -queuebot:#ubuntu-release- Unapproved: packagekit (noble-proposed/main) [1.2.8-2build3 => 1.2.8-2ubuntu1] (core) [16:20] -queuebot:#ubuntu-release- Unapproved: packagekit (jammy-proposed/main) [1.2.5-2ubuntu2 => 1.2.5-2ubuntu3] (core) === fuseteam1 is now known as fuseteam [17:29] -queuebot:#ubuntu-release- New binary: libjpeg-turbo [i386] (plucky-proposed/main) [2.1.5-3ubuntu2] (core, i386-whitelist) [17:29] -queuebot:#ubuntu-release- New binary: libjpeg-turbo [s390x] (plucky-proposed/main) [2.1.5-3ubuntu2] (core, i386-whitelist) [17:30] -queuebot:#ubuntu-release- New binary: libjpeg-turbo [amd64] (plucky-proposed/main) [2.1.5-3ubuntu2] (core, i386-whitelist) [17:32] -queuebot:#ubuntu-release- New binary: libjpeg-turbo [arm64] (plucky-proposed/main) [2.1.5-3ubuntu2] (core, i386-whitelist) [17:32] -queuebot:#ubuntu-release- New binary: libjpeg-turbo [ppc64el] (plucky-proposed/main) [2.1.5-3ubuntu2] (core, i386-whitelist) [17:33] -queuebot:#ubuntu-release- New binary: libjpeg-turbo [armhf] (plucky-proposed/main) [2.1.5-3ubuntu2] (core, i386-whitelist) [17:59] -queuebot:#ubuntu-release- New binary: libjpeg-turbo [riscv64] (plucky-proposed/main) [2.1.5-3ubuntu2] (core, i386-whitelist) [18:16] -queuebot:#ubuntu-release- New: accepted klevernotes [sync] (plucky-proposed) [1.1.0-1] [18:16] -queuebot:#ubuntu-release- New: accepted libjpeg-turbo [arm64] (plucky-proposed) [2.1.5-3ubuntu2] [18:16] -queuebot:#ubuntu-release- New: accepted libjpeg-turbo [i386] (plucky-proposed) [2.1.5-3ubuntu2] [18:16] -queuebot:#ubuntu-release- New: accepted libjpeg-turbo [riscv64] (plucky-proposed) [2.1.5-3ubuntu2] [18:16] -queuebot:#ubuntu-release- New: accepted libjpeg-turbo [amd64] (plucky-proposed) [2.1.5-3ubuntu2] [18:16] -queuebot:#ubuntu-release- New: accepted libjpeg-turbo [ppc64el] (plucky-proposed) [2.1.5-3ubuntu2] [18:16] -queuebot:#ubuntu-release- New: accepted libjpeg-turbo [armhf] (plucky-proposed) [2.1.5-3ubuntu2] [18:16] -queuebot:#ubuntu-release- New: accepted libjpeg-turbo [s390x] (plucky-proposed) [2.1.5-3ubuntu2] [19:43] ubuntu-release: I know somebody is probably working on it with the build failures and all, but did anyone happen to branch ubuntu-imagesfor plucky yet? [20:24] if someone wants to work out a hint for the exiv2 revdeps that are in -proposed and not migrating, this would fix the ubuntustudio build failure... [20:27] vorlon: Also affected edubuntu. [20:27] * Eickmeyer is juggling a lot today [20:35] -queuebot:#ubuntu-release- Unapproved: shadow (noble-proposed/main) [1:4.13+dfsg1-4ubuntu3.2 => 1:4.13+dfsg1-4ubuntu3.3] (core, i386-whitelist) [21:01] -queuebot:#ubuntu-release- Unapproved: accepted cockpit-machines [source] (noble-backports) [323-1~bpo24.04.1] [21:01] -queuebot:#ubuntu-release- Unapproved: accepted cockpit [source] (noble-backports) [327-1~bpo24.04.1] [21:02] -queuebot:#ubuntu-release- Unapproved: accepted cockpit-podman [source] (noble-backports) [98-1~bpo24.04.1] [21:11] -queuebot:#ubuntu-release- Unapproved: python-libmaas (oracular-proposed/universe) [0.6.8-0ubuntu2 => 0.6.8-0ubuntu2.24.10.1] (no packageset) [21:13] -queuebot:#ubuntu-release- Unapproved: python-libmaas (noble-proposed/universe) [0.6.8-0ubuntu2 => 0.6.8-0ubuntu2.24.04.1] (no packageset) [21:13] -queuebot:#ubuntu-release- Unapproved: python-libmaas (jammy-proposed/universe) [0.6.8-0ubuntu0.22.04.1 => 0.6.8-0ubuntu0.22.04.2] (no packageset) [21:44] * sudip can try a hint for exiv2 revdeps tomorrow if no-one else has done by then. [21:55] vorlon: entangled with boost1.83 and openmpi, so may take a while [23:07] -queuebot:#ubuntu-release- Packageset: Added liblist-moreutils-xs-perl to i386-whitelist in plucky [23:29] -queuebot:#ubuntu-release- New binary: dxvk [amd64] (plucky-proposed/universe) [2.5.1-1] (no packageset) [23:31] -queuebot:#ubuntu-release- New binary: dxvk [armhf] (plucky-proposed/universe) [2.5.1-1] (no packageset) [23:33] -queuebot:#ubuntu-release- New binary: dxvk [arm64] (plucky-proposed/universe) [2.5.1-1] (no packageset)