Trying to rsync from the mirror sg.rpmdb.org does not work because the mirror has broken links:
cL+++++++++ 8.6 → /data/rocky/8.6/
The resulting main subdirectories in the root look like (note the broken symlinks or 8.3, 8.4, 8.4-RC1, 8.6):
lrwxrwxrwx. 1 ftp ftp 3 Nov 16 00:41 8 -> 8.7
lrwxrwxrwx. 1 root root 18 May 22 12:18 8.3 -> ../data/rocky/8.3/
lrwxrwxrwx. 1 root root 16 Aug 2 08:37 8.4 -> /data/rocky/8.4/
lrwxrwxrwx. 1 root root 22 May 22 12:17 8.4-RC1 -> ../data/rocky/8.4-RC1/
drwxr-xr-x. 17 ftp ftp 8192 Nov 16 15:54 8.5
lrwxrwxrwx. 1 root root 16 Aug 2 08:49 8.6 -> /data/rocky/8.6/
drwxr-xr-x. 17 ftp ftp 8192 Nov 14 11:33 8.7
lrwxrwxrwx. 1 ftp ftp 3 Jul 14 09:55 9 -> 9.0
drwxr-xr-x. 18 ftp ftp 8192 Jul 12 11:38 9.0
Now, I guess I could maybe get this to work with some of the rsync options - or then not because I want symlinks to be symlinks (to my data), not traverse each of the symlinked directory and download duplicate content for the whole directory (for the symlinks 9 and 8, obviously).
I guess this works in HTTP/HTTPS because it follows the symlinks to the right place.
Any opinions? Try to find an rsync option that keeps symlinks as symlinks but link to the right directory? I have never had to work around this problem, in many years of mirroring numerous similar repositories - so I am inclined to say something is wrong at the sg.rpmdb.org mirror.
Could not find any contact information for the mirror administrators…
Why does the mirrormanager not detect this?
Maybe it too follows the symlinks and thus is able to download the repodata file?
Edited to add more problems:
This repository is also missing all files in 8.7/AppStream/x86_64/debug/tree/repodata/ , also visible in HTTP/HTTPS:
https://sg.rpmdb.org/rocky/8.7/AppStream/x86_64/os/
The above link gives 403 Forbidden. I know that mirrormanager is supposed to crawl the repository and check repodata/repomd.xml files. Is the AppStream repo somehow special and its repomd.xml file is not considered by mirrormanager?