Bug 7194 – does not interoperate with manual rpm or autorpm updates

Bug 7194 - does not interoperate with manual rpm or autorpm updates

Summary:	does not interoperate with manual rpm or autorpm updates

Status:	CLOSED NOTABUG

Aliases:	None

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

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

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-11-21 04:07 EST by John Bass
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	1999-11-29 10:28:24 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:

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

Groups: None (edit)

Description John Bass 1999-11-21 04:07:36 EST

up2date selects packages that have already been previously
installed by another method. If any of these packages are
selected for update in up2date, up2date fails with a message
that the package is already installed.

Comment 1 Preston Brown 1999-11-23 11:16:59 EST

up2date uses standard RPM database queries to determine the state of your
system.  It doesn't interfere with manual RPM updates or other rpm-based update
systems.

Please give a SPECIFIC example of your problem.

Comment 2 Preston Brown 1999-11-23 13:14:59 EST

the up2date "menu" of packages is built dynamically.  It should *not* include
packages that you already have installed.

I can't duplicate this behaviour here.  Please give a specific example.  Show
the output of rpm -q <packagename> and then verify that running up2date still
displays that package as available for download and installation.

Comment 3 Preston Brown 1999-11-29 10:28:59 EST

user had a corrupted RPM database from a buggy version of RPM.  Not an Update
Agent problem.

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