Hi, [src:cryptsetup co-maintainer here, but not involved in src:systemd]
>.. _systemd-cryptsetup-support-moved-to-separate-package: Thanks for the suggestion! Makes sense to add this in the release notes indeed. > The ``systemd`` package in Trixie recommends it, but on systems with > the installation of recommended packages diabled it will not be automatically > installed by the upgrade process, likely rendering the system unbootable. I think that statement is too strong, as the issue “only” affects systems with encrypted devices that are 1/ prerequisite for a unit file (for instance holding a file system to automount at boot time), and 2/ not unlocked at early boot stage (so not holding the root FS, /usr, or the resume device). So the “LVM-over-crypt” systems one gets out of d-i are unaffected. > If you have installation of recommended packages disabled, > and have any filesystem residing on an encrypted storage device > listed in ``/etc/fstab`` (or being mounted by a custom ``systemd`` unit file), > be sure to install the ``systemd-cryptsetup`` package > before rebooting the system. Suggestion: “If you have an encrypted device which is not holding the root FS, /usr, or a resume device, then be sure to …”. See also the systemd NEWS entry for version 256-2. -- Guilhem.
signature.asc
Description: PGP signature