[Bug 1989194] Re: Rename FK_FORCE_CONTAINER into FK_FORCE

[Launchpad Bug Tracker]

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 <jawn-smith at ubuntu.com>  Fri, 07 Oct
2022 09:49:30 -0500

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

-- 
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/1989194

Title:
  Rename FK_FORCE_CONTAINER into FK_FORCE

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

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.

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