Massive fallout from missing libssl.so.7 et al

[Tomas Mraz]

On Sat, 2009-01-17 at 13:33 +0000, Richard W.M. Jones wrote:
> On Fri, Jan 16, 2009 at 02:04:59PM +0100, Tomas Mraz wrote:
> > On Fri, 2009-01-16 at 13:51 +0100, Ralf Ertzinger wrote:
> > > Hi.
> > > 
> > > On Fri, 16 Jan 2009 13:46:25 +0100, Tomas Mraz wrote:
> > > 
> > > > I call ldconfig -X in the %post of openssl which should update the
> > > > cache and not remove the symlinks. Any subsequent calls to ldconfig
> > > > should not remove the symlinks - at least they do not on the system
> > > > where I tested that. So there must be someting else in play.
> > > 
> > > I manually created the two symlinks, and subsequent calls to ldconfig
> > > do not remove them, either.
> > 
> > I added a hack to create the symlinks in %post if they do not exist.
> > Hopefully that helps. I'm building openssl-0.9.8j-2.fc11 just now.
> 
> I have the -3 release installed here and it doesn't seem to work:

That's definitely weird - I'm really curious how do the links get
removed. On my local rawhide install it does not happen. Does it happen
for you on fresh install of rawhide or during updating?

> # wget
> wget: error while loading shared libraries: libcrypto.so.7: cannot open shared object file: No such file or directory
> 
> (same with other programs like git)
> 
> # rpm -q openssl
> openssl-0.9.8j-3.fc11.x86_64
> 
> # rpm -q --scripts openssl
> postinstall scriptlet (using /bin/sh):
> if [ "$(readlink /lib64/libcrypto.so.7)" != libcrypto.so.0.9.8j ] ; then
>     ln -sf libcrypto.so.0.9.8j /lib64/libcrypto.so.7 || :
> fi
> if [ "$(readlink /lib64/libssl.so.7)" != libssl.so.0.9.8j ] ; then
>     ln -sf libssl.so.0.9.8j /lib64/libssl.so.7 || :
> fi
> /sbin/ldconfig -X
> postuninstall scriptlet (using /bin/sh):
> /sbin/ldconfig -X
> postinstall scriptlet (using /bin/sh):
> /sbin/ldconfig -X
> postuninstall scriptlet (using /bin/sh):
> /sbin/ldconfig -X
Now this is really weird - it seems that there are the old scriptlets
from 0.9.8j-1.fc11 in the rpm database as well. How could that happen?
On my install it reports just the first two scriptlets.

> # ll /lib64/libcrypto.so.*
> -rwxr-xr-x 1 root root 1570656 2009-01-16 16:19 /lib64/libcrypto.so.0.9.8j
> lrwxrwxrwx 1 root root      19 2009-01-17 12:26 /lib64/libcrypto.so.8 -> libcrypto.so.0.9.8j
> 
> Anything else I need to try?
At least you could try to reinstall the 0.9.8j-3.fc11 whether it helps.
-- 
Tomas Mraz
No matter how far down the wrong road you've gone, turn back.
                                              Turkish proverb