rpm -v flags mode discrepancies on many symlinks. They are mode 755 or 644 in the package but get installed mode 777 (and it is impossible to change them to any other mode with chmod). ncurses-4.2-10 .M...... /usr/lib/libform.so.4 .M...... /usr/lib/libmenu.so.4 .M...... /usr/lib/libncurses.so.4 .M...... /usr/lib/libpanel.so.4
This bug, and the next several are really rpm anomalies, as info chmod indicates that symlinks always have permissions of 777 and that when one attempts to chmod a symlink the underlying file's permissions are changed.
see bug 528
Fixed in recent versions of rpm-2.5.x/rpm-2.90.x.
*** Bug 950 has been marked as a duplicate of this bug. *** In some packages of the Apollo release, there are symbolic links which RPM thinks should have mode lrwxr-xr-x (despite the fact that *every* symlink *always* has mode lrwxrwxrwx). See e.g. `/usr/bin/X11' in package `filesystem'. Fix: In build/files.c:add_file(), don't reset the file's mode if it is a symlink (i.e., if S_ISLNK(p->statbuf)). Also, in lib/verify.c:rpmVerifyFile(), don't verify the file's mode it it is a symlink. ------- Additional Comments From ayn2 01/25/99 22:43 ------- This is a duplicate of #528, #533 and #535
Commit pushed to master at https://github.com/openshift/origin https://github.com/openshift/origin/commit/0f50aa4f547e63ca059d45cc3be0d9a1b621efa9 Issue #333, #528 - add number to builds