Salut Guilhem, Guilhem Moulin <guil...@debian.org> (2025-05-24): > IMHO an ideal fix would be to install cryptsetup-initramfs only when > some device needs to be unlocked by initramfs-tools, and only install > systemd-cryptsetup if there are remaining encrypted devices. > > I recall suggesting that before in https://bugs.debian.org/930228 , but > apparently never opened a follow-up bug to track that let alone suggest > a patch for it… Anyway that's probably too late at this point of the > release cycle.
I'd be a little reluctant to add smart stuff at this stage, since such things might need some iterations to get it right. > AFAIK d-i won't allow setting up a system *requiring* systemd-cryptsetup > out of its menu, so perhaps echoing systemd's NEWS entry in the release > notes would be enough? If not, then installing systemd-cryptsetup > alongside cryptsetup-initramfs would solve the issue (after all systemd's > cryptsetup integration used be included in the systemd binary package up > to bookworm). The status quo isn't ideal, we get very vocal users doing advanced stuff and complaining loudly that it doesn't work. That doesn't make me want to dive into the specifics, quite the contrary… In any case, documentation is unlikely to be seen as enough, and if installing both package side by side (possibly within the same set of tests for simplicity's and consistency's stake?), that would work for me… > I have both installed on many systems and AFAIK they cohabit well. > cryptsetup's init scripts are inert and takes care of unlocking > remaining devices past initramfs stage. … especially if you're familiar with their apparent peaceful cohabitation. Thanks for your input! Cheers, -- Cyril Brulebois (k...@debian.org) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
signature.asc
Description: PGP signature
