What do you think about strategy #5 of https://wiki.debian.org/PackageTransition for the (a) rename of u-boot- amlogic to u-boot-amlogic-binaries? That would allow a smooth upgrade/transition to the new name, and is probably what should have been done in plucky forward, but that ship has sailed.
As for testing, I'd like to see at least raspberry pis tested, as these are very common. What we are doing for the RISC test seems it could apply to PIs as well. > Ubuntu does not provide armhf and arm64 images with preinstalled U-Boot. My Pi4 running plucky has u-boot 2025.01-1~0ubuntu2 installed. As does my Pi5. I just launched a noble arm64 VM on my pi5 and it has u-boot- tools installed. What I'm saying is that it looks like raspberry PIs will receive the update, and this hw is so common that we should be able to smoke test it. Note I'm focusing on regression testing here (about the PIs), but it would be awesome if we had a way to test some of the new arm hardware that this update is introducing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2110301 Title: [SRU] Backport u-boot 2025.01-3 to Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/2110301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
