Red Hat Bugzilla – Bug 56173
incorrect relative symbolic links to /lib/... , /bin/..., etc.
Last modified: 2008-05-01 11:38:01 EDT
From Bugzilla Helper: User-Agent: Mozilla/5.0 (compatible; MSIE 4.01 Fucking browser) Description of problem: This bug do not belongs to some component, it is genegic one. In many rpm's there are libraries in /lib and symlinks to these libraries in /usr/lib. Links under /usr/ are done in relative form ../../lib/something instead of absolute /lib/something For some reason, at my host /usr is symlink to /opt/usr while /lib is true directory on the root fs. In this setup, symlinks like ../../lib/something points to /opt/lib/something, which is invalid. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.Set up /usr as symlink to /opt/usr 2.install, for example, pam-... rpm 3.look at libpam* symlinks at /usr/lib - they are invalid Actual Results: invalid symbolic links in /usr/lib, /usr/bin and /usr/sbin Expected Results: valid symbolic links Additional info: Proposed fix: use absolute file names while symlinking files from /lib, /bin, /sbin.
The "bug" is generic to the distro, not rpm. Yes relative symlinks are used most everywhere, as relative symlinks into a nfs mount with a different mount point name don't break.