-
Bug
-
Resolution: Done-Errata
-
Major
-
CentOS Stream 10, rhel-10.0
-
dnf-4.20.0-12.el10_0
-
None
-
Important
-
rhel-swm
-
ssg_core_services
-
31
-
5
-
None
-
None
-
Approved Exception
-
-
Pass
-
Manual
-
x86_64
-
None
What were you trying to do that didn't work?
Utilize the DNF variables releasever_major and releasever_minor to construct repository URLs for EPEL.
What is the impact of this issue to you?
This is necessary because EPEL 10 has separate repos for each minor version of RHEL. RHEL users need to consume the minor version of EPEL that corresponds to the minor version of their system in order to receive compatible packages. Currently releasever_minor is not set. This will result in customers being presented with EPEL packages targeting RHEL 10.1 on RHEL 10.0 systems. Some of these packages will not be installable due to library differences or missing dependencies. It is also possible that a package is initially installable, and then future updates present dependency resolution issues that halt full system updates.
See RHEL-68034 for more details.
Please provide the package NVR for which the bug is seen:
dnf-4.20.0-11.el10
libdnf-0.73.1-7.el10
How reproducible is this bug?:
always
Steps to reproduce
python3 -c 'import dnf; print({k: v for k, v in dnf.Base().conf.substitutions.items() if k.startswith("releasever_")})'
Expected results
{'releasever_major': '10', 'releasever_minor': '0'}
Actual results
{'releasever_major': '10', 'releasever_minor': ''}
- clones
-
RHEL-74025 PackageKit fails to refresh with epel-release
-
- Closed
-
- is blocked by
-
RHEL-74025 PackageKit fails to refresh with epel-release
-
- Closed
-
- links to
-
RHBA-2024:139489 dnf bug fix and enhancement update