You are not logged in.
What's wrong? I just did an apt update && apt full-upgrade && apt autoremove --purge && apt autoclean and I get this output:
Fehl:1 http://deb.devuan.org/merged chimaera-security/main amd64 chromium-l10n all 106.0.5249.91-1~deb11u1
404 Not Found [IP: 2001:4ca0:4300::1:22 80]
Fehl:2 http://deb.devuan.org/merged chimaera-security/main amd64 chromium amd64 106.0.5249.91-1~deb11u1
404 Not Found [IP: 2001:4ca0:4300::1:22 80]
Fehl:3 http://deb.devuan.org/merged chimaera-security/main amd64 chromium-common amd64 106.0.5249.91-1~deb11u1
404 Not Found [IP: 2001:4ca0:4300::1:22 80]
Fehl:4 http://deb.devuan.org/merged chimaera-security/main amd64 chromium-sandbox amd64 106.0.5249.91-1~deb11u1
404 Not Found [IP: 2001:4ca0:4300::1:22 80]
E: Fehlschlag beim Holen von http://debian.bio.lmu.de/debian-security/pool/updates/main/c/chromium/chromium-l10n_106.0.5249.91-1~deb11u1_all.deb 404 Not Found [IP: 2001:4ca0:4300::1:22 80]
E: Fehlschlag beim Holen von http://debian.bio.lmu.de/debian-security/pool/updates/main/c/chromium/chromium_106.0.5249.91-1~deb11u1_amd64.deb 404 Not Found [IP: 2001:4ca0:4300::1:22 80]
How does this address get in?:
http://debian.bio.lmu.de
Offline
cat /etc/apt/sources.list
deb http://deb.devuan.org/merged/ chimaera main non-free contrib
deb-src http://deb.devuan.org/merged/ chimaera main non-free contrib
deb http://deb.devuan.org/merged chimaera-security main contrib non-free
deb-src http://deb.devuan.org/merged chimaera-security main contrib non-free
deb http://deb.devuan.org/merged/ chimaera-updates main contrib non-free
deb-src http://deb.devuan.org/merged/ chimaera-updates main contrib non-free
deb http://deb.devuan.org/merged/ chimaera-backports main contrib non-free
deb-src http://deb.devuan.org/merged/ chimaera-backports main contrib non-free
deb http://deb.devuan.org/devuan chimaera-proposed-updates main contrib non-free
deb-src http://deb.devuan.org/devuan chimaera-proposed-updates main contrib non-free
It only occurred temporarily, now it's back to normal:
apt update && apt full-upgrade && apt autoremove --purge && apt autoclean
OK:1 http://deb.devuan.org/merged chimaera InRelease
OK:2 http://deb.devuan.org/merged chimaera-security InRelease
OK:3 http://deb.devuan.org/merged chimaera-updates InRelease
OK:4 http://deb.devuan.org/merged chimaera-backports InRelease
OK:5 http://deb.devuan.org/devuan chimaera-proposed-updates InRelease
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Alle Pakete sind aktuell.
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Paketaktualisierung (Upgrade) wird berechnet… Fertig
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Last edited by jue-gen (2022-10-02 19:50:58)
Offline
Let me drop two tidbits as a matter of background knowledge:
a) the domain name deb.devuan.org, which is the right one to use, resolves into a collection of alternative IP addresses (ipv4 and ipv6). During any apt operation, every server request will use some IP from that list, and then that server will be the one providing the response to that request.
b) the apt system has meta-information files that tells "where" (in networking sense) the packages are. For Devuan those URLs include some forked packages that are directly served from Devuan package pool mirrors, and a majority of packages that Devuan mirrors handle by means of redirect URLs, to be served by Debian's package pool mirrors.
Your reported case for example shows that chromium is not forked but retrieved via such a redirect, and apparently that redirect pin-pointed http://debian.bio.lmu.de as redirection target. I.e., the Devuan mirror that was picked offered that redirect, and evidently there was some issue with access to 2001:4ca0:4300::1:22 (aka http://debian.bio.lmu.de) at that time.
Offline
... and apparently that redirect pin-pointed http://debian.bio.lmu.de as redirection target. I.e., the Devuan mirror that was picked offered that redirect, and evidently there was some issue with access to 2001:4ca0:4300::1:22 (aka http://debian.bio.lmu.de) at that time.
Thank you for the information. Have a nice evening.
Offline