Package: cryptsetup-initramfs Version: 2:2.3.4-1~bpo10+1 Severity: grave Justification: renders package unusable
apt upgrade installed cryptsetup-initramfs 2:2.3.4-2~bpo10+1 over 2:2.3.4-1~bpo10+1 despite the fact that initramfs-tools stayed at 0.133+deb10u1 (no newer version available in buster or buster-backports). apt-cache cryptsetup-initramfs (for version 2:2.3.4-2~bpo10+1) says it depends on "initramfs-tools (>= 0.137) | linux-initramfs-tool", while the changelog says it "now requires initramfs- tools 0.137 or later and no longer copies libgcc_s.so.1 to the initrd since recent initramfs-tools take care of it". After the upgrade, booting with a newly created initrd doesn't allow to unlock the encrypted root any more ("wrong password or unknown parameter"). Fortunately, the cryptsetup-initramfs' install script re-creates only the current kernel's initrd, so that booting from an older kernel allowed me to get into the system and to revert cryptsetup and cryptsetup-initramfs to 2:2.3.4-1~bpo10+1 which solved the problem. -- Package-specific info: -- System Information: Debian Release: 10.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.8-surface (SMP w/4 CPU cores) Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_USER, TAINT_CRAP, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_BE.UTF-8, LC_CTYPE=de_BE.UTF-8 (charmap=UTF-8), LANGUAGE=de_BE:de (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cryptsetup-initramfs depends on: ii busybox 1:1.30.1-4 ii cryptsetup 2:2.3.4-1~bpo10+1 ii debconf [debconf-2.0] 1.5.71 ii initramfs-tools [linux-initramfs-tool] 0.133+deb10u1 Versions of packages cryptsetup-initramfs recommends: ii console-setup 1.193~deb10u1 ii kbd 2.0.4-4 cryptsetup-initramfs suggests no packages. -- debconf information: cryptsetup-initramfs/prerm_active_mappings: true