Package: cryptsetup Version: 2:1.7.5-1 Severity: normal Dear Maintainer,
I spent a couple of hours today investigating why my system with an encrypted root suddenly stopped booting. The symptom was that the initrd could not find the root device. The cause turned out to be that the cryptsetup's hooks were not included in the initramfs. The cause of that turned out to be a missing lvm2 package, which some chain of events led to removal of from my system. This package is, obviously, rather relevant and it would be nice if the dependency system enforced its presence. Thanks! -- Package-specific info: -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (400, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages cryptsetup depends on: ii cryptsetup-bin 2:1.7.5-1 ii debconf [debconf-2.0] 1.5.65 ii dmsetup 2:1.02.145-4.1 ii libc6 2.25-2 Versions of packages cryptsetup recommends: ii busybox 1:1.27.2-2 ii console-setup 1.172 ii initramfs-tools [linux-initramfs-tool] 0.130 ii kbd 2.0.4-2 Versions of packages cryptsetup suggests: ii dosfstools 4.1-1 ii keyutils 1.5.9-9.2 ii liblocale-gettext-perl 1.07-3+b3 -- debconf information: cryptsetup/prerm_active_mappings: true