Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
As of writing, epel-release-8-8.el8.noarch is currently in both, epel and epel-testing, due to recent stable push (and not all mirrors being up-to-date yet).
$ dnf download --releasever=8 --resolve --alldeps --enablerepo=epel --enablerepo=epel-testing --destdir=/tmp/epel8 --arch=x86_64,noarch epel-release
Last metadata expiration check: 0:17:12 ago on Sun Jan 5 12:40:05 2020.
Error in resolve of packages:
epel-release-8-8.el8.noarch
epel-release-8-8.el8.noarch
Problem: cannot install both epel-release-8-8.el8.noarch and epel-release-8-8.el8.noarch
- conflicting requests
$
Removal of '--enablerepo=epel-testing' works around this issue.
Version-Release number of selected component (if applicable):
yum-4.0.9.2-5.el8.noarch
How reproducible:
Always, see above.
Actual results:
dnf treats identical package in two repositories (testing/stable) as conflicting request.
Expected results:
dnf not treat identical packages in two repositories (testing/stable) as conflicting request.
It will not, its set for RHEL 8.3.
Once there is a specific version the "Fixed In Version" field of this bz will be filled with appropriate nevra.
Thank you for patience.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (yum bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHEA-2020:4510
Description of problem: As of writing, epel-release-8-8.el8.noarch is currently in both, epel and epel-testing, due to recent stable push (and not all mirrors being up-to-date yet). $ dnf download --releasever=8 --resolve --alldeps --enablerepo=epel --enablerepo=epel-testing --destdir=/tmp/epel8 --arch=x86_64,noarch epel-release Last metadata expiration check: 0:17:12 ago on Sun Jan 5 12:40:05 2020. Error in resolve of packages: epel-release-8-8.el8.noarch epel-release-8-8.el8.noarch Problem: cannot install both epel-release-8-8.el8.noarch and epel-release-8-8.el8.noarch - conflicting requests $ Removal of '--enablerepo=epel-testing' works around this issue. Version-Release number of selected component (if applicable): yum-4.0.9.2-5.el8.noarch How reproducible: Always, see above. Actual results: dnf treats identical package in two repositories (testing/stable) as conflicting request. Expected results: dnf not treat identical packages in two repositories (testing/stable) as conflicting request.