If I can make a suggestion, how about redirecting[1] all arm64 ports.u.c 
traffic to a.u.c? I am not an expert on APT; I'm sure, I've read what `apt 
update` and `apt upgrade` do, but have forgotten most of it, but from looking 
at the tree of a.u.c, it looks like redirecting 
/ubuntu/dists/resolute/Contents-arm64.gz and 
/ubuntu/dists/resolute/{main,restricted,...}/binary-arm64/ to their 
counterparts on a.u.c could be a cheap (and more sustainable) way of hiding the 
fact that arm64 packages are no longer served from ports. Perhaps it could look 
like this --- don't know if ports is actually powered by Apache, but there must 
be equivalents in other HTTP servers, I'm sure:
```
RedirectMatch "/(ubuntu/dists/resolute/.*arm64.*)" 
"http://archive.ubuntu.com/$1";
```
That way the actual arm64 traffic goes to a.u.c. That could also help during 
the transition phase.

As for the decision on what to do during an upgrade, I think `dpkg
--print-foreign-architectures` could be queried; if it returns anything
other than a newline character, additional action needs to be taken,
e.g. @utkarsh's option 2 is only relevant *when* foreign architectures
are enabled.

In general I think @utkarsh summed it up rather nicely. I believe that,
in the future, *every* installation should just create sources stanzas
pinned to the primary DPKG architecture, so the first half of option 2.

[1] https://httpd.apache.org/docs/2.4/mod/mod_alias.html#redirectmatch

-- 
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

Reply via email to