I'll mark this invalid in stonking because the ports->archive transition
happened in resolute, and anybody upgrading to stonking will have to
pass through resolute anyway (this applies to future interims and LTS'
too). So the fix is only strictly required in resolute.
Hmm, actually ... another question occurs: what happens to a fresh
resolute install (with sources pointing at archive.u.c) if they dpkg
--add-arch armhf? I have a nasty feeling that's going to break too ...
** Changed in: ubuntu-release-upgrader (Ubuntu Resolute)
Status: New => Confirmed
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Invalid
** Changed in: ubuntu-release-upgrader (Ubuntu Resolute)
Milestone: None => ubuntu-26.04.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2154822
Title:
Upgrades to resolute with armhf foreign arch fail
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/2154822/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
