Your message dated Sun, 24 Jun 2018 22:19:14 +0000 with message-id <[email protected]> and subject line Bug#902183: fixed in cryptsetup 2:2.0.3-4 has caused the Debian Bug report #902183, regarding cryptsetup-initramfs: "ERROR: Couldn't find sysfs hierarchy for <unencrypted partition>" 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.) -- 902183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902183 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: cryptsetup-initramfs Version: 2:2.0.3-3 Severity: normal Hi, Just upgrading my sid systemm this morning: Setting up udev (239-1) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.130) ... update-initramfs: Generating /boot/initrd.img-4.16.0-2-amd64 cryptsetup: ERROR: Couldn't find sysfs hierarchy for /dev/sda1 cryptsetup: ERROR: Couldn't find sysfs hierarchy for UUID=2efdbd50-bc29-4134-9519-5a007c41c12a cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries nor crypto modules. If that's on purpose, you may want to uninstall the 'crypsetup-initramfs' package in order to disable the cryptsetup initramfs integration and avoid this warning. W: APT had planned for dpkg to do more than it reported back (0 vs 4). Affected packages: udev:amd64 So, I didn't look into the sysfs error at all — as I do not use cryptsetup on this machine, I thought I would just remove the cryptsetup-initramfs package and get on with my morning (NB. typo bug already filed in #901971!). I then did so: Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: cryptsetup-bin cryptsetup-run libcdio17 libgconfmm-2.6-1v5 libtgvoip1.0.3 libx265-151 Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: cryptsetup* cryptsetup-initramfs* 0 upgraded, 0 newly installed, 2 to remove and 1 not upgraded. After this operation, 180 kB disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 204402 files and directories currently installed.) Removing cryptsetup (2:2.0.3-3) ... Removing cryptsetup-initramfs (2:2.0.3-3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.130) ... update-initramfs: Generating /boot/initrd.img-4.16.0-2-amd64 (Reading database ... 204370 files and directories currently installed.) Purging configuration files for cryptsetup (2:2.0.3-3) ... Purging configuration files for cryptsetup-initramfs (2:2.0.3-3) ... [master aac91b8] committing changes in /etc after apt run 2 files changed, 40 deletions(-) $ echo $? 0 I'm only really filing this just in case it affects people actually using cryptsetup or similar and I want to avoid them rebooting and it not working; feel free to close if invalid am just being trigger-happy. Anything I should be concerned with? Regards, -- ,''`. : :' : Chris Lamb `. `'` [email protected] / chris-lamb.co.uk `-
--- End Message ---
--- Begin Message ---Source: cryptsetup Source-Version: 2:2.0.3-4 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, 24 Jun 2018 22:48:41 +0200 Source: cryptsetup Binary: cryptsetup-run cryptsetup-bin cryptsetup-initramfs cryptsetup libcryptsetup12 libcryptsetup-dev cryptsetup-udeb libcryptsetup12-udeb Architecture: source amd64 all Version: 2:2.0.3-4 Distribution: unstable Urgency: low Maintainer: Debian Cryptsetup Team <[email protected]> Changed-By: Guilhem Moulin <[email protected]> Description: cryptsetup - transitional dummy package for cryptsetup-{run,initramfs} cryptsetup-bin - disk encryption support - command line tools cryptsetup-initramfs - disk encryption support - initramfs integration cryptsetup-run - disk encryption support - startup scripts cryptsetup-udeb - disk encryption support - commandline tools (udeb) (udeb) libcryptsetup-dev - disk encryption support - development files libcryptsetup12 - disk encryption support - shared library libcryptsetup12-udeb - disk encryption support - shared library (udeb) (udeb) Closes: 901971 902116 902183 902245 Changes: cryptsetup (2:2.0.3-4) unstable; urgency=low . * debian/initramfs/hooks/cryptroot: + Fix typo in warning message. (Closes: #901971.) + sysfs_devdir(): don't croak when the normalized device pathname isn't of the form /dev/$blk. This is the case in the Debian installer, where the devtmpfs pseudo-filesystem exposes /dev/mapper/$name as a block device instead of a symlink to /dev/dm-$index. + sysfs_devdir(): return /sys/dev/block/$maj:$min (a symlink pointing the sysfs directory corresponding to the device) rather than /sys/block/$blk. While the latter is present for mapped devices, it's not present for block devices corresponding to disk partitions. See sysfs(5) for details. (Closes: #902183.) + get_crypttab_entry(): skip (harmless) warning if blkid_tag() fails to get the UUID of a dm-crypt device's slave (it's normal with plain dm-crypt devices). + get_crypttab_entry(): don't warn that key file doesn't exist if it's e.g., an existing character special device. * debian/functions:unlock_mapping(): translate crypttab(5) option 'size=<size>' to `cryptsetup --key-size=<size>`, not `--size` (which doesn't set the key size but the size of the device in number of 512 byte sectors). Regression since 2:2.0.3-2. (Closes: #902245.) * debian/initramfs/scripts/local-top/cryptroot, debian/cryptdisks-functions, debian/initramfs/cryptroot-unlock: Fix off-by-one unlock count. Some keyscripts (such as decrypt_keyctl) don't work properly if on first try the CRYPTTAB_TRIED environment variable isn't set to 0. Regression since 2:2.0.3-2. (Closes: #902116.) * debian/scripts/decrypt_keyctl: replace the source device path with the mapped device name in messages, to match the new askpass behavior. Checksums-Sha1: 39d3eda23732abfee61fd705454ee7d0577079a9 2800 cryptsetup_2.0.3-4.dsc 704fb27280cc7eaa8ebf4277a836dee9537da1d8 95180 cryptsetup_2.0.3-4.debian.tar.xz ba7b70315e7859ef448ae9c222892ab65b7b2cb9 164988 cryptsetup-bin-dbgsym_2.0.3-4_amd64.deb 8cbdf8bd12f15cfc7a61118b70f4d915be964559 243804 cryptsetup-bin_2.0.3-4_amd64.deb df494b2aab3571d74c977ce1f540feb39c2d412d 61452 cryptsetup-initramfs_2.0.3-4_all.deb f01e7cdd3ced73db9e819611c41a703dfd8764d5 17120 cryptsetup-run-dbgsym_2.0.3-4_amd64.deb 13de41685935667f18e6c22b30739cebab924956 179700 cryptsetup-run_2.0.3-4_amd64.deb 7c272bcd04d01739f104f47d2e2f12dfb9d62cd1 48244 cryptsetup-udeb_2.0.3-4_amd64.udeb cde28c42b25cad6e3b5ebdde1564c06eeb62ad58 46628 cryptsetup_2.0.3-4_all.deb de618cb72549d262c90e9be0f8a874c4cdde1ea8 9133 cryptsetup_2.0.3-4_amd64.buildinfo 7cc1368a0cbe84ae31be66ca45662951337f926b 61836 libcryptsetup-dev_2.0.3-4_amd64.deb c34435bbdbbd4bc1aca4ba08477c7dcf1e4b4ec4 339916 libcryptsetup12-dbgsym_2.0.3-4_amd64.deb 089038274d052edbb1705fb77e48375c6ed3268a 128956 libcryptsetup12-udeb_2.0.3-4_amd64.udeb 5eefcf5f715208b56fa8280a19b16faf2ffad241 174288 libcryptsetup12_2.0.3-4_amd64.deb Checksums-Sha256: 313044f1b646f76d3fee0d8c7ff5e0909b22b3a716ec39eda2a487581d800b8d 2800 cryptsetup_2.0.3-4.dsc 2216db547e788eb77786365da40a5c9102eba07808a492103fdea67fcedb6e14 95180 cryptsetup_2.0.3-4.debian.tar.xz b7ac19c236a8af80fbff45ce1aaeee5393b9775b6e1c297d36a3d4e7bac90694 164988 cryptsetup-bin-dbgsym_2.0.3-4_amd64.deb 8febb729c4647b6b20d0d24da11de8c408ea5e29a346f28af19ebf00cb89c006 243804 cryptsetup-bin_2.0.3-4_amd64.deb e637e60456733fc39c0381628c1217513bd78b61edfb32f4819600d419948ff1 61452 cryptsetup-initramfs_2.0.3-4_all.deb f04c67a9719ac58cb4ed683c64b0f9830ddb5cca616578f03c8909c46ef6b6fb 17120 cryptsetup-run-dbgsym_2.0.3-4_amd64.deb 45c0c317ad33edc38a0f257fdca7a954e94ed0e0b82cb3c9ed82c0f0d59e5136 179700 cryptsetup-run_2.0.3-4_amd64.deb a6ac649b282235b4a8b18393c00af01b9204b6faf940e340b82ae0962dd6a88c 48244 cryptsetup-udeb_2.0.3-4_amd64.udeb ca5dfa1dd99d5ee38a78239dc50a6cdddcac06686a012487592fa5507c65801d 46628 cryptsetup_2.0.3-4_all.deb 19d78e1fcf3cd71cd4e91dedfe0b6a5c5893e2b7e492029f5622aa6a55acb4dd 9133 cryptsetup_2.0.3-4_amd64.buildinfo 88decbd268d29eb5066b23ef259200bc24f5ca20847dbee96fbe63fa58dffb2c 61836 libcryptsetup-dev_2.0.3-4_amd64.deb 4f5ea62266e919ed09ba823c03c8f7aa3342aa60e073be3228572482baae64a4 339916 libcryptsetup12-dbgsym_2.0.3-4_amd64.deb 5f8205fe032052609e5d14ccc2a0717418a21cec20aac48fabf9baa0dfbb47c8 128956 libcryptsetup12-udeb_2.0.3-4_amd64.udeb 978c3348a2f678fafd4bd2d69c44364331a90881d9554630d26c0998cceff0cd 174288 libcryptsetup12_2.0.3-4_amd64.deb Files: 1ac7a4ea9789fa0e764806200ba8a342 2800 admin optional cryptsetup_2.0.3-4.dsc a22f3732fddfe29851571b7f883906d7 95180 admin optional cryptsetup_2.0.3-4.debian.tar.xz 7f434c9bf9fac2a4c1f15b1d0902b4f6 164988 debug optional cryptsetup-bin-dbgsym_2.0.3-4_amd64.deb 9631822a4265d3961282d8eb3b1501f9 243804 admin optional cryptsetup-bin_2.0.3-4_amd64.deb 634c61866560e82ffcc3ee68f506ea58 61452 admin optional cryptsetup-initramfs_2.0.3-4_all.deb da0b5a1fbdabe8f3336de30420126ba0 17120 debug optional cryptsetup-run-dbgsym_2.0.3-4_amd64.deb 5d7af4f20cd55a1d19a77f9b7afeadb7 179700 admin optional cryptsetup-run_2.0.3-4_amd64.deb c2d65a8984ae9407b2eb3b41f1d9f93b 48244 debian-installer optional cryptsetup-udeb_2.0.3-4_amd64.udeb 4cc8aea234a88f3744cdcacbee2ae5cb 46628 oldlibs optional cryptsetup_2.0.3-4_all.deb 32dc7d0813fb06e12b3573f4aebc84a2 9133 admin optional cryptsetup_2.0.3-4_amd64.buildinfo c55ec17ea57d2c53a6bd1788a3b70907 61836 libdevel optional libcryptsetup-dev_2.0.3-4_amd64.deb 9e84ca4f082191acc924bdbd367395e4 339916 debug optional libcryptsetup12-dbgsym_2.0.3-4_amd64.deb 5af59fa4f87f536cedcc45c2a04f74ea 128956 debian-installer optional libcryptsetup12-udeb_2.0.3-4_amd64.udeb 233f4963c2cf01f3fe6d9a9aaa0da4d6 174288 libs optional libcryptsetup12_2.0.3-4_amd64.deb -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEERpy6p3b9sfzUdbME05pJnDwhpVIFAlswBC0ACgkQ05pJnDwh pVK38A//X2B5xtrwhy8iRYTtRsMpIdHUqO/lsvkRDeK+2wyXinmq57HP6pI3wYti 5CYPOw6zi1RsoWfl8MEEOqcabdDH/W8OxcCbLjMqhUVBMV6ed/9EnuaM5A8ayIx+ ulXexvqS2oU7ghKUOUiLPhYUSMwMFpZ37kxfrDVVvHc0Kbww8bDwAcvSyPIJqhhG QuFsQpiT2CrV7zSvUbvTFBpydOmE/E2EY6K1owuMCABLZP75gl7YQ1qWeOP/hs89 XQDAQojvP7zKf7f4NxOjj1E/bJy/Q9ugXOm+7cIyBaYz4ogW/HCUgoKg9cgkfsFG Jj2POrZzgsYFsPLWjQ4GITGmF2Ej+c8k4oTZ29q2WfefAGbmU5BNYIiYIO4U3qVE ERpReyBu2jQhWAEEHaYalfm5Ml7AAKe2tiZ+6OY3vPS2KZ3L1u0IWJ+u7ARnwq7L xK3Jsyx3aS5YHRnRescZ7XYiEHa4ItBoM6eBagFzdCPNjYdRkHbyuhv8+gop8MkK F4NphOPi5Ogz/luZe1pq5+8wDTxzauwc0+1xPO1Vxq/Rst1f8My8i+lM4yxQfvBc cxSZK/ckvsk5X+J4RW/NVt4ry4NUoO05zrGnGCVDdqAaaLVJ54jANIZ4Q4Kh9v2c 5syzkeJA2gFBsIRnyKNarqJ22858v/9HjWxI+TqCvO9nw0bz02U= =L/Xe -----END PGP SIGNATURE-----
--- End Message ---
