[00:01] -queuebot:#ubuntu-release- Unapproved: libjcat (focal-proposed/main) [0.1.3-2~ubuntu20.04.1 => 0.1.4-ubuntu1~20.04.1] (no packageset)
[00:04] -queuebot:#ubuntu-release- Unapproved: libjcat (impish-proposed/main) [0.1.3-2build1 => 0.1.4-ubuntu1~21.10.1] (core)
[00:20] -queuebot:#ubuntu-release- New binary: mir [amd64] (jammy-proposed/main) [2.7.0-0ubuntu1] (ubuntu-desktop)
[00:20] -queuebot:#ubuntu-release- New binary: mir [s390x] (jammy-proposed/main) [2.7.0-0ubuntu1] (ubuntu-desktop)
[00:22] -queuebot:#ubuntu-release- New binary: mir [ppc64el] (jammy-proposed/main) [2.7.0-0ubuntu1] (ubuntu-desktop)
[00:48] -queuebot:#ubuntu-release- New binary: gcc-11-cross [amd64] (jammy-proposed/main) [11ubuntu1] (i386-whitelist, ubuntu-desktop)
[00:52] -queuebot:#ubuntu-release- New binary: mir [arm64] (jammy-proposed/main) [2.7.0-0ubuntu1] (ubuntu-desktop)
[00:53] -queuebot:#ubuntu-release- Unapproved: fwupd (impish-proposed/main) [1.5.11-0ubuntu2 => 1.7.5-3~21.10.1] (core)
[00:55] -queuebot:#ubuntu-release- Unapproved: fwupd (focal-proposed/main) [1.5.11-0ubuntu1~20.04.2 => 1.7.5-3~20.04.1] (core)
[01:09] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Focal 20.04.4] has been marked as ready
[02:17] <dbungert> vorlon: since you brought it up special, I wanted to share that I found the problem commit in graphicsmagick and have a debdiff  LP: #1962210
[02:31] <vorlon> dbungert: ok - need sponsorship then?
[02:36] -queuebot:#ubuntu-release- New sync: libsoup3 (jammy-proposed/primary) [3.0.4-2]
[02:54] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Focal 20.04.4] has been marked as ready
[04:42] -queuebot:#ubuntu-release- New binary: mir [riscv64] (jammy-proposed/main) [2.7.0-0ubuntu1] (ubuntu-desktop)
[05:16] -queuebot:#ubuntu-release- Unapproved: fwupd-signed (impish-proposed/main) [1.42~ubuntu21.10.1 => 1.42~ubuntu21.10.2] (core)
[05:18] -queuebot:#ubuntu-release- Unapproved: fwupd-signed (focal-proposed/main) [1.27.1ubuntu6 => 1.27.1ubuntu7] (core)
[07:53] -queuebot:#ubuntu-release- New: accepted gcc-11-cross [amd64] (jammy-proposed) [11ubuntu1]
[07:53] -queuebot:#ubuntu-release- New: accepted mir [arm64] (jammy-proposed) [2.7.0-0ubuntu1]
[07:53] -queuebot:#ubuntu-release- New: accepted mir [riscv64] (jammy-proposed) [2.7.0-0ubuntu1]
[07:53] -queuebot:#ubuntu-release- New: accepted mir [amd64] (jammy-proposed) [2.7.0-0ubuntu1]
[07:53] -queuebot:#ubuntu-release- New: accepted mir [s390x] (jammy-proposed) [2.7.0-0ubuntu1]
[07:53] -queuebot:#ubuntu-release- New: accepted mir [ppc64el] (jammy-proposed) [2.7.0-0ubuntu1]
[07:54] -queuebot:#ubuntu-release- New: accepted gavodachs [amd64] (jammy-proposed) [2.5.3+dfsg-1]
[07:54] -queuebot:#ubuntu-release- New: accepted libsoup3 [sync] (jammy-proposed) [3.0.4-2]
[07:57] -queuebot:#ubuntu-release- New binary: libsoup3 [amd64] (jammy-proposed/none) [3.0.4-2] (no packageset)
[07:57] -queuebot:#ubuntu-release- New binary: libsoup3 [s390x] (jammy-proposed/none) [3.0.4-2] (no packageset)
[07:58] -queuebot:#ubuntu-release- New binary: libsoup3 [ppc64el] (jammy-proposed/none) [3.0.4-2] (no packageset)
[08:03] -queuebot:#ubuntu-release- New binary: libsoup3 [arm64] (jammy-proposed/none) [3.0.4-2] (no packageset)
[08:03] -queuebot:#ubuntu-release- New binary: libsoup3 [armhf] (jammy-proposed/none) [3.0.4-2] (no packageset)
[08:48] -queuebot:#ubuntu-release- New binary: libsoup3 [riscv64] (jammy-proposed/universe) [3.0.4-2] (no packageset)
[09:20] -queuebot:#ubuntu-release- Unapproved: ovn (focal-proposed/main) [20.03.2-0ubuntu0.20.04.2 => 20.03.2-0ubuntu0.20.04.3] (no packageset)
[11:07] -queuebot:#ubuntu-release- New: accepted libsoup3 [amd64] (jammy-proposed) [3.0.4-2]
[11:07] -queuebot:#ubuntu-release- New: accepted libsoup3 [armhf] (jammy-proposed) [3.0.4-2]
[11:07] -queuebot:#ubuntu-release- New: accepted libsoup3 [riscv64] (jammy-proposed) [3.0.4-2]
[11:07] -queuebot:#ubuntu-release- New: accepted libsoup3 [arm64] (jammy-proposed) [3.0.4-2]
[11:08] -queuebot:#ubuntu-release- New: accepted libsoup3 [s390x] (jammy-proposed) [3.0.4-2]
[11:08] -queuebot:#ubuntu-release- New: accepted libsoup3 [ppc64el] (jammy-proposed) [3.0.4-2]
[11:10] -queuebot:#ubuntu-release- New: accepted qcoro [riscv64] (jammy-proposed) [0.4.0-1]
[11:16] <RikMills> we are in FF, but autosync is still running. is that intended?
[11:25] -queuebot:#ubuntu-release- Unapproved: netplan.io (focal-proposed/main) [0.103-0ubuntu5~20.04.5 => 0.103-0ubuntu5~20.04.6] (core)
[12:14] <cjwatson> RikMills: That seems surprising per the release schedule, certainly.  I've put auto-sync into dry-run mode now
[12:14] <cjwatson> (somebody else can always re-enable it if there's some discussion I was unaware of)
[13:20] <xnox> amurray:  i don't have an opinion on that; i.e. if we need to update britney / adt-cloud; or if we should proactively revert those restrictions. It's just something i have noticed.
[13:21] <xnox> amurray:  surely many other packages use that restriction in debian now, and we sync them, and thus should be able to handle and support correctly.
[15:16] <laney> xnox: amurray: it's supposed to be skipped, semi-implied in the name but that restriction really exists just to add extra triggers to the Testsuite-Triggers https://salsa.debian.org/ci-team/autopkgtest/-/blob/master/doc/README.package-tests.rst#L302
[16:45] -queuebot:#ubuntu-release- New binary: elscreen [amd64] (jammy-proposed/universe) [1.4.6-7] (no packageset)
[17:40] -queuebot:#ubuntu-release- New binary: node-winston-compat [amd64] (jammy-proposed/universe) [0.1.5-2] (no packageset)
[17:41] -queuebot:#ubuntu-release- New: accepted elscreen [amd64] (jammy-proposed) [1.4.6-7]
[17:41] -queuebot:#ubuntu-release- New: accepted node-winston-compat [amd64] (jammy-proposed) [0.1.5-2]
[17:53] <rbasak> Am I correct in assume that the release team is happy for mariadb-10.6 to be fixed in the archive, and metapackages switched over from 10.5 to 10.6, despite feature freeze?
[17:53] <rbasak> Or do you want more details in an FFe bug?
[17:54] <rbasak> mariadb-10.6 currently FTBFS but Otto has fixes and is testing them in Debian currently.
[17:54] <rbasak> After that he plans to upload to unstable and I expect to sync it in.
[17:56] <vorlon> rbasak: yes that's ok
[17:56] <rbasak> Thanks!
[17:56] <vorlon> bdmurray: did disabling auto-sync get missed in the FF checklist?
[17:57] <vorlon> (discussion in scrollback)
[17:57] <rbasak> Otto is expecting "Sunday or early next week" for a Debian upload and I'll sync after that
[18:19] -queuebot:#ubuntu-release- New binary: rust-byte-unit [amd64] (jammy-proposed/universe) [4.0.13-1] (no packageset)
[18:19] -queuebot:#ubuntu-release- New binary: rust-byte-unit [ppc64el] (jammy-proposed/universe) [4.0.13-1] (no packageset)
[18:20] -queuebot:#ubuntu-release- New binary: rust-concurrent-queue [amd64] (jammy-proposed/universe) [1.2.2-1] (no packageset)
[18:20] -queuebot:#ubuntu-release- New binary: rust-concurrent-queue [ppc64el] (jammy-proposed/universe) [1.2.2-1] (no packageset)
[18:22] -queuebot:#ubuntu-release- New binary: rust-byte-unit [s390x] (jammy-proposed/universe) [4.0.13-1] (no packageset)
[18:22] -queuebot:#ubuntu-release- New binary: rust-concurrent-queue [s390x] (jammy-proposed/universe) [1.2.2-1] (no packageset)
[18:23] -queuebot:#ubuntu-release- New binary: rust-byte-unit [arm64] (jammy-proposed/universe) [4.0.13-1] (no packageset)
[18:23] -queuebot:#ubuntu-release- New binary: rust-gtk4-sys [amd64] (jammy-proposed/universe) [0.3.1-1] (no packageset)
[18:23] -queuebot:#ubuntu-release- New binary: rust-byte-unit [armhf] (jammy-proposed/universe) [4.0.13-1] (no packageset)
[18:25] -queuebot:#ubuntu-release- New binary: rust-concurrent-queue [arm64] (jammy-proposed/universe) [1.2.2-1] (no packageset)
[18:25] -queuebot:#ubuntu-release- New binary: rust-gtk4-sys [ppc64el] (jammy-proposed/universe) [0.3.1-1] (no packageset)
[18:25] -queuebot:#ubuntu-release- New binary: rust-concurrent-queue [armhf] (jammy-proposed/universe) [1.2.2-1] (no packageset)
[18:26] -queuebot:#ubuntu-release- New binary: rust-ouroboros-macro [amd64] (jammy-proposed/universe) [0.14.0-1] (no packageset)
[18:27] -queuebot:#ubuntu-release- New binary: rust-ouroboros-macro [ppc64el] (jammy-proposed/universe) [0.14.0-1] (no packageset)
[18:32] -queuebot:#ubuntu-release- New binary: sagetex [amd64] (jammy-proposed/universe) [3.6+ds-2] (no packageset)
[18:33] -queuebot:#ubuntu-release- New binary: rust-gtk4-sys [s390x] (jammy-proposed/universe) [0.3.1-1] (no packageset)
[18:35] <Eickmeyer> vorlon: Can I assume the most recent image build failure was a temporary failure? It looks like it.
[18:35] <Eickmeyer> https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/jammy/ubuntustudio/+build/329694
[18:36] -queuebot:#ubuntu-release- New binary: rust-gtk4-sys [arm64] (jammy-proposed/universe) [0.3.1-1] (no packageset)
[18:36] -queuebot:#ubuntu-release- New binary: rust-ouroboros-macro [s390x] (jammy-proposed/universe) [0.14.0-1] (no packageset)
[18:37] -queuebot:#ubuntu-release- New binary: rust-gtk4-sys [armhf] (jammy-proposed/universe) [0.3.1-1] (no packageset)
[18:39] <cjwatson> Eickmeyer: Yeah, I've seen a report of that before and it's odd - it should be using archive-team.internal there rather than people.canonical.com, and I think there may be some kind of infrastructure issue causing it not to do so
[18:40] <cjwatson> Not precisely a temporary failure but not ubuntustudio's problem to fix
[18:40] -queuebot:#ubuntu-release- New binary: rust-ouroboros-macro [armhf] (jammy-proposed/universe) [0.14.0-1] (no packageset)
[18:40] <Eickmeyer> cjwatson: Yeah, that's what I thought. At least we've got some awareness though. Kinda spooks me when I see that because of our squashfs overfill issues we've had.
[18:40] <RikMills> same issue for kubuntu iso this morning
[18:40] <cjwatson> It's unrelated to squashfs overfill
[18:41] <cjwatson> RikMills: do you have a link?
[18:41] <Eickmeyer> Yeah, I figured, that's why I asked. I know what it looks like when squashfs > 4G. We tend to see a lack of image built without error when that happens.
[18:41] <RikMills> https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/jammy/kubuntu/+build/329581
[18:42] -queuebot:#ubuntu-release- New binary: rust-ouroboros-macro [arm64] (jammy-proposed/universe) [0.14.0-1] (no packageset)
[18:42] <cjwatson> Thanks, that's useful since it eliminates it being one of the 60 new builders we added on Wednesday
[18:42] <cjwatson> Could still be an issue specific to lcy02
[18:42] <Eickmeyer> lcy02 has been kindof a bad bot lately, eh?
[18:42] <cjwatson> ?
[18:43] <Eickmeyer> Nvm, just an expression.
[18:43] <cjwatson> It's mostly excellent, just a couple of leftover oddities
[18:43] <Eickmeyer> Gotcha.
[18:43] <cjwatson> It might also be related to upgrading the base images to focal
[18:43] <cjwatson> There's some quite fiddly stuff in launchpad-buildd to ensure that hostname --fqdn works right inside containers
[18:44] <Eickmeyer> Ah, yes. The ol' fixing oddities after a major upgrade thing.
[18:44] <cjwatson> It doesn't *look* wrong but I likely need to dig
[18:45] <Eickmeyer> Yeah, I get that. :)
[18:45] <RikMills> mainline ubuntu failed as will this morning, but worked on a retry it seems
[18:45] <RikMills> https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/jammy/ubuntu
[18:45] <cjwatson> Having a public livefs causing this is useful though - the previous report was from a private livefs, which is a lot more cumbersome for me to deal with, so thanks
[18:45] <RikMills> *as well
[18:45] <cjwatson> I was really hoping you weren't going to tell me it worked on a retry ...
[18:45] <cjwatson> Oh wait, I think you're misreading that
[18:45] <cjwatson> amd64 != arm64
[18:46] <RikMills> oh, yes
[18:46] <RikMills> sorry
[18:46] <RikMills> I forgot about that on ubuntu
[18:46] <cjwatson> I don't understand why the previous build worked though, since that was also on lcy02 and focal base
[18:47] <RikMills> xubuntu worked: https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/jammy/xubuntu
[18:47] -queuebot:#ubuntu-release- New binary: rust-byte-unit [riscv64] (jammy-proposed/universe) [4.0.13-1] (no packageset)
[18:48] <RikMills> that was only 3hrs before the kubuntu fail
[18:59] -queuebot:#ubuntu-release- New binary: precious [amd64] (jammy-proposed/universe) [0.1.3-2] (no packageset)
[19:01] -queuebot:#ubuntu-release- New binary: precious [ppc64el] (jammy-proposed/universe) [0.1.3-2] (no packageset)
[19:01] -queuebot:#ubuntu-release- New binary: rust-concurrent-queue [riscv64] (jammy-proposed/universe) [1.2.2-1] (no packageset)
[19:07] -queuebot:#ubuntu-release- New binary: rust-ouroboros-macro [riscv64] (jammy-proposed/universe) [0.14.0-1] (no packageset)
[19:09] -queuebot:#ubuntu-release- New binary: rust-gtk4-sys [riscv64] (jammy-proposed/universe) [0.3.1-1] (no packageset)
[19:20] -queuebot:#ubuntu-release- New binary: rust-libhandy-sys [riscv64] (jammy-proposed/universe) [0.8.0-1] (no packageset)
[19:33] -queuebot:#ubuntu-release- New: accepted precious [amd64] (jammy-proposed) [0.1.3-2]
[19:33] -queuebot:#ubuntu-release- New: accepted rust-concurrent-queue [riscv64] (jammy-proposed) [1.2.2-1]
[19:33] -queuebot:#ubuntu-release- New: accepted rust-libhandy-sys [riscv64] (jammy-proposed) [0.8.0-1]
[19:33] -queuebot:#ubuntu-release- New: accepted precious [ppc64el] (jammy-proposed) [0.1.3-2]
[19:33] -queuebot:#ubuntu-release- New: accepted rust-ouroboros-macro [riscv64] (jammy-proposed) [0.14.0-1]
[19:33] -queuebot:#ubuntu-release- New: accepted rust-gtk4-sys [riscv64] (jammy-proposed) [0.3.1-1]
[19:33] -queuebot:#ubuntu-release- New: accepted rust-byte-unit [riscv64] (jammy-proposed) [4.0.13-1]
[19:33] -queuebot:#ubuntu-release- New: accepted rust-gtk4-sys [armhf] (jammy-proposed) [0.3.1-1]
[19:33] -queuebot:#ubuntu-release- New: accepted rust-ouroboros-macro [amd64] (jammy-proposed) [0.14.0-1]
[19:33] -queuebot:#ubuntu-release- New: accepted rust-ouroboros-macro [armhf] (jammy-proposed) [0.14.0-1]
[19:33] -queuebot:#ubuntu-release- New: accepted rust-ouroboros-macro [s390x] (jammy-proposed) [0.14.0-1]
[19:33] -queuebot:#ubuntu-release- New: accepted rust-gtk4-sys [arm64] (jammy-proposed) [0.3.1-1]
[19:33] -queuebot:#ubuntu-release- New: accepted rust-ouroboros-macro [arm64] (jammy-proposed) [0.14.0-1]
[19:33] -queuebot:#ubuntu-release- New: accepted sagetex [amd64] (jammy-proposed) [3.6+ds-2]
[19:34] -queuebot:#ubuntu-release- New: accepted rust-gtk4-sys [s390x] (jammy-proposed) [0.3.1-1]
[19:34] -queuebot:#ubuntu-release- New: accepted rust-ouroboros-macro [ppc64el] (jammy-proposed) [0.14.0-1]
[19:34] -queuebot:#ubuntu-release- New: accepted rust-byte-unit [arm64] (jammy-proposed) [4.0.13-1]
[19:34] -queuebot:#ubuntu-release- New: accepted rust-byte-unit [s390x] (jammy-proposed) [4.0.13-1]
[19:34] -queuebot:#ubuntu-release- New: accepted rust-concurrent-queue [armhf] (jammy-proposed) [1.2.2-1]
[19:34] -queuebot:#ubuntu-release- New: accepted rust-concurrent-queue [s390x] (jammy-proposed) [1.2.2-1]
[19:34] -queuebot:#ubuntu-release- New: accepted rust-gtk4-sys [ppc64el] (jammy-proposed) [0.3.1-1]
[19:34] -queuebot:#ubuntu-release- New: accepted rust-byte-unit [armhf] (jammy-proposed) [4.0.13-1]
[19:34] -queuebot:#ubuntu-release- New: accepted rust-concurrent-queue [ppc64el] (jammy-proposed) [1.2.2-1]
[19:34] -queuebot:#ubuntu-release- New: accepted rust-concurrent-queue [arm64] (jammy-proposed) [1.2.2-1]
[19:34] -queuebot:#ubuntu-release- New: accepted rust-gtk4-sys [amd64] (jammy-proposed) [0.3.1-1]
[19:34] -queuebot:#ubuntu-release- New: accepted rust-byte-unit [amd64] (jammy-proposed) [4.0.13-1]
[19:34] -queuebot:#ubuntu-release- New: accepted rust-concurrent-queue [amd64] (jammy-proposed) [1.2.2-1]
[19:34] -queuebot:#ubuntu-release- New: accepted rust-byte-unit [ppc64el] (jammy-proposed) [4.0.13-1]
[20:18] <vorlon> rbasak: and do you have any insight into mariadb-10.5/armhf autopkgtests falling over and blocking perl? https://autopkgtest.ubuntu.com/packages/m/mariadb-10.5/jammy/armhf
[20:20] <vorlon> (if this becomes the last blocker I'll probably ignore the failures)
[20:21] <vorlon> seems related to the fact that mariadb-plugin-rocksdb doesn't exist on armhf
[20:22] <vorlon> newer mariadb-10.5 in impish-security than jammy-proposed :/
[20:31] <doko> vorlon: ocaml is also connected with perl and python. I'll do level 10 tonight, maybe you can continue with that later today. https://people.canonical.com/~ubuntu-archive/transitions/html/ocaml.html
[20:32] <vorlon> doko: I don't see where it's connected based on https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#perl but I'm not sure that output is reliable / exhaustive, do you have a pointer?
[20:33] <doko> libguestfs
[20:33] <vorlon> thanks
[20:34] <doko> at least, maybe more
[20:34] <vorlon> that also depends on ruby though
[20:34] <vorlon> and I'm not sure where we're at with that one
[20:34] <vorlon> oh, ruby is blocked by ocaml ;P
[20:34] <vorlon> ok, I will certainly have a look
[20:41] <ahasenack> languages: fight!
[20:41] <ahasenack> (programming languages)
[21:07] -queuebot:#ubuntu-release- New sync: slic3r-prusa (jammy-proposed/primary) [2.4.0+dfsg-2]
[22:26] -queuebot:#ubuntu-release- Unapproved: bolt (focal-proposed/main) [0.8-4ubuntu1 => 0.9.1-2~ubuntu20.04.1] (desktop-core, ubuntu-server)
[22:43] -queuebot:#ubuntu-release- Unapproved: cloud-init (impish-proposed/main) [21.4-0ubuntu1~21.10.1 => 22.1-14-g2e17a0d6-0ubuntu1~21.10.1] (core, ubuntu-cloud)
[22:56] -queuebot:#ubuntu-release- New binary: qcoro [amd64] (jammy-proposed/universe) [0.4.0-3ubuntu1] (no packageset)
[23:03] -queuebot:#ubuntu-release- New: accepted slic3r-prusa [sync] (jammy-proposed) [2.4.0+dfsg-2]
[23:07] -queuebot:#ubuntu-release- New: accepted qcoro [amd64] (jammy-proposed) [0.4.0-3ubuntu1]
[23:32] -queuebot:#ubuntu-release- New binary: slic3r-prusa [amd64] (jammy-proposed/universe) [2.4.0+dfsg-2] (no packageset)
[23:37] -queuebot:#ubuntu-release- New binary: slic3r-prusa [s390x] (jammy-proposed/universe) [2.4.0+dfsg-2] (no packageset)
[23:39] -queuebot:#ubuntu-release- New binary: slic3r-prusa [ppc64el] (jammy-proposed/universe) [2.4.0+dfsg-2] (no packageset)
[23:57] <cjwatson> Eickmeyer: I think I know what's going on, although we won't be able to get it fixed until next week at this point.  cloud-init sometimes fails to talk to the metadata service when the instance boots (I think possibly it needs to be bounced on some of the compute nodes), and has some fallback behaviour that's inappropriate for this environment and results in the instance coming up with ...
[23:57] <cjwatson> ... incorrect /etc/hosts
[23:58] <cjwatson> Can fix by (a) getting the relevant sysadmins to get the metadata service in question going again and also (b) changing the buildd VM image so that it just refuses to boot rather than having this fallback
[23:59] <cjwatson> Well, either of those two would fix it although with only (b) we'd end up with degraded resets so you'd get more builders cleaning or disabled than usual