Some of this has been discussed offline, but here are my thoughts on the current state of this.
I understand the justification of this to be "give users of recently- enabled RVA20 boards access to 24.04 for LTS, because they will not be able to upgrade to 26.04 LTS." It's unfortunate, because that means someone on 25.04 w/ RVA20 will have to re-install 24.04 LTS to get continued support. Or, they stay stranded on 25.04 when it eventually becomes EOL. In the future, I think bumping the ISA baseline should not be done in this way. It would be better for this to happen in LTS+1 releases only, so that hardware first enabled in an interim release does not get stranded in this way again. However, given that we enabled new hardware in 25.04 that will not be supported in 25.10, we need to give those users *something*, so SRU'ing that HWE to 24.04 LTS seems like the least bad option. Hence, in principle I think this is OK for noble. Now, for plucky, I don't think this is acceptable. As noted above, this is not actually enabling new hardware. That was already done. It appears to me that the plucky upload was done to preserve the upgrade path given the version string numbers (2025.01-3ubuntu0.24.04.1 in noble unapproved is greater than 2025.01-1~0ubuntu2 in plucky). For oracular, I am also not convinced this is appropriate to SRU. Why enable another interim release that a user will ultimately be stranded on? Would they not need to later re-install to 24.04 LTS to remain supported? Or am I missing something? It also seems to me that an ubuntu-release-upgrader quirks is needed alongside this SRU so that 24.04 users that install on this newly- enabled hardware do not then upgrade to an interim, and later become stranded. My concrete requests are as follows: 1. Re-upload noble with a version of 2025.01-0ubuntu0.24.04.1. This is less than the current plucky version, and upgrades will be possible without bumping the plucky version number. 2. Re-consider oracular. I understand that the current version string becomes an issue for noble -> oracular upgrades. But, EOL is fast approaching. Could we wait it out? Or is this needed sooner? 3. Consider upgrades. I think we need to have the ability to block upgrades on RVA20 hardware before/when this lands. I am rejecting all uploads based on the above. -- 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
