Bug 20747 - --freshen fails when multiple versions of the same package are specified
Summary: --freshen fails when multiple versions of the same package are specified
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: rpm
Version: 7.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeff Johnson
QA Contact: David Lawrence
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-11-13 07:54 UTC by Bryce McKinlay
Modified: 2007-04-18 16:29 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2000-11-13 07:54:25 UTC


Attachments (Terms of Use)

Description Bryce McKinlay 2000-11-13 07:54:23 UTC
I use the --freshen command to update packages from an ftp mirror of the
redhat/updates directory. eg:

rpm --freshen -vh ftp://some.place/pub/redhat/updates/*.rpm

However, given the way some mirroring software is often configured, it is
common for the updates directory to contain multiple versions of the same
package, when more than one errata for that package has been issued. For
example:

-r-xr-xr-x    1 root     root        82181 Oct  9 18:13
usermode-1.36-3.i386.rpm
-r-xr-xr-x    1 root     root        82399 Nov  9 20:45
usermode-1.37-2.i386.rpm

When the rpm --freshen command is issued against such a directory, and rpm
determines that this package needs to be updated, an error results:

file /usr/sbin/userhelper conflicts between attemped installs of
usermode-1.37-2 and usermode-1.36-3
file /usr/share/man/man1/userinfo.1.gz conflicts between attemped installs
of usermode-1.37-2 and usermode-1.36-3

It would be nice if --freshen were smart enough to install only the newwest
version found, rather than trying to install both.

Comment 1 Jeff Johnson 2002-07-13 20:07:51 UTC
rpm-4.1 should, when given 2 versions of
the same pacakge on the command line during upgrade,
should replace the older with the newer
version.


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