This bug was fixed in the package systemd - 252.5-2ubuntu3.1
---------------
systemd (252.5-2ubuntu3.1) lunar; urgency=medium
* debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229)
File: debian/tests/tests-in-lxd
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=2a443ddd5b67596647e463eee64d58c3c71bbf08
* udev-rules: fix nvme symlink creation on namespace changes (LP: #2028180)
File:
debian/patches/lp2028180-udev-rules-fix-nvme-symlink-creation-on-namespace-changes.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=064c7c00aa133b697ab3c0082b825e2f197f91cc
* core: reorder systemd arguments on reexec (LP: #2013543)
File:
debian/patches/lp2013543-core-reorder-systemd-arguments-on-reexec.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=45541ccbc16ed30b6a120cda7401f69cce164d54
* network/dhcp4: do not ignore the gateway even if the destination is in same
network (LP: #2009743)
Files:
-
debian/patches/lp2009743/network-dhcp4-do-not-ignore-the-gateway-even-if-the-desti.patch
-
debian/patches/lp2009743/test-network-add-one-more-testcase-for-DHCPv4-classless-r.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ddea3bcbca3421299b13cfe897157cfbf9f0f06d
* debian/systemd.postint: do not daemon re-exec if we could hit LP: #2013543
File: debian/systemd.postinst
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=e1a08bb427e19ced6c16f054ebdee43ccbc9c528
* Drop debian/UBUNTU-wait-online-exit-if-no-links-are-managed.patch (LP:
#1982218)
File:
debian/patches/debian/UBUNTU-wait-online-exit-if-no-links-are-managed.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8235427fd8859ee393a08d425e1a52e1ebcbe2f1
* sd-bus: bus_message_type_from_string is not pure (LP: #2031683)
File:
debian/patches/lp2031683-sd-bus-bus_message_type_from_string-is-not-pure.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=2d65b6c74864976a2bb42c884baf75d1674215fc
-- Nick Rosbrook <en...@ubuntu.com> Fri, 18 Aug 2023 14:15:03 -0400
** Changed in: systemd (Ubuntu Lunar)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2031683
Title:
systemd FTBFS on ppc64el due to fuzzer failures
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Lunar:
Fix Released
Bug description:
[Impact]
systemd FTBFS on ppc64el due to failing fuzz tests.
[Test Plan]
The build-time tests and fuzzing should pass so that the build
ultimately passes on ppc64el.
[Where problems could occur]
The patch just removes the "pure" attribute from
bus_message_type_from_string, because that attribute was incorrect for
the behavior of the function. Hence, the regression potential should
be limited to building the package.
[Original Description]
This PPA build[1] demonstrates the issue, the relevant part being:
[ ... ]
1061/1066 systemd:dist-check / check-help-networkctl
OK 0.04s
1062/1066 systemd:dist-check / check-version-networkctl
OK 0.03s
1063/1066 systemd:dist-check / check-help-kernel-install
OK 0.03s
1064/1066 systemd:dist-check / check-version-kernel-install
OK 0.02s
1065/1066 systemd:dist-check / check-directives
OK 0.18s
1066/1066 systemd:dist-check / parse-hwdb
OK 5.43s
Summary of Failures:
661/1066 systemd:fuzzers / fuzz-bus-match_bugzilla1935084.input
FAIL 0.22s killed by signal 11 SIGSEGV
667/1066 systemd:fuzzers / fuzz-bus-match_test.input
FAIL 0.25s killed by signal 11 SIGSEGV
Ok: 1032
Expected Fail: 0
Fail: 2
Unexpected Pass: 0
Skipped: 32
Timeout: 0
Full log written to
/<<PKGBUILDDIR>>/obj-powerpc64le-linux-gnu/meson-logs/testlog.txt
make[1]: *** [debian/rules:308: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:312: binary-arch] Error 2
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit
status 2
This appears to be related to a toolchain change, because I get the
same result when doing a no-change rebuild of systemd on ppc64el in
Lunar (i.e. the FTBFS is not introduced by the changes I am testing).
[1] https://launchpadlibrarian.net/682104329/buildlog_ubuntu-lunar-
ppc64el.systemd_252.5-2ubuntu4~ppa11_BUILDING.txt.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2031683/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
