Bug 22984 – up2date install fails if multiple versions of updateable RPMs already installed

Bug 22984 - up2date install fails if multiple versions of updateable RPMs already installed

Summary:	up2date install fails if multiple versions of updateable RPMs already installed

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	up2date (Show other bugs)
Sub Component:
Version:	7.0
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Preston Brown
QA Contact:	Jay Turner
Docs Contact:

URL:
Whiteboard:
Keywords:

Duplicates:	28536 (view as bug list)
Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2000-12-29 10:38 EST by Frank Ch. Eigler
Modified:	2015-01-07 18:42 EST (History)
CC List:	3 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2001-03-13 15:30:21 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Frank Ch. Eigler 2000-12-29 10:38:21 EST

If somehow multiple versions of a ordinary updateable RPMs are installed,
up2date 2.1.7-1 can fail to recognize that the most recent version is
already installed.  In other words, during the "Removing installed packages
from list of updates..." phase, up2date appears to notice that an earlier
version of RPM foo is there (and therefore in need of update), but not that
the later version is also there (and therefore no need to update).  Then
up2date fetches the duplicate newer-version RPM, and causes a failure
during installation.

up2date should be more tolerant of the possibility of multiple generations
of the same package being installed.

Comment 1 Aleksey Nogin 2001-01-03 16:21:20 EST

I have the same problem with up2date-2.1.7-0.6.x on RedHat 6.2. In particular, I
have two versions of kernel-smp installed:
% rpm -q kernel-smp
kernel-smp-2.2.16-3
kernel-smp-2.2.14-12

and when I run up2date, it offers me to download kernel-smp-2.2.16-3

Comment 2 Andrew Bartlett 2001-01-04 05:21:49 EST

Ditto here, I had 2.2.14 and 2.2.16 kernels installed, including sources.  This
also meant that it wanted to download over 100MB, both unnecercery and
time-consuming.  (And in some places, quite expencive).

To cap it off I never got the updates installed, as I also didn't have the space
either.

Comment 3 Preston Brown 2001-02-09 00:30:13 EST

working on this.  thanks.

Comment 4 Cristian Gafton 2001-02-19 20:33:58 EST

Assigned QA to jturner

Comment 5 Preston Brown 2001-03-01 12:44:36 EST

*** Bug 28536 has been marked as a duplicate of this bug. ***

Comment 6 Preston Brown 2001-03-01 15:47:06 EST

fixed in CVS.

Comment 7 Ryan Hill 2001-03-13 15:30:17 EST

Also noticed the same problem today with a manual kernel upgrade in 7.0 from
2.2.16 to 2.2.17-14.  Both kernels are currently installed, but up2date is
apparently seeing only 2.2.16 and ignoring 2.2.17, even after up2date -p.

Comment 8 Preston Brown 2001-04-12 16:56:35 EDT

addressed in errata due out today.

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