[00:02] -queuebot:#ubuntu-release- New binary: libdevice-i2c-perl [riscv64] (lunar-proposed/universe) [0.06-1] (no packageset)
[02:43] -queuebot:#ubuntu-release- Unapproved: ubuntustudio-installer (kinetic-proposed/universe) [0.13 => 0.13.1] (ubuntustudio)
[05:24] -queuebot:#ubuntu-release- New binary: libdevice-i2c-perl [arm64] (lunar-proposed/universe) [0.06-2] (no packageset)
[05:24] -queuebot:#ubuntu-release- New binary: libio-termios-perl [amd64] (lunar-proposed/universe) [0.09-2] (no packageset)
[05:24] -queuebot:#ubuntu-release- New binary: libdevice-i2c-perl [armhf] (lunar-proposed/universe) [0.06-2] (no packageset)
[05:25] -queuebot:#ubuntu-release- New binary: libdevice-i2c-perl [amd64] (lunar-proposed/universe) [0.06-2] (no packageset)
[05:25] -queuebot:#ubuntu-release- New binary: libdevice-i2c-perl [ppc64el] (lunar-proposed/universe) [0.06-2] (no packageset)
[05:25] -queuebot:#ubuntu-release- New binary: gnome-browser-connector [amd64] (lunar-proposed/universe) [42.1-3] (no packageset)
[05:28] -queuebot:#ubuntu-release- New binary: libdevice-i2c-perl [s390x] (lunar-proposed/universe) [0.06-2] (no packageset)
[05:48] -queuebot:#ubuntu-release- New binary: libdevice-i2c-perl [riscv64] (lunar-proposed/universe) [0.06-2] (no packageset)
[08:22] -queuebot:#ubuntu-release- New: accepted gnome-browser-connector [amd64] (lunar-proposed) [42.1-3]
[08:22] -queuebot:#ubuntu-release- New: accepted libdevice-i2c-perl [arm64] (lunar-proposed) [0.06-1]
[08:22] -queuebot:#ubuntu-release- New: accepted libdevice-i2c-perl [ppc64el] (lunar-proposed) [0.06-1]
[08:22] -queuebot:#ubuntu-release- New: accepted libdevice-i2c-perl [s390x] (lunar-proposed) [0.06-1]
[08:22] -queuebot:#ubuntu-release- New: accepted libdevice-i2c-perl [arm64] (lunar-proposed) [0.06-2]
[08:22] -queuebot:#ubuntu-release- New: accepted libdevice-i2c-perl [ppc64el] (lunar-proposed) [0.06-2]
[08:22] -queuebot:#ubuntu-release- New: accepted libdevice-i2c-perl [s390x] (lunar-proposed) [0.06-2]
[08:22] -queuebot:#ubuntu-release- New: accepted libio-termios-perl [amd64] (lunar-proposed) [0.09-2]
[08:22] -queuebot:#ubuntu-release- New: accepted libsyntax-highlight-perl-perl [amd64] (lunar-proposed) [1.00-2]
[08:22] -queuebot:#ubuntu-release- New: accepted ruby-telesign [amd64] (lunar-proposed) [2.2.3-1]
[08:22] -queuebot:#ubuntu-release- New: accepted libdevice-i2c-perl [amd64] (lunar-proposed) [0.06-1]
[08:22] -queuebot:#ubuntu-release- New: accepted libdevice-i2c-perl [riscv64] (lunar-proposed) [0.06-1]
[08:22] -queuebot:#ubuntu-release- New: accepted libdevice-i2c-perl [armhf] (lunar-proposed) [0.06-2]
[08:22] -queuebot:#ubuntu-release- New: accepted libio-termios-perl [amd64] (lunar-proposed) [0.09-1]
[08:22] -queuebot:#ubuntu-release- New: accepted mpv.el [amd64] (lunar-proposed) [0.2.0-1]
[08:22] -queuebot:#ubuntu-release- New: accepted libdevice-i2c-perl [armhf] (lunar-proposed) [0.06-1]
[08:22] -queuebot:#ubuntu-release- New: accepted libdevice-i2c-perl [riscv64] (lunar-proposed) [0.06-2]
[08:22] -queuebot:#ubuntu-release- New: accepted libdevice-i2c-perl [amd64] (lunar-proposed) [0.06-2]
[08:22] -queuebot:#ubuntu-release- New: accepted libmath-amoeba-perl [amd64] (lunar-proposed) [0.05-2]
[10:10] -queuebot:#ubuntu-release- New binary: dpdk [amd64] (lunar-proposed/main) [22.11.1-2] (kernel-dkms, ubuntu-server)
[10:16] -queuebot:#ubuntu-release- New binary: dpdk [ppc64el] (lunar-proposed/main) [22.11.1-2] (kernel-dkms, ubuntu-server)
[10:20] -queuebot:#ubuntu-release- New binary: dpdk [arm64] (lunar-proposed/main) [22.11.1-2] (kernel-dkms, ubuntu-server)
[11:03] -queuebot:#ubuntu-release- New binary: libtk-codetext-perl [amd64] (lunar-proposed/universe) [0.3.4-2] (no packageset)
[12:54] -queuebot:#ubuntu-release- Unapproved: php7.4 (focal-proposed/main) [7.4.3-4ubuntu2.15 => 7.4.3-4ubuntu2.16] (i386-whitelist, ubuntu-server)
[15:02] <kanashiro[m]> rbasak: could you take a look at the container stack SRUs (runc/containerd/docker.io)? Some users are complaining especially because containerd in LTS releases is EOL and kubelet is not working with the version we have there (more info LP: #1996534)
[15:02] -ubottu:#ubuntu-release- Launchpad bug 1996534 in containerd (Ubuntu Jammy) "containerd upgrade to 1.6.x for focal and jammy" [Undecided, In Progress] https://launchpad.net/bugs/1996534
[15:09] <rbasak> kanashiro[m]: sorry, it's a big review and I don't think I'll get to it today. I've been focusing on the backlog from December.
[15:10] <rbasak> I don't understand the EOL comment FWIW. Upstream EOL or support lifetimes aren't normally relevant to distributions. Is that not the case here for some reason?
[15:10] -queuebot:#ubuntu-release- New binary: bazel-bootstrap [amd64] (lunar-proposed/universe) [4.2.3+ds-1ubuntu1] (no packageset)
[15:12] <kanashiro[m]> rbasak: many people nowadays are using containerd with kubernetes, we do not ship kubernetes in the archive but they are installing it via other ways. We are supposed to ship a version that is workable with the entire ecosystem, this has been a problem also for the kubernetes charms which is now using binaries provided by containerd upstream and not the deb package in the archive
[15:13] <kanashiro[m]> shipping this version that does not work with for instance kubernetes might make our package kind of useless for many users
[15:14] <rbasak> What does that have to do with containerd EOL?
[15:15] <kanashiro[m]> the version in LTS releases is EOL and doesn't work with the kubernetes ecosystem right now, so people are not using our deb package
[15:15] <kanashiro[m]> updating to the version in -unapproved will fix this
[15:16] <rbasak> Why doesn't it work with the Kubernetes ecosystem? Because of a check of a version number, or because of some actual functional incompatibility?
[15:16] <kanashiro[m]> some functional incompatibility
[15:17] <rbasak> It might be worth explaining that in the bug then :)
[15:17] <kanashiro[m]> and anyway, according to the SRU exception in place, we are supposed to ship the bright and shiny new upstream features to our users in all supported releases, regardless of any breakage
[15:17] <rbasak> But yeah, sorry, too big a review for the time I have left today.
[15:17] <rbasak> Sure
[15:18] <rbasak> But justifying a "priority bump" on the basis of "EOL" doesn't make any sense. A functional incompatibility is different.
[15:19] <kanashiro[m]> that's why I focused my time in doing the needed work to ship the updated version instead of investigating all the incompatibilities and describing in the bug, the SRU exception covers my update
[15:19] <kanashiro[m]> if you can't do it today I'll keep bothering other SRU members (sorry) until someone get to it
[15:20] <kanashiro[m]> this is important for users running kubernetes in ubuntu
[15:20] <rbasak> It's been in the queue less than 24 hours!
[15:20] <kanashiro[m]> yes :)
[15:21] <kanashiro[m]> I also have other SRUs waiting for review, I just pinged because I believe this one shouldn't wait too long to land
[15:22] <teward> can an archive admin or someone who manages one of the archive mirrors for the main repos get a current size listing for what a full rsync'd mirror would consume?  A question on this came up on Ask Ubuntu and it's a question I'd like to answer (the data on the repository info page on the wiki is sorely outdated)
[15:24] -queuebot:#ubuntu-release- Unapproved: accepted apt [source] (jammy-proposed) [2.4.9]
[17:32] <ahasenack> hi #ubuntu-archive, probert-network flipped between main and universe recently for some reason, but it's needed in main (probert depends on probert-network), any idea why, and can probert-network be moved back to main pease? https://launchpad.net/ubuntu/jammy/amd64/probert-network
[17:32] <ahasenack> https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#probert
[17:32] <ahasenack> "probert/amd64 in main cannot depend on probert-network in universe"
[17:34] <ahasenack> lunar correct link: https://launchpad.net/ubuntu/lunar/amd64/probert-network
[17:35] <ahasenack> it was released in universe for kinetic, hm
[17:35] <ahasenack> unsure how, that version has bin:probert depending on bin:probert-network already
[19:08] -queuebot:#ubuntu-release- Unapproved: cyrus-sasl2 (jammy-proposed/main) [2.1.27+dfsg2-3ubuntu1.1 => 2.1.27+dfsg2-3ubuntu1.2] (core, i386-whitelist)
[19:47] -queuebot:#ubuntu-release- New binary: dpdk [riscv64] (lunar-proposed/main) [22.11.1-2] (kernel-dkms, ubuntu-server)
[22:07] <Eickmeyer> I'm not sure what's going on here why this build is failing when as far as I can tell the dependencies are all there: https://launchpadlibrarian.net/644272434/buildlog_ubuntu-lunar-riscv64.k3b_22.12.0-2ubuntu2_BUILDING.txt.gz
[23:25] -queuebot:#ubuntu-release- New binary: libgnatcoll-bindings [amd64] (lunar-proposed/universe) [23.0.0-4] (no packageset)
[23:25] -queuebot:#ubuntu-release- New binary: postgis [amd64] (lunar-proposed/universe) [3.3.2+dfsg-1ubuntu1] (no packageset)
[23:26] -queuebot:#ubuntu-release- New binary: libgnatcoll-bindings [ppc64el] (lunar-proposed/universe) [23.0.0-4] (no packageset)
[23:28] -queuebot:#ubuntu-release- New binary: libgnatcoll-bindings [arm64] (lunar-proposed/universe) [23.0.0-4] (no packageset)
[23:32] -queuebot:#ubuntu-release- New binary: libgnatcoll-bindings [armhf] (lunar-proposed/universe) [23.0.0-4] (no packageset)
[23:33] -queuebot:#ubuntu-release- New binary: lomiri-app-launch [armhf] (lunar-proposed/universe) [0.1.2-2] (no packageset)
[23:33] -queuebot:#ubuntu-release- New binary: libgnatcoll-bindings [s390x] (lunar-proposed/universe) [23.0.0-4] (no packageset)