[Bug 1983599] Re: RISC-V cloud images FTBFS after recent StarFive/Nezha changes

[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.9 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.

** Changed in: livecd-rootfs (Ubuntu Jammy)
       Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-jammy

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/1983599

Title:
  RISC-V cloud images FTBFS after recent StarFive/Nezha changes

Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  When adding the new RISC-V platforms, some of the generic non-SUBARCH
  code went missing and some invalid assumptions have been made
  (forgetting that we're building RISC-V images that have no SUBARCH),
  causing cloud images to fail building. So this is basically a fix for
  an updates regression.

  [Test Case]

   * Build all our preinstalled RISC-V images with PROPOSED=1 via cdimage and make sure those images build and boot correctly:
     - unleashed
     - starfive
     - nezha
   * Ask the CPC team to build a proposed-enabled cloud image for RISC-V and confirm that it builds correctly

  [Regression Potential]

  The fix here can cause same kind of regressions, so it can cause other
  existing RISC-V images to either not build correctly or build
  unbootable images (test case checks that). A general check of all
  cloud images could be good, since you never know if we didn't break
  something outside of the RISC-V use case (highly unlikely though).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1983599/+subscriptions