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: everytime Steps to Reproduce: 1.remove /etc/logrotate.d/apache 2.upgrade logrotate 3. Actual results: /etc/logrotate.d/apache recreated Expected results: /etc/logrotate.d/apache left not there Additional info:
Use --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