Bug 480312

Summary: libssh2 needs libssl.so.7, which is not available.
Product: [Fedora] Fedora Reporter: Horst H. von Brand <vonbrand>
Component: opensslAssignee: Chris Weyl <cweyl>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: rawhideCC: antoalbe, antoine.gaillard13, bugzilla, cweyl, djuran, johannbg, mcepl, michal, tmraz
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: libssh2 needs libssl.so.7, which is not available.
Fixed In Version: openssl-0.9.8j-5.fc11 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-01-19 07:18:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Horst H. von Brand 2009-01-16 12:25:16 UTC
Description of problem:
Trying to link git form git here I get:

  /usr/bin/ld: warning: libssl.so.7, needed by /usr/lib64/libssh2.so.1, not found (try using -rpath or -rpath-link)
  /usr/bin/ld: warning: libcrypto.so.7, needed by /usr/lib64/libssh2.so.1, not found (try using -rpath or -rpath-link)

Broken/missing Requires: somewhere?

Version-Release number of selected component (if applicable):
libssh2-0.18-7.fc9.x86_64

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 David Juran 2009-01-16 15:32:40 UTC
Actually libssl.so.7 is available in rawhide (openssl-0.9.8g-12.fc10) and libssh2 does depend on this package... 
What exact action is it that you are trying that fails?

Comment 2 Horst H. von Brand 2009-01-16 16:42:05 UTC
Really a bug in openssl-0.9.8j-1.fc11.x86_64 (or perhaps in how yum handles updates).

Digging around, I found out that /lib64/lib{ssl,crypto}.so.7 were broken symlinks to lib{ssl,crypto}.so.0.9.8g (from the previous openssl). Fixing them up by hand got things working fine.

Comment 3 Horst H. von Brand 2009-01-16 16:43:43 UTC
*** Bug 480310 has been marked as a duplicate of this bug. ***

Comment 4 Tomas Mraz 2009-01-16 16:59:06 UTC
*** Bug 480348 has been marked as a duplicate of this bug. ***

Comment 5 Tomas Mraz 2009-01-16 17:00:53 UTC
openssl-0.9.8j-3.fc11.x86_64 which will be in the next rawhide push should hopefully fix this.

Comment 6 Matěj Cepl 2009-01-17 09:36:10 UTC
*** Bug 480386 has been marked as a duplicate of this bug. ***

Comment 7 Michal Jaegermann 2009-01-17 23:25:31 UTC
> openssl-0.9.8j-3.fc11.x86_64 which will be in the next rawhide push should
> hopefully fix this.

I just run an update from openssl-0.9.8g-12.fc10.x86_64 to openssl-0.9.8j-3.fc11.x86_64 and something _ate_ /lib64/libssl.so.7 and
/lib64/libcrypto.so.7 links.  Forcing a reinstallation of 0.9.8j-3.fc11 runs postinstall scripts and links do show up and besided they belong to that package as well.

I would suspect a cleanup phase in yum but, at least apperently, these links should not be touched.  OTOH before an update they are links to libssl.so.0.9.8g and libcrypto.so.0.9.8g respectively so maybe on an installation of a new package they are left alone and later removed as they are wrong links?  That does not sound right as postinstall is using "ln -sf ..." but maybe?

Unfortunately backing off openssl updates with "--nodeps" breaks python, and hence yum, and running an update with "just rpm" works fine - as expected.  If the theory above is right then maybe a removal of libssl.so.7 and libcrypto.so.7 in a preinstall script would help?  That should be "survivable" until the package installation will create new ones.  I am puzzled.

Comment 8 Horst H. von Brand 2009-01-18 22:26:22 UTC
Here I have the correct links (after fixing the links by hand for openssl-0.9.8j-1.fc11.x86_64, and then updating, now at openssl-0.9.8j-5.fc11.x86_64).

The links for i386 are right (I didn't fix those up by hand before).

Comment 9 Tomas Mraz 2009-01-19 07:18:38 UTC
The 0.9.8j-5.fc11 tries to reinstate the symlinks in a triggerpostun.

I've tried updating directly from 0.9.8g to 0.9.8j-5.fc11 and the links are OK, so I think it is fixed now.

Comment 10 Antoine Gaillard 2009-02-06 01:00:35 UTC
I have the same issue I'm running FC11 i686 and I have the same missing dependencies while trying to install ffmpeg. I tried to make the symlinks manually but it doesn't work.

Comment 11 Tomas Mraz 2009-02-06 08:10:38 UTC
ffmpeg is not part of Fedora repositories. The maintainers of packages in other repositories (rpmfusion and so on) have to rebuild the dependent packages themselves.