Bug 4201 – Can't remove a redhat package

Bug 4201 - Can't remove a redhat package

Summary:	Can't remove a redhat package

Status:	CLOSED NOTABUG

Aliases:	None

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

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Jeff Johnson
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-07-26 14:20 EDT by bmann
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:	2000-09-14 14:09:28 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)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description bmann 1999-07-26 14:20:36 EDT

I created a package with a hyphen in the release field
(package: pbs-mom version: 2.1 release: 15-RH5).  The
resulting package is called pbs-mom-2.1-15-RH5.  It
installed correctly, but when I try and remove the package,
RPM tells me the package is not installed.  I checked with
rpm -q and it says the package does exist.  I upgraded to
rpm 3.0.2-6 and it didn't fix the problem.

Comment 1 Jeff Johnson 1999-07-26 17:25:59 EDT

Try specifying rpm -e --allmatches your_package_here to uninstall
package. You also need to do "rpm --rebuilddb" after upgrading
to rpm-3.0.x.

Comment 2 bmann 1999-07-26 17:54:59 EDT

I rebuilt the database and tried rpm -e <package name> and rpm -e
-allmatches <package name> and still got the same result.
I can provide the package for testing if needed.

Comment 3 Elliot Lee 2000-02-03 12:16:59 EST

Erase it by package name only (e.g. 'pbs-mom'), not by the full package
name-version-release combo.

Comment 4 Jeff Johnson 2000-12-30 14:14:04 EST

This problem appears long since resolved.

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