-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]00:00
=== guiverc2 is now known as guiverc
zhsjplease retry yggdrasil autopkgtest, it was badpkg state, dependencies should be avail now. (btw is the right channel for such request?03:17
tjaaltonRAOF: hey, does your semi-AA powers allow to remove packages from proposed?04:36
RAOFtjaalton: My full-AA powers definitely do :)04:37
RAOFWhat can I do you for?04:37
tjaaltonremovr directx-headers from jammy-proposed, so that the current mesa sru could build on amd64/arm6404:38
tjaaltoncan be added back later when that one has migrated to updates04:39
arraybolt3RAOF: Hey, whenever you get a free moment, are you available for SRU vanguard stuff? sil2100 never replied to my last ping.04:39
tjaaltonthen mesa from jammy queue can be dropped04:40
tjaaltonRAOF: should be safer this way than patching mesa to build04:41
arraybolt3(Sorry, failed to check timestamps, didn't realize I was interrupting something else.)04:41
RAOFtjaalton: Seems reasonable.04:41
RAOFtjaalton: Is this request documented in any bug (eg: #1991761)?04:44
RAOFarraybolt3: What's your SRU request? I don't have context.04:48
arraybolt3RAOF: https://bugs.launchpad.net/ubuntu/+source/lubuntu-update-notifier/+bug/200225504: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:49
RAOFYou want that accepted into {jammy,kinetic}-proposed?04:52
arraybolt3Yes please.04:52
arraybolt3I already uploaded it.04:52
RAOFtjaalton: directx-headers removed from proposed; time to get your mesa on!04:55
tjaaltonRAOF: thanks! no this approach is something I didn't think of first04:57
-queuebot:#ubuntu-release- Unapproved: rejected mesa [source] (jammy-proposed) [22.0.5-0ubuntu0.4]04:59
RAOFarraybolt3: 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
tjaaltonRAOF: I'll kick the builds once the archive is settled05:00
RAOF(This should be possible, at-worst with the terrible hammer of Pre-Depends?)05:00
arraybolt3RAOF: 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:00
arraybolt3As for Pre-Depends, we sorta tried that, sadly enough.05:01
arraybolt3(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
RAOFOh, right! That'll ensure the new l-u-n is installed and configured, but the broken process is *already running)05:01
arraybolt3Right. And apt apparently is like "Sure, I'll configure l-u-n first, then lubuntu-desktop! Just lemme configure SDDM first." :-/05:02
RAOFYeah, 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:04
RAOFarraybolt3: 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:06
arraybolt3RAOF: 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
RAOFThe one in the lunar version is enough, but it needs to make it into the .changes file.05:07
arraybolt3OK... so, this is something I've not done before - do I manually edit the .changes files? I currently generate them with debuild.05:08
arraybolt3(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
RAOFYou need to pass -v$PREVIOUS_ARCHIVE_VERSION to debuild.05:10
RAOFIn this case, -v0.4 looks to be the right incantation.05:10
arraybolt3Oh. That's what you mean by build flags. OK. Thanks, I'll do that real quick.05:10
RAOFThat means "include all changelog entries since 0.4 in the .changes file".05:10
-queuebot:#ubuntu-release- Unapproved: rejected lubuntu-update-notifier [source] (jammy-proposed) [0.5.1~22.04.1]05:12
-queuebot:#ubuntu-release- Unapproved: lubuntu-update-notifier (jammy-proposed/universe) [0.4 => 0.5.1~22.04.2] (lubuntu)05:14
arraybolt3RAOF: I think you'll probably want to reject 0.5.1~22.10.1 also.05:14
RAOFI do indeed; just waiting for the tooling to catch up :)05:15
arraybolt3Ah, makes sense. Thanks for your patience with me while I'm learning how this works.05:15
-queuebot:#ubuntu-release- Unapproved: rejected lubuntu-update-notifier [source] (kinetic-proposed) [0.5.1~22.10.1]05:16
-queuebot:#ubuntu-release- Unapproved: lubuntu-update-notifier (kinetic-proposed/universe) [0.4 => 0.5.1~22.10.2] (lubuntu)05:17
RAOFWe need to edit the test-case, of course, to not test the PPA packages :)05:19
arraybolt3Good point, will do.05:19
-queuebot:#ubuntu-release- New binary: securestring [amd64] (lunar-proposed/universe) [0.2-2] (no packageset)05:24
-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:26
-queuebot:#ubuntu-release- New binary: securestring [ppc64el] (lunar-proposed/universe) [0.2-2] (no packageset)05:27
arraybolt3Test cases updated.05:28
-queuebot:#ubuntu-release- New binary: securestring [s390x] (lunar-proposed/universe) [0.2-2] (no packageset)05:29
-queuebot:#ubuntu-release- Unapproved: accepted lubuntu-update-notifier [source] (jammy-proposed) [0.5.1~22.04.2]05:36
-queuebot:#ubuntu-release- Unapproved: accepted lubuntu-update-notifier [source] (kinetic-proposed) [0.5.1~22.10.2]05:37
-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:42
arraybolt3RAOF: Thank you for everything!05:50
-queuebot:#ubuntu-release- New binary: securestring [riscv64] (lunar-proposed/universe) [0.2-2] (no packageset)05:57
LocutusOfBorghello ubuntu-archive, please old binaries left on amd64: librocksdb7.7 (from 7.7.8-1)06:38
LocutusOfBorgack vorlon thanks06:40
LocutusOfBorgvorlon, https://ci.debian.net/packages/b/bernhard/unstable/arm64/06:43
LocutusOfBorgit always failed in debian too06:43
LocutusOfBorgso maybe we can just hint it?06:45
LocutusOfBorg(I know its a regression, I'm taking a look anyway, sad that Debian is failing for different reasons)06:46
LocutusOfBorga no change rebuild of bernhard works06:53
LocutusOfBorgoh... pb.py is the culprit06:54
* LocutusOfBorg opens an RC in Debain06:55
LocutusOfBorgso if you can restore protobuf, I can issue the rebuild06:57
LocutusOfBorg<BTS> Opened #1028371 in src:bernhard by Gianfranco Costamagna (locutusofborg) «bernhard: needs rebuilds on top of new protobuf». https://bugs.debian.org/102837107:04
-ubottu:#ubuntu-release- Debian bug 1028371 in src:bernhard "bernhard: needs rebuilds on top of new protobuf" [Serious, Open]07:04
-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
tjaalton^ this is the same that RAOF removed on request08:51
tjaaltonsil2100: so, getting back to the mesa hwe backport.. it'd be time to build the second upload of llvm-1508:52
-queuebot:#ubuntu-release- New: accepted securestring [riscv64] (lunar-proposed) [0.2-2]08:53
sil2100tjaalton: o/08:53
tjaaltonalso directx-headers from above08:53
sil2100tjaalton: ok, I have an interview in a moment, after that I'll poke you and we can get things reviewed/accepted08:53
ricotzhello :), are the s390x autopkgtests meant to be working again? it looks like they are still looping?09:49
seb128ricotz, hey, those were working for a bit and are having issues again, bdmurray and paride are working with IS on the issue09:52
ricotzseb128, hey :), thank you09:53
LocutusOfBorghello ubuntu-archive, please old binaries left on amd64: librocksdb7.7 (from 7.7.8-1)10:02
LocutusOfBorgNBS cleanup please?10:02
seb128LocutusOfBorg, it's not only amd64, removed10:17
sil2100tjaalton: ok, so I'll review the llvm15 and directx-headers uploads in the queue - anything else that needs review for .2?10:23
LocutusOfBorgyep thanks10:26
tjaaltonsil2100: after that it is mesa itself, which I need to reupload10:28
sil2100ACK. Of course I have another meeting just now, but I'll handle that after this one ;p10:29
tjaaltonheh, take your time11:07
tjaaltonllvm surely will11:07
-queuebot:#ubuntu-release- New binary: lib2geom [amd64] (lunar-proposed/universe) [1.2.2-3] (no packageset)11:22
-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:23
-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:24
-queuebot:#ubuntu-release- Unapproved: accepted llvm-toolchain-15 [source] (kinetic-proposed) [1:15.0.6-3~ubuntu0.22.10.2]11:29
-queuebot:#ubuntu-release- Unapproved: accepted llvm-toolchain-15 [source] (jammy-proposed) [1:15.0.6-3~ubuntu0.22.04.2]11:32
sil2100tjaalton: hmm, the directx-headers one - the same version already built in the archive. Do you want to resurrect the old binaries?11:34
sil2100Since launchpad will reject it as is. I can either ressurect the old binaries or you'll have to no-change bump the version number11:35
tjaaltonsil2100: ah, you can use the old ones11:36
sil2100Ok, rejecting the upload and ressurecting the old one then11:42
-queuebot:#ubuntu-release- New binary: gdcm [amd64] (lunar-proposed/universe) [3.0.20-2] (kubuntu)11:45
-queuebot:#ubuntu-release- Unapproved: rejected directx-headers [source] (jammy-proposed) [1.606.4-1~ubuntu0.22.04.1]11:46
-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:48
-queuebot:#ubuntu-release- Unapproved: accepted directx-headers [sync] (jammy-proposed) [1.606.4-1~ubuntu0.22.04.1]11:50
-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]11:54
ginggsfresh update_excuses...12:16
ginggshello perl sync :(12:16
laneyjust found some old-ish messages in moderation for ubuntu-release, don't be too surprised12:45
-queuebot:#ubuntu-release- Unapproved: systemd-hwe (kinetic-proposed/main) [251.2.1 => 251.4.2] (no packageset)13:15
-queuebot:#ubuntu-release- Unapproved: systemd-hwe (jammy-proposed/main) [249.11.1 => 249.11.3] (no packageset)13:19
slyonhey 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:22
-queuebot:#ubuntu-release- Unapproved: rejected systemd-hwe [source] (kinetic-proposed) [251.4.1]13:30
-queuebot:#ubuntu-release- Unapproved: rejected systemd-hwe [source] (jammy-proposed) [249.11.2]13:31
-queuebot:#ubuntu-release- Unapproved: systemd-hwe (kinetic-proposed/main) [251.2.1 => 251.4.3] (no packageset)14:09
-queuebot:#ubuntu-release- Unapproved: systemd-hwe (jammy-proposed/main) [249.11.1 => 249.11.4] (no packageset)14:14
slyonsorry, 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/200206514:16
sil2100No problem14:25
-queuebot:#ubuntu-release- Unapproved: rejected systemd-hwe [source] (jammy-proposed) [249.11.3]14:26
-queuebot:#ubuntu-release- Unapproved: rejected systemd-hwe [source] (kinetic-proposed) [251.4.2]14:27
slyonthank you!14:27
-queuebot:#ubuntu-release- Unapproved: alsa-ucm-conf (kinetic-proposed/main) [ =>] (core)14:40
Eickmeyerbdmurray: 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/196543915:29
vorlonLocutusOfBorg: cleaned up all the "old binaries" NBS listed on update_excuses16:08
LocutusOfBorgand if you want to restore protobuf, I can no change rebuild the library16:08
LocutusOfBorgbut I can understand if you want to hold it for some bit16:08
vorlonLocutusOfBorg: 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 in16:09
LocutusOfBorgplease ping once you do, so I can issue the rebuild16:11
vorlonLocutusOfBorg: I'll try to keep track of it and let you know16:12
vorlonit's s390x and the queue is still dire, so16:13
vorlonand ick, protobuf being rolled back breaks a *different* autopkgtest (bcnc) because protobuf was an soname change and now libopencv-dnn406 is uninstallable16:14
vorlonginggs: any idea about the boost* autopkgtest regressions with python3.11?16:17
ginggsvorlon: yes, boost1.74 is fixed in 1.74.0-18.1ubuntu116:27
ginggsand boost1.81 is fixed in...16:28
vorlonginggs: ok then the retry I just did should take care of that one.  Does boost1.81 need the same fix?16:28
ginggs1.74.0-18.1ubuntu1 :)16:28
ginggsbecause #102839016:28
ginggsdebian #102839016:29
-ubottu:#ubuntu-release- Debian bug 1028390 in src:boost1.81 "boost1.81: autopkgtests test boost-defaults" [Normal, Open] https://bugs.debian.org/102839016:29
ginggsthanks ubottu16:29
vorlonoh lol16:29
vorlonso I should retrigger that one too?16:29
vorlon(or you could hint it as badtest)16:29
ginggsah, the test should pass with all proposed, but i can hint if you prefer16:33
vorlonginggs: the hint would mean less need to chase it over the next days wrt e.g. s390x16:35
vorlonand that bug report says to me that the tests are invalid, so it's not wrong to have a version-specific badtest hint16:36
ginggsvorlon: ack, i'll do it16:37
vorloncoreycb: 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?16:40
ginggsvorlon: to remove numba, did you mean you already did remove 16 source packages, or you would have to?17:01
coreycbvorlon: yes, thanks for raising this. I'll take a look.17:03
vorlonginggs: did remove17:08
vorloncoreycb: thank you!17:08
-queuebot:#ubuntu-release- Unapproved: python-websockets (jammy-backports/universe) [9.1-1 => 10.2-1~bpo22.04.1] (no packageset)17:09
ginggsvorlon: ok, thanks, but numba itself not removed?17:19
vorlonginggs: 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 removals17:19
vorlonginggs: removed now17:20
ginggsvorlon: ta17:20
=== ahasenack_ is now known as ahasenack
LocutusOfBorgnew perl came just in time for me to fix nodejs merge :D18:17
EickmeyerAnybody 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/196543918:27
bdmurrayI'm looking at ubuntustudio-default-settings.19:13
bdmurrayAnd for the record the bug only got verified this year so the ancientness isn't on the SRU team this time.19:16
Eickmeyerbdmurray: Yeah, that was my fault. :) Last week, my time.19:23
EickmeyerActually, I verified it, but lost the bug and forgot it with Prague and all.19:24
EickmeyerMy fault for not marking the bug as such.19:25
Eickmeyerbdmurray: Thanks! To be clear, I wasn't blaming the SRU team for anything. Completely my fault. :)19:52
bdmurraySometime the SRU team is a bottleneck, just not this time!19:57
vorlonschopin, 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 conquer20:43
athosI 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:20
athosvorlon: thanks for the test hint on postgresql-common yesterday, btw :)21:21
-queuebot:#ubuntu-release- Unapproved: systemd-hwe (jammy-proposed/main) [249.11.1 => 249.11.2] (no packageset)21:33
-queuebot:#ubuntu-release- Unapproved: rejected systemd-hwe [source] (jammy-proposed) [249.11.4]21:34
-queuebot:#ubuntu-release- Unapproved: accepted ca-certificates-java [source] (jammy-proposed) [20190909ubuntu1.1]21:44
-queuebot:#ubuntu-release- Unapproved: accepted systemd-hwe [source] (kinetic-proposed) [251.4.3]22:14
-queuebot:#ubuntu-release- Unapproved: accepted systemd-hwe [source] (jammy-proposed) [249.11.2]22:15
vorlonathos: 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 transitions22:59
-queuebot:#ubuntu-release- New binary: netpbm-free [amd64] (lunar-proposed/universe) [2:10.98.00-1] (i386-whitelist, kubuntu)23:29
-queuebot:#ubuntu-release- New binary: netpbm-free [i386] (lunar-proposed/universe) [2:10.98.00-1] (i386-whitelist, kubuntu)23:30
-queuebot:#ubuntu-release- New binary: elpa [amd64] (lunar-proposed/universe) [2022.11.001-2] (no packageset)23:33
-queuebot:#ubuntu-release- New binary: netpbm-free [ppc64el] (lunar-proposed/universe) [2:10.98.00-1] (i386-whitelist, kubuntu)23:34
-queuebot:#ubuntu-release- New binary: netpbm-free [s390x] (lunar-proposed/universe) [2:10.98.00-1] (i386-whitelist, kubuntu)23:37
-queuebot:#ubuntu-release- New binary: elpa [s390x] (lunar-proposed/universe) [2022.11.001-2] (no packageset)23:41
-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:42
-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:44
-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:46
-queuebot:#ubuntu-release- New binary: elpa [armhf] (lunar-proposed/universe) [2022.11.001-2] (no packageset)23:52

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!