This URL does not resolve:
https://mirrors.centos.org/metalink?repo=centos-hyperscale-sig-packages-main-$stream&arch=source&protocol=https,http
but this (for centos-hyperscale) does:
https://mirrors.centos.org/metalink?repo=centos-hyperscale-sig-packages-main-$stream&arch=$basearch&protocol=https,http
The debuginfo metalink also works.
If I uncomment the baseURL, that does work: http://mirror.stream.centos.org/SIGs/9-stream/hyperscale/source/packages-main/
Same with centos-hyperscale-experimental-source
❯ sudo dnf --disablerepo=* --enablerepo=centos-hyperscale-source,centos-hyperscale-experimental-source list CentOS Stream 9 - Hyperscale Experimental - Source 41 kB/s | 97 kB 00:02 Errors during downloading metadata for repository 'centos-hyperscale-experimental-source': - Status code: 404 for https://mirrors.centos.org/metalink?repo=centos-hyperscale-sig-packages-experimental-9-stream&arch=source&protocol=https,http (IP: 2600:2701:4000:5211:dead:beef:fe:fed3) Error: Failed to download metadata for repo 'centos-hyperscale-experimental-source': Cannot prepare internal mirrorlist: Status code: 404 for https://mirrors.centos.org/meta
@adrian : can you see with Michel ? clearly arch=source isn't correct but how is that managed by MirrorManager ? (and so how to call it ?)
arch=source
Metadata Update from @arrfab: - Issue assigned to adrian - Issue tagged with: mirrormanager
Metadata Update from @arrfab: - Issue assigned to arrfab (was: adrian) - Issue tagged with: doc, high-gain, low-trouble
@salimma : it seems there is a way to query for possible repositories directly to MirrorManager :
curl "https://mirrors.centos.org/metalink?repo=unknown&arch=x86_64" -s | grep hyperscale # repo=centos-hyperscale-sig-packages-experimental-9-stream&arch=aarch64 # repo=centos-hyperscale-sig-packages-experimental-9-stream&arch=x86_64 # repo=centos-hyperscale-sig-packages-experimental-debug-9-stream&arch=aarch64 # repo=centos-hyperscale-sig-packages-experimental-debug-9-stream&arch=x86_64 # repo=centos-hyperscale-sig-packages-experimental-source-9-stream&arch=source # repo=centos-hyperscale-sig-packages-facebook-9-stream&arch=aarch64 # repo=centos-hyperscale-sig-packages-facebook-9-stream&arch=x86_64 # repo=centos-hyperscale-sig-packages-facebook-debug-9-stream&arch=aarch64 # repo=centos-hyperscale-sig-packages-facebook-debug-9-stream&arch=x86_64 # repo=centos-hyperscale-sig-packages-facebook-source-9-stream&arch=source # repo=centos-hyperscale-sig-packages-main-9-stream&arch=aarch64 # repo=centos-hyperscale-sig-packages-main-9-stream&arch=x86_64 # repo=centos-hyperscale-sig-packages-main-debug-9-stream&arch=aarch64 # repo=centos-hyperscale-sig-packages-main-debug-9-stream&arch=x86_64 # repo=centos-hyperscale-sig-packages-main-source-9-stream&arch=source # repo=centos-hyperscale-sig-packages-spin-9-stream&arch=aarch64 # repo=centos-hyperscale-sig-packages-spin-9-stream&arch=x86_64 # repo=centos-hyperscale-sig-packages-spin-debug-9-stream&arch=aarch64 # repo=centos-hyperscale-sig-packages-spin-debug-9-stream&arch=x86_64 # repo=centos-hyperscale-sig-packages-spin-source-9-stream&arch=source
So that means that for debug and source it should added to repo name and before 9-stream
debug
source
9-stream
Then it works with for example curl 'https://mirrors.centos.org/metalink?repo=centos-hyperscale-sig-packages-main-source-9-stream&arch=x86_64
curl 'https://mirrors.centos.org/metalink?repo=centos-hyperscale-sig-packages-main-source-9-stream&arch=x86_64
Now that I found it out, I'll directly update https://sigs.centos.org/guide to explain the MirrorManager logic
Metadata Update from @arrfab: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.