Bug#930229: finish-install: cryptsetup's initramfs integration was moved to a separate package

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#930229: finish-install: cryptsetup's initramfs integration was moved to a separate package

Guilhem Moulin-2
Package: finish-install
Version: 2.100
Severity: wishlist
Tags: patch

Hi there,

Since 2:2.0.3-1 the ‘cryptsetup’ package is a transitional dummy package
for ‘cryptsetup-run’ (various scripts and helpers/wrappers) and
‘cryptsetup-initramfs’ (initramfs integration, depending on the former).

    https://tracker.debian.org/news/965549/accepted-cryptsetup-2203-1-source-amd64-all-into-unstable-unstable/

finish-install's ‘finish-install.d/10update-initramfs’ currently
(v2.100) runs `dpkg-query -s cryptsetup`, while it only needs to
re-generate the initramfs image if cryptsetup's initramfs installed.
Trivial patch enclosed.

Thanks for maintaining d-i in Debian!
--
Guilhem.

finish-install.diff (877 bytes) Download Attachment
signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Bug#930229: finish-install: cryptsetup's initramfs integration was moved to a separate package

Guilhem Moulin-2
Also if #930228 is fixed before #930229 (if ‘partman-crypto’ installs
‘cryptsetup-initramfs’ iff. there are devices to be unlocked early in
the boot process), then #930229's Severity should raise to ≥important.

Otherwise if the resume devices(s) and the device(s) holding / and /usr
are not encrypted, but say the one(s) holding /var and/or /home are,
then the initramfs image won't be rebuilt at finish-install stage.

--
Guilhem.

signature.asc (849 bytes) Download Attachment