rsync errors in tier2 mirrors
It is possible for arch mirrors to be in an inconsistent state if rsync fails at some point. This is due to mirrors not generating their own package databases but rather copying the one from lower tier mirrors. In these cases, trying to grab a package from these mirrors may result in a 404 error due to incomplete syncing. The method described in Tier 2 requirements does not adequately protect this case.
The following code will re-run rsync if it ever fails to ensure mirrors are properly synced.
RET=1 COUNTER=100 until [[ RET -eq 0 && COUNTER -gt 0 ]]; do rsync -rtlH --safe-links --delete-after --progress -h --timeout=600 --contimeout=60 -p \ --delay-updates --no-motd --bwlimit=4096 \ --temp-dir="/tmp" \ --exclude='*.links.tar.gz*' \ --exclude='/other' \ --exclude='/sources' \ --exclude='/iso' \ 'rsync://mirror.pkgbuild.com/packages/' \ "/srv/repo" && RET=0 COUNTER=$[COUNTER-1] done;
List by speed procedure
Looking at the procedure for Mirrors#List_by_speed it seems a bit odd to me that it suggests editing the backup that was taken of the local mirror list. I would think the instructions should either suggest creating a second working copy to delete once completed or, since a backup has already been taken, just modify the mirrorlist in place rather than modifying the backup.
Sorting mirrors - Methods order
It seems to me that usingis easier and more powerful than using . What about putting it first for newcomers ?
Also, I was thinking about putting the part where you make a backup of mirrors at the beginning of this section.
Any objection ?
- Server-side ranking does not consider the user's location and the link speed between the user's computer and the servers, so rankmirrors is actually more powerful and the separate "server-side ranking" section makes sense. -- Lahwaacz (talk) 20:14, 22 June 2019 (UTC)
- I agree but has the ability to use both server side ranking and client side ranking. I planned to refactor it this way (none of the current content would be deleted):
- (Section) Sorting mirros - Make a backup - Use reflector - Client side ranking - Server side ranking
The article remarks "HTTP mirrors are faster than FTP due to persistent HTTP connection: with FTP, a new connection to server has to be established each time pacman requests a package to be downloaded, which results in a brief pause." However there aren't any FTP mirrors on the mirror list. Is this note obsolete and can be removed? --Pyfisch (talk) 17:52, 20 February 2021 (UTC)
- An argument against removing the note: there can still be FTP mirrors in internal networks. Just because there are not any public mirrors using FTP anymore does not mean that there are no mirrors using FTP.
- -- NetSysFire (talk) 17:56, 20 February 2021 (UTC)
rankmirrors does not work
The described procedure is no longer valid, as `rankmirrors` is now a symbolic link to `pacman-mirrors` ;
$ ls -lah `which rankmirrors`
lrwxrwxrwx 1 root root 23 24 jul. 22:12 /usr/bin/rankmirrors -> /usr/bin/pacman-mirrors
Trying to follow the procedure gives the following error :
rankmirrors: error: unrecognized arguments: 6 /etc/pacman.d/mirrorlist.backup
The equivalent seems to be using `pacman-mirrors`'s 'fasttrack' argument (?), e.g;
sudo pacman-mirrors -f 6
ABelliqueux, 08 Sept 2023