Plymouth 0.9.5 release

[Daniel van Vugt]

Plymouth 0.9.5 release:

https://www.freedesktop.org/software/plymouth/releases/

[Balint Reczey (rbalint)]

The failing systemd-fscks autopkgtest is a test bug and should be fixed in systemd.

[Christian Ehrhardt  (paelzer)]

[17:48] <cpaelzer> rbalint: I was checking the systemd autopkgtests which were flaky retries and which were real issues
[17:48] <cpaelzer> rbalint: and it seems all were flaky (most resolved now and src:audit in the queue to be tested)
[17:49] <cpaelzer> rbalint: but one remained - plymouth - that seemed to be a genuine issue and I found https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1886886/comments/2
[17:49] <ubottu> Launchpad bug 1886886 in plymouth (Ubuntu) "Plymouth 0.9.5 release" [Wishlist,Fix committed]
[17:49] <cpaelzer> I wanted to ask what became of this and if you could update the bug if something was e.g. added to systemd/245.7-1ubuntu1 for it
[19:35] <rbalint> cpaelzer, seb128 i plan adding a fix to next systemd upload, will update the bug, too

Thanks for the FYI - adding here a systemd task and marking it update-excuse

[Christian Ehrhardt  (paelzer)]

FYI - the original bug would be tackled once https://launchpad.net/ubuntu/+source/plymouth/0.9.5-0ubuntu2 migrates

[Balint Reczey (rbalint)]

I'm testing the fix in Bileto and will upload it if the tests found no regression:

https://bileto.ubuntu.com/#/ticket/3801

[Launchpad Janitor (janitor)]

This bug was fixed in the package plymouth - 0.9.5-0ubuntu2

---------------
plymouth (0.9.5-0ubuntu2) groovy; urgency=medium

  * Clear twostep footer, at the end of fsck, and clear lingering Ctrl+C
    message LP: #1880250

plymouth (0.9.5-0ubuntu1) groovy; urgency=medium

  * New upstream version (lp: #1886886)
  * debian/control:
    - remove the intltool Build-Depends, the new version uses gettext
  * debian/patches/git-drm-improve.patch,
    debian/patches/gitlab-center-messages.patchs:
    - removed, the changes are in the new version
  * debian/libplymouth5.symbols:
    - refreshed for the new version
  * debian/patches/gitlab_correct_keynames.patch:
    - use the correct title and subtitle key names

 -- Dimitri John Ledkov <email address hidden> Wed, 12 Aug 2020 22:03:42 +0100

[Launchpad Janitor (janitor)]

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
    implementation...