On 2025-11-12 2:56 PM, Neal Gompa wrote:
We tried. If the package provided the full releasever, a lot of things would have been simpler, but there were arguments that some Red Hat tooling couldn't handle it currently.
OK. Then, can the epel repo configs do the ugly but reliable thing? metalink is set up to provide a URL to the correct places, when clients ask for it.
I don't know if this is the simplest expression, but it results in 10.0 systems getting packages built for 10.0 (and remains compatible with CentOS Stream):
metalink=https://mirrors.fedoraproject.org/metalink?repo=epel${releasever_minor:+-z}-$releasever${releasever_minor:+.}$releasever_minor&arch=$basearch -- _______________________________________________ epel-devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
