On UBI 10.0, the EPEL repo configuration will provide packages built for
10.1. I don't know if that's a bug in the repo definition, or in the
redhat-release package, but it seems like it must be one of the two.
To reproduce the problem, I'm running a UBI 10.0 container image:
$ podman run -it --rm ubi:10.0 /bin/bash
# cat /etc/redhat-release
Red Hat Enterprise Linux release 10.0 (Coughlan)
In that image, the redhat-release package sets "releasever" to "10"
# rpm -q --provides redhat-release
...
system-release(releasever) = 10
system-release(releasever_major) = 10
system-release(releasever_minor) = 0
When releasever is set to "10" and releasever_minor is set, the metalink
url is set to request "epel-z-10"
# dnf config-manager --dump epel | grep metalink
metalink =
https://mirrors.fedoraproject.org/metalink?repo=epel-z-10&arch=x86_64
The repo "epel-z-10" provides content built for 10.1:
# curl
'https://mirrors.fedoraproject.org/metalink?repo=epel-z-10&arch=x86_64'
| grep 'https.*umich'
<url protocol="https" type="https" location="US"
preference="83">https://mirror.its.umich.edu/epel/10.1/Everything/x86_64/repodata/repomd.xml</url>
If I set releasever to 10.0 via a command line option, then the metalink
url is set to request "epel-z-10.0"
# dnf --setopt releasever=10.0 config-manager --dump epel | grep metalink
metalink =
https://mirrors.fedoraproject.org/metalink?repo=epel-z-10.0&arch=x86_64
The repo "epel-z-10.0" provides content build for 10.0, which seems like
the correct outcome.
# curl
'https://mirrors.fedoraproject.org/metalink?repo=epel-z-10.0&arch=x86_64'
| grep 'https.*umich'
<url protocol="https" type="https" location="US"
preference="89">https://mirror.its.umich.edu/epel/10.0/Everything/x86_64/repodata/repomd.xml</url>
So, I'd think that either the redhat-release package should provide
"system-release(releasever) = 10.0", or the epel repo definition should
detect and append the minor version in the URL (but that seems really
really ugly).
--
_______________________________________________
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
