jik:~$ rpm -q rpm rpm-4.2.2-0.7 jik:~$ rpm -q net-snmp net-snmp-5.1-3 jik:~$ rpm -q prelink prelink-0.3.0-17 jik:~$ sudo rpm --verify net-snmp prelink: /usr/sbin/snmpd: at least one of file's dependencies has changed since prelinking S.?..... /usr/sbin/snmpd prelink: /usr/sbin/snmptrapd: at least one of file's dependencies has changed since prelinking S.?..... /usr/sbin/snmptrapd jik:~$ sudo prelink /usr/sbin/snmpd /usr/sbin/snmptrapd prelink: /usr/sbin/snmptrapd: Cannot prelink against non-PIC shared library /usr/lib/librpmdb-4.2.so prelink: /usr/sbin/snmpd: Cannot prelink against non-PIC shared library /usr/lib/librpmdb-4.2.so jik:~$ sudo rpm --verify net-snmp prelink: /usr/sbin/snmpd: at least one of file's dependencies has changed since prelinking S.?..... /usr/sbin/snmpd prelink: /usr/sbin/snmptrapd: at least one of file's dependencies has changed since prelinking S.?..... /usr/sbin/snmptrapd jik:~$
Not rpm that is chatty, rather prelink -u.
See ftp://people.redhat.com/prelink/prelink.pdf for some details (e.g. plans what to do about at least one of file's dependencies has changed error with lower security). It is a rpm bug that librpmdb-4.2.so is non-PIC though. Jeff, once you fix that, please reassign the bug to me again.
OK, -fPIC on all platforms, not just where mandatory (x86_64/s390/s390x). Will be in 4.2.2-0.9 and later when built. Pong. I'm really not sure what is planned after reading your (otherwise excellent) prelink draft.
One thing planned is less secure verify mode, which will not bail if there are changed dependencies, but instead just verify that all but the prelink info are ok (when dependencies are changed, prelinking info is never used). This would make the above case quiet. Things to think about are: 1) whether it is desirable to prelink -u automatically programs/shared libraries which have been prelinked successfully before but cannot be prelinked against the changed dependencies 2) what to do about orphaned shared libraries, which were prelinked because some prelinked program required them, but that program has been removed since then and there are no users of that shared library any more. As prelink only tracks executables and shared libraries those binaries depend on (transitively), such orphaned libraries are not tracked and thus left prelinked, although their dependencies might have changed since then. In both 1) and 2) ATM this can be cured by manual prelink -u on the files in question, but the question is whether and how to do it automatically.
*** Bug 103739 has been marked as a duplicate of this bug. ***
'Red Hat Raw Hide' refers to the development tree for Red Hat Linux. Red Hat Linux is no longer supported by Red Hat, Inc. If you are still running Red Hat Linux, you are strongly advised to upgrade to a current Fedora Core release or Red Hat Enterprise Linux or comparable. Some information on which option may be right for you is available at http://www.redhat.com/rhel/migrate/redhatlinux/. Red Hat apologizes that these issues were not resolved in a more timely manner. However, we do want to make sure that important don't slip through the cracks. If these issues are still present in a current release, such as Fedora Core 5, please move these bugs to that product and version. Note that any remaining Red Hat Raw Hide bugs will be closed as 'CANTFIX' on September 30, 2006. Thanks again for your help.
This was resolved at some point.