Bug#932625: [pkg-cryptsetup-devel] Bug#932625: Bug#932625: cryptsetup: removing transitional cryptsetup-run produces scary debconf question

2019-07-21 Thread Guilhem Moulin
On Sun, 21 Jul 2019 at 21:57:09 -0300, Guilhem Moulin wrote: > cryptsetup <2:2.0.3-1's (≤Stretch) functionalities have been subsumed > by the combination of cryptsetup-run and cryptsetup-initramfs between > 2:2.0.3-1 and 2:2.0.3-5 (Buster); and the combination of > cryptsetup-run and

Bug#932625: [pkg-cryptsetup-devel] Bug#932625: cryptsetup: removing transitional cryptsetup-run produces scary debconf question

2019-07-21 Thread Guilhem Moulin
Control: tag -1 pending Hi, On Sun, 21 Jul 2019 at 12:58:28 +0100, Simon McVittie wrote: > 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? Yup it's safe to remove

Bug#932625: cryptsetup: removing transitional cryptsetup-run produces scary debconf question

2019-07-21 Thread Simon McVittie
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