- This topic has 17 replies, 7 voices, and was last updated Sep 6-8:26 am by andfree.
-
Posts
-
andfree
$ sudo apt-get update Get:1 http://deb.debian.org/debian buster-backports InRelease [46.7 kB] Hit:2 http://security.debian.org buster/updates InRelease Get:3 http://mirror.eu.oneandone.net/debian buster-updates InRelease [51.9 kB] Hit:4 http://la.mxrepo.com/antix/buster buster InRelease Err:5 http://ftp.gr.debian.org/debian buster InRelease Could not connect to ftp.gr.debian.org:80 (147.102.222.211). - connect (111: Connection refused) Could not connect to ftp.gr.debian.org:80 (2001:648:2000:de::211), connection timed out Fetched 98.6 kB in 32s (3,068 B/s) Reading package lists... Done W: Failed to fetch http://ftp.gr.debian.org/debian/dists/buster/InRelease Could not connect to ftp.gr.debian.org:80 (147.102.222.211). - connect (111: Connection refused) Could not connect to ftp.gr.debian.org:80 (2001:648:2000:de::211), connection timed out W: Some index files failed to download. They have been ignored, or old ones used instead.This occurs since yesterday. I don’t think it has to do with the network connection.
- This topic was modified 1 year, 8 months ago by anticapitalista. Reason: added solved
anticapitalista
I had the same. Seems like the Greek debian repo is down. Use repo-manager to choose another for Debian.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
sybok
Hi,
some of the repositories connected well, i.e. your connection is/was sufficiently working.
The last one ‘ftp.gr.debian.org’ failed to connect.
Sometimes, the repository is down for maintenance etc.
When I execute
ping ftp.gr.debian.org
and kill it by Ctrl+C after some time, I get 100% loss of packets, i.e. the repository is down indeed.
(You may verify it using web-testers “is a website down” from your browser as well.)You may wait till it is restored or change the repository to a mirror that is close(r) to your home country.
The change can be performed via Control Centre (accessible in menu-tree: “Main menu” -> ‘Applications’ -> ‘System’ -> open ‘Control Centre’ -> select ‘Software’ in left-panel -> ‘Repo Manager’).As the wise anticapitalista has already pointed out (few minutes earlier), modify the “Debian” repository only since it is the only one with the issue.
- This reply was modified 1 year, 8 months ago by sybok. Reason: Edit: emphasize Debian
- This reply was modified 1 year, 8 months ago by sybok.
Thanks for the replies. But, how can I modify only the “Debian” repository?
Anonymous
hello andfree,
under the “/etc/apt/sources.list.d” directory the repos can be edited manually.
just be careful as an update will overwrite them. could mark them read-only afterwards
so update will ask to overwrite them.an update will overwrite them
???
an update involving what?
I wouldn’t expect the lists within the sources.d directory to ever be “automagically, unexpectedly” disturbed.hey skidoo. an updated list will.
or if enabled another repo …. if the repos change in the future, if a user modifies
system files care should be taken and take notes on which has been changed.
a dist upgrade will if going between versions —
stretch to buster or buster to bullseye.I would try another mirror close by in repo manager than changing just one or two.
or try updating the next day and see if their repo is back online.sybok
Hi, if you use the Control Centre (suggested in my earlier post), it will become rather obvious.
Alternately, you can (backup and) modify the file ‘/etc/apt/sources.list.d/debian.list’ manually.
Dave
an update will overwrite them
???
an update involving what?
I wouldn’t expect the lists within the sources.d directory to ever be “automagically, unexpectedly” disturbed.Only if you answer yes during the upgrade to the question like: do you wish to change your custom file out with the package maintainers version (y/n).
Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown
Thanks for all the replies, but I’m afraid I’m not less confused now.
I would try another mirror close by in repo manager than changing just one or two.
or try updating the next day and see if their repo is back online.I try updating every day, but the problem remains. Do you mean you would try to choose another mirror from the list with national flags under the “antiX repos” tab? This doesn’t seem to fix the problem and the cause for this seems to be that the debian repos remain unchanged whatever flag I choose.
caprea
Does this not solve your problem?
Error netselect-apt could not detect fastest repo.anticapitalista
You will have to edit a file manually.
In /etc/apt/sources.list.d/debian./list change any gr to de (you will need to do this as root/sudo)
Then
sudo apt updatePhilosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
caprea
You are right. I just tried it, the fastest mirror-button only works for the antiX-list and not for debian.
You can change the mirror for debian manually by opening it with geany
sudo geany /etc/apt/sources.list.d/debian.listIn the file you see the part for” Debian Stable. Default for antiX-19 ”
It should look like this# Debian Stable. Default for antiX-19. # Use for maximum stability INSTEAD of the 'rolling' TESTING release concept. deb http://debian.otenet.gr/debian/ buster main contrib non-free deb http://security.debian.org/ buster/updates main contrib non-freeEdit:Ups, I didn’t see anti’s post.
- This reply was modified 1 year, 8 months ago by caprea.
- You must be logged in to reply to this topic.
