RISC-V 64 images support
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
livecd-rootfs (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned | ||
Groovy |
Fix Released
|
Undecided
|
Unassigned | ||
Hirsute |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
* Add support to build risc-v 64 cpc & buildd images for LXD, cloud-images, buildd and hifive (focal-only) preinstalled image targets.
[Test Case]
* Execute a riscv64 livefs build for the buildd subproject of ubuntu-base
* Execute a riscv64 livefs build for the ubuntu-cpc project
* Execute a riscv64 livefs build for the ubuntu-server preinstalled project
* Build should succeed since we have lxd builders, and the required packages to produce the above images.
[Regression Potential]
* Care has been taken to modify riscv64 code paths only, and correct some mistakes in the common hooks that are used to determine which image types to build (i.e. MBR images were built on ARM when they are not needed, and AMD64 MBR image is in fact needed!). This changes are now tested extensively in hirsute to ensure other image types are unaffected, and these images work correctly.
Changed in livecd-rootfs (Ubuntu Hirsute): | |
status: | New → Fix Released |
Changed in livecd-rootfs (Ubuntu Groovy): | |
status: | New → In Progress |
Changed in livecd-rootfs (Ubuntu Focal): | |
status: | New → In Progress |
milestone: | none → ubuntu-20.04.2 |
Hello Dimitri, or anyone else affected,
Accepted livecd-rootfs into groovy-proposed. The package will build now and be available at https:/ /launchpad. net/ubuntu/ +source/ livecd- rootfs/ 2.694.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- groovy to verification- done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed- groovy. 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/ PerformingSRUVe rification . 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.