Control: severity -1 normal On Sat, 08 Jun 2019 at 22:05:42 +0200, Guilhem Moulin wrote: > Our (cryptsetup maintaining team) plan is to rename ‘cryptsetup-run’ to > ‘cryptsetup’ once Buster is released, hence this bug should be RC at > this point: with `apt-install cryptsetup` the initramfs integration > won't be installed anymore.
Since 2:2.1.0-6 we reclaimed the name ‘cryptsetup’:
Package: cryptsetup
Recommends: cryptsetup-initramfs, cryptsetup-run
Description: disk encryption support - startup scripts
Package: cryptsetup-initramfs
Depends: cryptsetup
Description: disk encryption support - initramfs integration
Package: cryptsetup-run
Depends: cryptsetup
Description: transitional dummy package for cryptsetup
Thanks to the Recommends: d-i will automatically pull the initramfs
integration, at least on systems where APT::Install-Recommends hasn't
been turned off by preseeding. (The Recommends: cryptsetup-run is there
to improve the upgrade path, cf. #932625.) I'm therefore only raising
the severity to ‘normal’.
> The real fix would be to have a detection logic triggering `apt-install
> cryptsetup` whenever there are crypt targets in the dm table, and
> `apt-install cryptsetup-initramfs` if any volume needs to be unlocked at
> initramfs stage, i.e., holding /, /usr, and/or the resume device(s).
--
Guilhem.
signature.asc
Description: PGP signature
