RPM

  1. Bug #635851
  2. Comment #5

Comment 5 for bug 635851

Revision history for this message
In , Ville (ville-redhat-bugs) wrote :

(In reply to comment #3)
> Yes, on files that the sysadmin has not altered.

It does it on upgrades also for files which the sysadmin _has_ altered by changing the files' permissions.

# rpm -i noreplace-perms-1.0-1.x86_64.rpm
# ls -l /tmp/noreplace-perms
-rw-r--r-- 1 root root 4 2009-04-10 00:33 /tmp/noreplace-perms
# chown bin:bin /tmp/noreplace-perms ; chmod 400 /tmp/noreplace-perms
# ls -l /tmp/noreplace-perms
-r-------- 1 bin bin 4 2009-04-10 00:33 /tmp/noreplace-perms
# rpm -U noreplace-perms-1.1-1.x86_64.rpm
# ls -l /tmp/noreplace-perms
-rw-r----- 1 apache apache 4 2009-04-10 00:35 /tmp/noreplace-perms

> Your comment is irrelevant to your original RFE.

I disagree. To summarize differently, this RFE is about consistent behavior wrt. what happens to permissions of actual/effective (not .rpm* backups) config files on package upgrades.