backport ubuntu-core-installer code to noble
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
livecd-rootfs (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Noble |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I added code in oracular to build an installer for UC24. We would like to (slightly) productionize this installer and so building on a noble base would be better.
[test plan]
We should build a livefs with a command like:
$ start-livefs-build --livefs=
[regression potential]
looking at the change that has already been merged to git:
https:/
It is clear that the risk of compromising other builds is negligible and indeed the same code did not when landed in devel. The ubuntu-
Changed in livecd-rootfs (Ubuntu): | |
status: | New → Invalid |
Changed in livecd-rootfs (Ubuntu Noble): | |
status: | New → In Progress |
summary: |
- backport ubnutu-core-installer code to noble + backport ubuntu-core-installer code to noble |
description: | updated |
Hello Michael, or anyone else affected,
Accepted livecd-rootfs into noble-proposed. The package will build now and be available at https:/ /launchpad. net/ubuntu/ +source/ livecd- rootfs/ 24.04.75 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- noble to verification- done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed- noble. 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.