[pkg-cryptsetup-devel] Bug#931749: cryptsetup: "no longer required" on encrypted system!

Conrad J.C. Hughes (for Debian package stuff) debbugs at xrad.org
Wed Jul 10 00:01:00 BST 2019


Package: cryptsetup
Version: 2:2.1.0-5
Severity: normal

Dear Maintainer,

So this is probably a buster upgrade issue, but not sure where to report it..

After upgrading to buster, deborphan --guess-dummy (seemingly correctly)
identified cryptsetup as a transitional dummy package, suitable for removal.
However after removing cryptsetup, apt now tells me all the time that
cryptsetup-bin, cryptsetup-initramfs and cryptsetup-run "were automatically
installed and are no longer required".  But my system's LUKS1-on-LVM-RAID-1..
Running "apt autoremove" at this point would surely cause chaos?

Conrad



-- Package-specific info:

-- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cryptsetup depends on:
ii  cryptsetup-initramfs  2:2.1.0-5
ii  cryptsetup-run        2:2.1.0-5

cryptsetup recommends no packages.

cryptsetup suggests no packages.

-- debconf information:
  cryptsetup/prerm_active_mappings: true



More information about the pkg-cryptsetup-devel mailing list