[Bug 1982571] Re: Switch Loader* partition names to loader* ones

[Launchpad Bug Tracker]

This bug was fixed in the package cd-boot-images-riscv64 - 5.1

---------------
cd-boot-images-riscv64 (5.1) jammy; urgency=medium

  * meta/gadget.yaml: use loader1 and loader2 instead of their capitalized
    versions for the u-boot partitions. This is then consistent with our
    preinstalled images (LP: #1982571).

 -- Łukasz 'sil2100' Zemczak <lukasz.zemczak at ubuntu.com>  Fri, 22 Jul
2022 12:33:07 +0200

** Changed in: cd-boot-images-riscv64 (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 cd-boot-images-riscv64 in
Ubuntu.
https://bugs.launchpad.net/bugs/1982571

Title:
  Switch Loader* partition names to loader* ones

Status in cd-boot-images-riscv64 package in Ubuntu:
  Fix Released
Status in cd-boot-images-riscv64 source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  For consistency, we want to keep partition names of RISC-V unmatched
  preinstalled images and the installer images the same. When creating
  the initial cd-boot-images-riscv64 package during Jammy, we mistakenly
  used capitalized partition names for loader1 and loader2. We'd like to
  change that for consistency. This change is already in cd-boot-images-
  riscv64 in kinetic.

  For jammy it's actually also fixed already. For building jammy riscv64
  images, we're actually not using the gadget.yaml from the cd-boot-
  images-riscv64 package but instead from debian-cd itself - and we
  already modified the partition names there. That being said, I want to
  backport this change to the jammy package in case at some moment we
  decide to start using the gadget.yaml from the package instead of the
  code. I'm worried at that moment we'd just forget that this rename was
  needed.

  The change is basically a no-op. But if needed, it can also be simply
  block-proposed - but I think it's not even necessary as there is no
  bandwidth implication of getting it released (package is only used for
  installer image builds, and only riscv64 ones).

  [Test Case]

  No real test case as the jammy machinery does not use this file as of
  yet. Simply a diff of the gadget.yaml contents between kinetic and
  jammy should be enough of a test-case really. Please see 'Impact' for
  all the reasoning why we should still accept this as an SRU.

  [Regression Potential]

  In case the rename is wrong, we might get unbootable installer images,
  once we decide to switch the jammy builds to use the file from this
  package. But we'd notice that instantly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cd-boot-images-riscv64/+bug/1982571/+subscriptions