> Except on RISC-V none of the U-Boot packages has post install scripts. Changes to the U-Boot packages affect current installations only if the user manually updates the firmware.
One minor exception to this is the u-boot-rpi package, which was auto- installed via flash-kernel historically, but as already noted, u-boot is not used on rpi on noble [1]. Speaking more generally about testing: There are no official images (that we know of) that use u-boot-amlogic or any of the other arm64 or armhf builds. The is at least one unofficial image using one of the arm64 builds (Ubuntu Asahi, which uses u-boot-asahi) but given these are unsupported platforms we lack any capacity to test these builds in a meaningful way [2]. However, there is a proxy of sorts... The general story with testing these binaries is: * For officially supported hardware (read: RISC-V at the present time), the binaries do indeed receive testing and verification. * For unsupported hardware: we bump u-boot for a new release and ... see if anyone complains. Anyone using these binaries on unsupported platforms might reasonably expect dist-upgrades to be a risky prospect, and hopefully will file a bug if they encounter a problem. The corollary to this practice is that, if a given version has been in service in a release for a while without incident, we have a reasonable expectation that it is "good" [3]. Given 2025.01 has been used throughout plucky's existence (and will also be the version in questing), this is our proxy that the version is "okay". It could be argued that this version is different as it'll be running in noble's environment rather than plucky's. However, bootloaders are fairly uniquely "disconnected" from the rest of the environment (having effectively no presence once the kernel gets going, beyond the influence of the artefacts they have passed to the kernel), which (at least partially) mitigates this concern. [1] I could test the u-boot-rpi package on my Raspberry Pis, but that doesn't tell us much that's genuinely useful (it tells us one set of binaries works on a board where we don't use them, but it doesn't tell us that any other binaries will boot any another board). [2] I could test the u-boot-asahi package as my husband uses Ubuntu on a Mac M1 Mini. [3] ... or "not used by anybody" -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
