what does this mean (/usr/bin/curl: /lib64/libcrypto.so.10: no version information available (required by /usr/lib64/libssl.so.10)

[Bill Davidsen]

Ranjan Maitra wrote:
> How do I fix these messages:
>
> /usr/bin/curl: /lib64/libcrypto.so.10: no version information available
> (required
> by /usr/lib64/libssh2.so.1) /usr/bin/curl: /lib64/libcrypto.so.10: no
> version information available (required
> by /usr/lib64/libssl.so.10) /usr/bin/curl: relocation
> error: /usr/lib64/libssh2.so.1: symbol EVP_aes_256_ctr, version li
>
> Alternatively:
>
> sudo yum update yum
> There was a problem importing one of the Python modules
> required to run yum. The error leading to this problem was:
>
>     /usr/lib64/libssl.so.10: symbol EVP_rc4_hmac_md5, version
> libcrypto.so.10 not defined in file libcrypto.so.10 with link time
> reference
>
> Please install a package which provides this module, or
> verify that the module is installed correctly.
>
> It's possible that the above module doesn't match the
> current version of Python, which is:
> 2.7.5 (default, May 16 2013, 13:44:12)
> [GCC 4.8.0 20130412 (Red Hat 4.8.0-2)]
>
> If you cannot solve this problem yourself, please go to
> the yum faq at:
>    http://yum.baseurl.org/wiki/Faq
>
>
> Any suggestions? I am trying to upgrade from F16->F19 using yum (lost
> cause, I know, but wanted to see how it went).
>
I have to go from 16-18, not touching 19 for a bit. Anyway, I got it to go with 
--skip-broken option and running it several times. I *think* the issue was 
originally an out-of-date repo, once the magic gets broken it tends not to be 
self-correcting.

> I have less physical access to this machine, hence I wanted to try out
> upgrading using yum first.
>
> Many thanks,
> Ranjan
>
>


-- 
Bill Davidsen <davidsen at tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot