The proposal to merge ~dbungert/curtin:cryptoswap-dmc-type into curtin:master has been updated.
Commit message changed to: dm_crypt: create and use cryptoswap as PLAIN Previously, cryptoswap was acting strangely, in that at install time it was considered to be a LUKS2 device and durign actual system use it would be considered a PLAIN device, in the cryptsetup(8) meanings of these terms. This caused problems when attempting to reference the device, as we would do get_volume_spec(), the returned /dev/disk/by-id/dm-uuid-... value would be wrong - it would change from dm-uuid-CRYPT-LUKS2-... to dm-uuid-CRYPT-PLAIN-... As the real runtime behavior is to be a PLAIN device for cryptoswap, stop creating it as a LUKS2 device and just use it as a PLAIN device, which doesn't involve a "create" step at all, you just open it as PLAIN directly. For more details, see: https://code.launchpad.net/~dbungert/curtin/+git/curtin/+merge/460874 -- Your team curtin developers is subscribed to branch curtin:master. -- Mailing list: https://launchpad.net/~curtin-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~curtin-dev More help : https://help.launchpad.net/ListHelp
