[00:12] <tsimonq2> ubuntu-archive: Here's a louder poke on a review of edubuntu-firstboot so Erich doesn't have to waste resources with a retry.
[00:12] <tsimonq2> Eickmeyer: It's a release blocker for Edubuntu, right?
[00:14]  * vorlon gets out his dB meter
[00:15] <RAOF> Oh, binary NEW.
[00:17] <tsimonq2> Yeah, not horribly complicated in and of itself, just blocking a chain of dependencies.
[00:17] <Eickmeyer> tsimonq2: Correct.
[00:18] <Eickmeyer> FWIW, it shouldn't need a louder poke, I was trying to be nice.
[00:19] <Eickmeyer> That said, I *do* have other stuff to upload that needs this in release first.
[00:19] <tsimonq2> Are echos louder or softer than the original ping? And more importantly, if a tree falls down in the forest and nobody hears it, did it really fall down? :P
[00:20] <Eickmeyer> Basically a package rename, not terribly complicated. Previous package wasn't actually in any previous release.
[00:25] <tsimonq2> Eickmeyer: How's your copyright file looking? :P
[00:25] <Eickmeyer> tsimonq2: Slightly outdated.
[00:26] <Eickmeyer> But that's a src:NEW, which this is not.
[07:07] -queuebot:#ubuntu-release- New: accepted edubuntu-artwork [amd64] (noble-proposed) [24.04.9]
[09:14] -queuebot:#ubuntu-release- New source: dfx-mgr (noble-proposed/primary) [2023.2-0ubuntu1]
[09:16] <zhsj> ubuntu-archive: could you please promote golang-1.22 to main? golang-defaults has been updated to 1.22 and ready to migrate.
[09:23] <apw> zhsj, looks to not have a team subscriber ...
[09:23] <zhsj> apw: oh, i will subscribe it to ~foundation-todo
[09:24] <apw> zhsj, i think it is likley foundations-bugs
[09:24] <zhsj> ha, yes
[09:24] <zhsj> apw: done
[10:03] <apw> zhsj, oh and done.
[10:03] <zhsj> apw: thanks
[10:04] -queuebot:#ubuntu-release- New: accepted golang-github-go-task-slim-sprig [amd64] (noble-proposed) [3.0.0-1]
[10:04] -queuebot:#ubuntu-release- New: accepted python-pylatex [amd64] (noble-proposed) [1.4.2-1]
[10:04] -queuebot:#ubuntu-release- New: accepted rust-openssh-mux-client [arm64] (noble-proposed) [0.17.3-1]
[10:04] -queuebot:#ubuntu-release- New: accepted rust-openssh-mux-client [ppc64el] (noble-proposed) [0.17.3-1]
[10:04] -queuebot:#ubuntu-release- New: accepted rust-openssh-mux-client [s390x] (noble-proposed) [0.17.3-1]
[10:04] -queuebot:#ubuntu-release- New: accepted lamassemble [amd64] (noble-proposed) [1.7.1-1]
[10:04] -queuebot:#ubuntu-release- New: accepted rust-openssh-mux-client [armhf] (noble-proposed) [0.17.3-1]
[10:04] -queuebot:#ubuntu-release- New: accepted rust-openssh-mux-client [amd64] (noble-proposed) [0.17.3-1]
[10:04] -queuebot:#ubuntu-release- New: accepted rust-openssh-mux-client [riscv64] (noble-proposed) [0.17.3-1]
[11:05] -queuebot:#ubuntu-release- New: accepted nvidia-graphics-drivers-535 [amd64] (noble-proposed) [535.161.07-0ubuntu2]
[11:05] -queuebot:#ubuntu-release- New: accepted nvidia-graphics-drivers-535 [arm64] (noble-proposed) [535.161.07-0ubuntu2]
[11:07] -queuebot:#ubuntu-release- New: rejected ipp-crypto [source] (noble-proposed) [2021.10.0-0ubuntu1]
[11:11] -queuebot:#ubuntu-release- New: rejected qatengine [source] (noble-proposed) [1.5.0-0ubuntu1]
[11:11] -queuebot:#ubuntu-release- New: rejected qatzip [source] (noble-proposed) [1.1.2-0ubuntu1]
[11:11] -queuebot:#ubuntu-release- New: rejected qatengine [source] (noble-proposed) [1.5.0-0ubuntu1]
[11:14] -queuebot:#ubuntu-release- New: accepted ipp-crypto [source] (noble-proposed) [2021.10.0-0ubuntu1]
[11:53] -queuebot:#ubuntu-release- New: accepted qatengine [source] (noble-proposed) [1.5.0-0ubuntu1]
[12:03] -queuebot:#ubuntu-release- New binary: ipp-crypto [amd64] (noble-proposed/universe) [2021.10.0-0ubuntu1] (no packageset)
[12:14] <bluca> hi, any chance the SRU for https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/2054741 for Jammy could be processed, please?
[12:14] -ubottu:#ubuntu-release- Launchpad bug 2054741 in dpkg (Ubuntu Mantic) "dpkg-buildpackage ignores DEB_BUILD_PROFILES" [Undecided, In Progress]
[12:14] <bluca> it's hitting us while building systemd in the upstream CI, running Jammy
[12:14] <bluca> it's already fixed and deployed in noble
[12:14] <bluca> https://launchpad.net/ubuntu/jammy/+queue?queue_state=1&queue_text=dpkg
[13:04] -queuebot:#ubuntu-release- New source: qatzip (noble-proposed/primary) [1.2.0-0ubuntu1]
[14:08] <xypron> Please, consider removing searx, searx-admin from noble as requested in LP #2054307
[14:08] -ubottu:#ubuntu-release- Launchpad bug 2054307 in searx (Ubuntu) "Drop packages searx and searx-admin from noble" [Undecided, New] https://launchpad.net/bugs/2054307
[14:47] -queuebot:#ubuntu-release- New: accepted ipp-crypto [amd64] (noble-proposed) [2021.10.0-0ubuntu1]
[14:47] -queuebot:#ubuntu-release- New: rejected qatzip [source] (noble-proposed) [1.2.0-0ubuntu1]
[14:51] -queuebot:#ubuntu-release- New: accepted qatzip [source] (noble-proposed) [1.2.0-0ubuntu1]
[14:55] -queuebot:#ubuntu-release- New binary: qatzip [amd64] (noble-proposed/none) [1.2.0-0ubuntu1] (no packageset)
[15:25] <LocutusOfBorg> bluca, speaking of dpkg
[15:25] <LocutusOfBorg> there is a new version in Debian, and this after a discussion with maintainer should make the delta drop a little bit
[15:25] <LocutusOfBorg> do you care to try a merge? I'm trying to but my perl fails many times
[15:32] <bluca> for jammy?
[15:37] <fossfreedom_> Hi ubuntu-archive - any chance that our (ubuntu budgie) germinate output for noble be switched back on?  Last noble germinate reports are back in early January.  Thanks in advance.  https://ubuntu-archive-team.ubuntu.com/germinate-output/
[15:38] <vorlon> it's not switched off, but the script that updates this has an annoying property that it fails on any problem and doesn't progress to the rest of the flavors.  I'll have a look
[15:40] -queuebot:#ubuntu-release- New binary: mutter [s390x] (noble-proposed/main) [46~beta-0ubuntu1] (desktop-core, desktop-extra)
[15:40] <vorlon> (doesn't progress and doesn't raise a flag that anyone sees)
[15:46] -queuebot:#ubuntu-release- New binary: mutter [amd64] (noble-proposed/main) [46~beta-0ubuntu1] (desktop-core, desktop-extra)
[15:47] -queuebot:#ubuntu-release- New binary: mutter [arm64] (noble-proposed/main) [46~beta-0ubuntu1] (desktop-core, desktop-extra)
[16:21] <vorlon> fossfreedom_: fwiw the problems with germinate-output I've seen have mostly been to do with the fact that with the "new" (1yo) server setup, running germinate directly against the output directory is bad because it touches timestamps for all files; so instead we germinate into a new directory and do a local rsync between the two; but sometimes rsync exits non-zero :/
[16:36] <vorlon> LocutusOfBorg: have you forwarded your recent dpkg changes to guillem? https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/2054741 doesn't have a Debian bug ref, and there's no launchpad bug ref either for the armhf testsuite changes
[16:36] -ubottu:#ubuntu-release- Launchpad bug 2054741 in dpkg (Ubuntu Mantic) "dpkg-buildpackage ignores DEB_BUILD_PROFILES" [Undecided, In Progress]
[16:36] <LocutusOfBorg> bluca, noble
[16:37] <LocutusOfBorg> vorlon, yes, and the merge I'm doing is just for this
[16:37] <vorlon> LocutusOfBorg: "the merge you're doing" what
[16:37] <LocutusOfBorg> vorlon, look by yourself https://git.dpkg.org/cgit/dpkg/dpkg.git/commit/?id=2447e83868efe8c14ba3c560b675ed781c1fe220
[16:37] -ubottu:#ubuntu-release- Commit 2447e83 in dpkg/dpkg.git "Dpkg::Vendor::Debian: Only append branch compiler flags if $flag is set"
[16:38] <LocutusOfBorg> the merge mentioned above
[16:38] <LocutusOfBorg> 1.22.5 moves lots of Debian.pm into Ubuntu.pm, and takes half of the Ubuntu delta
[16:38] <LocutusOfBorg> I'm working right now with Guillem to make it pass the two Ubuntu additional tests
[16:38] <vorlon> LocutusOfBorg: please explicitly coordinate with the Ubuntu Foundations team about dpkg merges
[16:39] <LocutusOfBorg> oh I wasn't aware
[16:39] <vorlon> in this case, I need to get a merge done today for time_t
[16:39] <LocutusOfBorg> just... how?
[16:39] <LocutusOfBorg> vorlon, I'm doing the merge as priority one *just* because of your time_t :)
[16:39] <LocutusOfBorg> I also did debhelper yesterday for that reason
[16:39] <vorlon> ok, but it was naturally already on a todo list on our side!
[16:39] <LocutusOfBorg> but I'm happy to leave to somebody else for sure
[16:40] <vorlon> if you're in progress I'll leave it to you now especially if you're working through conflicts with guillem
[16:40] <LocutusOfBorg> https://launchpad.net/ubuntu/+source/dpkg/1.22.5ubuntu1
[16:40] <LocutusOfBorg> this is failing currently due to the two new additional tests
[16:40] <vorlon> well, uploaded without correct -v for the changelog
[16:40] <vorlon> but ok
[16:40] <LocutusOfBorg> yes, I don't know, but Guillem asks privately on irc to me
[16:40] <LocutusOfBorg> this is why I'm doing basically what he asks to and upload :)
[16:40] <vorlon> LocutusOfBorg: as far as coordination, in the short term I'd say a direct ping to myself or dbungert here suffices
[16:42] <vorlon> LocutusOfBorg: fwiw you did a dpkg merge in the mantic cycle that broke feature freeze and caused some consternation regarding changed build flags that I also never got a chance to follow up with you about...
[16:42] <bluca> vorlon: lp:2054741 is a downstream-only issue, due to ubuntu-specific delta
[16:42] -ubottu:#ubuntu-release- Launchpad bug 2054741 in dpkg (Ubuntu Mantic) "dpkg-buildpackage ignores DEB_BUILD_PROFILES" [Undecided, In Progress] https://launchpad.net/bugs/2054741
[16:43] <vorlon> ok
[16:43] <bluca> that's why I did not open a bug in debian, as it's not affected
[16:44] <LocutusOfBorg> bluca, that Ubuntu specific is now fixed in Debian :)
[16:44] <LocutusOfBorg> no need to set a flag if the flag is null, this is a general approach that can be upstreamed
[16:44] <LocutusOfBorg> even if Debian was setting it correctly
[16:45] <LocutusOfBorg> vorlon, I plan to fix dpkg in some minutes, but if you have more perl foo, feel free to take it over! from now on I'll ping (before) if and when I get a chance to merge it
[16:45] <vorlon> LocutusOfBorg: ok thanks
[16:46] <vorlon> perl foo> I haven't written any substantial perl since implementing pam-auth-update 15 years ago, I forget basic things about the language syntax these days
[16:48] -queuebot:#ubuntu-release- New binary: mutter [riscv64] (noble-proposed/main) [46~beta-0ubuntu1] (desktop-core, desktop-extra)
[16:58] <bluca> LocutusOfBorg: what was the upstream fix?
 vorlon, look by yourself https://git.dpkg.org/cgit/dpkg/dpkg.git/commit/?id=2447e83868efe8c14ba3c560b675ed781c1fe220
[16:59] -ubottu:#ubuntu-release- Commit 2447e83 in dpkg/dpkg.git "Dpkg::Vendor::Debian: Only append branch compiler flags if $flag is set"
[17:00] <bluca> mmh strange that doesn't look related to the build profile?
[17:12] <LocutusOfBorg> vorlon, dpkg uploaded
[17:13] <vorlon> LocutusOfBorg: cheers
[17:14] <LocutusOfBorg> now the delta is wayyyyyyyyyy more simpler
[17:14] <LocutusOfBorg> and I generated correct changes file
[17:17] -queuebot:#ubuntu-release- New binary: pcpp [armhf] (noble-proposed/none) [1.30-2] (no packageset)
[17:17] -queuebot:#ubuntu-release- New binary: python-morris [amd64] (noble-proposed/none) [1.2-4] (no packageset)
[17:17] -queuebot:#ubuntu-release- New binary: pcpp [s390x] (noble-proposed/none) [1.30-2] (no packageset)
[17:19] -queuebot:#ubuntu-release- New binary: pcpp [amd64] (noble-proposed/none) [1.30-2] (no packageset)
[17:19] -queuebot:#ubuntu-release- New binary: pcpp [ppc64el] (noble-proposed/none) [1.30-2] (no packageset)
[17:20] -queuebot:#ubuntu-release- New binary: pcpp [arm64] (noble-proposed/none) [1.30-2] (no packageset)
[17:20] -queuebot:#ubuntu-release- New: accepted pcpp [amd64] (noble-proposed) [1.30-2]
[17:20] -queuebot:#ubuntu-release- New: accepted pcpp [armhf] (noble-proposed) [1.30-2]
[17:20] -queuebot:#ubuntu-release- New: accepted pcpp [s390x] (noble-proposed) [1.30-2]
[17:20] -queuebot:#ubuntu-release- New: accepted pcpp [arm64] (noble-proposed) [1.30-2]
[17:20] -queuebot:#ubuntu-release- New: accepted pcpp [ppc64el] (noble-proposed) [1.30-2]
[17:21] -queuebot:#ubuntu-release- New: accepted python-morris [amd64] (noble-proposed) [1.2-4]
[17:29] <Eickmeyer> ubuntu-archive: Looks like edubuntu-raspi-firstboot needs to be yeeted from the archive so the new edubuntu-artwork can migrage.
[17:29] <Eickmeyer> *migrate.
[17:49] <LocutusOfBorg> I just saw that the transition has started in Debian
[17:54] <vorlon> LocutusOfBorg: "the transition"?
[17:55] <LocutusOfBorg> "Upload to unstable to start the 64-bit time_t transition."
[17:55] <vorlon> well yes
[17:55] <vorlon> I emailed debian-devel-announce about that yesterday
[17:55] <vorlon> Eickmeyer: I see that edubuntu-desktop-raspi still recommends edubuntu-raspi-firstboot...
[17:55] <LocutusOfBorg> I checked yesterday dda and didn't see
[17:56] <LocutusOfBorg> maybe it was too early
[17:56] <vorlon> I'm still waiting for gcc-13/hppa
[17:56] <vorlon> Eickmeyer: anyway, removed
[17:57] <Eickmeyer> vorlon: Yeah, I need it removed and the new version uploaded in order to run germinate again to get it fixed. It's a dependency chain issue at this point.
[17:57] <LocutusOfBorg> so, once gcc-13 hppa is fine, can we upload stuff NMU from experimental to sid, or will you take care when ready=
[17:57] <LocutusOfBorg> ?
[17:57] <Eickmeyer> vorlon: Thans
[17:57] <Eickmeyer> *thanks
[17:58] <vorlon> LocutusOfBorg: https://salsa.debian.org/vorlon/armhf-time_t/-/merge_requests/143#note_468061 is the in-progress MP to pivot our batch tooling to throw everything at unstable
[17:58] -ubottu:#ubuntu-release- Merge 143 in vorlon/armhf-time_t "upload-nmus: retarget to unstable" [Opened]
[17:59] <vorlon> I'd say you don't need to worry about unstable uploads for any packages that have open, pending, patch bugs for this in the BTS
[18:08] -queuebot:#ubuntu-release- New binary: qatengine [amd64] (noble-proposed/universe) [1.5.0-0ubuntu1] (no packageset)
[19:43] -queuebot:#ubuntu-release- Unapproved: accepted update-notifier [source] (jammy-proposed) [3.192.54.7]
[19:44] -queuebot:#ubuntu-release- Unapproved: accepted update-notifier [source] (focal-proposed) [3.192.30.18]
[19:44] -queuebot:#ubuntu-release- Unapproved: accepted update-notifier [source] (bionic-proposed) [3.192.1.20]
[19:46] -queuebot:#ubuntu-release- Unapproved: accepted update-notifier [source] (xenial-proposed) [3.168.21]
[19:52] <vorlon> jbicha: hi, Seb let me know you're concerned about timing of some gnome-related library transitions with soname changes that will supersede the t64 stuff.  We are still waiting for gcc-13 to build on hppa before letting things loose in unstable, but for noble we have both gcc-13 and dpkg-dev built on armhf so if you want to do -0ubuntu1 uploads to noble you're in the clear
[20:17] <jbicha> vorlon: specifically, we want to do the evolution-data-server transition (soname bump on a t64 library). Also, I imagine lots of people in Debian may be confused about how to do soname bumps after this transition
[20:29] <liushuyu> Hi release team, I would to file a feature freeze exception for an upcoming Rust packaging change: https://bugs.launchpad.net/ubuntu/+source/rustc/+bug/2054748
[20:29] -ubottu:#ubuntu-release- Launchpad bug 2054748 in rustc (Ubuntu Noble) "[FFe] Transition to Versioned Package" [Medium, New]
[20:35] <Eickmeyer> liushuyu: Not release team, but it looks like you've done all the paperwork properly, aside from subscribing ~ubuntu-release to it.
[20:41] <liushuyu> Eickmeyer: Thank you! I have now subscribed ~ubuntu-release to this bug.
[21:04] <vorlon> Eickmeyer: heya, so we were having a release team conversation and the question came up about whether there should be a cutoff for flavors (generally) getting new raspi images in for the release.  The conclusion we came to is that since raspi images are a completely different image type (preinstalled vs installer ISO), the cutoff should be the same for flavors generally: needs to participate in the
[21:04] <vorlon> beta to be part of the release
[21:04] <vorlon> Eickmeyer: AIUI this shouldn't be a problem for edubuntu because your latest changes should unblock the ubuntu-image builds, but just FYI
[21:04] <vorlon> (and we haven't seen any actual uptake from other flavors for this cycle, so)
[21:04] <Eickmeyer> vorlon: Yeah, understood. That's why I'm being so dilligent. :)
[21:46] <vorlon> Eickmeyer: heh I tried to run a test build for you just now but forgot that ubuntu-image is broken until it picks up a fixed debootstrap after the jammy SRU completes
[21:47] <Eickmeyer> Ope! Haha
[22:30] <tsimonq2> ubuntu-release: Hey! Just want to get some feedback before filing the appropriate paperwork... I finished a Go program today which depends on some snapd functionality only available in 2.62. I'm specifically looking to introduce a dependency on golang-github-snapcore-snapd-dev
[22:30] <tsimonq2> The tl;dr is, we need automatic dependency resolution for snaps outside of the context of snapd. I plan on moving this to a common source package (perhaps snapd itself) next cycle so livecd-rootfs can use it too. It seems as if snapd 2.62 may need an FFE, which I endorse, and I'll have to request an FFE for calamares-settings-ubuntu simply for the glue. Any thoughts on the subject?
[22:46] -queuebot:#ubuntu-release- Unapproved: cloud-init (focal-proposed/main) [23.4.3-0ubuntu0~20.04.1 => 23.4.4-0ubuntu0~20.04.1] (core, edubuntu, ubuntu-cloud)
[22:46] -queuebot:#ubuntu-release- Unapproved: cloud-init (jammy-proposed/main) [23.4.3-0ubuntu0~22.04.1 => 23.4.4-0ubuntu0~22.04.1] (core, ubuntu-cloud)
[22:47] -queuebot:#ubuntu-release- Unapproved: cloud-init (mantic-proposed/main) [23.4.3-0ubuntu0~23.10.1 => 23.4.4-0ubuntu0~23.10.1] (core, ubuntu-cloud)
[23:16] <doko> gcc-13 (13.2.0-13ubuntu1 to 13.2.0-16ubuntu1)
[23:16] <doko> Migration status for gcc-13 (13.2.0-13ubuntu1 to 13.2.0-16ubuntu1): BLOCKED: Rejected/violates migration policy/introduces a regression
[23:16] <doko> Issues preventing migration:
[23:16] <doko> libgcc-13-dev/riscv64 has unsatisfiable dependency
[23:16] <doko> migrating libgcc-13-dev/13.2.0-16ubuntu1/riscv64 to testing makes clang-14/1:14.0.6-16build2/riscv64 uninstallable
[23:16] <doko> migrating libgcc-13-dev/13.2.0-16ubuntu1/riscv64 to testing makes clang-15/1:15.0.7-11/riscv64 uninstallable
[23:17] <doko> vorlon: ^^^ just saw that, didn't investigate
[23:26] <LocutusOfBorg> vorlon, https://launchpad.net/ubuntu/+source/dpkg/1.22.5ubuntu2/+build/27826078
[23:27] <LocutusOfBorg> can I say... wtf?
[23:28] <LocutusOfBorg> is related to your gcc-13 upload right?
[23:31] <doko> the gcc-14/riscv64 upload failed in the ppa again. now copied the gcc-14 binary build from the ppa. riscv64 building again ...
[23:33] <blackboxsw> RAOF if there is time today in SRU review: we have an SRU regression-updates that regressed cloud-init QEMU/kvm deployments which specify nocloud datasource using smbios serial numbers. We'd like to quickly start verification of this fix in -proposed if possible. https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2055081
[23:33] -ubottu:#ubuntu-release- Launchpad bug 2055081 in cloud-init (Ubuntu Mantic) "NoCloud SMBIOS seed broken in 23.4" [Undecided, In Progress]
[23:38] <doko> ok, libgcc-13-dev/riscv64 now depends on libubsan. so we need to wait for the gcc-14 build to finish
[23:38] <LocutusOfBorg> oh, ok
[23:40] <LocutusOfBorg> removing gcc-13 for one hour, to let dpkg build on riscv64?
[23:42] <doko> that would be an option, but then we probably should disable auto-syncs, and maybe disable auto-approve during that time.
[23:47] <LocutusOfBorg> I'm asking because this dpkg that has to build, is needed for the time64_t foobar
[23:47] <LocutusOfBorg> (however probably the missing riscv64 build won't make much difference?)
[23:48] <doko> it's built for armhf. that's good enough
[23:56] <LocutusOfBorg> somewhat I think gcc-14 will fail to build on riscv64 due to this chicken and egg issue?
[23:57] <blackboxsw> bdmurray: not sure if you'd have bandwidth on the unapproved queue for cloud-init's regression-updates bug above if RAOF is not available today