This question already has an answer here:
- how to get rid of arm64 in apt 4 answers
I have a very nearly fresh 16.04 installation (only installed a couple of weeks ago). Today, when I try to
$ sudo apt update $ sudo apt install openssh-server
I'm greeted with
The following NEW packages will be installed ncurses-term openssh-server openssh-sftp-server ssh-import-id 0 to upgrade, 4 to newly install, 0 to remove and 2 not to upgrade. Need to get 373 kB/633 kB of archives. After this operation, 5,136 kB of additional disk space will be used. Do you want to continue? [Y/n] Y Err:1 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 openssh-sftp-server amd64 1:7.2p2-4ubuntu2.5 404 Not Found [IP: 126.96.36.199 80] Err:2 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 openssh-server amd64 1:7.2p2-4ubuntu2.5 404 Not Found [IP: 188.8.131.52 80] E: Failed to fetch http://gb.archive.ubuntu.com/ubuntu/pool/main/o/openssh/openssh-sftp-server_7.2p2-4ubuntu2.5_amd64.deb 404 Not Found [IP: 184.108.40.206 80] E: Failed to fetch http://gb.archive.ubuntu.com/ubuntu/pool/main/o/openssh/openssh-server_7.2p2-4ubuntu2.5_amd64.deb 404 Not Found [IP: 220.127.116.11 80] E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
So obviously, I tried
sudo apt update --fix-missing, which changed nothing.
Clearly, either my system is looking for a version of the package that no longer exists, or some server administrator deleted something they shouldn't have. My money's on the former.
Does anybody have any idea how I might debug or fix this problem? I'd like to tackle the root cause, rather than just have a workaround for openssh.
The one relevant difference on my system, which may affect things, is that I have an NVIDIA SDK installed which, amongst other things, adds
arm64 architecture to apt so it can download some packages for cross-compilation. I'm using an
arm64) system. This means that when I
apt update, I get a bunch of errors relating to repositories that don't carry arm64 pacakges, like this:
E: Failed to fetch http://gb.archive.ubuntu.com/ubuntu/dists/xenial/main/binary-arm64/Packages 404 Not Found [IP: 18.104.22.168 80]
This isn't a problem (and I believe is a necessary evil of working with this SDK). I only mention it because it might have a bearing on my current issue.
The root cause of the problem is related to this, but the problem itself is different.