On Thu, 2019-07-25 at 01:02 -0300, Guilhem Moulin wrote: > 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’. APT::Install-Recommends is only enabled after the base-installer phase. of installation. I don't know what stage cryptsetup is installed at, but I suggest it's worth checking that this assumption is correct. Ben. -- Ben Hutchings compatible: Gracefully accepts erroneous data from any source
Attachment:
signature.asc
Description: This is a digitally signed message part