* 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)
This bug was fixed in the package systemd - 246.2-1ubuntu1
---------------
systemd (246.2-1ubuntu1) groovy; urgency=medium
* Merge from Debian unstable patches/ debian/ Add-env- variable- for-machine- ID-path. patch patches/ test-accept- that-char- device- 0-0-can- now-be- created- witou.patch /git.launchpad. net/~ubuntu- core-dev/ ubuntu/ +source/ systemd/ commit/ ?id=57909a0fa49 99ba9ff918cfe6b b3fa53c230dd36 tests/systemd- fsckd: Fail plymouth-start with overriding ExecStart= tests/systemd- fsckd /git.launchpad. net/~ubuntu- core-dev/ ubuntu/ +source/ systemd/ commit/ ?id=efcc25b6011 f23b9f90841f4ca 0ee29ee674157f patches/ network- only-process- non-error- message. patch /git.launchpad. net/~ubuntu- core-dev/ ubuntu/ +source/ systemd/ commit/ ?id=dc97e3f5330 ae64909ef640ad1 ac401374f18c16 patches/ network- wait-for- previous- address- removal- before- configur. patch /git.launchpad. net/~ubuntu- core-dev/ ubuntu/ +source/ systemd/ commit/ ?id=31390403bc0 00892ada9cb0cbe db198dd83fe7a2 patches/ network- do-not- fail-if- UseMTU- yes-on- DHCP-lease- lost.patch /git.launchpad. net/~ubuntu- core-dev/ ubuntu/ +source/ systemd/ commit/ ?id=21c23966e8d c5fd0858664a5b8 9d6a9460c41f61 systemd. postinst: Restart systemd- networkd. socket on incompatible change systemd. postinst /git.launchpad. net/~ubuntu- core-dev/ ubuntu/ +source/ systemd/ commit/ ?id=e144a644488 c6ff52c2bb7cee7 1f50aa95c4efd8 tests/control: Mark systemd-fsckd test as flaky. tests/control /git.launchpad. net/~ubuntu- core-dev/ ubuntu/ +source/ systemd/ commit/ ?id=8c55289624c 6f44beb2c5bbae7 8aabc074d36b1a
* 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/
- debian/
https:/
* debian/
The 'process-killer' stopped working with plymouth 0.9.5 (LP: #1886886)
File: debian/
https:/
* cherry-pick from stable: network: only process non-error message
File: debian/
https:/
* network: wait for previous address removal before configuring static addresses.
Fixes systemd-networkd to establish connection after resume from suspend
Files:
- debian/
https:/
* network: do not fail if UseMTU=yes on DHCP lease lost
File: debian/
https:/
* debian/
(Closes: #968589) (LP: #1891716)
File: debian/
https:/
* debian/
It is flaky on Ubuntu CI infrastructure (LP: #1892358)
File: debian/
https:/
systemd (246.2-1) unstable; urgency=medium
* New upstream version 246.2 pull-resolved. service to be pull-resolved. path. ions.
* 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-
continuously triggered by resolvconf-
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
implementat
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 <email address hidden> Thu, 20 Aug 2020 23:37:48 +0200