[ubuntu/kinetic-proposed] systemd 251.4-1ubuntu3 (Accepted)

[Lukas Märdian]

systemd (251.4-1ubuntu3) kinetic; urgency=medium

  * Fix version of backported sd_hwdb_new_from_path symbol.
    The systemd-hwdb binary calling into this library is linked statically,
    but we still want to keep a future proof ABI, just in case.
    Files:
    - debian/libsystemd0.symbols
    - debian/patches/sd-hwdb-add-sd_hwdb_new_from_path.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=dee01ca169cd41e514658f8a631847c9e852e842

systemd (251.4-1ubuntu2) kinetic; urgency=medium

  [ Lukas Märdian ]
  * Provide upgrade path (Replaces:) for Jammy's systemd-repart (LP: 1897932)
    File: debian/control
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=2281670aa8007179170d5cc485bb94e3bbc3b63c

  [ Luca Boccassi ]
  * resolved: switch from .links to postinst/rm (LP: #1988300)
    dpkg refuses to install the symlink in chroot/container environments
    where /etc/resolv.conf is bind mounted:
    | Unpacking systemd-resolved (251.4-1) ...
    | dpkg: error processing archive /var/cache/apt/archives/systemd-resolved_251.4-1_amd64.deb (--unpack):
    |  unable to make backup link of './etc/resolv.conf' before installing new version: Invalid cross-device link
    So unfortunately manual handling via maintainerscripts is necessary.
    Use maintainer scripts to avoid failing the installation, and provide
    feedback to the user if the symlink cannot be successfully installed.
    Also on removal, either copy /run/systemd/resolve/resolv.conf or
    create an empty /etc/resolv.conf.
    Amend to use the correct Ubuntu version string (251.4-1ubuntu2).
    Author: Luca Boccassi
    Files:
    - debian/systemd-resolved.links
    - debian/systemd-resolved.postinst
    - debian/systemd-resolved.postrm
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=faf479a6158aac977c2cdb32fd1eaecc0862a7ef
  * resolv.conf: take backup as a fallback
    piuparts doesn't like seeing an empty resolv.conf after removing
    the package, so take a backup and use it in case resolved/resolv.conf
    is not available
    Author: Luca Boccassi
    Files:
    - debian/systemd-resolved.postinst
    - debian/systemd-resolved.postrm
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c2b15f43eb7779953a3dda7f461edbb1bf038701

  [ Nick Rosbrook ]
  * debian/systemd-resolved.{postinst,postrm}: do not use DPKG_ROOT.
    We cherry-picked "resolved: switch from .links to postinst/rm" and
    "resolv.conf: take backup as a fallback" from debian/251.4-3 to fix a
    systemd-resolved installation issue, but we are not taking the DPKG_ROOT
    changes at the moment due to feature freeze.
    Files:
    - debian/systemd-resolved.postinst
    - debian/systemd-resolved.postrm
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=5664be09ce9813cb2dd2bd71c5d325036655c312

Date: Thu, 01 Sep 2022 12:42:10 +0200
Changed-By: Lukas Märdian <slyon at ubuntu.com>
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
https://launchpad.net/ubuntu/+source/systemd/251.4-1ubuntu3
-------------- next part --------------
Format: 1.8
Date: Thu, 01 Sep 2022 12:42:10 +0200
Source: systemd
Built-For-Profiles: noudeb
Architecture: source
Version: 251.4-1ubuntu3
Distribution: kinetic
Urgency: medium
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
Changed-By: Lukas Märdian <slyon at ubuntu.com>
Launchpad-Bugs-Fixed: 1988300
Changes:
 systemd (251.4-1ubuntu3) kinetic; urgency=medium
 .
   * Fix version of backported sd_hwdb_new_from_path symbol.
     The systemd-hwdb binary calling into this library is linked statically,
     but we still want to keep a future proof ABI, just in case.
     Files:
     - debian/libsystemd0.symbols
     - debian/patches/sd-hwdb-add-sd_hwdb_new_from_path.patch
     https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=dee01ca169cd41e514658f8a631847c9e852e842
 .
 systemd (251.4-1ubuntu2) kinetic; urgency=medium
 .
   [ Lukas Märdian ]
   * Provide upgrade path (Replaces:) for Jammy's systemd-repart (LP: 1897932)
     File: debian/control
     https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=2281670aa8007179170d5cc485bb94e3bbc3b63c
 .
   [ Luca Boccassi ]
   * resolved: switch from .links to postinst/rm (LP: #1988300)
     dpkg refuses to install the symlink in chroot/container environments
     where /etc/resolv.conf is bind mounted:
     | Unpacking systemd-resolved (251.4-1) ...
     | dpkg: error processing archive /var/cache/apt/archives/systemd-resolved_251.4-1_amd64.deb (--unpack):
     |  unable to make backup link of './etc/resolv.conf' before installing new version: Invalid cross-device link
     So unfortunately manual handling via maintainerscripts is necessary.
     Use maintainer scripts to avoid failing the installation, and provide
     feedback to the user if the symlink cannot be successfully installed.
     Also on removal, either copy /run/systemd/resolve/resolv.conf or
     create an empty /etc/resolv.conf.
     Amend to use the correct Ubuntu version string (251.4-1ubuntu2).
     Author: Luca Boccassi
     Files:
     - debian/systemd-resolved.links
     - debian/systemd-resolved.postinst
     - debian/systemd-resolved.postrm
     https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=faf479a6158aac977c2cdb32fd1eaecc0862a7ef
   * resolv.conf: take backup as a fallback
     piuparts doesn't like seeing an empty resolv.conf after removing
     the package, so take a backup and use it in case resolved/resolv.conf
     is not available
     Author: Luca Boccassi
     Files:
     - debian/systemd-resolved.postinst
     - debian/systemd-resolved.postrm
     https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c2b15f43eb7779953a3dda7f461edbb1bf038701
 .
   [ Nick Rosbrook ]
   * debian/systemd-resolved.{postinst,postrm}: do not use DPKG_ROOT.
     We cherry-picked "resolved: switch from .links to postinst/rm" and
     "resolv.conf: take backup as a fallback" from debian/251.4-3 to fix a
     systemd-resolved installation issue, but we are not taking the DPKG_ROOT
     changes at the moment due to feature freeze.
     Files:
     - debian/systemd-resolved.postinst
     - debian/systemd-resolved.postrm
     https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=5664be09ce9813cb2dd2bd71c5d325036655c312
Checksums-Sha1:
 cd6f3926339d0a18ff631292e971014f04e5b0d1 6439 systemd_251.4-1ubuntu3.dsc
 52f637f0696a617a88895aa35822190a4ba12611 225056 systemd_251.4-1ubuntu3.debian.tar.xz
 e264b26947775c475f199da1afe17e2e7fc5f023 12898 systemd_251.4-1ubuntu3_source.buildinfo
Checksums-Sha256:
 855b3a25788311ca5d3020cf7d0c42afaae59b8c4d30b6a1e554bae9dcd74b73 6439 systemd_251.4-1ubuntu3.dsc
 5e8818f502b0173caac525dc433b87d688363db981affeedcd0bc1583aa5d7e6 225056 systemd_251.4-1ubuntu3.debian.tar.xz
 10adc2bebcd266c69970b440c6e3b487ccfcd55f186bd76ef835bc071e66a022 12898 systemd_251.4-1ubuntu3_source.buildinfo
Files:
 51433c3d1d5a7c11f24b919f3615a8de 6439 admin optional systemd_251.4-1ubuntu3.dsc
 01b3d0a85793f7cdf9c8dddc4a37d4a9 225056 admin optional systemd_251.4-1ubuntu3.debian.tar.xz
 4650d5dd0fe6fd06662a2129cca1ad85 12898 admin optional systemd_251.4-1ubuntu3_source.buildinfo
Original-Maintainer: Debian systemd Maintainers <pkg-systemd-maintainers at lists.alioth.debian.org>