I agree the dpkg issue is not the priority (and it may simply be the solution there is "document it visibly and move on").
On the u-r-u issue, there is presumably a third option: move armhf to archive.u.c as well? Obviously not a "quick" fix, but a longer term solution? If we're planning to move historical releases to archive.u.c, this is probably also something that should be considered prior to doing so. In other words, should we have a policy that "associated archs" (for some value of "associated", like register-sized variants, or instruction- subsets like amd64v3) should always be served from the same apt source? In the meantime though, option 2 also gets my vote. I'll post something on discourse about the situation. -- 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
