Jammy raspi daily-preinstalled builds failing to build due to gadget changes

[Łukasz Zemczak]

[Impact]

We did not have new preinstalled raspi jammy images since many months, mostly due to the `classic` branch of the pi gadget changing to the new ubuntu-image 3.x features. This is a critical bug.
The proposed, safest way forward is to create a reverted, ubuntu-image 2.x targeted gadget branch and make sure that livecd-rootfs uses that one instead.

[Test Case]

After accepting the package to -proposed, run a test build of arm64 and armhf raspi daily-preinstalled images. Those should now succeed.

Download the image and do a boot test + perform a few basic smoke tests.

[Regression Potential]

There should be none per-se, as currently no raspi builds are succeeding. That being said, the images need to be checked if no essential gadget changes have been missed, seeing if the resulting new raspi jammy images work as intended.
In theory this change might break other, non-raspi preinstalled image builds - but considering that in jammy ubuntu-image is only used to build Pi images, there's no real regression potential.

[Łukasz Zemczak (sil2100)]

Uploaded to the jammy-proposed queue. This is critical as right now we had no new jammy pi images since months.

[Brian Murray (brian-murray)]

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.35 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.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted livecd-rootfs (2.765.35) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

livecd-rootfs/2.765.35 (amd64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/jammy/update_excuses.html#livecd-rootfs

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Steve Langasek (vorlon)]

An upload of livecd-rootfs to jammy-proposed has been rejected from the upload queue for the following reason: "needs to be accompanied in same SRU cycle with fix for LP: #2049723".

[Łukasz Zemczak (sil2100)]

I have confirmed that the jammy builds now work (dailies) and seem to be in decent shape. This should be good to go.

[Launchpad Janitor (janitor)]

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

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

  * For raspi preinstalled builds, use a per-series dedicated gadget branch.
    (LP: #2049373)

 -- Łukasz 'sil2100' Zemczak <email address hidden> Mon, 15 Jan 2024 11:32:47 +0100

[Łukasz Zemczak (sil2100)]

The verification of the Stable Release Update for livecd-rootfs has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.