Bug 20747

Summary:	--freshen fails when multiple versions of the same package are specified
Product:	[Retired] Red Hat Linux	Reporter:	Bryce McKinlay <bryce>
Component:	rpm	Assignee:	Jeff Johnson <jbj>
Status:	CLOSED RAWHIDE	QA Contact:	David Lawrence <dkl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.0	CC:	shishz
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2000-11-13 07:54:25 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.