Bug 234807 - yum 3.0.x cli skips packages to install
yum 3.0.x cli skips packages to install
Status: CLOSED NEXTRELEASE
Product: Fedora
Classification: Fedora
Component: yum (Show other bugs)
6
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
: Patch
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-04-02 05:01 EDT by Ville Skyttä
Modified: 2014-01-21 17:57 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-04-02 14:10:06 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Fix for yum 3.0.x (733 bytes, patch)
2007-04-02 05:01 EDT, Ville Skyttä
no flags Details | Diff

  None (edit)
Description Ville Skyttä 2007-04-02 05:01:35 EDT
yum 3.0.x's cli silently drops remaining packages to install if a virtual
package is listed on the command line and something providing it is already
installed.

For example:

# rpm -q --whatprovides "perl(ExtUtils::MakeMaker)"
perl-5.8.8-10.x86_64
# rpm -q seamonkey
package seamonkey is not installed
# yum install "perl(ExtUtils::MakeMaker)" seamonkey
[...]
Nothing to do

seamonkey should have been installed.

Fix attached against upstream 3.0.x branch - the code in 3.1.x looks
substantially different and I don't have a box to test this with it at the moment.
Comment 1 Ville Skyttä 2007-04-02 05:01:35 EDT
Created attachment 151409 [details]
Fix for yum 3.0.x
Comment 2 Seth Vidal 2007-04-02 14:10:06 EDT
nice catch. took me a few tries to get it to replicate

applied upstream and should come out in 3.0.5-2 in fc6
Comment 3 Paul Howarth 2007-04-05 04:42:15 EDT
FWIW, building sendmail in mock with autocache where the buildsystem has
yum-3.0.5-1.fc6 triggers this bug quite nicely (it BR's "setup >= some version",
which is already in the unpacked cache and then forgets to install most of the
rest of the buildreqs).

3.0.5-2.fc6 from updates-testing fixes it as suggested.

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