[Bug 2119049] Re: [SRU] Handle rename of u-boot-amlogic as part of noble backport

[Dave Jones]

On a Raspberry Pi 5, under a lxd noble container (which at the time of
writing contains a 2024 version of u-boot-amlogic) the following was
tested:

install u-boot-amlogic (old name)
do-release-upgrade to plucky with --proposed

Unfortunately that only used the proposed version of u-r-u, but does not
include the proposed pocket of the target release, so although the
rename actually worked successfully (u-boot-amlogic-binaries installed,
u-boot-amlogic removed), all that demonstrated was that the "Provides"
clause isn't required in this case.

I then tested the same set up, but placed u-boot-amlogic on hold prior
to do-release-upgrade, ensuring a plucky environment with the 2024
u-boot-amlogic. Then enabled the proposed pocket, unheld u-boot-amlogic,
and ran through a test upgrade and full-upgrade (ensuring the proposed
version was indeed the intended version). In both scenarios the rename
proceeded correctly: u-boot-amlogic-binaries was installed, taking the
"manual" mark from u-boot-amlogic and leaving the latter "no longer
required".

Setting verification to "done"

** Tags removed: verification-needed-plucky
** Tags added: verification-done-plucky

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to u-boot in Ubuntu.
https://bugs.launchpad.net/bugs/2119049

Title:
  [SRU] Handle rename of u-boot-amlogic as part of noble backport

Status in u-boot package in Ubuntu:
  Fix Released
Status in u-boot source package in Plucky:
  Fix Committed
Status in u-boot source package in Questing:
  Fix Released

Bug description:
  [ Impact ]

  See where things could go wrong section for full description;
  somewhere between "nothing" and "broken boot".

  [ Test Plan ]

  For each affected series:

  * Under an Ubuntu arm-based image, install u-boot-amlogic from an older version (<2025)
  * Run upgrade to proposed version
  * Ensure upgrade pulls in u-boot-amlogic-binaries

  * Under an Ubuntu noble arm-based image, install a pre-2024 version
  * dist-upgrade to a later release
  * Ensure dist-upgrade also pulls in u-boot-amlogic-binaries package automatically

  Note: we don't require the board used for this to actually use u-boot-
  amlogic; this is not testing the bootloader function just the package
  rename

  [ Where things could go wrong ]

  The bootloader functionality is not under consideration with this
  change as we don't have any boards that actually use this package any
  more. The only question is whether both upgrade and dist-upgrade will
  implicitly migrate the u-boot-amlogic package to u-boot-amlogic-
  binaries.

  If it does not, the best case scenario is either that no (extant)
  boards still use this package, or that they continue booting because
  (for example) the bootloader itself is only flashed manually. The
  worst case scenario is this leaves anyone relying on this package with
  a broken boot (assuming whatever is flashing boot assets will flash
  them automatically, even when the bootloader is missing).

  [ Original Description ]

  During the backport of 2025.01 to noble (to mitigate the movement to
  RVA23 as part of questing) (LP: #2110301), the SRU team noted that
  u-boot-amlogic has been replaced by u-boot-amlogic-binaries, and that
  the effective renaming of this package should have an empty
  transitional package and "Provides" clause to comply with renaming
  practices [1]. This change is also required in the plucky and questing
  releases.

  [1]: https://wiki.debian.org/PackageTransition case 5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/2119049/+subscriptions