El 25/02/18 a las 20:46, Adrian Reber escribió:
Thanks for your report and for looking so closely at the mirrors.
The mirrorlist (https://admin.fedoraproject.org/mirrormanager/) you mentioned is, however, not really authoritative. This is a list, generated once a day, to give an overview. The actual data is generated every hour and made available via the mirrorlist/metalink interface:
$ curl 'http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-f25&ar...' # repo = updates-released-f25 arch = x86_64 country = ES http://ftp.cica.es/fedora/linux/updates/25/x86_64/ http://mirror.uv.es/mirror/fedora/linux/updates/25/x86_64/
ftp.udl.es is not returned for clients in Spain. So that seems correct:
$ curl 'http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-f26&ar...' # repo = updates-released-f26 arch = x86_64 country = ES http://ftp.cica.es/fedora/linux/updates/26/x86_64/ http://mirror.uv.es/mirror/fedora/linux/updates/26/x86_64/
But, this is not correct, because ftp.cica.es is not updated for over 2 months. Putting ftp.cica.es in CC to let them know that there mirror is stuck.
But as we are using metalinks for DNF to find updates, DNF will just skip ftp.cica.es as the checksums of the repomd.xml file on that mirror are different than specified in the metalink.
So thanks, for finding the outdated mirrors, but our tools should handle this, hopefully, so that the users will get re-directed to up to date mirrors.
Adrian
Thank you for reporting us this problem. It seems that our upstream mirror (http://archive.linux.duke.edu/) is outdated:
* http://archive.linux.duke.edu/fedora/pub/fedora/linux/updates/26/
We are synchronizing now against another server to update all packages.
Greetings.