[pkg-cryptsetup-devel] Bug#932643: cryptsetup upgrade causes cryptsetup-initramfs autoremoval and boot failure
Ben Caradoc-Davies
ben at transient.nz
Mon Jul 22 00:37:24 BST 2019
And I should mention the precise symptoms: at boot, there is no Plymouth
passphrase entry and the console displays error messages about not being
able to mount the volume group.
cryptsetup 2:2.1.0-5 had the following:
Depends: cryptsetup-initramfs (>= 2:2.0.3-1), cryptsetup-run (>= 2:2.0.3-1)
cryptsetup 2:2.1.0-6 has no dependency on cryptsetup-initramfs so the
latter will be autoremoved if only cryptsetup was marked manual by the
installer.
The affected sid system was installed with a testing installer in April
2017. I do not know what the current installer marks as manual for
LUKS/LVM installations but the affected system had only cryptsetup
marked as manual and was relying on its Depends: cryptsetup-initramfs to
boot.
Kind regards,
--
Ben Caradoc-Davies <ben at transient.nz>
Director
Transient Software Limited <https://transient.nz/>
New Zealand
More information about the pkg-cryptsetup-devel
mailing list