Bug 82060

Summary: rpm does not preserve modified binaries when upgrading packages
Product: [Retired] Red Hat Linux Reporter: Ben Elliston <bje>
Component: rpmAssignee: Jeff Johnson <jbj>
Status: CLOSED NOTABUG QA Contact: Mike McLean <mikem>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-01-17 14:37:52 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Ben Elliston 2003-01-16 23:52:26 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3; Linux)

Description of problem:
I had Amanda installed on a 7.3 system and had replaced its /usr/lib/amanda/taper program with a locally modified version.  I had expected that when upgrading to RHL 8.0, that rpm would have either skipped upgrading that package because it contains a modified binary (whose checksum does not match the installed version) or at least moved it to a .rpmsave file.  Instead, RPM upgraded Amanda and overwrite the modified binary.

Shouldn't RPM be a little friendlier in this circumstance?


Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Install a package.
2. Change a binary managed by the package (say, in /usr/bin).
3. Upgrade that package.  Notice that the modified binary is lost.

Actual Results:  The modified binary is overwritten with the corresponding one from the new package.

Expected Results:  The modified binary should have been renamed.

Additional info:

Comment 1 Jeff Johnson 2003-01-17 14:37:52 UTC
rpm does package, not file, management. That means that
files are installed from packages.

If you want to preserve your own binaries, then
uninstall the package before building your own
amanda from sources.