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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2119049 Title: [SRU] Handle rename of u-boot-amlogic as part of noble backport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/2119049/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
