@klatls ah, that's a different problem. In your case the upgrade hasn't happened at all because the resolver couldn't figure out a solution for the current selection of packages, so you're still on noble. This fix *might* help with that, but I'm not entirely sure...
The fix forces the selection of piboot-try *after* calculation of the upgrade (in PostDistUpgradeCache) rather than before (in PreDistUpgradeCache). We also move the dracut selection into PostDistUpgradeCache because in PreDistUpgradeCache it resulted in exactly the situation you've run into when piboot-try was selected too; moving both selections to PostDistUpgradeCache worked around that. So, this *might* unblock the upgrade, it might not (that other bug probably shouldn't have been marked duplicate, but I'll leave it as is until we can see whether this fixes the issue too). I've uploaded the patch, but it won't be ready for testing until it's accepted into proposed for resolute. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2151216 Title: [SRU] Force switch to piboot-try on Raspberry Pi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2151216/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
