[SOLVED] Update

jue-gen · 2024-08-16 07:03:55

What's going on? Since yesterday I get errors (Temporary failure resolving deb.devuan.org) and the sources are ignored. I probably just have to wait, right?
Here is my sources.list:

deb http://deb.devuan.org/merged/ daedalus main contrib non-free non-free-firmware 
deb-src http://deb.devuan.org/merged/ daedalus main contrib non-free non-free-firmware 

#Updates
deb http://deb.devuan.org/merged/ daedalus-updates main contrib non-free non-free-firmware 
deb-src http://deb.devuan.org/merged/ daedalus-updates main contrib non-free non-free-firmware 

#Security
deb http://deb.devuan.org/merged/ daedalus-security main contrib non-free non-free-firmware 
deb-src http://deb.devuan.org/merged/ daedalus-security main contrib non-free non-free-firmware 

#Proposed-Updates
deb http://deb.devuan.org/devuan/ daedalus-proposed-updates main contrib non-free 
deb-src http://deb.devuan.org/devuan/ daedalus-proposed-updates main contrib non-free 

#Backports
deb http://deb.devuan.org/merged/ daedalus-backports main contrib non-free non-free-firmware 
deb-src http://deb.devuan.org/merged/ daedalus-backports main contrib non-free non-free-firmware

Last edited by jue-gen (2024-08-16 07:07:40)

Ron · 2024-08-16 08:17:18

I got the same thing yesterday (Thursday). Just tried it again now (Fri early morning) and it updated. So yeah, sometimes this happens and you have to wait a couple of hours.

jue-gen · 2024-08-16 08:56:10

Hi Ron, you're luckier than me. It looks like this for me at the moment (German language setting):

root@rechner:~# apt update
OK:1 https://packages.mozilla.org/apt mozilla InRelease
Ign:2 http://deb.devuan.org/merged daedalus InRelease
Ign:3 http://deb.devuan.org/merged daedalus-updates InRelease
Ign:4 http://deb.devuan.org/merged daedalus-security InRelease
Ign:5 http://deb.devuan.org/devuan daedalus-proposed-updates InRelease
Ign:6 http://deb.devuan.org/merged daedalus-backports InRelease
Ign:2 http://deb.devuan.org/merged daedalus InRelease
Ign:3 http://deb.devuan.org/merged daedalus-updates InRelease
Ign:4 http://deb.devuan.org/merged daedalus-security InRelease
Ign:5 http://deb.devuan.org/devuan daedalus-proposed-updates InRelease
Ign:6 http://deb.devuan.org/merged daedalus-backports InRelease
Ign:2 http://deb.devuan.org/merged daedalus InRelease
Ign:3 http://deb.devuan.org/merged daedalus-updates InRelease
Ign:4 http://deb.devuan.org/merged daedalus-security InRelease
Ign:5 http://deb.devuan.org/devuan daedalus-proposed-updates InRelease
Ign:6 http://deb.devuan.org/merged daedalus-backports InRelease
Fehl:2 http://deb.devuan.org/merged daedalus InRelease
  Temporärer Fehlschlag beim Auflösen von »deb.devuan.org«
Fehl:3 http://deb.devuan.org/merged daedalus-updates InRelease
  Temporärer Fehlschlag beim Auflösen von »deb.devuan.org«
Fehl:4 http://deb.devuan.org/merged daedalus-security InRelease
  Temporärer Fehlschlag beim Auflösen von »deb.devuan.org«
Fehl:5 http://deb.devuan.org/devuan daedalus-proposed-updates InRelease
  Temporärer Fehlschlag beim Auflösen von »deb.devuan.org«
Fehl:6 http://deb.devuan.org/merged daedalus-backports InRelease
  Temporärer Fehlschlag beim Auflösen von »deb.devuan.org«
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Alle Pakete sind aktuell.
W: Fehlschlag beim Holen von http://deb.devuan.org/merged/dists/daedalus/InRelease Temporärer Fehlschlag beim Auflösen von »deb.devuan.org«
W: Fehlschlag beim Holen von http://deb.devuan.org/merged/dists/daedalus-updates/InRelease Temporärer Fehlschlag beim Auflösen von »deb.devuan.org«
W: Fehlschlag beim Holen von http://deb.devuan.org/merged/dists/daedalus-security/InRelease Temporärer Fehlschlag beim Auflösen von »deb.devuan.org«
W: Fehlschlag beim Holen von http://deb.devuan.org/devuan/dists/daedalus-proposed-updates/InRelease Temporärer Fehlschlag beim Auflösen von »deb.devuan.org«
W: Fehlschlag beim Holen von http://deb.devuan.org/merged/dists/daedalus-backports/InRelease Temporärer Fehlschlag beim Auflösen von »deb.devuan.org«
W: Einige Indexdateien konnten nicht heruntergeladen werden. Sie wurden ignoriert oder alte an ihrer Stelle benutzt.

alexkemp · 2024-08-16 10:38:45

My Daedalus was successfully updated this morning (3 packages updated). For the record, here is another update:

$ ~/.local/sbin/update
Hit:1 https://josm.openstreetmap.de/apt alldist InRelease
Hit:2 http://deb.devuan.org/merged daedalus InRelease
Hit:3 http://deb.devuan.org/merged daedalus-updates InRelease
Hit:4 http://deb.devuan.org/merged daedalus-security InRelease
Hit:5 http://deb.devuan.org/merged daedalus-proposed-updates InRelease
Hit:6 http://deb.devuan.org/merged daedalus-backports InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
W: https://josm.openstreetmap.de/apt/dists/alldist/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

I cannot recall a problem across the last 5 years, though there must have been a temporary problem at some point.

rolfie · 2024-08-16 11:42:08

Just done an apt update for Daedalus. Worked ok. Try again.

If it fails again check if your DNS is working alright.

# apt update
Holen:1 http://deb.devuan.org/merged daedalus InRelease [43,0 kB]
Holen:2 http://deb.devuan.org/merged daedalus-security InRelease [33,2 kB]
Holen:3 http://deb.devuan.org/merged daedalus-updates InRelease [33,4 kB]
Holen:4 http://deb.devuan.org/merged daedalus-backports InRelease [33,2 kB]
Holen:5 http://deb.devuan.org/merged daedalus-security/main amd64 Packages [178 kB]
Holen:6 http://deb.devuan.org/merged daedalus-security/main i386 Packages [176 kB]
Holen:7 http://deb.devuan.org/merged daedalus-security/main Translation-en [107 kB]
Holen:8 http://deb.devuan.org/merged daedalus-backports/main amd64 Packages [227 kB]
Holen:9 http://deb.devuan.org/merged daedalus-backports/main i386 Packages [224 kB]
Holen:10 http://deb.devuan.org/merged daedalus-backports/main Translation-en [203 kB]
Holen:11 http://deb.devuan.org/merged daedalus-backports/main i386 Contents (deb) [747 kB]
Holen:12 http://deb.devuan.org/merged daedalus-backports/main amd64 Contents (deb) [644 kB]
Holen:13 http://deb.devuan.org/merged daedalus-backports/contrib i386 Packages [5.520 B]
Holen:14 http://deb.devuan.org/merged daedalus-backports/contrib amd64 Packages [5.652 B]
Holen:15 http://deb.devuan.org/merged daedalus-backports/non-free i386 Packages [1.296 B]
Holen:16 http://deb.devuan.org/merged daedalus-backports/non-free amd64 Packages [1.648 B]
Es wurden 2.663 kB in 5 s geholt (554 kB/s).                        
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Aktualisierung für 15 Pakete verfügbar. Führen Sie »apt list --upgradable« aus, um sie anzuzeigen.

Last edited by rolfie (2024-08-16 11:43:42)

jue-gen · 2024-08-16 12:04:57

My transmission has also become slow. Maybe that's a problem with us. I mean here in Germany in Weil der Stadt.

Hi rolfie, how can i check if my DNS is working alright? Just a keyword, I can then continue searching myself.

Addendum: I get to devuan.org excellently and the answer is fast. But the subdomain deb.devuan.org refuses to work for me.

ping: http://deb.devuan.org: The name or the service is not known
ping: https://deb.devuan.org: The name or the service is not known
ping: deb.devuan.org: Temporary error during name resolution

Last edited by jue-gen (2024-08-16 13:49:08)

chris2be8 · 2024-08-16 16:20:22

The first thing to try when an update fails is host deb.devuan.org
Then ping deb.devuan.org to see if you get a response.
Then try going to http://deb.devuan.org in a browser, to see if http connctions to it work.

You may find you can only connect to some of the round robin addresses. If so temporarily putting one of the ones that works into your sources.list should get you going (preferably one that's near to you).

jue-gen · 2024-08-16 16:31:37

Hi chris2be8, thank you. This is what it looks like:

host deb.devuan.org
deb.devuan.org has address 185.38.15.84
deb.devuan.org has address 141.84.43.19
deb.devuan.org has address 147.78.194.22
deb.devuan.org has address 125.228.189.120
deb.devuan.org has address 185.178.192.43
deb.devuan.org has address 190.64.49.124
deb.devuan.org has address 67.219.104.166
deb.devuan.org has address 131.188.12.211
deb.devuan.org has address 95.216.15.86
deb.devuan.org has address 198.58.118.8
deb.devuan.org has address 195.85.215.180
deb.devuan.org has address 103.146.168.12
deb.devuan.org has address 130.225.254.116
deb.devuan.org has address 94.16.114.15
deb.devuan.org has address 185.236.240.103
deb.devuan.org has address 46.4.50.2
deb.devuan.org has address 5.161.180.234
deb.devuan.org has address 160.16.137.156
deb.devuan.org has address 106.178.112.231
deb.devuan.org has address 185.183.113.131
deb.devuan.org has address 200.236.31.1
deb.devuan.org is an alias for deb.rr.devuan.org.

ping deb.devuan.org
ping: deb.devuan.org: Temporärer Fehler bei der Namensauflösung

English: Temporary error during name resolution

Browser: http://deb.devuan.org/
Seite wurde nicht gefunden
Die Verbindung mit dem Server deb.devuan.org schlug fehl.

English: Page was not found
The connection to the server deb.devuan.org failed.

Strange and difficult for me.

chris2be8 · 2024-08-16 16:49:50

Check your /etc/resolv.conf to see what nameserver(s) you are using. You could change which you use if that's the problem.

Also try host -v deb.devuan.org to get some more info.
And host deb.rr.devuan.org in case that works for some reason.

But it works for me so I can't debug it any further.

alexkemp · 2024-08-16 18:44:38

I had a similar problem to yours & posted about it: Virgin Media blocking Open-Source Sites.

tl;dr: VM had buggered up their BGP routing & I could not reach, kde.org, devuan.org or dev1galaxy.org (all HETZNER-AS hosted sites). A useful site in situations like this is https://downforeveryoneorjustme.com/. My problem was fixed only when VM fixed their routing after I emailed them.

PS BGP routing is used to traceroute to a site:

$ traceroute devuan.org
traceroute to devuan.org (116.202.138.214), 30 hops max, 60 byte packets
 1  192.168.0.1 (192.168.0.1)  1.612 ms  2.243 ms  3.152 ms
 2  * * *
 3  nott-core-2b-ae80-650.network.virginmedia.net (81.109.166.69)  22.865 ms  23.166 ms  23.401 ms
 4  * * *
 5  eislou2-ic-1-ae3-0.network.virginmedia.net (62.254.85.145)  37.897 ms  37.283 ms  43.205 ms
 6  ae21-0.lon20.core-backbone.com (80.255.9.125)  36.841 ms  15.679 ms  22.071 ms
 7  ae1-2014.nbg40.core-backbone.com (81.95.9.14)  36.162 ms  36.527 ms  37.013 ms
 8  core-backbone.hetzner.com (81.95.15.6)  35.085 ms core-backbone.hetzner.com (5.56.20.254)  36.375 ms core-backbone.hetzner.com (81.95.15.6)  34.779 ms
 9  core11.nbg1.hetzner.com (213.239.229.161)  34.982 ms  36.123 ms core12.nbg1.hetzner.com (213.239.229.165)  35.627 ms
10  ex9k1.dc1.nbg1.hetzner.com (213.239.203.226)  34.409 ms ex9k1.dc1.nbg1.hetzner.com (213.239.203.222)  33.108 ms  40.247 ms
11  bonito.devuan.org (85.10.193.185)  37.010 ms  35.436 ms  30.039 ms
12  www.devuan.org (116.202.138.214)  36.284 ms  43.089 ms  35.657 ms

2024-08-17 update: I originally said "used in ping to trace to a site" & corrected + added an example to make it clearer.

Last edited by alexkemp (2024-08-17 07:53:53)

jue-gen · 2024-08-16 20:15:35

I replaced deb.devuan.org in the sources.list with us.deb.devuan.org and this is the result:

apt-get update
OK:1 http://us.deb.devuan.org/merged daedalus InRelease
OK:2 https://packages.mozilla.org/apt mozilla InRelease
OK:3 http://us.deb.devuan.org/merged daedalus-updates InRelease
OK:4 http://us.deb.devuan.org/merged daedalus-security InRelease
OK:5 http://us.deb.devuan.org/devuan daedalus-proposed-updates InRelease
OK:6 http://us.deb.devuan.org/merged daedalus-backports InRelease
Paketlisten werden gelesen… Fertig

There are no problems.

I replaced deb.devuan.org in the sources.list with de.deb.devuan.org and this is the result:

apt-get update
OK:1 http://de.deb.devuan.org/merged daedalus InRelease
OK:2 http://de.deb.devuan.org/merged daedalus-updates InRelease
OK:3 http://de.deb.devuan.org/merged daedalus-security InRelease
OK:4 http://de.deb.devuan.org/devuan daedalus-proposed-updates InRelease
OK:5 http://de.deb.devuan.org/merged daedalus-backports InRelease
OK:6 https://packages.mozilla.org/apt mozilla InRelease
Paketlisten werden gelesen… Fertig

No problems here either.

And I can also access http://de.deb.devuan.org/ with the browser without any problems.

Last edited by jue-gen (2024-08-16 20:39:16)

em-777 · 2024-08-16 20:39:26

I had this exact same problem. I managed to fix it by going into /etc/resolv.conf and changing the nameserver from 127.0.0.1 to 8.8.8.8.

jue-gen · 2024-08-16 20:43:06

Hi em-777,

This is the Google DNS server ...

For me here:

cat /etc/resolv.conf
# Generated by Connection Manager
nameserver ::1
nameserver 127.0.0.1

Last edited by jue-gen (2024-08-16 20:56:41)

rolfie · 2024-08-16 21:00:36

That means you are not resolving anything - nameserver ::1, nameserver 127.0.0.1 means localhost.

That kills any DNS re. internet access.

Last edited by rolfie (2024-08-16 21:06:57)

ExposeGlobalistsMadness · 2024-08-16 21:04:46

After attempting Daedalus install onto a USB to be run on a Raspberry Pi (4 or 400 series, aarch64) first by using yesterday's image, and then today's from the community's RPi trial ARM images, I too have been getting similar error responses to those shown above by jue-gen when trying sudo apt update: it was not able to resolve deb.devuan.org, although displayed in this case in the default English.

I had first run menu-config to a) enforce sudo; b) to change hostname to localhost (from the ??default devuan); c) to set compose key, and on earlier attempts another key as well; d) to set locale to a certain UTF locale (prefer not to disclose); e) to set timezone.

When trialling both images over roughly the last two days, doing $ ping deb.devuan.org repeatedly in a shell gave responses such as, "Temporary failure resolving 'deb.devuan.org'", whereas ping google.com responded ok with 0% packet loss.

Could a significant clue be that upon attempting other cli instructions, not obviously related to networking lately (I think one was an ls instruction!) during one of those USB sessions, I have been getting the response, "Unable to resolve ... localhost.localdomain". Is some daedalus package setting the host name wrong, such as menu-config?

As an aside (let's have a laugh!), perhaps agents (a man-in-the-middle?) may want to read diagnoses of our own systems to thwart us further during choice moments for them to intervene: during a post-install, before a firewall is able to be downloaded?

jue-gen · 2024-08-16 21:15:30

Hi rolfie,

you say: "That means you are not resolving anything - localhost". But why does it work with us.deb* and de.deb*? And why do I get to other pages on the net? Aren't nameserver ::1 and nameserver 127.0.0.1 just the placeholder for the ISP's IP address assignment?

ralph.ronnquist · 2024-08-16 21:16:00

Don't use connman

jue-gen · 2024-08-16 21:18:22

Hi ralph.ronnquist,

I use connman. Do you think this is the Problem? Is it better to use network-manager or wicd?

ralph.ronnquist · 2024-08-16 21:25:28

I use ifupdown on its own.

But, yes, connman apparently includes DNS caching with built-in assumption that the network world is unchanging. Not that I know much about it; for me it turned up as a debian hack when wicd was abandoned, but there may well be more history to it than that.

The easiest and best (I say) is to just use traditional network configuration with ifupdown together with wpa_supplicant and possibly its wpagui gui tool,

EDIT: start with man interfaces

jue-gen · 2024-08-16 21:39:38

Hi ralph.ronnquist,

I wouldn't have thought of anything like that. That solved my problem! Thank you very much.

Addendum:
I have uninstalled Connman. Because I use KDE Plasma almost exclusively, I have installed plasma-nm, which accesses the network manager. Yes, that's certainly not the purist option, but it's convenient for me and it works. However, I will actually have to deal with ifupdown, wpa_supplicant and wpagui. Yes, I'm also thinking about the man interfaces ;-)

Last edited by jue-gen (2024-08-17 09:28:10)

The officially official Devuan Forum!

#1 2024-08-16 07:03:55

[SOLVED] Update

#2 2024-08-16 08:17:18

Re: [SOLVED] Update

#3 2024-08-16 08:56:10

Re: [SOLVED] Update

#4 2024-08-16 10:38:45

Re: [SOLVED] Update

#5 2024-08-16 11:42:08

Re: [SOLVED] Update

#6 2024-08-16 12:04:57

Re: [SOLVED] Update

#7 2024-08-16 16:20:22

Re: [SOLVED] Update

#8 2024-08-16 16:31:37

Re: [SOLVED] Update

#9 2024-08-16 16:49:50

Re: [SOLVED] Update

#10 2024-08-16 18:44:38

Re: [SOLVED] Update

#11 2024-08-16 20:15:35

Re: [SOLVED] Update

#12 2024-08-16 20:39:26

Re: [SOLVED] Update

#13 2024-08-16 20:43:06

Re: [SOLVED] Update

#14 2024-08-16 21:00:36

Re: [SOLVED] Update

#15 2024-08-16 21:04:46

Re: [SOLVED] Update

#16 2024-08-16 21:15:30

Re: [SOLVED] Update

#17 2024-08-16 21:16:00

Re: [SOLVED] Update

#18 2024-08-16 21:18:22

Re: [SOLVED] Update

#19 2024-08-16 21:25:28

Re: [SOLVED] Update

#20 2024-08-16 21:39:38

Re: [SOLVED] Update

Board footer