-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
1
-
False
-
None
-
False
-
Testable
-
-
https://pagure.io/fedora-infrastructure/issue/12178
n.b. I'm volunteering myself to work on this.
- Describe what you would like us to do:
Due to the change for EPEL 10 to temporarily use rawhide-style composes until official launch and subsequent change from `new-updates-sync` to `compose-partial-copy`, the location of the EPEL 10 repositories is now at `pub/epel/10/Everything/x86_64/os/` instead of `pub/epel/10/Everything/x86_64/`. I.e., a 'os' subdirectory now exists under the architecture.
It appears that this has resulted in scan-primary-mirror no longer finding and registering the `epel-10.X` repository mappings which were previously working, referenced here: https://src.fedoraproject.org/rpms/epel-release/blob/epel10/f/epel.repo#_6
I did notice that the `testing-epel-10.X` repos were still being shown by the mirrorlist-server--but I'm not sure if that is a red herring.
-
-
- What would you like to see done?
-
One of the following:
1. Update the scan-primary-mirror config to pick up this new path (/os/)
2. Reconfigure the manner in which epel 10 is being synchronized to go back to the old path (i.e., w/o `/os/`)
-
-
- What alternatives have you considered?
-
- It's possible this isn't actually the problem happening, and we (i've) jumped to conclusions about the root cause.
- the scan-primary-mirror config appears to seemingly support this matching, @kevin suggested it could be some stuck artifacts in MM from the previous repository's paths
- When do you need this to be done by? (YYYY/MM/DD)
before epel 10 release, afterwards it is invalid as the previous bodhi-style will be restored (so, this change is a short period of time, anyways)