Bug#998668: anna: Make it possible to install with a mismatched kernel
Hi,
Vagrant Cascadian <vagrant@debian.org> wrote (Fri, 05 Nov 2021 18:13:58 -0700):
> https://salsa.debian.org/installer-team/anna/-/commit/f6d5052a00df58c8f9d27d74c8ab585cc4d341e2
>
> commit f6d5052a00df58c8f9d27d74c8ab585cc4d341e2
> Author: Holger Wansing <hwansing@mailbox.org>
> Date: Wed Nov 6 00:04:45 2019 +0100
>
> Change template, to give a senseful message to the user, when no
> kernel modules can be found. Also, turn that from a question into an
> error message, since continuing isn't possible without kernel modules
> anyway.
>
> While I understand the motivation for making this a hard error in the
> default case, there are valid use-cases for testing with a mismatched
> kernel.
>
> I used to rely on being able to skip this step when testing new arm*
> platforms or platforms that depend on a newer kernel version or features
> using a custom kernel, or where there is a mismatch in the kernel
> version due to a recent ABI bump where debian-installer hasn't yet
> caught up with the archive...
>
> Maybe an explicit debconf question with low priority could be used to
> skip this step instead of issuing a hard error? That way expert installs
> or debconf preseeding could be used with the default images in the less
> typical use cases...
Hmm, isn't that exactly the situation, we had before the above mentioned change?
There were reasons, why this change was made:
it was mentioned, that proceeding without kernel modules in the correct
version isn't possible at all. (That was #749991, #367515.)
Was that statement incorrect?
Holger
--
Holger Wansing <hwansing@mailbox.org>
PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Reply to: