On my systems /usr and /usr/local are always mounted
read/only, like they were meant to be.
The problem is that when I try to install an rpm, it may
do an incomplete install, but especially if I remove an
existing rpm, it will be removed from the database without
its files being removed from /usr.
So far, I've worked around this problem by moving
/var/lib/rpm to /usr/lib/rhs/rpm, which prevents rpm from
getting a lock on the dabase if /usr is mounted read only,
but it'd be much better if RPM checked if it has write
permissions before doing anything, and abort right away,
instead of doing half the job and bailing out later
Rpm was not designed to manage packages on file systems, some
of which are mounted read-only. Maybe some day ...
*** Bug 4098 has been marked as a duplicate of this bug. ***
rpm fails to realize it cannot write when /usr is mounted
RO and an rpm -e or rpm -U
Result: partly updated /deleted rpms that are marked as
updated/deleted in the rpm database.
rpm needs to check if it can write on a filesystem
------- Additional Comments From firstname.lastname@example.org 07/19/99 09:42 -------
This issue has been assigned to a developer for further action.
*** This bug has been marked as a duplicate of 4098 ***