Bug 14056
| Summary: | RPM doesn't upgrade some files in 'setup' at all. | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Pekka Savola <pekkas> |
| Component: | rpm | Assignee: | Jeff Johnson <jbj> |
| Status: | CLOSED NOTABUG | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.1 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2000-07-15 23:13:22 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: | |||
This is a feature, not a bug in rpm. For config files, if the attributes (MD5 sum, mode, perms, etc) of a file from a new package are identical to the old package, then a modified local copy of the file on disk is not changed, nor are *.rpmnew and *.rpmorig files created. |
Writing from memory as the testbox is down at the moment. I think this happened "inside" the beta3 system, ie. I was force-upgrading setup from beta3 to setup from beta3. 1) Modify some files in /etc/ a little, like profile or bashrc 2) Check that they're changed by rpm -V 3) Upgrade the respective RPM. 4) Notice that that file was _not_ upgraded (even though it was significantly changed). Also .rpm{save, orig} was not created either. Effectively, changes in the file were lost. The only way to get around that was to delete the file, and then upgrade.