[Bug 2119049] Please test proposed package

[Andreas Hasenack]

Hello Dave, or anyone else affected,

Accepted u-boot into plucky-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/u-boot/2025.01-1~0ubuntu2.1 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-
plucky to verification-done-plucky. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-plucky. 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.

-- 
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:
  Triaged
Status in u-boot source package in Plucky:
  Fix Committed
Status in u-boot source package in Questing:
  Triaged

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