Seems the same issue on BOTH Ubuntu 22.10 and Pop!OS 22.04…
DO NOT EVER change your country for local repos if you’re on armhf or arm64…
It breaks Ubuntu 22.10 anyway (which is hardly surprising)…
I pointed mine at “Server for Australia” and it’s completely hosed my deb / apt database.
Wasn’t able to reset it to default. Tried using sed to remove “au.” from all the URLs to no great effect - because :
What happens is that when you tell “Software and Updates” to use “Server for Austraila” which is AARNET - and - the URL paths are broken because some GOBSHITE IDIOT didn’t even check if those URL paths were correct or existed! I cannot find ARM64 or binary-arm64 ANYWHERE in AARNET’s Ubuntu mirrors!
Reckon I’ll maybe try and go back to Ubuntu 22.04… but in the interim I’m also going to try to spin up a Ubuntu 22.10 amd64 VM and compare its sources.list file with my arm64 hosed pezzo di merda…
Copied 22.10 amd64 (x86_64) /etc/apt/sources.list over to my arm64 Pi4 :
sudo apt update
...
Err:4 http://archive.ubuntu.com/ubuntu kinetic/universe arm64 Packages
404 Not Found [IP: 185.125.190.36 80]
Ign:39 http://archive.ubuntu.com/ubuntu kinetic/multiverse arm64 Packages
Err:40 http://archive.ubuntu.com/ubuntu kinetic-updates/universe arm64 Packages
404 Not Found [IP: 185.125.190.36 80]
Ign:41 http://archive.ubuntu.com/ubuntu kinetic-updates/multiverse arm64 Packages
Err:42 http://archive.ubuntu.com/ubuntu kinetic-security/universe arm64 Packages
404 Not Found [IP: 185.125.190.36 80]
Ign:43 http://archive.ubuntu.com/ubuntu kinetic-security/multiverse arm64 Packages
Fetched 494 kB in 9s (52.7 kB/s)
Reading package lists... Done
E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/kinetic/universe/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80]
E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/kinetic-updates/universe/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80]
E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/kinetic-security/universe/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80]
No repos, not AU, not the main Ubuntu Archive (assume in the USA : 185.125.190.36 reverse DNS lookup resolves to actiontoad.canonical.com, and that IP address is owned by Canonical in the UK - so owned in the UK, but maybe located in the USA?).
Err:5 http://us.archive.ubuntu.com/ubuntu kinetic/main arm64 Packages
404 Not Found [IP: 91.189.91.39 80]
Ign:67 http://us.archive.ubuntu.com/ubuntu kinetic-security/main arm64 Packages
Ign:74 http://us.archive.ubuntu.com/ubuntu kinetic-security/restricted arm64 Packages
Ign:77 http://us.archive.ubuntu.com/ubuntu kinetic-security/universe arm64 Packages
Ign:84 http://us.archive.ubuntu.com/ubuntu kinetic-security/multiverse arm64 Packages
Ign:13 http://us.archive.ubuntu.com/ubuntu kinetic/restricted arm64 Packages
Ign:17 http://us.archive.ubuntu.com/ubuntu kinetic/universe arm64 Packages
Ign:25 http://us.archive.ubuntu.com/ubuntu kinetic/multiverse arm64 Packages
Err:33 http://us.archive.ubuntu.com/ubuntu kinetic-updates/main arm64 Packages
404 Not Found [IP: 91.189.91.39 80]
Ign:40 http://us.archive.ubuntu.com/ubuntu kinetic-updates/restricted arm64 Packages
Ign:43 http://us.archive.ubuntu.com/ubuntu kinetic-updates/universe arm64 Packages
Ign:50 http://us.archive.ubuntu.com/ubuntu kinetic-updates/multiverse arm64 Packages
Err:59 http://us.archive.ubuntu.com/ubuntu kinetic-backports/universe arm64 Packages
404 Not Found [IP: 91.189.91.38 80]
Err:67 http://us.archive.ubuntu.com/ubuntu kinetic-security/main arm64 Packages
404 Not Found [IP: 91.189.91.39 80]
Ign:74 http://us.archive.ubuntu.com/ubuntu kinetic-security/restricted arm64 Packages
Ign:77 http://us.archive.ubuntu.com/ubuntu kinetic-security/universe arm64 Packages
Ign:84 http://us.archive.ubuntu.com/ubuntu kinetic-security/multiverse arm64 Packages
Fetched 29.2 MB in 36s (814 kB/s)
Reading package lists... Done
E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/kinetic/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.39 80]
E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/kinetic-updates/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.39 80]
E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/kinetic-backports/universe/binary-arm64/Packages 404 Not Found [IP: 91.189.91.38 80]
E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/kinetic-security/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.39 80]
E: Some index files failed to download. They have been ignored, or old ones used instead.
That whole "Not Found [IP:....]" is a red herring and clouding the issue AFAIK, it’s NOT an issue with DNS or IP addresses - it’s 'cause the expected f–king folder path does NOT EXIST on the webserver!
I guess I should just be patient maybe? Someone hosed that folder path when rsync’ing a mirror? They’re all asleep in the nighttime on the weekend in their part of the world? Maybe I shouldn’t expect to see this resolved until it’s MONDAY morning in that locale?
Can’t be arsed fixing malformed URLs from Canonical - they need to pay me - already gave Microsoft a freebie when I fixed a shonky Python script their support people sent me…
Going back to try out Ubuntu 22.04 on Pi4…
I’ve still got Pop!OS on a thumb drive if I want to go back to that…
and going to try ddrescue for the first time “ever” (which Canonical suggest, except they DO NOT install it by default, and unintuitively, the package name in Ubuntu is NOT “ddrescue” it’s “gddrescue” - who’d a thunk it?)…
I’m so sorry I ever cheated on you “dd” - it will never happen again
Maybe I will, maybe I won’t (cheat on “dd”)…
Oh well, that didn’t work either, then Raspberry Pi Imager walked by, made eye contact and flirted with me :
Trying that now…
Fingers crossed Raspberry Pi Imager will do the trick. The /etc/fstab on that dd’d image was set correctly to use labels, not device names… The firmware on this Pi4 was updated (ALL 3 of mine) to support USB boot years ago… But when it booted it just went into a loop :
failed to open device: sdcard
...
failed to open device: sdcard
...
failed to open device: sdcard
(not the exact string - but very similar - ad nauseam)
There’s also balena or whatever it’s called…
Booting properly now - first thing I’m gonna do so I don’t waste any more of my time - ensure “apt get update” and “apt get uprade” work and there are no dead repos or crappy malformed URLs in the vendor supplied config (/etc/apt/sources.list)…
It’s still 22.10 I’m trying again - I didn’t tell it where I was and left it defaulting to New York - and then I’ll see what happens…
The correct form of the repo URL should be ports.ubuntu.com - if I’d only known that I could have used sed to search and replace, but because I’d let it (the previous 22.10 install) know I was in Australia, it POINT BLANK refused to let me reset it back again to the default (worldwide) - even though some idiot “published” that URL that had a non-existent path (NO binary-arm64 folder!).
root@uc-ntu-arm64:~# cat /etc/apt/sources.list
# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.
deb http://ports.ubuntu.com/ubuntu-ports/ kinetic main restricted
# deb-src http://ports.ubuntu.com/ubuntu-ports/ kinetic main restricted
## Major bug fix updates produced after the final release of the
## distribution.
deb http://ports.ubuntu.com/ubuntu-ports/ kinetic-updates main restricted
# deb-src http://ports.ubuntu.com/ubuntu-ports/ kinetic-updates main restricted
## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
deb http://ports.ubuntu.com/ubuntu-ports/ kinetic universe
# deb-src http://ports.ubuntu.com/ubuntu-ports/ kinetic universe
deb http://ports.ubuntu.com/ubuntu-ports/ kinetic-updates universe
# deb-src http://ports.ubuntu.com/ubuntu-ports/ kinetic-updates universe
## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://ports.ubuntu.com/ubuntu-ports/ kinetic multiverse
# deb-src http://ports.ubuntu.com/ubuntu-ports/ kinetic multiverse
deb http://ports.ubuntu.com/ubuntu-ports/ kinetic-updates multiverse
# deb-src http://ports.ubuntu.com/ubuntu-ports/ kinetic-updates multiverse
## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
deb http://ports.ubuntu.com/ubuntu-ports/ kinetic-backports main restricted universe multiverse
# deb-src http://ports.ubuntu.com/ubuntu-ports/ kinetic-backports main restricted universe multiverse
deb http://ports.ubuntu.com/ubuntu-ports/ kinetic-security main restricted
# deb-src http://ports.ubuntu.com/ubuntu-ports/ kinetic-security main restricted
deb http://ports.ubuntu.com/ubuntu-ports/ kinetic-security universe
# deb-src http://ports.ubuntu.com/ubuntu-ports/ kinetic-security universe
deb http://ports.ubuntu.com/ubuntu-ports/ kinetic-security multiverse
# deb-src http://ports.ubuntu.com/ubuntu-ports/ kinetic-security multiverse
On this instance - I’m going to FORCE it to continue to use the US site at ports.ubuntu.com (but will continue to use Aussie mirrors for my x86_64 instances).
Still utterly broken - won’t let me install Synergy 'cause :
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
synergy : Depends: libgdk-pixbuf2.0-0 (>= 2.22.0) but it is not going to be installed
Depends: libssl1.1 (>= 1.1.0) but it is not installable
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
beyond fixing… Of course there’s no “libssl1” that’s deprecated GARBAGE everyone should be on libssl3 - so it’s not Canonical’s fault - it’s F-CKING Synergy! No Wayland support, no SSL3 (and the FIRST thing I do when I install synergy is DISABLE SSL because it slows the piece of crap down - and I’ve asked if this can be turned off by default - but no answer)… FFS - I’m running Synergy only on my LAN over ETHERNET (it’s too sluggish to even cope with good WiFi) - so I’m hardly going to worry about f–king SSL! If someone’s on my LAN trying to snoop on me - SSL is the LEAST of my worries - I’ll be grabbing my can of pepper spray and my baseball bat out of the bucket with the softball and mitt, and doing a patrol around my house!
So : going to try the Raspberry Pi Image Writer with Ubuntu 22.04 for arm64 next… But I know what to do next time Buntie screws up their configuration - use the “pool.ubuntu.com” URL in my sources.list…
(but still not completely - fixed with sudo apt install -f)
sudo apt install -f
This fixes the 2nd failed dependancy (pixbuf) - but it cannot fix the libssl dependancy, because Canonical (and most big vendors) have dropped legacy support for libssl1 - EVERYBODY (except Symless) should be on libssl3… They (Symless) are also suggesting trying a beta of version 3 of their product, and this “product” even has libssl3 in the f–king file download name (on Linux)! So they know there’s a problem but they’re not interested in fixing it in the “Production” version of the software 1.x - and there’s no armhf or arm64 version of Synergy 3 to download anyway…
Now I have synergy, but it’s an ugly kludge, because one of the kludgiest companies that sell software mostly to the OSS market, can’t get off their arses and fix their crap…
See if this itself was open source, I wouldn’t be that bothered, but I paid for a “Pro” license for this amateurish hobbiest grade software…
I looked up barrier. It says it is a fork of an early version of synergy, before it went commercial.
Last update was a year ago … that sounds mildly active… perhaps it just works without constant fixes.
