Switch Loader* partition names to loader* ones

[Łukasz Zemczak]

[Impact]

For consistency, we want to keep partition names of RISC-V unmatched preinstalled images and the installer images the same. When creating the initial cd-boot-images-riscv64 package during Jammy, we mistakenly used capitalized partition names for loader1 and loader2. We'd like to change that for consistency. This change is already in cd-boot-images-riscv64 in kinetic.

For jammy it's actually also fixed already. For building jammy riscv64 images, we're actually not using the gadget.yaml from the cd-boot-images-riscv64 package but instead from debian-cd itself - and we already modified the partition names there. That being said, I want to backport this change to the jammy package in case at some moment we decide to start using the gadget.yaml from the package instead of the code. I'm worried at that moment we'd just forget that this rename was needed.

The change is basically a no-op. But if needed, it can also be simply block-proposed - but I think it's not even necessary as there is no bandwidth implication of getting it released (package is only used for installer image builds, and only riscv64 ones).

[Test Case]

No real test case as the jammy machinery does not use this file as of yet. Simply a diff of the gadget.yaml contents between kinetic and jammy should be enough of a test-case really. Please see 'Impact' for all the reasoning why we should still accept this as an SRU.

[Regression Potential]

In case the rename is wrong, we might get unbootable installer images, once we decide to switch the jammy builds to use the file from this package. But we'd notice that instantly.

[Steve Langasek (vorlon)]

Hello Łukasz, or anyone else affected,

Accepted cd-boot-images-riscv64 into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cd-boot-images-riscv64/5.1 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.

[Steve Langasek (vorlon)]

Accepting this as a trivial no-op change for current systems - like livecd-rootfs this should not be installed on end-user systems, and the package is not even being used for images at present.

Provided there are no regressions in daily builds of riscv64 images on jammy, this SRU should be released to -updates.

[Łukasz Zemczak (sil2100)]

I double checked the contents of the binary packages for 5.1 and I see everything feels to be in order. Marking as verified.

[Launchpad Janitor (janitor)]

This bug was fixed in the package cd-boot-images-riscv64 - 5.1

---------------
cd-boot-images-riscv64 (5.1) jammy; urgency=medium

  * meta/gadget.yaml: use loader1 and loader2 instead of their capitalized
    versions for the u-boot partitions. This is then consistent with our
    preinstalled images (LP: #1982571).

 -- Łukasz 'sil2100' Zemczak <email address hidden> Fri, 22 Jul 2022 12:33:07 +0200

[Brian Murray (brian-murray)]

The verification of the Stable Release Update for cd-boot-images-riscv64 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.