this package is supposed to contain cryptsetup-reencrypt

[Eli]

This package is supposed to contain cryptsetup-reencrypt.
Entering that cryptsetup-reencrypt on the command line prompts installing cryptsetup-bin even when it is already installed.
```
Command 'cryptsetup-reencrypt' not found, but can be installed with:
sudo apt install cryptsetup-bin
```

`apt satisfy cryptsetup-bin` does nothing
Reinstalling does nothing.

The only executable containing "cryptsetup" in /usr/sbin/ is cryptsetup, no other similar ones.
Seems to be either a package issue, or maybe the package adds a command to cryptsetup itself, but if so the functionality appears to be reduced, because the only reencrypt option for cryptsetup is "--force-offline-reencrypt" and that is not the functionality which is missing.

lsb_release -rd:
Description: Ubuntu 22.10
Release: 22.10

Version info:
cryptsetup:
  Installed: 2:2.5.0-2ubuntu1
  Candidate: 2:2.5.0-2ubuntu1
  Version table:
 *** 2:2.5.0-2ubuntu1 500
        500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
        100 /var/lib/dpkg/status

cryptsetup-bin:
  Installed: 2:2.5.0-2ubuntu1
  Candidate: 2:2.5.0-2ubuntu1
  Version table:
 *** 2:2.5.0-2ubuntu1 500
        500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
        100 /var/lib/dpkg/status

(this one is probably unnecessary)
cryptsetup-initramfs:
  Installed: 2:2.5.0-2ubuntu1
  Candidate: 2:2.5.0-2ubuntu1
  Version table:
 *** 2:2.5.0-2ubuntu1 500
        500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
        500 http://us.archive.ubuntu.com/ubuntu kinetic/main i386 Packages
        100 /var/lib/dpkg/status

(I'm hitting some bug when I enter either cryptsetup or cryptsetup-bin in the package search on the bug report page: "Sorry, something went wrong with your search. We've recorded what happened, and we'll fix it as soon as possible. (Error ID: OOPS-f3a60b1127f27e9b6d2ce6196f55ff09)")

Link to an askubuntu question of a user also encountering this, 3 months ago:
https://askubuntu.com/questions/1445879/missing-cryptsetup-reencrypt-command-in-packages

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: cryptsetup-bin 2:2.5.0-2ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17
Uname: Linux 5.19.0-38-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Fri Mar 31 14:31:37 2023
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: cryptsetup
UpgradeStatus: Upgraded to kinetic on 2022-12-19 (102 days ago)

[Eli (biblicabeebli)]

For some reason the package search here does not contain cryptsetup-bin despite the apt-cache policy command clearly stating it is from kinetic/main. I have no expertise in this so its totally opaque to me why it would be missing.

[Steve Langasek (vorlon)]

Confirmed. It's there in jammy, but somehow absent in kinetic and later *despite* the fact the manpage is still shipped.

[Steve Langasek (vorlon)]

From the changelog:

  * d/control: Remove cryptsetup-reencrypt from cryptsetup-bin package
    description since the utility was removed upstream in v2.5.0-rc1.

So the removal of the binary is deliberate, the bugs are that we're still shipping a manpage and that the command-not-found index still points to it.

[Eli (biblicabeebli)]

For anyone that finds this issue in future searching:
The underlying reason this happened is because the cryptsetup core package WAS updated to include the cryptsetup-reencrypt functionality.

From the changelog:
  * New upstream release candidate 2.5.0. Highlights include:
    + Remove cryptsetup-reencrypt(8) executable, use `cryptsetup reencrypt`
      instead (for both LUKS1 and LUKS2).

 - https://launchpad.net/debian/+source/cryptsetup/+changelog

[Brian Murray (brian-murray)]

The command-not-found indexing service was broken at the time Kinetic was released and had been for some time. Subsequently, the command-not-found indexes for packages in the release pocket for Kinetic may be out of date. This is somewhat documented in bug 1998001.