Bug 17250 - rpm --upgrade fails if package list contains any installed packages
rpm --upgrade fails if package list contains any installed packages
Status: CLOSED WONTFIX
Product: Red Hat Linux
Classification: Retired
Component: rpm (Show other bugs)
6.2
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeff Johnson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-09-05 08:31 EDT by jhs28
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-09-05 08:31:43 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)

  None (edit)
Description jhs28 2000-09-05 08:31:39 EDT
rpm --upgrade seems to parse the package list in "all or nothing" mode.
That is, if the upgrade is only applied if every item in the package list
requires upgrading. If even one package in the list is up to date, then
none of the packages in the list will be upgraded.

I feel this is incorrect behavior. This behavior makes maintenance
difficult (indendent rpm -U calls for each package), and is not in
agreement with the man page.

This behavior has the potential to be a security bug if admins still use
the upgrade option instead of freshen. 

Please back port any fix to rpm version 3 machines.


Example of problem follows:

# rpm -q mpg123 make
package mpg123 is not installed
make-3.78.1-4
# rpm --upgrade mpg123-0.59r-4.i386.rpm make-3.78.1-4.i386.rpm 
package make-3.78.1-4 is already installed
# rpm -q mpg123 make
package mpg123 is not installed
make-3.78.1-4
# rpm --upgrade mpg123-0.59r-4.i386.rpm                      
# rpm -q mpg123 make
mpg123-0.59r-4
make-3.78.1-4
Comment 1 Jeff Johnson 2000-09-05 10:07:26 EDT
This is a feature, not a bug. All of rpm-3.0.x  groups packages to be
installed/updated/erased
into a trasaction set that has "all or nothing" semantics as you have observed.

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