Your message dated Fri, 30 Dec 2022 10:46:26 +0100
with message-id <[email protected]>
and subject line Re: Bug#1027299: cryptsetup: on buster with
linux-image-5.10-686-pae aes-xts-plain is not available
has caused the Debian Bug report #1027299,
regarding cryptsetup: on buster with linux-image-5.10-686-pae aes-xts-plain is
not available
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 [email protected]
immediately.)
--
1027299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027299
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: cryptsetup-initramfs
Version: 2:2.1.0-5+deb10u2
Severity: important
X-Debbugs-Cc: none, Łukasz Stelmach <[email protected]>
Dear Maintainer,
The version of cryptsetup-initramfs in buster is affected by
#959423[1]. Although it works with the default 4.19 kernel[2] it fails with
5.10 which is available from the main suite and NOT from
buster-backports. Installing cryptsetup-initramfs from buster-backports
helps.
IMHO the version of cryptsetup-initramfs in buster or buster-updates
should support 5.10 kernels.
I am upgrading from jessie to bullseye and need 5.10 kernel before the
last upgrade.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959423
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959423#10
--
Miłego dnia,
Łukasz Stelmach
--- End Message ---
--- Begin Message ---
Hi,
On Fri, 30 Dec 2022 at 00:30:32 +0100, Łukasz Stelmach wrote:
> The version of cryptsetup-initramfs in buster is affected by
> #959423[1]. Although it works with the default 4.19 kernel[2] it fails with
> 5.10 which is available from the main suite and NOT from
> buster-backports.
No, buster, buster-security, buster-backports respectively have linux
4.19.249-2, 4.19.269-1, and 5.10.127-2~bpo10+1. Debian doesn't support
a mix and match between oldstable and stable, so if you install the
kernel from stable you need to install cryptsetup-initramfs from
stable as well.
OTOH mixing buster and buster-backports *is* supported (that's the
reason why backport exist in the first place), so this bug is valid.
But unfortunately buster had its final point release last summer and
IMHO the fix #959423 doesn't qualify for an upload to buster-security,
so I'm closing this.
> IMHO the version of cryptsetup-initramfs in buster or buster-updates
> should support 5.10 kernels.
It does with the default MODULES=dep, and arguably does too in most
situations (these days most systems do support AES-NI, and this has been
the case since the default LUKS cipher mode was changed to XTS during
the jessie release cycle). In other situations, workarounds include
rebuilding the initramfs with MODULES=most, or after adding ‘ecb’ to
/etc/initramfs-tools/modules, or installing cryptsetup-initramfs from
buster-backports.
> I am upgrading from jessie to bullseye and need 5.10 kernel before the
> last upgrade.
Upgrades are only supported from n to n+1. A supported upgrade path
would be to dist-upgrade to stretch first and reboot (into the stretch
kernel 4.9), then to buster and reboot (into the buster kernel 4.19)
before finally dist-upgrading to bullseye. Following that upgrade path
you shouldn't stumble onto #959423.
Cheers,
--
Guilhem.
signature.asc
Description: PGP signature
--- End Message ---
