Bug 81499 - upgrade should not put back files deliberately removed
upgrade should not put back files deliberately removed
Product: Red Hat Linux
Classification: Retired
Component: rpm (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeff Johnson
Mike McLean
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2003-01-09 17:38 EST by Neil Prockter
Modified: 2007-04-18 12:49 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-01-10 14:17:25 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Neil Prockter 2003-01-09 17:38:14 EST
Description of problem:
rpm upgrades replace files that have been deliberately removed.
For example
I remove /etc/logrotate.d/apache because I handle loging and I don't want apache
restarted every day
after upgrading logrotate the file is put back and apache gets restarted again.
this is undesirable.
I know these are trival solutions that won't scale but they'd do for me for now,
perhaps a system wide list of files never to create, or a group (say
rpmleavealone) that if a file belongs to it gets left alone (I can leave it empty)

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

How reproducible:

Steps to Reproduce:
1.remove /etc/logrotate.d/apache
2.upgrade logrotate
Actual results:
/etc/logrotate.d/apache recreated

Expected results:
/etc/logrotate.d/apache left not there

Additional info:
Comment 1 Jeff Johnson 2003-01-10 14:17:25 EST
--excludepath=<path>             skip files with leading component <path>
when upgrading. Upgrades with rpm are not (and should not imho) be
stateful and persistent in the manner you are expecting

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