Comment 5 for bug 2014228

Revision history for this message
Eli (biblicabeebli) wrote :

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