Rename FK_FORCE_CONTAINER into FK_FORCE

Bug #1989194 reported by Alexandre Ghiti
12
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

Revision history for this message
Alexandre Ghiti (alexghiti) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package livecd-rootfs - 2.777

---------------
livecd-rootfs (2.777) kinetic; urgency=medium

  * Rename FK_FORCE_CONTAINER into FK_FORCE as its role was extended to also
    support chroot (LP: #1989194).

 -- Alexandre Ghiti <email address hidden> Thu, 08 Sep 2022 16:25:36 +0200

Changed in livecd-rootfs (Ubuntu):
status: New → Fix Released
Changed in livecd-rootfs (Ubuntu Jammy):
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Timo Aaltonen (tjaalton) wrote : Please test proposed package

Hello Alexandre, 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.11 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: Triaged → Fix Committed
tags: added: verification-needed verification-needed-jammy
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

Per recent nezha jammy images, looking at their build logs: https://launchpadlibrarian.net/635127700/buildlog_ubuntu_jammy_riscv64_nezha_cpc_BUILDING.txt.gz - we can see that flash-kernel uses FK_FORCE and still correctly installs the DTB: "Installing new sun20i-d1-nezha.dtb."

And all that using: "livecd-rootfs riscv64 2.765.11"

tags: added: verification-done verification-done-jammy
removed: verification-needed verification-needed-jammy
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package livecd-rootfs - 2.765.11

---------------
livecd-rootfs (2.765.11) jammy; urgency=medium

  * Rename FK_FORCE_CONTAINER into FK_FORCE as its role was extended to also
    support chroot (LP: #1989194).

 -- William 'jawn-smith' Wilson <email address hidden> Fri, 07 Oct 2022 09:49:30 -0500

Changed in livecd-rootfs (Ubuntu Jammy):
status: Fix Committed → Fix Released
Revision history for this message
Łukasz Zemczak (sil2100) wrote : Update Released

The verification of the Stable Release Update for livecd-rootfs 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.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.