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.

Bug 1073406

Summary: Yum depsolver doesn't compare versions of virtual provides
Product: Red Hat Enterprise Linux 6 Reporter: Karel Srot <ksrot>
Component: yumAssignee: Packaging Maintenance Team <packaging-team-maint>
Status: CLOSED ERRATA QA Contact: Karel Srot <ksrot>
Severity: high Docs Contact:
Priority: high    
Version: 6.5CC: james.antill, sgallagh, vmukhame
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: yum-3.2.29-51.el6 Doc Type: Bug Fix
Doc Text:
Cause: have several packages providing different versions of a virtual provides and install a package which requires that provides Consequence: yum's depsolver doesn't select the package with the highest version of virtual provides Fix: patch Result: yum's depsolver respects versions of virtual provides
 Story Points: ---
Clone Of: 998707 Environment:
Last Closed: 2014-10-14 04:37:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Karel Srot 2014-03-06 11:43:12 UTC 
confirmed on RHEL-6 with yum yum-3.2.29-40.el6

+++ This bug was initially created as a clone of Bug #998707 +++

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.

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.
Comment 6 errata-xmlrpc 2014-10-14 04:37:22 UTC 
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, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-1410.html