[Bug 1897620] Re: ABI breakage: paths changed for sysusers.d/sysctl.d/binfmt/modules-load.d

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 246.6-2ubuntu1

---------------
systemd (246.6-2ubuntu1) hirsute; urgency=medium

  [ Dan Streetman ]
  * d/t/boot-smoke: update test to avoid false negatives
    File: debian/tests/boot-smoke
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=205c30ca53b0e421db28bb56afaf5f88650ce592
  * d/t/boot-and-services: remove unneeded test lines
    File: debian/tests/boot-and-services
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=71853082af4e668996db574915c5a156f9897fd3
  * d/t/systemd-fsckd: rewrite test to try to fix false negatives (LP: #1892358)
    Files:
    - debian/tests/control
    - debian/tests/systemd-fsckd
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=6ae6be039ec582410769d2d6d131e12bdcd19a68

  [ Balint Reczey ]
  * debian/gbp.conf: Update debian-branch to ubuntu-hirsute
    File: debian/gbp.conf
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=e0b78512dbb5141458468ba5e9c2a4e966ada088
  * Merge from Debian unstable
    - Move sysusers.d/sysctl.d/binfmt.d/modules-load.d back to /usr
    (LP: #1897620)
  * debian/tests/systemd-fsckd: Plymouth-start stays active in 20.10 and later
    (LP: #1892358)
    File: debian/tests/systemd-fsckd
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c46eda821e97df5595a4cdc5f5c41a9b49a51745

systemd (246.6-2) unstable; urgency=medium

  * XDG autostart improvements
    - Add support for Path= in XDG Desktop File
    - Ignore more common XDG Desktop Entry fields
    - Lower most info messages to debug level (Closes: #968116)
  * Re-enable seccomp support on riscv64.
    This should be safe now, as the code has fallbacks for systems with
    older libseccomp versions.
  * Move sysusers.d/sysctl.d/binfmt.d/modules-load.d back to /usr.
    In Debian, late mounting of /usr is no longer supported, so it is safe
    to install those files in /usr.
    We want those facilities in /usr, not /, as this will make an eventual
    switch to a merged-usr setup easier. (Closes: #971282)
  * units: update serial-getty at .service to support 57600 baud rate
    (Closes: #969144)
  * bootspec: don't fail with EIO if searching for ESP and finding one without
    an enveloping partition table
    (Closes: #970534)

 -- Balint Reczey <rbalint at ubuntu.com>  Thu, 29 Oct 2020 18:38:15 +0100

** Changed in: systemd (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1897620

Title:
  ABI breakage: paths changed for sysusers.d/sysctl.d/binfmt/modules-
  load.d

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd package in Debian:
  New

Bug description:
  Imported from Debian bug http://bugs.debian.org/971282:

  Package: systemd
  Version: 246.6-1
  Severity: important

  Upstream changed the paths in systemd.pc from prefix to rootprefix in
  v246 for sysusers_dir, sysctl_dir, binfmt_dir and modules-load_dir:
  https://github.com/systemd/systemd/commit/4a56315a990b802860170ecd1bbd3eb68e14a38b

  This breaks packages which use pkg-config to determine those paths and
  where .install files reference /usr/. An example is mandos.

  I think we should revert this change. I don't see a compelling reason to
  move those files from /usr to /lib given that we require /usr to be
  pre-mounted by initramfs, if it's separate.
  Moving files from /usr to /lib files kinda backwards nowadays.

  I intend to apply a patch like the attached one in Debian.
  That said, I hope I can convince Lennart to revert this change upstream
  as well.

  Thoughts, Comments?

  Michael

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1897620/+subscriptions