cryptsetup-run is transitional package, but removing it also removes cryptsetup-initramfs

[Andreas Hasenack]

cryptsetup-run 2:2.2.2-3ubuntu1 claims to be a transitional dummy package, but removing it will also remove cryptsetup-initramfs, which doesn't looks like a transitional package:

$ dpkg -l|grep -i transitional
ii cryptsetup-run 2:2.2.2-3ubuntu1 all transitional dummy package for cryptsetup

$ sudo apt remove cryptsetup-run
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
  cryptsetup-initramfs cryptsetup-run
0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
After this operation, 234 kB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: cryptsetup-run 2:2.2.2-3ubuntu1
ProcVersionSignature: User Name 5.4.0-15.18-generic 5.4.21
Uname: Linux 5.4.0-15-generic x86_64
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
Date: Sun Feb 23 11:36:26 2020
PackageArchitecture: all
ProcEnviron:
 TERM=screen-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: cryptsetup
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Adam Collard (adam-collard)]

See also https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1862215

[Adam Collard (adam-collard)]

This makes it far too easy to make your system unbootable.

Snippet from /var/log/apt/history.log: https://paste.ubuntu.com/p/kvgN6zhyQm/

This shows why I hit bug 1862215, I had purge'd all dummy transitional packages in the belief that they were ... dummy, and transitional. It turns out for crypetsetup-run that's not true since removing it means initramfs lacks dm-crypt.ko and rendering my FDE'd HDD unusable with kernels installed after it.

[Neil McPhail (njmcphail)]

Same issue here, as a result of running `apt autoremove` on the 22nd February.

[Steve Langasek (vorlon)]

> Same issue here, as a result of running `apt autoremove` on the 22nd February.

That doesn't sound like the same issue. The issue Adam encountered was that he manually removed cryptsetup-run because it identified itself as a transitional dummy package, and didn't notice that this also removed cryptsetup-initramfs from his system.

If autoremoval caused cryptsetup-initramfs to be removed from your system, that's a different problem.

[Neil McPhail (njmcphail)]

Ok, I'll open a new bug and post my apt logs. No idea what package to raise the bug against, though.

[Neil McPhail (njmcphail)]

I've update https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1864293 with details.

[Launchpad Janitor (janitor)]

This bug was fixed in the package cryptsetup - 2:2.2.2-3ubuntu2

---------------
cryptsetup (2:2.2.2-3ubuntu2) focal; urgency=medium

  * Depend on cryptsetup from cryptsetup-initramfs instead of the dummy
    cryptsetup-run package. LP: #1864360.

 -- Steve Langasek <email address hidden> Thu, 27 Feb 2020 00:16:14 -0600