Bug 23651 - "rpm -e" removes package from database even on errors
"rpm -e" removes package from database even on errors
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: rpm (Show other bugs)
7.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeff Johnson
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-01-09 09:20 EST by jlehrke
Modified: 2007-04-24 14:47 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-01-09 09:20:09 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)

  None (edit)
Description jlehrke 2001-01-09 09:20:06 EST
"rpm -e" removes the package from the database even if the package files
can not be removed due to e.g. read-only file systems. Without enforcement
(--force) it should print out the error messages and not touch the
database. To ensure a consistent system rpm must prove (e.g. by touching
the package files), that all files are removable before it removes a
package.
Comment 1 Jeff Johnson 2001-01-09 09:49:34 EST
You need to add you RO files systems to rpm configuration, something like
	mkdir -p /etc/rpm
	echp "%_netsharedpath /path/to/fs/1:/path/to/fs/2" >> /etc/rpm/macros

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