This bug was fixed in the package systemd - 247.1-4ubuntu1
---------------
systemd (247.1-4ubuntu1) hirsute; urgency=medium
[ Dan Streetman ]
* d/p/lp1905044-test-use-cap_last_cap-for-max-supported-cap-number-n.patch:
Fix test use of new cap numbers with 5.8 kernel (LP: #1905044)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d55c6f8186cb2cb73f61d6ff5b2e0ded82ef265c
[ Balint Reczey ]
* Merge to Ubuntu from Debian unstable
* Refresh patches
- Dropped changes:
* debian/patches/dhcp-Allow-setting-request-options-again.patch
(Upstream code has been changed in a similar way)
*
debian/patches/Revert-network-do-not-drop-foreign-config-if-interface-is.patch
debian/patches/network-Set-link-state-to-LINK_STATE_PENDING-instead-of-t.patch
(Revert-network-prevent-interfaces-to-be-initialized-multi.patch is
still kept)
*
debian/patches/lp1845909/0002-network-add-link-setting_genmode-flag.patch
* d/p/lp1905044-test-use-cap_last_cap-for-max-supported-cap-number-n.patch
(Present in upstream 247.)
* debian/udev.NEWS: Mention udev rules changes in 247
File: debian/udev.NEWS
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9f33f19683c2b864384c2ae59b312b2c844ed633
* Don't start systemd-udev-trigger.service in containers.
It fails and is not likely to be useful.
File:
debian/patches/units-Don-t-start-systemd-udev-trigger.service-in-a-conta.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7b04fe5f98a4d204f73a1ec22884b9b3053a9a82
* test: use modern qemu numa arguments (LP: #1908259)
File: debian/patches/test-use-modern-qemu-numa-arguments.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=158106e74d452cf6cd5cd737432cbe6b7d47286c
systemd (247.1-4) unstable; urgency=medium
[ наб ]
* debian/extra/kernel-install.d/85-initrd.install: Don't install initrd when
an explicit path was passed (Closes: #970213)
* debian/extra/kernel-install.d/85-initrd.install: Match initrd installation
messages and uninstallation to 90-loaderentry.install
[ Michael Biebl ]
* sd-device: keep escaped strings in DEVLINK= property (Closes: #976699)
systemd (247.1-3) unstable; urgency=medium
* d/t/timedated: Ignore return code of dbus-monitor in wait_mon()
We are not really interested in the return code and error messages from
dbus-monitor after killing it, so ignore them to avoid undesired
autopkgtest failures.
systemd (247.1-2) unstable; urgency=medium
[ Michael Biebl ]
* Upload to unstable
* Revert "d/t/timedated: use /bin/bash to work around job handling issue in
dash"
[ Balint Reczey ]
* debian/tests/timedated: Wait for the killed child only.
There may be other children of the script due to autopkgtest machinery
and they exit after the script exited. (LP: #1904406)
systemd (247.1-1) experimental; urgency=medium
* New upstream version 247.1
systemd (247-1) experimental; urgency=medium
* New upstream version 247
* Rebase patches
* Update symbol versions for the v247 release
systemd (247~rc2-3) experimental; urgency=medium
* Merge changes from unstable
* sd-device: make sd_device_has_current_tag() compatible with udev database
generated by older udevd
(Closes: #974730)
* Add Breaks: udev (<< 247~) to systemd.
This ensures that udev is upgraded alongside systemd and both support
the new udev tags concept introduced in v247. (Closes: #975554)
systemd (247~rc2-2) experimental; urgency=medium
* missing: define several syscall numbers for MIPS arch (Closes:
#974619)
systemd (247~rc2-1) experimental; urgency=medium
[ Michael Biebl ]
* New upstream version 247~rc2
- tmpfiles: Handle filesystems without ACL support in more cases
(Closes: #972135)
* Rebase patches
* Explicitly disable oomd
* Use -Dmode=release as we want a release, not developer, build
* Update symbols file for libudev1 and libsystemd0
[ Luca Boccassi ]
* systemd-container: install systemd-dissect binary.
Required for TEST-50-DISSECT since:
https://github.com/systemd/systemd/pull/16046
* d/t/control: install squashfs-tools for upstream test.
Required by TEST-50-DISSECT since upstream PR:
https://github.com/systemd/systemd/pull/16046
[ Dan Streetman ]
* d/control: update meson minimum version
https://github.com/systemd/systemd/pull/13842#issuecomment-601105975
* d/t/upstream: convert 'blacklist' term to 'deny-list'
Support transition for upstream-ci from
https://github.com/systemd/systemd/pull/16262
-- Balint Reczey <rbal...@ubuntu.com> Wed, 16 Dec 2020 10:27:06 +0100
** Changed in: systemd (Ubuntu Hirsute)
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/1905044
Title:
systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Bionic:
In Progress
Status in systemd source package in Focal:
In Progress
Status in systemd source package in Groovy:
In Progress
Status in systemd source package in Hirsute:
Fix Released
Bug description:
[impact]
autopkgtest failure when running with 5.8 kernel, if systemd is built
with earlier kernel (e.g. 5.4)
[test case]
see autopkgtest results, e.g. links in original description below
[regression potential]
as this only fixes a test case, any regression would likely result in
an incorrectly passing, or incorrectly failing, test.
[scope]
this is needed for b/f/g/h.
this bug was introduced by upstream commit 23cc81e7c22 which first
added testing for 'invalid' cap numbers, but incorrectly using
capability_list_length() instead of cap_last_cap(). That commit was
first included in v236, so this bug does not exist before Bionic.
this is fixed upstream by commit
ebc815cd1c647faa934a446ceea91ff4bc9dffa4, which was first included in
v247, so this is needed for h and earlier.
Also note that even though the 5.8 kernel is not planned to be
released for Bionic, this test also runs at build time, and since the
LP build farm builds inside chroots, if the build farm ever moved up
to Focal with a 5.8 kernel, the build of systemd for Bionic would
start failing (since it would still be building using the older kernel
headers, inside the chroot), so this does need to be fixed in Bionic
systemd as well.
[other info]
there is a non-test bug related to this in bug 1905245
[original description]
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20201117_174614_4ece6@/log.gz
arm64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20201117_221555_48b91@/log.gz
ppc64el:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/s/systemd/20201117_175806_e779f@/log.gz
s390x:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/s/systemd/20201117_153051_90e7e@/log.gz
The failing testcases are:
- root-unittests
Assertion 'capability_set_to_string_alloc(c, &t1) == 0' failed at
src/test/test-cap-list.c:60, funct
ion test_capability_set_one(). Aborting.
FAIL: test-cap-list (code: 134)
- upstream
TEST-24-UNIT-TESTS:
--- test-cap-list begin ---
Assertion 'capability_set_to_string_alloc(c, &t1) == 0' failed at
src/test/test-cap-list.c:60, funct
ion test_capability_set_one(). Aborting.
--- test-cap-list end ---
Both seem to be failing with the same assertion.
These tests are successful on Focal with linux 5.4, therefore they
would regress when upgrading the kernel from 5.4 to 5.8.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905044/+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
