What were you trying to do that didn't work?

With commit https://github.com/rpm-software-management/dnf/commit/2c1a38875e94353b0ff58b423340aca6441521ab , dnf split releasever into releasever-major and releasever-minor, and epel also use them. However, rpm-ostree cannot parse these two variables during rpm-ostree install, and the execution exits.

What is the impact of this issue to you?

If epel-release is installed, then rpm-ostree install cannot install any pkg.

Please provide the package NVR for which the bug is seen:

rpm-ostree-2025.8-1.el10.x86_64

Distro: RHEL-10.1-20250513.3

How reproducible is this bug?:

always

Steps to reproduce

1. rpm-ostree install stress

Expected results

rpm-ostree can parse releasever_major and releasever_minor to continue the install process.

Actual results

rpm-ostree install stress
Checking out tree 05ad6f1... done
Enabled rpm-md repositories: beaker-harness beaker-tasks rcm-tools-rhel-10-baseos-rpms rcm-tools-rhel-10-server-optional-rpms RHEL-10.1-20250513.3-BaseOS RHEL-10.1-20250513.3-AppStream RHEL-10.1-20250513.3-CRB beaker-tasks beaker-AppStream beaker-BaseOS beaker-CRB beaker-HighAvailability beaker-NFV beaker-RT beaker-SAP beaker-SAPHANA epel
Updating metadata for 'epel'... done
error: Updating rpm-md repo 'epel': Failed to download gpg key for repo 'epel': Curl error (37): Could not read a file:// file for file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-$releasever_major [Couldn't open file /etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-$releasever_major]