Rename FK_FORCE_CONTAINER into FK_FORCE
Bug #1989194 reported by
Alexandre Ghiti
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
livecd-rootfs (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Medium
|
Unassigned |
Bug Description
[ Impact ]
flash-kernel renamed FK_FORCE_CONTAINER into FK_FORCE so that the environment variable can also encompass chroots. This modification will be SRUed to jammy (which is the only release using this) so we need to SRU the renaming otherwise RISC-V images would fail to build.
[ Test Plan ]
I'll trigger a rebuild of nezha/visionfive images once it lands in the archive.
[ Where problems could occur ]
The renaming should be pretty straightforward, and those are the only places where we install flash-kernel so it should not break other images.
Related branches
~xypron/livecd-rootfs:jammy-riscv64
- Łukasz Zemczak: Approve
-
Diff: 186 lines (+83/-11)4 files modifiedlive-build/auto/config (+2/-2)
live-build/ubuntu-cpc/hooks.d/base/disk-image-uefi.binary (+71/-9)
live-build/ubuntu-cpc/hooks.d/base/riscv64/grub/cmdline.cfg (+4/-0)
live-build/ubuntu-cpc/hooks.d/base/riscv64/initramfs-tools/modules_list.conf (+6/-0)
~alexghiti/livecd-rootfs:int/alex/fk_force
Ready for review
for merging
into
livecd-rootfs:ubuntu/master
- William Wilson: Approve
- Thomas Bechtold (community): Approve
-
Diff: 37 lines (+9/-2)2 files modifieddebian/changelog (+7/-0)
live-build/ubuntu-cpc/hooks.d/base/disk-image-uefi.binary (+2/-2)
Changed in livecd-rootfs (Ubuntu Jammy): | |
status: | New → Triaged |
importance: | Undecided → Medium |
To post a comment you must log in.
https:/ /code.launchpad .net/~alexghiti /livecd- rootfs/ +git/livecd- rootfs/ +merge/ 429646