8. Solution:
For each RPM for your particular architecture, run:
where filename is the name of the RPM.
Administrators with existing databases should also move their NEXTID and *.dbb
files from /usr/tmp to /var/lib/ldap, and verify that the 'directory' setting in
/etc/openldap/slapd.conf is changed accordingly.
9. Verification:
MD5 sum Package Name
-------------------------------------------------------------------------
fa79c61565a72407db4695ef8468a482 6.1/en/os/alpha/openldap-1.2.9-6.alpha.rpm
058c4aa63710da7490f98da4b3cad53d 6.1/en/os/i386/openldap-1.2.9-6.i386.rpm
17fbdb33172a7884f56b4fc746b1b763 6.1/en/os/SRPMS/openldap-1.2.9-6.src.rpm
816fccd85990833f7c5dfb7f2dc6e0a1 6.1/en/os/sparc/openldap-1.2.9-6.sparc.rpm
fa79c61565a72407db4695ef8468a482 6.2/en/os/alpha/openldap-1.2.9-6.alpha.rpm
816fccd85990833f7c5dfb7f2dc6e0a1 6.2/en/os/sparc/openldap-1.2.9-6.sparc.rpm
17fbdb33172a7884f56b4fc746b1b763 6.2/en/os/SRPMS/openldap-1.2.9-6.src.rpm
058c4aa63710da7490f98da4b3cad53d 6.2/en/os/i386/openldap-1.2.9-6.i386.rpm
These packages are GPG signed by Red Hat, Inc. for security. Our key
is available at:
http://www.redhat.com/about/contact.html
You can verify each package with the following command:
rpm --checksig filename
If you only wish to verify that each package has not been corrupted or
tampered with, examine only the md5sum with the following command:
rpm --checksig --nogpg filename
Note that you need RPM >= 3.0 to check GnuPG keys.
10. References:
Thanks also go to Stan Bubrouski for reporting this problem.