Bug 79094
Summary: | rpm -e silently fails, yet still modifies the db | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Chris Ricker <chris.ricker> |
Component: | rpm | Assignee: | Jeff Johnson <jbj> |
Status: | CLOSED DEFERRED | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 8.0 | CC: | barryn |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-12-06 17:27:39 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Chris Ricker
2002-12-05 16:50:28 UTC
rpm does provide error messages, but only if -vv is supplied. The rationale is that many packages don't supply sufficient dependency information to order sufficiently correctly that a directory is removed iff empty. Configure %_netsharedpath if you wannt to use rpm with R/O mounts. It's not at all clear what should be done in this case, the current behavior, removing the package header w/o removing the file is arguably as good as any other behavior. Hmm, let me reword this. The bigger problem here is that the failed rpm -e commands silently left the system in a completely inconsistent state. rpm -e * removed the packages from the databases * removed some of the files from the system for those packages, but not others Shouldn't rpm be handling rpm -e as a transaction (ie, remove files and rpm database entries iff both can be done successfully, and if both can't be done, exit)? Now that rpm has rollback support, this should be possible to implement.... Re-opening as an RFE -- feel free to close if you don't think that makes sense.... Sure this is needed, but packaging won't support yet, hence not bothering the user needlessly with an error message. |