RH 7.1/Fail upgrading to Python2: Why? 
Author Message
 RH 7.1/Fail upgrading to Python2: Why?

Hi,

        I did read the archives, and also find that others failed
installing Python2 through RPMs because of failed dependencies
(Personally, I need to do this because Zope 2.4 requires Python2.):

EXHIBIT A
-------------------------------------------------------
# ldconfig -v | grep cry
        libcrypt.so.1 -> libcrypt-2.2.2.so
        libcrypto.so.1 -> libcrypto.so.0.9.6
        libk5crypto.so.3 -> libk5crypto.so.3.0

# ldconfig -v | grep ssl
        libkssl.so.2 -> libkssl.so.2.0.0
        libssl.so.1 -> libssl.so.0.9.6

# rpm -Uvh --test python2-2.1-6.i386.rpm
error: failed dependencies:
        libcrypto.so.0.9.6   is needed by python2-2.1-6
        libssl.so.0.9.6   is needed by python2-2.1-6

FWIW, I also added a symlink between /usr/lib/libssl.so.0.9.6 and
/lib/libssl.so.9.6, and ran ldconfig to update its cache, with no
change.

EXHIBIT B
-------------------------------------------------------
Next, someone in this ng suggested adding openssl95a because it would
install symlinks libssl.so.0 and libcrypto.so.0... The python2 RPM
still complains:

# rpm -Uvh openssl095a-0.9.5a-9.i386.rpm

# ldconfig -v | grep ssl
        libssl.so.0 -> libssl.so.0.9.5a
        libkssl.so.2 -> libkssl.so.2.0.0
        libssl.so.1 -> libssl.so.0.9.6

# ldconfig -v | grep cry
        libcrypt.so.1 -> libcrypt-2.2.2.so
        libcrypto.so.0 -> libcrypto.so.0.9.5a
        libcrypto.so.1 -> libcrypto.so.0.9.6
        libk5crypto.so.3 -> libk5crypto.so.3.0

# rpm -Uvh --test python2-2.1-6.i386.rpm
error: failed dependencies:
        libcrypto.so.0.9.6   is needed by python2-2.1-6
        libssl.so.0.9.6   is needed by python2-2.1-6

QUESTION
------------------------------
=> Since this kind of thing happens every so often with RPM, does
anyone know where it comes from? There has to be a logical explanation
for this behavior, especially since it occurs on a clean and recently
installed host.
If the RPM database knows that a given library is available, and ld
also knows about it through its cache, what can possibly keep an RPM
complaining?

=> I see that python2-2.1-6.i386.rpm installs /usr/bin/python2 and
/usr/bin/python2.1 instead of plain "python", which I assume Zope
expects.
Can I just create a symlink from python2 to python with no
side-effects for older applications that expect to work with python1?

Puzzled
FF.



Mon, 23 Feb 2004 04:01:42 GMT  
 RH 7.1/Fail upgrading to Python2: Why?

Quote:

> Hi,

>    I did read the archives, and also find that others failed
> installing Python2 through RPMs because of failed dependencies
> (Personally, I need to do this because Zope 2.4 requires Python2.):

Have you tried recompiling from the SRPM?

--



Mon, 23 Feb 2004 04:22:54 GMT  
 RH 7.1/Fail upgrading to Python2: Why?
On Wed, 5 Sep 2001 16:22:54 -0400 (EDT), Ignacio Vazquez-Abrams

Quote:

>Have you tried recompiling from the SRPM?

No, and the RPM for Python 2.1.1 worked. The reason I asked, however,
is to understand what can possibly keep RPM to complain: If all the
required libraries are installed through RPM, and rpm -qa shows that
all is well, what's the problem? This has already happened to me in
the past, so it was an opportunity to understand the cause for such
behavior.

Thx
FF.



Mon, 23 Feb 2004 22:56:27 GMT  
 
 [ 3 post ] 

 Relevant Pages 

1. Problem installing Python2.1 on RH 7.1

2. FlagShip 4.48 and RH 7.1 (kernel 2.4.2)

3. python2.1 install problem on redhat 7.1

4. Problem Building Python2.1 on RedHat 7.1

5. no RHL 7.1 RPMs for python2.1

6. Freezing problem with shared libraries in python2.0 under RedHatLinux 7.1

7. redhat 7.1 linux upgrade of Python 1.52 to 2.0

8. PHP upgrade on RH Linux

9. Solved: problem uploading large files after RH 8.0 upgrade

10. upgrading to python2.2

11. Build Python2.1 fails on Solaris in readline, crypt

12. building python2-2.1-4.src.rpm on mdk7.2 fails

 

 
Powered by phpBB® Forum Software