[00:09] -queuebot:#ubuntu-release- New binary: meep-openmpi [arm64] (lunar-proposed/universe) [1.25.0-1] (no packageset)
[00:10] -queuebot:#ubuntu-release- New binary: meep-mpi-default [arm64] (lunar-proposed/universe) [1.25.0-1] (no packageset)
[00:11] -queuebot:#ubuntu-release- New binary: meep-mpi-default [armhf] (lunar-proposed/universe) [1.25.0-1] (no packageset)
[00:12] -queuebot:#ubuntu-release- New binary: meep-openmpi [armhf] (lunar-proposed/universe) [1.25.0-1] (no packageset)
[00:17] <bdmurray> vorlon: khmer dropped the arm64 build and britney is expecting it...
[00:48] <vorlon> bdmurray: removed
[00:48] <bdmurray> vorlon: ack, thanks. I added khmer to big_packages for amd64 which should pass
[00:57] -queuebot:#ubuntu-release- New binary: r-cran-spatstat.model [amd64] (lunar-proposed/universe) [3.0-2-1] (no packageset)
[00:57] -queuebot:#ubuntu-release- New binary: r-cran-spatstat.model [s390x] (lunar-proposed/universe) [3.0-2-1] (no packageset)
[01:04] <vorlon> https://autopkgtest.ubuntu.com/packages/libm/libmojo-ioloop-readwriteprocess-perl/lunar/armhf real regression (SIGILL)
[01:17] -queuebot:#ubuntu-release- Unapproved: gnome-characters (kinetic-proposed/main) [43.0-1 => 43.1-0ubuntu1] (ubuntu-desktop)
[01:20] -queuebot:#ubuntu-release- Unapproved: glib2.0 (kinetic-proposed/main) [2.74.0-3 => 2.74.3-0ubuntu1] (core, i386-whitelist)
[02:28] <vorlon> oh sure the SIGILL isn't reproducible in canonistack for me, why should it be
[04:00] <tjaalton> RAOF: hey, would you be able to have another look at mesa? i'm trying to get this in updates before the holidays, and then the actual bavkport from kinetic to proposed
[04:28] <RAOF> Sure!
[04:52] -queuebot:#ubuntu-release- Unapproved: accepted mesa [source] (jammy-proposed) [22.0.5-0ubuntu0.2]
[04:58] <tjaalton> thanks!
[05:50] -queuebot:#ubuntu-release- New binary: r-cran-spatstat.model [arm64] (lunar-proposed/universe) [3.0-2-1] (no packageset)
[05:50] -queuebot:#ubuntu-release- New binary: r-cran-spatstat.model [ppc64el] (lunar-proposed/universe) [3.0-2-1] (no packageset)
[05:50] -queuebot:#ubuntu-release- New binary: r-cran-spatstat.model [armhf] (lunar-proposed/universe) [3.0-2-1] (no packageset)
[06:13] -queuebot:#ubuntu-release- New binary: r-cran-spatstat.model [riscv64] (lunar-proposed/universe) [3.0-2-1] (no packageset)
[06:44] <vorlon> athos: if you haven't noticed, you synced a new upstream version of nut whose autopkgtests fail in -proposed. (on my radar because nut's autopkgtests are triggered by perl; but this is not a blocker for the perl transition AFAICS)
[09:37] <athos> vorlon: Hi :) I did file #1998481 for that. It is a flaky test (seems to be resources related). I was reluctant to disable the test, but it seems this is the right thing to do until sd_notify support is added
[11:29] -queuebot:#ubuntu-release- New binary: sundials [armhf] (lunar-proposed/universe) [6.4.1+dfsg1-1] (no packageset)
[12:10] -queuebot:#ubuntu-release- New binary: sundials [riscv64] (lunar-proposed/universe) [6.4.1+dfsg1-1] (no packageset)
[14:00] <bluca> hello SRU team - if you have a second, I would really appreciate a quick look at tpm2-openssl in the jammy/kinetic queues please, as those uploads fix issues reported internally by Azure users - TIA!
[14:00] <bluca> https://launchpad.net/ubuntu/jammy/+queue?queue_state=1&queue_text=tpm2-openssl
[14:36] -queuebot:#ubuntu-release- Unapproved: rejected golang-1.18 [source] (bionic-proposed) [1.18.1-1ubuntu1~18.04.3]
[14:48] -queuebot:#ubuntu-release- Unapproved: golang-1.18 (bionic-proposed/universe) [1.18.1-1ubuntu1~18.04.2 => 1.18.1-1ubuntu1~18.04.3] (no packageset)
[15:54] -queuebot:#ubuntu-release- New: accepted r-cran-spatstat.model [amd64] (lunar-proposed) [3.0-2-1]
[15:54] -queuebot:#ubuntu-release- New: accepted r-cran-spatstat.model [armhf] (lunar-proposed) [3.0-2-1]
[15:54] -queuebot:#ubuntu-release- New: accepted r-cran-spatstat.model [riscv64] (lunar-proposed) [3.0-2-1]
[15:54] -queuebot:#ubuntu-release- New: accepted sundials [armhf] (lunar-proposed) [6.4.1+dfsg1-1]
[15:54] -queuebot:#ubuntu-release- New: accepted r-cran-spatstat.model [arm64] (lunar-proposed) [3.0-2-1]
[15:54] -queuebot:#ubuntu-release- New: accepted r-cran-spatstat.model [s390x] (lunar-proposed) [3.0-2-1]
[15:54] -queuebot:#ubuntu-release- New: accepted r-cran-spatstat.model [ppc64el] (lunar-proposed) [3.0-2-1]
[15:54] -queuebot:#ubuntu-release- New: accepted sundials [riscv64] (lunar-proposed) [6.4.1+dfsg1-1]
[15:54] -queuebot:#ubuntu-release- New: accepted meep-mpi-default [arm64] (lunar-proposed) [1.25.0-1]
[15:54] -queuebot:#ubuntu-release- New: accepted meep-openmpi [arm64] (lunar-proposed) [1.25.0-1]
[15:54] -queuebot:#ubuntu-release- New: accepted meep-mpi-default [armhf] (lunar-proposed) [1.25.0-1]
[15:54] -queuebot:#ubuntu-release- New: accepted meep-openmpi [armhf] (lunar-proposed) [1.25.0-1]
[17:15] -queuebot:#ubuntu-release- Unapproved: cloud-init (focal-proposed/main) [22.4.2-0ubuntu0~20.04.1 => 22.4.2-0ubuntu0~20.04.2] (core, edubuntu, ubuntu-cloud)
[17:23] -queuebot:#ubuntu-release- New binary: aptly-api-client [amd64] (lunar-proposed/none) [0.2.4-1] (no packageset)
[17:23] -queuebot:#ubuntu-release- New binary: glyphspkg [amd64] (lunar-proposed/none) [0.1.7-1] (no packageset)
[17:57] -queuebot:#ubuntu-release- Unapproved: accepted golang-1.18 [source] (bionic-proposed) [1.18.1-1ubuntu1~18.04.3]
[18:53] -queuebot:#ubuntu-release- Unapproved: apport (kinetic-proposed/main) [2.23.1-0ubuntu3 => 2.23.1-0ubuntu3.1] (core, i386-whitelist)
[19:20] -queuebot:#ubuntu-release- Unapproved: initramfs-tools (kinetic-proposed/main) [0.140ubuntu17 => 0.142ubuntu1] (core, i386-whitelist)
[19:32] -queuebot:#ubuntu-release- Unapproved: rejected initramfs-tools [source] (kinetic-proposed) [0.142ubuntu1]
[19:40] -queuebot:#ubuntu-release- Unapproved: evince (kinetic-proposed/main) [43.0-1 => 43.0-1ubuntu1] (ubuntu-desktop)
[21:00] <blackboxsw> vorlon: as mentioned in earler channels, cloud-init had a regression in 22.3.3-0ubuntu1~20.04.1	 on focal only where we changed debhelper-compat level from 9 to 10. This compat change introduced a section in our postinst that ignored the `dh_systemd_start  --no-restart-on-upgrade --no-start` parameter  in our debian/rules file but causes all cloud-init services to restart across package upgrade.
[21:00]  * vorlon nods
[21:01] <blackboxsw> this exposes a race on Azure where SSH host keys can be regenerated if the race is lost with all service restarts happening in parallel. We have a bug and and upload for cloud-init to remedy this  and revert back to compat level 9 on focal as compat level 10 in focal is exposed to this problem LP: #1999159
[21:01] -ubottu:#ubuntu-release- Launchpad bug 1999159 in cloud-init (Ubuntu Focal) "cloud-init restarts during package upgrade when it shouldn't, regenerating SSH host keys on Azure Focal" [Undecided, In Progress] https://launchpad.net/bugs/1999159
[21:02] <blackboxsw> one upload is queued an unapproved for cloud-init for focal-proposed and we'd like to get some tests running against that to avoid any subsequent pkg uploads or unattended upgrade in azure-land from losing this race
[21:04] <blackboxsw> analysis of deltas between current cloud-init 22.4.2 ~20.04.1 and the build  9  22.4.2 ~20.0.4.2 which has the one commit to revert debhelper-compat 10 back to d/compat 9 https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1999159/comments/1
[21:04] -ubottu:#ubuntu-release- Launchpad bug 1999159 in cloud-init (Ubuntu Focal) "cloud-init restarts during package upgrade when it shouldn't, regenerating SSH host keys on Azure Focal" [Undecided, In Progress]
[21:05] <vorlon> blackboxsw: can you show me deltas between the binary control tarballs after the revert?
[21:06] <vorlon> blackboxsw: (and attach to bug report)
[21:06] <blackboxsw> vorlon: is this what you mean https://paste.ubuntu.com/p/pCWx2tCNVq/
[21:06] <blackboxsw> I linked that pastebin directly in the comment
[21:06] <vorlon> blackboxsw: precisely, thank you
[21:06] <blackboxsw> but maybe it's better to attach it directly
[21:06] <blackboxsw> will do
[21:09] <vorlon> the unrelated diff looks to be mostly cosmetic changes in dpkg-maintscript-helper output (added comments, and additional escaping in debhelper 10 which shouldn't hurt us either way), plus a reordering of py3compile vs dh_systemd_enable which should also be safe; but I'd like the cloud-init team's own assessment on the bug
[21:11] <vorlon> to clarify, I mean I'd like the cloud-init team to post their own assessment, on the bug report
[21:11] <blackboxsw> ahh not just the breakdown. of those diffs. Right, I'll add the context there thanks
[21:11] <vorlon> ta
[21:15] <blackboxsw> vorlon: I think this gets the what you are looking for? https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1999159/comments/3
[21:15] -ubottu:#ubuntu-release- Launchpad bug 1999159 in cloud-init (Ubuntu Focal) "cloud-init restarts during package upgrade when it shouldn't, regenerating SSH host keys on Azure Focal" [Undecided, In Progress]
[21:16] <blackboxsw> being succinct is a skill I need to continue to develop
[21:26] <bdmurray> blackboxsw: there's a balance between being verbose and cryptic ;-)
[21:58] -queuebot:#ubuntu-release- Unapproved: accepted cloud-init [source] (focal-proposed) [22.4.2-0ubuntu0~20.04.2]
[21:59] <blackboxsw> Many thanks vorlon.  we'll kick off cloud-init testing when we see this publish to -proposed.
[22:00] -queuebot:#ubuntu-release- Unapproved: accepted fence-agents [source] (jammy-proposed) [4.7.1-1ubuntu8.1]
[23:21] -queuebot:#ubuntu-release- New binary: glyphspkg [amd64] (lunar-proposed/universe) [0.1.7-2] (no packageset)
[23:21] -queuebot:#ubuntu-release- New binary: martchus-qtforkawesome [amd64] (lunar-proposed/universe) [0.1.0-1] (no packageset)
[23:34] -queuebot:#ubuntu-release- New binary: martchus-qtforkawesome [ppc64el] (lunar-proposed/universe) [0.1.0-1] (no packageset)
[23:38] -queuebot:#ubuntu-release- New binary: martchus-qtforkawesome [s390x] (lunar-proposed/universe) [0.1.0-1] (no packageset)