On 22/07/2019 13:09, Guilhem Moulin wrote:
Ooops. We don't want ‘cryptsetup’ to hard-depend on ‘cryptsetup-initramfs’,
as that would make the 2:2.0.3-1 package split moot. I just uploaded
2:2.1.0-7 where ‘cryptsetup’ *Recommends* ‘cryptsetup-initramfs’, which
is enough to convince APT not to au
On Mon, 22 Jul 2019 at 11:37:24 +1200, Ben Caradoc-Davies wrote:
> 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.
Ooops. We don't want ‘cryptsetup’ to hard-depend on ‘cryptsetup-initramfs’
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)
Package: cryptsetup
Version: 2:2.1.0-6
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
upgrading cryptsetup from 2:2.1.0-5 to 2:2.1.0-6 causes autoremoval of
cryptsetup-initramfs and consequent failure to boot from LUKS/LVM.
Workaround is to boot previous kernel (with
4 matches
Mail list logo
