[Bug 1989194] Re: Rename FK_FORCE_CONTAINER into FK_FORCE

[Łukasz Zemczak]

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 removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy

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