When Rocky 9.6 came out 9.5 moved on the package mirror from /pub/ to /vault. We have our sources setup like so
[appstream-debuginfo]
baseurl = http://dl.rockylinux.org/pub/rocky/$releasever/AppStream/$basearch/debug/tree/
http://dl.rockylinux.org/vault/rocky/$releasever/AppStream/$basearch/debug/tree/
enabled = 1
gpgcheck = 1
gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-Rocky-9
name = Rocky Linux $releasever - appstream-debuginfo
And we have the releasever set to 9.5. This works for most repos but not for the one above. The Index of /vault/rocky/9.5/AppStream/x86_64/debug/tree/ doesn’t have a repodata directory. Compare it to 9.4 and you can see one there. Index of /vault/rocky/9.4/AppStream/x86_64/debug/tree/
Did some replication job not happen? Am I missing something?
I can see mirrors listed using https://mirrors.rockylinux.org/mirrorlist?arch=x86_64&repo=rocky-AppStream-debug-9.5 so might see if I can move us over to that if this is a known problem.
I’ve replaced my baseurl method with the mirrorlist. Seems to work!
So still having a problem here. The Appstream mirrorlist is giving a load of 404s when queried from an AWS instance. e.g. URLs given are
https://rocky-linux-us-east1.production.gcp.mirrors.ctrliq.cloud/pub/rocky//9.5/AppStream/x86_64/os/repodata/repomd.xml
Also I’ve noticed that the repodata for 9.5 in the vault is one level up to where it is for other releases
Whilst for 9.4 is in /vault/rocky/9.5/AppStream/x86_64/debug/tree/repodata/
@neil I noticed that you were able to fix a similar issue here. Would you be able to check if there’s an issue with the mirror setup with regards to being able to pin to a minor Rocky release e.g. 9.5?
Background: We create AWS images for testing on various platforms and want to control our uptake of releases without development cadence. So we need images to not automatically upgrade to the latest when it arrives.
Many thanks