This bug was fixed in the package systemd - 246.2-1ubuntu1
---
systemd (246.2-1ubuntu1) groovy; urgency=medium
* Merge from Debian unstable
* Refresh patches
* test: accept that char device 0/0 can now be created witout privileges.
This fixes tests with Linux 5.8 and later (LP: #1891527)
Files:
- debian/patches/debian/Add-env-variable-for-machine-ID-path.patch
-
debian/patches/test-accept-that-char-device-0-0-can-now-be-created-witou.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=57909a0fa4999ba9ff918cfe6bb3fa53c230dd36
* debian/tests/systemd-fsckd: Fail plymouth-start with overriding ExecStart=
The 'process-killer' stopped working with plymouth 0.9.5 (LP: #1886886)
File: debian/tests/systemd-fsckd
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=efcc25b6011f23b9f90841f4ca0ee29ee674157f
* cherry-pick from stable: network: only process non-error message
File: debian/patches/network-only-process-non-error-message.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=dc97e3f5330ae64909ef640ad1ac401374f18c16
* network: wait for previous address removal before configuring static
addresses.
Fixes systemd-networkd to establish connection after resume from suspend
Files:
-
debian/patches/network-wait-for-previous-address-removal-before-configur.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=31390403bc000892ada9cb0cbedb198dd83fe7a2
* network: do not fail if UseMTU=yes on DHCP lease lost
File:
debian/patches/network-do-not-fail-if-UseMTU-yes-on-DHCP-lease-lost.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=21c23966e8dc5fd0858664a5b89d6a9460c41f61
* debian/systemd.postinst: Restart systemd-networkd.socket on incompatible
change
(Closes: #968589) (LP: #1891716)
File: debian/systemd.postinst
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=e144a644488c6ff52c2bb7cee71f50aa95c4efd8
* debian/tests/control: Mark systemd-fsckd test as flaky.
It is flaky on Ubuntu CI infrastructure (LP: #1892358)
File: debian/tests/control
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8c55289624c6f44beb2c5bbae78aabc074d36b1a
systemd (246.2-1) unstable; urgency=medium
* New upstream version 246.2
* Remove resolvconf.conf drop-in, resolved integration moved to resolvconf
package
* Rebase patches
* Add versioned Breaks against resolvconf (<< 1.83~) to systemd.
The PathExists= directive was changed in v246 to match the documented
behaviour but now causes resolvconf-pull-resolved.service to be
continuously triggered by resolvconf-pull-resolved.path.
This requires a fix in the resolvconf package, see #968015.
(Closes: #967906)
* Keep journal files compatible with older versions.
Disable the KEYED-HASH journal feature by default and keep LZ4 (instead
of ZSTD) as default compression for new journal files. Otherwise journal
files are incompatible and can't be read by older journalctl
implementations.
This patch can be dropped in bullseye+1, as journalctl from bullseye
will then be able to read journal files with those features.
(Closes: #968055)
systemd (246.1-1) unstable; urgency=medium
* New upstream version 246.1
* Rebase patches
-- Balint Reczey Thu, 20 Aug 2020 23:37:48 +0200
** Changed in: systemd (Ubuntu)
Status: In Progress => 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/1891527
Title:
systemd unit tests need updates for Linux 5.8 and later
To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1891527/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
