Jammy RISC-V nezha and licheerv (allwinner kernel) images failing to build due to no kernel found

[Łukasz Zemczak]

[Impact]

Latest builds of RISC-V nezha and licheerv platforms fail to build:
https://launchpadlibrarian.net/715172443/buildlog_ubuntu_jammy_riscv64_nezha_cpc_BUILDING.txt.gz

The problem is a missing handling switch statement for allwinner.

[Test Case]

Builds of nezha and licheerv building correctly with the new livecd-rootfs.

[Regression Potential]

Other, unrelated builds can start failing due to "No kernel output for ...", but risk is minimal.

[Łukasz Zemczak (sil2100)]

Hello Łukasz, or anyone else affected,

Accepted livecd-rootfs into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/livecd-rootfs/2.765.40 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Launchpad Janitor (janitor)]

This bug was fixed in the package livecd-rootfs - 2.765.40

---------------
livecd-rootfs (2.765.40) jammy; urgency=medium

  * Handle the allwinner kernel in the same way as we handle generic. This
    change seems to been missed, as it was present in noble. (LP: #2054412)

 -- Łukasz 'sil2100' Zemczak <email address hidden> Tue, 20 Feb 2024 09:48:10 +0100