Bug 965695 - yum install '*/sesearch' doesn't work
yum install '*/sesearch' doesn't work
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: yum (Show other bugs)
Unspecified Unspecified
medium Severity medium
: rc
: ---
Assigned To: packaging-team-maint
Karel Srot
: Regression
Depends On:
  Show dependency treegraph
Reported: 2013-05-21 10:59 EDT by Karel Srot
Modified: 2014-10-14 00:36 EDT (History)
4 users (show)

See Also:
Fixed In Version: yum-3.2.29-57.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2014-10-14 00:36:26 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Karel Srot 2013-05-21 10:59:56 EDT
Description of problem:

# rpm -q yum
# yum install '*/sesearch'
Loaded plugins: auto-update-debuginfo, downloadonly, security
Setting up Install Process
No package */sesearch available.
Error: Nothing to do

This seems to be broken since RHEL-6.2. 

On RHEL-6.1 yum-3.4.3-86.el7.noarch it is working properly:

# yum --disablerepo=beaker\* install '*/sesearch'
Loaded plugins: product-id, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
Resolving Dependencies
--> Running transaction check
---> Package setools-console.s390x 0:3.3.7-38.el7 will be installed

According to James it was broken by the upgrade-to commands

commit 63f729d5ce3c13ae592ccd637532a5a8286718e3
Author: James Antill <james@and.org>
Date:   Wed Mar 30 18:00:08 2011 -0400

    Add update-to and upgrade-to commands, as "hidden" alias for

...as that changed returnPackagesByDep() from using .searchProvides()
to .getProvides() and the later doesn't do wildcard expansion on the
Comment 8 errata-xmlrpc 2014-10-14 00:36:26 EDT
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.


Note You need to log in before you can comment on or make changes to this bug.