I tried to run dnf builddep sddm in the CentOS Hyperscale 9 container, but it failed because MirrorManager returned 404 errors for all the metalink requests for the Hyperscale source repos.
dnf builddep sddm
ngompa@fedora ~> podman run --rm -it quay.io/centoshyperscale/centos:stream9 bash-5.1# dnf builddep sddm enabling centos-hyperscale-source repository enabling centos-hyperscale-experimental-source repository enabling centos-hyperscale-spin-source repository enabling baseos-source repository enabling appstream-source repository enabling crb-source repository enabling extras-common-source repository enabling epel-source repository enabling epel-next-source repository CentOS Stream 9 - Hyperscale 197 kB/s | 228 kB 00:01 CentOS Stream 9 - Hyperscale - Source 50 kB/s | 102 kB 00:02 Errors during downloading metadata for repository 'centos-hyperscale-source': - Status code: 404 for https://mirrors.centos.org/metalink?repo=centos-hyperscale-sig-packages-main-9-stream&arch=source&protocol=https,http (IP: 152.19.134.142) - Status code: 404 for https://mirrors.centos.org/metalink?repo=centos-hyperscale-sig-packages-main-9-stream&arch=source&protocol=https,http (IP: 18.192.40.85) - Status code: 404 for https://mirrors.centos.org/metalink?repo=centos-hyperscale-sig-packages-main-9-stream&arch=source&protocol=https,http (IP: 18.159.254.57) Error: Failed to download metadata for repo 'centos-hyperscale-source': Cannot prepare internal mirrorlist: Status code: 404 for https://mirrors.centos.org/metalink?repo=centos-hyperscale-sig-packages-main-9-stream&arch=source&protocol=https,http (IP: 18.159.254.57) bash-5.1# exit
If I manually fix each of the repo files to use the baseurl variant instead, it works. But the metalinks are not functional. This is the case of Hyperscale, Hyperscale Experimental, and Hyperscale Spin source repos.
cc: @dcavalca @salimma
Seems to be a duplicate of #978 which has been fixed in 1.
Short summary: The metalinks are wrong.
Metadata Update from @arrfab: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.