Your message dated Mon, 22 Jul 2019 01:19:27 +0000 with message-id <[email protected]> and subject line Bug#932625: fixed in cryptsetup 2:2.1.0-7 has caused the Debian Bug report #932625, regarding cryptsetup: removing transitional cryptsetup-run produces scary debconf question to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 932625: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932625 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: cryptsetup Version: 2:2.1.0-5 Severity: normal My root filesystem is a LVM volume on a dm-crypt/cryptsetup/LUKS encrypted partition. When I upgrade from cryptsetup 2:2.1.0-5 to 2:2.1.0-6, aptitude suggests removing the transitional cryptsetup-run package. However, when I do, I get this debconf question that suggests that I am doing something wrong, because cryptsetup-run in buster was not transitional (and cryptsetup was): Configuring cryptsetup-run This system has unlocked dm-crypt devices: [my dm-crypt device name] If these devices are managed with cryptsetup, you might be unable to lock the devices after the package removal, though other tools can be used for managing dm-crypt devices. Any system shutdown or reboot will lock the devices. Do not choose this option if you want to lock the dm-crypt devices before package removal. Continue with cryptsetup removal? <Yes> <No> My understanding is that it's fine for me to remove cryptsetup-run, because its functionality has been subsumed by the combination of cryptsetup and cryptsetup-initramfs? I suspect that swapping the transitional/non-transitional status of two pre-existing packages is only going to cause confusion on upgrade from buster to bullseye. It might be more robust to leave cryptsetup-run as the real package, drop the transitional cryptsetup, and choose one: either keep that situation indefinitely, or reinstate cryptsetup (with a transition from cryptsetup-run) in bullseye+1 or later. smcv
--- End Message ---
--- Begin Message ---Source: cryptsetup Source-Version: 2:2.1.0-7 We believe that the bug you reported is fixed in the latest version of cryptsetup, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [email protected], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Guilhem Moulin <[email protected]> (supplier of updated cryptsetup package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Sun, 21 Jul 2019 21:21:10 -0300 Source: cryptsetup Architecture: source Version: 2:2.1.0-7 Distribution: unstable Urgency: low Maintainer: Debian Cryptsetup Team <[email protected]> Changed-By: Guilhem Moulin <[email protected]> Closes: 932625 932643 Changes: cryptsetup (2:2.1.0-7) unstable; urgency=low . * debian/cryptsetup.NEWS: Mention the 'cryptsetup' and 'cryptsetup-run' package swap. * debian/control: Add 'cryptsetup-initramfs' to 'cryptsetup's Recommends:, so upgrading systems pull it automatically on upgrade. (cryptsetup <2:2.1.0-6 was a dummy transitional package depending on cryptsetup-run and cryptsetup-initramfs.) Closes: #932643. * debian/control: Add 'cryptsetup-run' to 'cryptsetup's Recommends. This avoids it being removed by `apt upgrade --autoremove` from <2:2.1.0-6, thus avoids the old cryptsetup-run's prerm script showing a scary (but moot) warning. After upgrading the prerm script is gone and the package can be removed without troubles, so we can get rid of it after Bullseye. (Closes: #932625.) * cryptsetup-initramfs: Add loud warning upon "prerm remove" if there are mapped crypt devices (like for cryptsetup.prerm). Checksums-Sha1: dc6962ef9e5d0ec0b4fce0ef9364ef92edfdd57d 2819 cryptsetup_2.1.0-7.dsc 38a6811ebfa560d05c15ee5893553e064e39b431 110272 cryptsetup_2.1.0-7.debian.tar.xz 4b3f1049066277ffa3b1a26647e52b0d4590e56a 9539 cryptsetup_2.1.0-7_amd64.buildinfo Checksums-Sha256: dfd7906fb341973e3cdda8c271c4de368b3ca15c11d1ebd43c1c37a862802f9a 2819 cryptsetup_2.1.0-7.dsc e3b79457dc286cf4240f720947472c2721a82744a07ce3e6fec7e245b1401f9f 110272 cryptsetup_2.1.0-7.debian.tar.xz c321d2d6a78dc02c9edef0e76dd590ebd557b201f2715ca2f2390f313cd94458 9539 cryptsetup_2.1.0-7_amd64.buildinfo Files: 5e3ab99d946245d63e4d3269de688699 2819 admin optional cryptsetup_2.1.0-7.dsc 5adc7bc7d91aa582f8f809c0775f4250 110272 admin optional cryptsetup_2.1.0-7.debian.tar.xz abe4c4567bb5b90a620a69cc425c1376 9539 admin optional cryptsetup_2.1.0-7_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEERpy6p3b9sfzUdbME05pJnDwhpVIFAl01BKAACgkQ05pJnDwh pVKVqw/9FszNB/O03VjNzCsv3GIoFtf9z66X7ifNQV5hGu4DnKZNOHE3aiq+fJSI dqy4FQ3TGGmMaMnDKYASjZjSC5NZQ0S7rL5SwC+VLwoc/MLm6+117xDUjURAwb9s wjK/1Bg9gxoeE3FOkLVlY9US6ND8Lbbhgt3XF6ScLtJ1CnQMvceA/Y5+/VSqdWXc JNUQNLx6xQAwSAyWPbN54452AfZNq+ASLYfFM1v1j8KIxyoCmbtDHcaNx6ak3Esn fQVTZCVTqZO/uXRO6eChS/EL7JD6k9w+M0MYCJpNUpwQQlrRiCDXKaKLFlHaQEBt xMZCIePyBAL2z84nMMEOaRrPIt5VBkh9Qy4q9edygPUja6z4HG3JAFuhgkrNnATG LMfY8HGRh9PUTOCEBLqp1p/iSyRyYcQDOgTfGwXWhB0R9azRO/ONnu+J6U1WUgFD K1S1F1Y+aacJ90g7AsS5BiLAenVTNfR501X+b6FbYFImpOqnvw3kFR3M5HudaxFr cufGG4ER7igCHSeriBDsGe04qSDXuePGLIzg2iXgKZna55ERfnDFGQpMyXiFJKiN jV1+UDFBWfNEmyFDTw5aIZ3BT5gKhR7/UOSThrfrSffEI9dDUAH0gEHlts6leA/O 1kaq7HTC35SLqaG+DsIWCNe3gXYaUbLJuy9ECONGhR34oA/Rlzs= =vI22 -----END PGP SIGNATURE-----
--- End Message ---
