Your message dated Wed, 31 Jul 2019 19:19:12 +0000
with message-id <e1hsu80-000fz6...@fasolo.debian.org>
and subject line Bug#932643: fixed in cryptsetup 2:2.2.0~rc1-2
has caused the Debian Bug report #932643,
regarding cryptsetup upgrade causes cryptsetup-initramfs autoremoval and boot
failure
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 ow...@bugs.debian.org
immediately.)
--
932643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932643
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cryptsetup
Version: 2:2.1.0-6
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
upgrading cryptsetup from 2:2.1.0-5 to 2:2.1.0-6 causes autoremoval of
cryptsetup-initramfs and consequent failure to boot from LUKS/LVM.
Workaround is to boot previous kernel (with unaffected initramfs) and repair
latest initramfs with:
apt-get install cryptsetup-initramfs
Kind regards,
Ben.
-- Package-specific info:
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages cryptsetup depends on:
ii cryptsetup-bin 2:2.1.0-6
ii debconf [debconf-2.0] 1.5.72
ii dmsetup 2:1.02.155-3
ii libc6 2.28-10
cryptsetup recommends no packages.
Versions of packages cryptsetup suggests:
ii dosfstools 4.1-2
pn keyutils <none>
ii liblocale-gettext-perl 1.07-3+b4
-- debconf information excluded
--- End Message ---
--- Begin Message ---
Source: cryptsetup
Source-Version: 2:2.2.0~rc1-2
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 932...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Guilhem Moulin <guil...@debian.org> (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 ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Wed, 31 Jul 2019 20:52:24 +0200
Source: cryptsetup
Architecture: source
Version: 2:2.2.0~rc1-2
Distribution: experimental
Urgency: low
Maintainer: Debian Cryptsetup Team
<pkg-cryptsetup-de...@alioth-lists.debian.net>
Changed-By: Guilhem Moulin <guil...@debian.org>
Closes: 913233 930696 932625 932643 933487
Changes:
cryptsetup (2:2.2.0~rc1-2) experimental; urgency=low
.
* Rebase changes from 2:2.1.0-6 and 2:2.1.0-7 to enable smooth upgrade path
from sid to experimental. (Closes: #933487)
* debian/*: Remove compatibility warnings regarding setting 'CRYPTSETUP' in
the initramfs hook configuration. The variable is no longer honored, and
cryptsetup is always integrated to the initramfs when the
'cryptsetup-initramfs' package is installed.
* debian/cryptsetup.NEWS: Mention the 'cryptsetup' and 'cryptsetup-run'
package swap.
* debian/control:
+ Swap 'cryptsetup' and 'cryptsetup-run' packages: the former now contains
init scripts, libraries, keyscripts, etc. while the latter is now a
transitional dummy package.
+ Remove obsolete cryptsetup.maintscript.
+ Bump Standards-Version to 4.4.0 (no changes necessary).
+ 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.) Thanks to David Prévot for the precious help!
Closes: #932643.
+ 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.)
* debian/initramfs/conf-hook: Clarify that KEYFILE_PATTERN isn't expanded
for crypttab(5) entries with a 'keyscript=' option. (Closes: #930696)
* debian/doc/crypttab.xml: Point to README.initramfs in the "See Also"
section. (Closes: #913233)
* cryptsetup-initramfs: Add loud warning upon "prerm remove" if there are
mapped crypt devices (like for cryptsetup.prerm).
Checksums-Sha1:
d75c5ec70d5151da93c868dae0a58c556f6110c7 2847 cryptsetup_2.2.0~rc1-2.dsc
ab7c2791f9503d1e0992822d1a36e0af22ece1ee 110520
cryptsetup_2.2.0~rc1-2.debian.tar.xz
b95193ed09a4f89f4536f67d453dbea4edb9150b 9569
cryptsetup_2.2.0~rc1-2_amd64.buildinfo
Checksums-Sha256:
e15ad92cc607d0eb22682dc58d3bb7f98220c15914e1f4067f402681d735afc2 2847
cryptsetup_2.2.0~rc1-2.dsc
0735f0618e82dc7dded248c3e89391c8a22a160f7ce9f948adcbde94e8b9100d 110520
cryptsetup_2.2.0~rc1-2.debian.tar.xz
44afc7aaa618be24d6880e6f98f27dd45b2787908fd2fcb7049680cc015dcd73 9569
cryptsetup_2.2.0~rc1-2_amd64.buildinfo
Files:
bcab8dc34cb3ad22a5ba62288a52897a 2847 admin optional cryptsetup_2.2.0~rc1-2.dsc
f357f380d02ae1e98c227258507ed9c2 110520 admin optional
cryptsetup_2.2.0~rc1-2.debian.tar.xz
6c4d03604654a996fad2c52f28adcfdf 9569 admin optional
cryptsetup_2.2.0~rc1-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEERpy6p3b9sfzUdbME05pJnDwhpVIFAl1B5EgACgkQ05pJnDwh
pVLzMQ/+MJJfKmKQ+pq0BSvRhRdyGh2c/wG9/BLNHoAb/vQIiMsQS6rGQhxivq9n
i8H+MpvD6iKGordOSMb44Y1mHk9hCDoTXvwsU33Wvt1UBYncFFJn+r8io4h1msRJ
Sue86vRI3AQZExxKWB+SAfqz0WONgOCOXIUP8K/JQITt8/MziX+J4/jwrEpnJ9SJ
J/AFVeWr1vK9ICsq7vm9hU79GOd6e5OUNSz4TeoQmInWFIQM8g3mVVeVyiHlKh8L
JsAfggyxZklTAkclK6c6cWNxtY6694RK1N7LPhMG2ItKyIl47S2nprxjM6oqEltE
2mK3I4hyo2zQj3SgR/wlCM80aT6mEX8++c4PMVegky0tnKanEUWYKA3zqxSO+z2s
1OON9eYrR4Yl6ZpZf2HucZlhwrrTJMFqR71WdytX1Lqk79x6p2Zl/c1tWwk5fWrP
UOTm2xnecI13u07hrveNqzx68n5flOz6bd6feIDvOhbq285XAr0lU9gnmw4iCyWh
wJmKbErCM8f/Hz5p73qJcFgHzQxezrTttAvo+pvvv8o3F4r+SEcOBCLNDxPeFa3v
5qN/Ywq0Ft5Vn5TNZeRayoSiFL2xvfngZUneAZq6CPhRFSU5wrLXzzU628DU8ulU
Rii/PEMvfIiGbxk/H5h/akq28AyKJkMPUx/LFEoeTMMOCiyoXB8=
=3Aq+
-----END PGP SIGNATURE-----
--- End Message ---