You are not logged in.
Pages: 1
I'm on a Raspberry PI 4b currently running daedalus
mike@DevuanPI4b:~> uname -a
Linux MikesPI 6.1.70 #1 SMP PREEMPT Sun Jan 7 04:13:59 CET 2024 aarch64 GNU/Linux
Since I have a talent for breaking things and the PI runs off a microSD it's relatively easy to setup a new install to upgrade rather than breaking a working install then having none.
I DLd rpi-4-devuan-daedalus-6.1.93-arm64-ext4-2025-12-08-0310.zip unzipped it and used dd to burn it to a fresh microSD.
When I tried 'apt update' I got no joy but a bunch if 'Ign:' statements for main contrib non-free non-free-firmware.
The line in sources.list was:
deb http://deb.devuan.org/merged daedalus main contrib non-free non-free-firmware
and I couldn't update until I used sed to change it to:
deb http://us.deb.devuan.org/merged daedalus main contrib non-free non-free-firmware
Has anyone else run into this or is there something flukey with my system?
Thanks,
Mike
Offline
Can confirm that this has happened to me a few times, i have had to switch back and forth between different mirrors when they stop working or the round robin gets stuck for some reason.
Offline
Thanks for the heads up.
I'll have to look into how to select/switch mirrors.
Be well,
Mike
Offline
You might want to try a Debian install converted to Devuan. Those images you download do not allow upgrades of the kernel to the latest version they are broken frozen in time at the moment of creation. This is why I did it on my Pi4 that way after fighting with trying to get it upgraded and it constantly failing to do so. You are roughly 90 revisions behind the current
.158 available in the repositories.
Offline
That's an old problem. It's not the Devuan repos, however.
The problems stem from more and more lousy ISP infrastructure set-ups. Kind of round-robin DNS name resolution doesn't work on them.
The solution is simple:
Exactly,
the same old problem with the resolution of these "round-robin" DNS names resurfaces again and again.
I had to switch from my old, trusty own DNS named server (BIND) to the typical service-provider setup and that made me unhappy again.
The only solution was and is to replace "deb.devuan.org" with somewhat "XY.deb.devuan.org" in the /etc/apt/sources.list file, replacing the XY with the nearest mirror-country-code.
I don't know what HPFM is behind all these silly ISPs.
I'm not good enough to know how the Devuan community could set up a /etc/apt/sources.list file that would remedy the situation for once and ever.
Refer to:
https://dev1galaxy.org/viewtopic.php?pid=53413#p53413
https://dev1galaxy.org/viewtopic.php?pid=55385#p55385
https://dev1galaxy.org/viewtopic.php?id=6834
Last edited by Andre4freedom (Today 10:11:03)
Offline
Pages: 1