[Bug 2051939] Re: [SRU exception] backport 5.32 to Jammy and Mantic

2024-04-04 Thread Paride Legovini
** Changed in: autopkgtest (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051939 Title: [SRU exception] backport 5.32 to Jammy and Mantic To manage

[Bug 2051939] Re: [SRU exception] backport 5.32 to Jammy and Mantic

2024-03-21 Thread Launchpad Bug Tracker
This bug was fixed in the package autopkgtest - 5.32ubuntu3~22.04.1 --- autopkgtest (5.32ubuntu3~22.04.1) jammy; urgency=medium * SRU to jammy (LP: #2051939) autopkgtest (5.32ubuntu3) noble; urgency=medium * Remove .mypy_cache cruft from the previous upload Thanks: Alex

[Bug 2051939] Re: [SRU exception] backport 5.32 to Jammy and Mantic

2024-03-21 Thread Launchpad Bug Tracker
This bug was fixed in the package autopkgtest - 5.32ubuntu3~23.10.1 --- autopkgtest (5.32ubuntu3~23.10.1) mantic; urgency=medium * SRU to mantic (LP: #2051939) autopkgtest (5.32ubuntu3) noble; urgency=medium * Remove .mypy_cache cruft from the previous upload Thanks: Alex

[Bug 2051939] Re: [SRU exception] backport 5.32 to Jammy and Mantic

2024-03-21 Thread Andreas Hasenack
The remaining dep8 systemd/ppc64el failure on jammy cleared after the migration-reference/0 run also failed, expectedly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051939 Title: [SRU exception]

[Bug 2051939] Re: [SRU exception] backport 5.32 to Jammy and Mantic

2024-03-21 Thread Andreas Hasenack
I see new runs of the patched systemd package in noble, and even though tests-in-lxd is still failing, now the reason is not the patch failing to apply, it's something else: Starting autopkgtest-prepare-Rk7 4650s Created symlink /etc/systemd/system/serial-getty@getty.service → /dev/null. 4656s

[Bug 2051939] Re: [SRU exception] backport 5.32 to Jammy and Mantic

2024-03-14 Thread Andreas Hasenack
I'm trying to verify that the systemd dep8 fix is working, but looks like it hasn't run yet in noble. The fix landed in systemd 255.4-1ubuntu1 according to the changelog. Noble now has 255.4-1ubuntu4 (proposed), but I can't find any 255.4-* dep8 run in

[Bug 2051939] Re: [SRU exception] backport 5.32 to Jammy and Mantic

2024-03-11 Thread Skia
** Tags removed: verification-needed verification-needed-jammy verification-needed-mantic ** Tags added: verification-done verification-done-jammy verification-done-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 2051939] Re: [SRU exception] backport 5.32 to Jammy and Mantic

2024-02-29 Thread Skia
I've performed some manual verification on local podman containers and encountered no issue. Here are my tests in details, if someone wants to replicate them. I run the containers with the following command: ``` podman run -it --rm -v /srv/images/:/srv/images -v /dev/kvm:/dev/kvm ubuntu:jammy

[Bug 2051939] Re: [SRU exception] backport 5.32 to Jammy and Mantic

2024-02-27 Thread Skia
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2055200 here is a bug with a debdiff fixing the systemd tests-in-lxd issue. It will be block-proposed until a more important systemd SRU is done. -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 2051939] Re: [SRU exception] backport 5.32 to Jammy and Mantic

2024-02-27 Thread Skia
Regarding autopkgtest regressions: On Mantic: * the surf tests are very flaky[1], and have been so for a while[2]. With some retriggers, arm64 could pass, but with the current load on the infra, I couldn't make armhf to pass. Still the error reported in the log file[3] is `Too few characters