The problem is that JetPack installed dependencies to the update system that cannot be successfully satisfied at this time, resulting in a failure of the entire update system! This was a known problem with 3.1 as well. The only way a developer can unblock system updates is to run the following two commands (on the host computer) to remove the improper multiarch configuration that JetPack installs:
sudo apt-get remove .*:arm64
sudo dpkg --remove-architecture arm64
After that, I can successfully run updates (either from the Ubuntu UI or command line).
A system can go weeks without this problem being noticed, thus it becomes a security issue as all system updates are blocked! It is NOT OK to break updates on a customer’s system.
For your reference, the issue can be observed when running the Ubuntu update ui. Launch the “Software Updater” application and the following error will be displayed:
“Failed to download repository information … Check your internet connection”
To observe the issue from the command line, run the command
sudo apt-get update
You will see many errors like the following:
“E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/xenial/main/binary-arm64/Packages 404 Not Found [IP: 126.96.36.199 80]”
My host system is an amd64 architecture machine. It cannot run arm64, at all, and as such it SHOULD NOT be set up as a multi-architecture platform supporting arm64. Even cross compilers for arm64 that run on my machine are amd64 architecture binaries. Please explain this to your installer team.
In short, again, your installer team has broken system-wide updates on host machines on which JetPack has been installed.