Re: Bug#1108823: trixie: mention issue with cryptsetup support having been moved to systemd-cryptsetup

Paul Gevers <[email protected]> Sun, 6 Jul 2025 10:31:14 +0200

Newsgroups	gmane.linux.debian.devel.documentation
Message-ID	<[email protected]>

Hi,

On 05-07-2025 21:33, Justin B Rye wrote:
> This issue is a big
> enough risk that it seems to me we probably do want to flag it up, but
> it might even be worth taking the opportunity to hint that this kind
> of consequence is why it's not recommended.

Fully agree.

>   .. _systemd-cryptsetup-support-moved-to-separate-package:
> 
> (Shouldn't there be a visible heading here?)

Indeed.

>   Support in `systemd` for opening and mounting encrypted storage devices
>   at boot has been moved into a separate package, `systemd-cryptsetup`,
>   which is recommended by the `systemd` package in trixie.
> 
>   Users of encrypted filesystems should double-check that this package is
>   installed as intended before rebooting. This is a case where overriding
>   standard dependency resolution in `apt` can result in an unbootable
>   system.

I know what you want to say in the last sentence because I have the 
context, but I don't expect most readers to grasp what you mean here. 
Probably worth being explicit about that we're talking about 
"--no-install-recommends" here:

   This is a case where overriding
   standard dependency resolution in `apt` (e.g. by using
   `--no-install-recommends`) can result in an unbootable
   system.

Paul

OpenPGP_signature.asc (application/pgp-signature, 585 B)