From Bugzilla Helper: User-Agent: Mozilla/4.77 [sv] (X11; U; Linux 2.2.19-7.0.1 i686) Description of problem: On a system where openssl-0.9.5a-1 already existed, I installed openssl095a-0.9.5a-7 from beta 1. Rpm did not complain about this, and both packages live side by side. 22:16 uebn> rpm -q --whatprovides libcrypto.so.0 openssl-0.9.5a-1 openssl095a-0.9.5a-7 In particular the situation in /usr/lib is a bit confusing: 22:26 uebn> ls -l /usr/lib/libcrypto* lrwxrwxrwx 1 root root 18 Sep 9 2000 /usr/lib/libcrypto.so -> libcrypto.so.0.9.5 lrwxrwxrwx 1 root root 19 Jul 18 22:10 /usr/lib/libcrypto.so.0 -> libcrypto.so.0.9.5a -rwxr-xr-x 1 root root 908558 Apr 1 2000 /usr/lib/libcrypto.so.0.9.5 -rwxr-xr-x 1 root root 887109 Jun 25 08:01 /usr/lib/libcrypto.so.0.9.5a I'm not sure if this actually causes any problems when executing programs. But I see no point in allowing this, so I would suggest openssl095a to conflict (in the RPM sense) with openssl < 0.9.6. How reproducible: Always Steps to Reproduce: Take a system where openssl-0.9.5a is installed, and install openssl095a-0.9.5a.
This defect considered SHOULD-FIX for Fairfax.
The ldconfig symlink is normal, and I don't think we've shipped libssl.so.0.9.5 in any of our openssl packages, but adding the conflicts is a good idea -- they'll be in openssl095a-0.9.5a-11 and openssl096-0.9.6-6. Thanks!