[pkg-cryptsetup-devel] Bug#903246: cryptdisks_start now says device UUID "does not exist"

[Ian Tester]

Package: cryptsetup-run
Version: 2:2.0.3-5
Severity: grave
File: /sbin/cryptdisks_start
Justification: renders package unusable

Dear Maintainer,
	I've been using cryptdisk for years. It appears the recent changes to
crypttab parsing has broken UUID discovery (at least, for me).

~# cryptdisks_start encrypted
[FAIL] Starting crypto disk...encrypted (skipped, device UUID=xxx does not exist)...failed.

in /etc/crypttab:
encrypted	UUID=xxx	none	luks,noauto

But blkid works:
~# blkid -l -t UUID=xxx
/dev/mapper/vg_cubie-encrypted_crypt: UUID="xxx" TYPE="crypto_LUKS"

(name changed and UUID removed for privacy)

-- Package-specific info:

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: armhf (armv7l)

Kernel: Linux 4.17.4+ (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages cryptsetup-run depends on:
ii  cryptsetup-bin         2:2.0.3-5
ii  debconf [debconf-2.0]  1.5.67
ii  dmsetup                2:1.02.145-4.1
ii  libc6                  2.27-3

cryptsetup-run recommends no packages.

Versions of packages cryptsetup-run suggests:
ii  dosfstools              4.1-2
ii  keyutils                1.5.9-9.2
ii  liblocale-gettext-perl  1.07-3+b3

-- debconf information:
* cryptsetup/prerm_active_mappings: false