Control: tag -1 - moreinfo Hi,
On Thu, 21 Dec 2023 at 21:59:40 +0000, Jonathan Wiltshire wrote:
> On Mon, Dec 18, 2023 at 02:10:20PM +0100, Guilhem Moulin wrote:
>> [ Reason ]
>>
>> 1. cryptsetup-suspend 2:2.6.1-4~deb12u1 was found incompatible with
>> systemd 254.1-3 and later, in particular with systemd/bookworm-backports.
>>
>> 2. cryptsetup-initramfs 2:2.6.1-4~deb12u2 dos not support kernel
>> shipping compressed modules under MODULES=dep, as is done by default
>> with linux 6.6 (currently in Debian experimental).
>
> Aren't these problems better sorted out in the relevant suites, e.g. with
> Breaks? It seems an unnecessary change in stable when stable isn't actually
> broken.
It's correct that stable isn't broken at the moment, but some users also
build their own kernels, and we can't warn about the incompatibilty
there; they just won't be able to boot when these 3 conditions are
satisfied:
1. Linux is configured with CONFIG_MODULE_COMPRESS_* (Debian currently
does that in experimental only but the setting is also available in
<6.0);
2. initramfs.conf(5) sets MODULES=dep; and
3. There is a device to be unlocked at initramfs stage (for instance
the root FS).
Moreover the issue stands in the way of kernel maintainers enabling
CONFIG_MODULE_COMPRESS_* in stable should that be needed or desired
in some point release. (Compressed modules are already suported in
Bookworm's initramfs-tools, but currently not in cryptsetup-initramfs.)
The other issue I see with ‘Breaks: cryptsetup-initramfs (<< 2:2.6.1-6~)’
without having a recent enough cryptsetup-initramfs available is that
apt will hapilly suggest to remove cryptsetup-initramfs. That too would
yield an unbootable system whenever there is any device to be unlocked
at initramfs stage.
Note that the proposed change is a no-op with Bookworm's current kernel
and systemd. It just adds forward compatibility in the same way
initramfs-tools did.
--
Guilhem.
signature.asc
Description: PGP signature
