=== guiverc2 is now known as guiverc === flag is now known as ppisati [10:31] 4 [10:31] oops [11:21] xnox: thank you for the correction. But note that we *collaborate* on bug descriptions. It's perfectly acceptable for anyone to edit a bug description in good faith. It's like a wiki - no consultation is required. [11:22] In any case, it's an important edge case for which an explanation should exist in the SRU documentation, IMHO, so I don't think entirely removing the mention is appropriate either. Feel free to correct it though. [11:22] (on bug 2008086) [11:22] -ubottu:#ubuntu-devel- Bug 2008086 in wireguard (Ubuntu Kinetic) "Cannot install wireguard-tools on systems without .deb kernel - Drop useless depends on wireguard-modules / wireguard-dkms" [Undecided, In Progress] https://launchpad.net/bugs/2008086 [12:08] actually did learn something from that [13:51] hi, is it expected that python packages which only provide a pyproject.toml can't be built in 22.04 with pybuild using the pyproject plugin? AFAIU setuptools 59.6 might be too old to support it? [13:51] https://paste.ubuntu.com/p/hnQP5HrYXg/ is the error I get [15:43] rbasak: sure, but it looked sneaky, because it was direct description update, without any changelog or comment, and reading bug activity is hard to notice what has been added and by whom. [16:02] !dmb-ping [16:02] bdmurray, kanashiro, rbasak, seb128, sil2100, teward, utkarsh2102: DMB ping [16:02] *pushes rbasak out the airlock* [16:36] hi ubuntu-sru, what kind of hint is needed for when a migration-reference/0 run fails in a stable release? [16:37] specifically, https://autopkgtest.ubuntu.com/packages/e/exim4/kinetic/ppc64el [16:37] investigation ongoing in https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/1983605 [16:37] -ubottu:#ubuntu-devel- Launchpad bug 1983605 in exim4 (Ubuntu) "exim4 autopkgtest failure on ppc64el" [High, Triaged] [16:37] but it's not caused by the openldap SRU [16:37] https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/1983605/comments/4 has the most up-do-date info. tl;dr: building exim4 with -pie shows the problem [16:38] and it also happens in lunar === rs20090 is now known as rs2009 [16:49] ahasenack: "A regression not caused by the SRU may be badtest or reset-tested away (doesn't matter which for SRUs)." --https://wiki.ubuntu.com/StableReleaseUpdates#Expected_resolution_for_reported_autopkgtest_failures [17:26] ubuntu-sru: https://code.launchpad.net/~ubuntu-release/britney/+git/hints-ubuntu/+merge/440264 [17:28] or maybe a reset-test would have been better? I didn't understand what it does, and the britney doc didn't mention it [17:28] given its name, perhaps it lets the package migrate once? I don't know [17:56] Can a core dev please retry these autopkgtests? retry-autopkgtest-regressions --blocks systemd -s focal | grep -v -E "package=linux-|package=fwupd". [18:09] And these too please: `retry-autopkgtest-regressions --blocks systemd -s jammy` and `retry-autopkgtest-regressions --blocks systemd -s kinetic` [18:10] These are almost all s390x test bed failures. [18:43] enr0n: done [18:45] vorlon: thanks [19:29] Hi, can someone help me retry one autopkgtest here: https://autopkgtest.ubuntu.com/request.cgi?release=kinetic&arch=i386&package=dkms&trigger=migration-reference/0 [19:29] Thank you in advance! [19:35] liushuyu: done [19:38] dbungert: Thank you! [21:27] Hi, can someone help me retry one autopkgtest here: https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=amd64&package=rust-ahash&trigger=rust-ahash%2F0.8.3-2 it seems like a testbed error [21:27] Thank you in advance! [21:29] liushuyu: done [21:30] bdmurray: Thank you! [21:31] The testbed at that time was failed to shutdown correctly: https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/r/rust-ahash/20230401_201403_c96f4@/log.gz