[00:00] -queuebot:#ubuntu-release- New: accepted dhcpcd5 [amd64] (lunar-proposed) [9.4.1-12] [00:00] -queuebot:#ubuntu-release- New: accepted lomiri-indicator-network [amd64] (lunar-proposed) [1.0.0~git20221216.698b753-2] === guiverc2 is now known as guiverc [03:17] please retry yggdrasil autopkgtest, it was badpkg state, dependencies should be avail now. (btw is the right channel for such request? [04:36] RAOF: hey, does your semi-AA powers allow to remove packages from proposed? [04:37] tjaalton: My full-AA powers definitely do :) [04:37] What can I do you for? [04:37] ooh [04:37] muaahahahahahaha [04:38] removr directx-headers from jammy-proposed, so that the current mesa sru could build on amd64/arm64 [04:39] can be added back later when that one has migrated to updates [04:39] RAOF: Hey, whenever you get a free moment, are you available for SRU vanguard stuff? sil2100 never replied to my last ping. [04:40] then mesa from jammy queue can be dropped [04:41] RAOF: should be safer this way than patching mesa to build [04:41] (Sorry, failed to check timestamps, didn't realize I was interrupting something else.) [04:41] tjaalton: Seems reasonable. [04:44] tjaalton: Is this request documented in any bug (eg: #1991761)? [04:48] arraybolt3: What's your SRU request? I don't have context. [04:49] RAOF: https://bugs.launchpad.net/ubuntu/+source/lubuntu-update-notifier/+bug/2002255 [04:49] -ubottu:#ubuntu-release- Launchpad bug 2002255 in lubuntu-update-notifier (Ubuntu Jammy) "lubuntu-update-notifier provides no good way to resolve a forcibly terminated system update" [Critical, In Progress] [04:52] You want that accepted into {jammy,kinetic}-proposed? [04:52] Yes please. [04:52] I already uploaded it. [04:55] tjaalton: directx-headers removed from proposed; time to get your mesa on! [04:57] RAOF: thanks! no this approach is something I didn't think of first [04:59] -queuebot:#ubuntu-release- Unapproved: rejected mesa [source] (jammy-proposed) [22.0.5-0ubuntu0.4] [05:00] arraybolt3: So, "the update mechanism needs new features to make updates not broken" is something that we're generally sympathetic to in SRU-land. It would *also* be good to make the sddm update not trigger the updater-hangs-indefinitely bug. [05:00] RAOF: I'll kick the builds once the archive is settled [05:00] (This should be possible, at-worst with the terrible hammer of Pre-Depends?) [05:00] RAOF: The problem is that SDDM didn't do anything wrong here. All it does is trigger a perfectly normal prompt that is supposed to be handled by the end user. The fact that lubuntu-update-notifier couldn't handle it beofre is 100% lubuntu-update-notifier's fault. [05:01] As for Pre-Depends, we sorta tried that, sadly enough. [05:01] (Basically we tried to Pre-Depends on lubuntu-update-notifier in lubuntu-desktop to try and force it to install and configure first, which failed. And we can't Pre-Depends on lubuntu-update-notifier in SDDM since SDDM is used in Kubuntu, which would be damaged by the introduction of lubuntu-update-notifier.) [05:01] Oh, right! That'll ensure the new l-u-n is installed and configured, but the broken process is *already running) [05:02] Right. And apt apparently is like "Sure, I'll configure l-u-n first, then lubuntu-desktop! Just lemme configure SDDM first." :-/ [05:04] Yeah, it's *not possible* for apt to do what you need there, which is "sddm is not an update candidate until the version of l-u-n *that is running* is at least $FOO" [05:06] arraybolt3: You've missed a `-v0.4` in your package build flags; the .changes file doesn't include the relevant changelog entries or LP bug reference. [05:07] RAOF: The LP bug reference is actually in the *previous* version, the real version that's in Lunar. Are duplicate LP: #XYZ entries allowable, or is the one in the Lunar version enough? [05:07] The one in the lunar version is enough, but it needs to make it into the .changes file. [05:08] OK... so, this is something I've not done before - do I manually edit the .changes files? I currently generate them with debuild. [05:10] (Sorry, I didn't know that the reference being in the .changes file was a requirement. The SRU docs only require that "there is a reference to the SRU bug number in the changelog", which I did. This is my first SRU, so I'm not exactly experienced at this yet.) [05:10] You need to pass -v$PREVIOUS_ARCHIVE_VERSION to debuild. [05:10] In this case, -v0.4 looks to be the right incantation. [05:10] Oh. That's what you mean by build flags. OK. Thanks, I'll do that real quick. [05:10] That means "include all changelog entries since 0.4 in the .changes file". [05:12] -queuebot:#ubuntu-release- Unapproved: rejected lubuntu-update-notifier [source] (jammy-proposed) [0.5.1~22.04.1] [05:14] -queuebot:#ubuntu-release- Unapproved: lubuntu-update-notifier (jammy-proposed/universe) [0.4 => 0.5.1~22.04.2] (lubuntu) [05:14] RAOF: I think you'll probably want to reject 0.5.1~22.10.1 also. [05:15] I do indeed; just waiting for the tooling to catch up :) [05:15] Ah, makes sense. Thanks for your patience with me while I'm learning how this works. [05:16] -queuebot:#ubuntu-release- Unapproved: rejected lubuntu-update-notifier [source] (kinetic-proposed) [0.5.1~22.10.1] [05:17] -queuebot:#ubuntu-release- Unapproved: lubuntu-update-notifier (kinetic-proposed/universe) [0.4 => 0.5.1~22.10.2] (lubuntu) [05:19] We need to edit the test-case, of course, to not test the PPA packages :) [05:19] Good point, will do. [05:24] -queuebot:#ubuntu-release- New binary: securestring [amd64] (lunar-proposed/universe) [0.2-2] (no packageset) [05:26] -queuebot:#ubuntu-release- New binary: securestring [arm64] (lunar-proposed/universe) [0.2-2] (no packageset) [05:26] -queuebot:#ubuntu-release- New binary: securestring [armhf] (lunar-proposed/universe) [0.2-2] (no packageset) [05:27] -queuebot:#ubuntu-release- New binary: securestring [ppc64el] (lunar-proposed/universe) [0.2-2] (no packageset) [05:28] Test cases updated. [05:29] -queuebot:#ubuntu-release- New binary: securestring [s390x] (lunar-proposed/universe) [0.2-2] (no packageset) [05:36] -queuebot:#ubuntu-release- Unapproved: accepted lubuntu-update-notifier [source] (jammy-proposed) [0.5.1~22.04.2] [05:37] -queuebot:#ubuntu-release- Unapproved: accepted lubuntu-update-notifier [source] (kinetic-proposed) [0.5.1~22.10.2] [05:42] -queuebot:#ubuntu-release- New: accepted securestring [amd64] (lunar-proposed) [0.2-2] [05:42] -queuebot:#ubuntu-release- New: accepted securestring [armhf] (lunar-proposed) [0.2-2] [05:42] -queuebot:#ubuntu-release- New: accepted securestring [s390x] (lunar-proposed) [0.2-2] [05:42] -queuebot:#ubuntu-release- New: accepted securestring [arm64] (lunar-proposed) [0.2-2] [05:42] -queuebot:#ubuntu-release- New: accepted securestring [ppc64el] (lunar-proposed) [0.2-2] [05:50] RAOF: Thank you for everything! [05:57] -queuebot:#ubuntu-release- New binary: securestring [riscv64] (lunar-proposed/universe) [0.2-2] (no packageset) [06:38] hello ubuntu-archive, please old binaries left on amd64: librocksdb7.7 (from 7.7.8-1) [06:40] ack vorlon thanks [06:43] vorlon, https://ci.debian.net/packages/b/bernhard/unstable/arm64/ [06:43] it always failed in debian too [06:45] so maybe we can just hint it? [06:46] (I know its a regression, I'm taking a look anyway, sad that Debian is failing for different reasons) [06:53] a no change rebuild of bernhard works [06:54] oh... pb.py is the culprit [06:55] * LocutusOfBorg opens an RC in Debain [06:57] so if you can restore protobuf, I can issue the rebuild [07:04] Opened #1028371 in src:bernhard by Gianfranco Costamagna (locutusofborg) «bernhard: needs rebuilds on top of new protobuf». https://bugs.debian.org/1028371 [07:04] -ubottu:#ubuntu-release- Debian bug 1028371 in src:bernhard "bernhard: needs rebuilds on top of new protobuf" [Serious, Open] [08:51] -queuebot:#ubuntu-release- Unapproved: directx-headers (jammy-proposed/universe) [1.600.10-1 => 1.606.4-1~ubuntu0.22.04.1] (no packageset) [08:51] ^ this is the same that RAOF removed on request [08:52] sil2100: so, getting back to the mesa hwe backport.. it'd be time to build the second upload of llvm-15 [08:53] -queuebot:#ubuntu-release- New: accepted securestring [riscv64] (lunar-proposed) [0.2-2] [08:53] tjaalton: o/ [08:53] also directx-headers from above [08:53] tjaalton: ok, I have an interview in a moment, after that I'll poke you and we can get things reviewed/accepted [08:53] ack [09:49] hello :), are the s390x autopkgtests meant to be working again? it looks like they are still looping? [09:52] ricotz, hey, those were working for a bit and are having issues again, bdmurray and paride are working with IS on the issue [09:53] seb128, hey :), thank you [09:53] np! [10:02] hello ubuntu-archive, please old binaries left on amd64: librocksdb7.7 (from 7.7.8-1) [10:02] NBS cleanup please? [10:17] LocutusOfBorg, it's not only amd64, removed [10:23] tjaalton: ok, so I'll review the llvm15 and directx-headers uploads in the queue - anything else that needs review for .2? [10:26] yep thanks [10:26] merci! [10:28] sil2100: after that it is mesa itself, which I need to reupload [10:29] ACK. Of course I have another meeting just now, but I'll handle that after this one ;p [11:07] heh, take your time [11:07] llvm surely will [11:22] -queuebot:#ubuntu-release- New binary: lib2geom [amd64] (lunar-proposed/universe) [1.2.2-3] (no packageset) [11:23] -queuebot:#ubuntu-release- New binary: lib2geom [arm64] (lunar-proposed/universe) [1.2.2-3] (no packageset) [11:23] -queuebot:#ubuntu-release- New binary: lib2geom [ppc64el] (lunar-proposed/universe) [1.2.2-3] (no packageset) [11:24] -queuebot:#ubuntu-release- New binary: lib2geom [armhf] (lunar-proposed/universe) [1.2.2-3] (no packageset) [11:24] -queuebot:#ubuntu-release- New binary: lib2geom [s390x] (lunar-proposed/universe) [1.2.2-3] (no packageset) [11:29] -queuebot:#ubuntu-release- Unapproved: accepted llvm-toolchain-15 [source] (kinetic-proposed) [1:15.0.6-3~ubuntu0.22.10.2] [11:32] -queuebot:#ubuntu-release- Unapproved: accepted llvm-toolchain-15 [source] (jammy-proposed) [1:15.0.6-3~ubuntu0.22.04.2] [11:34] tjaalton: hmm, the directx-headers one - the same version already built in the archive. Do you want to resurrect the old binaries? [11:35] Since launchpad will reject it as is. I can either ressurect the old binaries or you'll have to no-change bump the version number [11:36] sil2100: ah, you can use the old ones [11:42] Ok, rejecting the upload and ressurecting the old one then [11:45] -queuebot:#ubuntu-release- New binary: gdcm [amd64] (lunar-proposed/universe) [3.0.20-2] (kubuntu) [11:46] -queuebot:#ubuntu-release- Unapproved: rejected directx-headers [source] (jammy-proposed) [1.606.4-1~ubuntu0.22.04.1] [11:48] -queuebot:#ubuntu-release- Unapproved: directx-headers (jammy-proposed/universe) [1.600.10-1 => 1.606.4-1~ubuntu0.22.04.1] (no packageset) (sync) [11:50] -queuebot:#ubuntu-release- Unapproved: accepted directx-headers [sync] (jammy-proposed) [1.606.4-1~ubuntu0.22.04.1] [11:54] -queuebot:#ubuntu-release- New: accepted gdcm [amd64] (lunar-proposed) [3.0.20-2] [11:54] -queuebot:#ubuntu-release- New: accepted lib2geom [arm64] (lunar-proposed) [1.2.2-3] [11:54] -queuebot:#ubuntu-release- New: accepted lib2geom [ppc64el] (lunar-proposed) [1.2.2-3] [11:54] -queuebot:#ubuntu-release- New: accepted lib2geom [amd64] (lunar-proposed) [1.2.2-3] [11:54] -queuebot:#ubuntu-release- New: accepted lib2geom [s390x] (lunar-proposed) [1.2.2-3] [11:54] -queuebot:#ubuntu-release- New: accepted lib2geom [armhf] (lunar-proposed) [1.2.2-3] [12:16] fresh update_excuses... [12:16] hello perl sync :( [12:45] just found some old-ish messages in moderation for ubuntu-release, don't be too surprised [13:15] -queuebot:#ubuntu-release- Unapproved: systemd-hwe (kinetic-proposed/main) [251.2.1 => 251.4.2] (no packageset) [13:19] -queuebot:#ubuntu-release- Unapproved: systemd-hwe (jammy-proposed/main) [249.11.1 => 249.11.3] (no packageset) [13:22] hey ubuntu-sru! Could somebody please drop systemd-hwe 249.11.2 from the Jammy unapproved queue, and systemd-hwe 251.4.1 from the Kinetic unapproved queue? Those got superseeded/bundled with 249.11.3 and 251.4.2 respectively. [13:29] o/ [13:30] -queuebot:#ubuntu-release- Unapproved: rejected systemd-hwe [source] (kinetic-proposed) [251.4.1] [13:31] -queuebot:#ubuntu-release- Unapproved: rejected systemd-hwe [source] (jammy-proposed) [249.11.2] [13:47] thx! [14:09] -queuebot:#ubuntu-release- Unapproved: systemd-hwe (kinetic-proposed/main) [251.2.1 => 251.4.3] (no packageset) [14:14] -queuebot:#ubuntu-release- Unapproved: systemd-hwe (jammy-proposed/main) [249.11.1 => 249.11.4] (no packageset) [14:16] sorry, there was another bug that could be bundled for those SRUs (LP: #2002065), so we can drop the old ones, again: 251.4.3/kinetic & 249.11.3/jammy ^ [14:16] -ubottu:#ubuntu-release- Launchpad bug 2002065 in systemd-hwe (Ubuntu) "Add ACCEL_LOCATION=base property for Dell machines (0C41, 0C42)" [Undecided, In Progress] https://launchpad.net/bugs/2002065 [14:25] No problem [14:26] -queuebot:#ubuntu-release- Unapproved: rejected systemd-hwe [source] (jammy-proposed) [249.11.3] [14:27] -queuebot:#ubuntu-release- Unapproved: rejected systemd-hwe [source] (kinetic-proposed) [251.4.2] [14:27] thank you! [14:40] -queuebot:#ubuntu-release- Unapproved: alsa-ucm-conf (kinetic-proposed/main) [1.2.6.3-1ubuntu2 => 1.2.6.3-1ubuntu3] (core) [15:29] bdmurray: If it's not too much trouble, could you possibly push sru bug 1965439 for ubuntustudio-default-settings over the finish line in Jammy? I don't know where RikMills is at with it for kubuntu-settings (he probably forgot about it completely), but it's on the brink of ancient. [15:29] -ubottu:#ubuntu-release- Bug 1965439 in kubuntu-settings (Ubuntu Jammy) "[SRU] kdesu fails to authenticate with sudo from Jammy" [High, In Progress] https://launchpad.net/bugs/1965439 [16:08] LocutusOfBorg: cleaned up all the "old binaries" NBS listed on update_excuses [16:08] thanks! [16:08] and if you want to restore protobuf, I can no change rebuild the library [16:08] but I can understand if you want to hold it for some bit [16:09] LocutusOfBorg: yeah what I want is to get python3-defaults unblocked as quickly as possible, so first I've triggered a retest of bernhard/s390x with the archive in the current state; once that's done, we can bring protobuf and a fixed bernhard back in [16:11] thanks! [16:11] please ping once you do, so I can issue the rebuild [16:12] LocutusOfBorg: I'll try to keep track of it and let you know [16:13] it's s390x and the queue is still dire, so [16:14] and ick, protobuf being rolled back breaks a *different* autopkgtest (bcnc) because protobuf was an soname change and now libopencv-dnn406 is uninstallable [16:17] ginggs: any idea about the boost* autopkgtest regressions with python3.11? [16:27] vorlon: yes, boost1.74 is fixed in 1.74.0-18.1ubuntu1 [16:28] and boost1.81 is fixed in... [16:28] ginggs: ok then the retry I just did should take care of that one. Does boost1.81 need the same fix? [16:28] 1.74.0-18.1ubuntu1 :) [16:28] because #1028390 [16:29] debian #1028390 [16:29] -ubottu:#ubuntu-release- Debian bug 1028390 in src:boost1.81 "boost1.81: autopkgtests test boost-defaults" [Normal, Open] https://bugs.debian.org/1028390 [16:29] thanks ubottu [16:29] oh lol [16:29] so I should retrigger that one too? [16:29] (or you could hint it as badtest) [16:33] ah, the test should pass with all proposed, but i can hint if you prefer [16:35] ginggs: the hint would mean less need to chase it over the next days wrt e.g. s390x [16:36] and that bug report says to me that the tests are invalid, so it's not wrong to have a version-specific badtest hint [16:37] vorlon: ack, i'll do it [16:40] coreycb: unicode-cldr-core is on https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.html because python-babel-localedata is Built-Using it. python-babel appears to be an autosynced package owned by the openstack team. Could someone from the openstack team drive an MIR for this please? [17:01] vorlon: to remove numba, did you mean you already did remove 16 source packages, or you would have to? [17:03] vorlon: yes, thanks for raising this. I'll take a look. [17:08] ginggs: did remove [17:08] coreycb: thank you! [17:09] -queuebot:#ubuntu-release- Unapproved: python-websockets (jammy-backports/universe) [9.1-1 => 10.2-1~bpo22.04.1] (no packageset) [17:19] vorlon: ok, thanks, but numba itself not removed? [17:19] ginggs: isn't it? if I didn't already remove it it's because I wanted to re-check reverse-depends output after the spate of removals [17:20] ginggs: removed now [17:20] vorlon: ta === ahasenack_ is now known as ahasenack [18:17] new perl came just in time for me to fix nodejs merge :D [18:17] 🎉 [18:27] Anybody on the SRU team available? If it's not too much trouble, could you possibly push sru bug 1965439 for ubuntustudio-default-settings over the finish line in Jammy? I don't know where RikMills is at with it for kubuntu-settings (he probably forgot about it completely), but it's on the brink of ancient. [18:27] -ubottu:#ubuntu-release- Bug 1965439 in kubuntu-settings (Ubuntu Jammy) "[SRU] kdesu fails to authenticate with sudo from Jammy" [High, In Progress] https://launchpad.net/bugs/1965439 [19:13] I'm looking at ubuntustudio-default-settings. [19:16] And for the record the bug only got verified this year so the ancientness isn't on the SRU team this time. [19:23] bdmurray: Yeah, that was my fault. :) Last week, my time. [19:24] Actually, I verified it, but lost the bug and forgot it with Prague and all. [19:25] My fault for not marking the bug as such. [19:52] bdmurray: Thanks! To be clear, I wasn't blaming the SRU team for anything. Completely my fault. :) [19:57] Sometime the SRU team is a bottleneck, just not this time! [20:04] :) [20:43] schopin, athos: hi, I just want to check if the both of you are focused on python3-defaults migration this week for +1 (find-proposed-cluster ;), and if we should coordinate at all to divide and conquer [21:20] I supposed someone else would focus on that. I ran your new script and decided to tackle some rust stuff, considering someone would go for python3-defoaults. Should I abort and fall back to python3-defaults? :) [21:21] vorlon: thanks for the test hint on postgresql-common yesterday, btw :) [21:33] -queuebot:#ubuntu-release- Unapproved: systemd-hwe (jammy-proposed/main) [249.11.1 => 249.11.2] (no packageset) [21:34] -queuebot:#ubuntu-release- Unapproved: rejected systemd-hwe [source] (jammy-proposed) [249.11.4] [21:44] -queuebot:#ubuntu-release- Unapproved: accepted ca-certificates-java [source] (jammy-proposed) [20190909ubuntu1.1] [22:14] -queuebot:#ubuntu-release- Unapproved: accepted systemd-hwe [source] (kinetic-proposed) [251.4.3] [22:15] -queuebot:#ubuntu-release- Unapproved: accepted systemd-hwe [source] (jammy-proposed) [249.11.2] [22:59] athos: python3-defaults is bigger by an order of magnitude and there's plenty of work to go around; and the longer it stays the more it risks entanglement with other transitions [23:29] -queuebot:#ubuntu-release- New binary: netpbm-free [amd64] (lunar-proposed/universe) [2:10.98.00-1] (i386-whitelist, kubuntu) [23:30] -queuebot:#ubuntu-release- New binary: netpbm-free [i386] (lunar-proposed/universe) [2:10.98.00-1] (i386-whitelist, kubuntu) [23:33] -queuebot:#ubuntu-release- New binary: elpa [amd64] (lunar-proposed/universe) [2022.11.001-2] (no packageset) [23:34] -queuebot:#ubuntu-release- New binary: netpbm-free [ppc64el] (lunar-proposed/universe) [2:10.98.00-1] (i386-whitelist, kubuntu) [23:37] -queuebot:#ubuntu-release- New binary: netpbm-free [s390x] (lunar-proposed/universe) [2:10.98.00-1] (i386-whitelist, kubuntu) [23:41] -queuebot:#ubuntu-release- New binary: elpa [s390x] (lunar-proposed/universe) [2022.11.001-2] (no packageset) [23:42] -queuebot:#ubuntu-release- New binary: elpa [ppc64el] (lunar-proposed/universe) [2022.11.001-2] (no packageset) [23:42] -queuebot:#ubuntu-release- New binary: netpbm-free [arm64] (lunar-proposed/universe) [2:10.98.00-1] (i386-whitelist, kubuntu) [23:44] -queuebot:#ubuntu-release- New binary: elpa [arm64] (lunar-proposed/universe) [2022.11.001-2] (no packageset) [23:44] -queuebot:#ubuntu-release- New binary: netpbm-free [armhf] (lunar-proposed/universe) [2:10.98.00-1] (i386-whitelist, kubuntu) [23:46] -queuebot:#ubuntu-release- New: accepted elpa [amd64] (lunar-proposed) [2022.11.001-2] [23:46] -queuebot:#ubuntu-release- New: accepted elpa [ppc64el] (lunar-proposed) [2022.11.001-2] [23:46] -queuebot:#ubuntu-release- New: accepted netpbm-free [amd64] (lunar-proposed) [2:10.98.00-1] [23:46] -queuebot:#ubuntu-release- New: accepted netpbm-free [armhf] (lunar-proposed) [2:10.98.00-1] [23:46] -queuebot:#ubuntu-release- New: accepted netpbm-free [ppc64el] (lunar-proposed) [2:10.98.00-1] [23:46] -queuebot:#ubuntu-release- New: accepted elpa [arm64] (lunar-proposed) [2022.11.001-2] [23:46] -queuebot:#ubuntu-release- New: accepted netpbm-free [arm64] (lunar-proposed) [2:10.98.00-1] [23:46] -queuebot:#ubuntu-release- New: accepted netpbm-free [s390x] (lunar-proposed) [2:10.98.00-1] [23:46] -queuebot:#ubuntu-release- New: accepted elpa [s390x] (lunar-proposed) [2022.11.001-2] [23:46] -queuebot:#ubuntu-release- New: accepted netpbm-free [i386] (lunar-proposed) [2:10.98.00-1] [23:52] -queuebot:#ubuntu-release- New binary: elpa [armhf] (lunar-proposed/universe) [2022.11.001-2] (no packageset)