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.
DescriptionStephen Gallagher
2013-08-19 20:21:03 UTC
Description of problem:
When installing a package with a Requires: on a virtual provides, the version provided by the virtual provides: has no impact on the resolution and the depsolver ends up falling back on further techniques (such as fewest additional dependencies or shortest package name) to select the package to resolve.
Version-Release number of selected component (if applicable):
yum-3.4.3-101.el7
How reproducible:
Every time
Steps to Reproduce:
I discovered this today while debugging an issue with OpenLMI.
We added a virtual "Provides: cim-server" to the packages sblim-sfcb (giving cim-server a version of 0) and tog-pegasus (giving cim-server a version of 1).
The expectation is that installing "openlmi-providers" which "Requires: cim-server" would automatically select tog-pegasus, since it provided the highest version of cim-server (unless sblim-sfcb was also manually provided on the yum command-line).
Actual results:
The yum resolver skipped this version comparison and fell back on using the number of additional dependent packages (1 for Pegasus vs. 0 for SFCB) and selected SFCB instead.
Expected results:
When only "Requires: cim-server" is provided, we would expect it to select the higher version unless sblim-sfcb was already installed or provided on the command-line.
Additional info:
We want to encourage the use of Pegasus for OpenLMI over SFCB as it is more fully-featured. To this end, we have manually added versioning to the 'cim-server' virtual Provides:
I debugged this with James Antill today on IRC and he discovered the source of this bug and has provided a one-liner patch here: http://yum.baseurl.org/gitweb?p=yum.git;a=commitdiff;h=3eaca8456a9b8c4321a2d3facf6e1084853ef492
Please pull this patch into yum in RHEL 7.0
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.