How to install python on clean RH7.1 install

Joal Heagney s713221 at student.gu.edu.au
Sat Jun 23 20:45:43 EDT 2001


Ken wrote:
 
> Thanks for your response.  I'm going to give up on the idea of
> replacing 1.5 for now... in the effort to get 2.1-5 up.
> 
> I'm still stuck.  I already have the rpm openssl (and its development
> library) installed, and the rpm install for python still claims that
> it's failing dependencies for the files in question.  Here is a
> snippet of the RPM install, using -vv
> 
> -----------------------
> # rpm -i -vv python2-2.1-5.i386.rpm
> ...
> D:  Requires: libutil.so.1                                  YES (db
> provides)
> D: opening db index       /var/lib/rpm/Name create mode=0x42
> D:  Requires: libcrypto.so.0.9.6                            NO
> D: package python2-2.1-5 require not satisfied: libcrypto.so.0.9.6
> D:  Requires: libcrypt.so.1                                 YES (db
> provides)
> ...
> D:  Requires: libreadline.so.4.1                            YES (db
> provides)
> D:  Requires: libssl.so.0.9.6                               NO
> D: package python2-2.1-5 require not satisfied: libssl.so.0.9.6
> ...
> D: opening db index       /var/lib/rpm/Conflictname create mode=0x42
> error: failed dependencies:
>         libcrypto.so.0.9.6   is needed by python2-2.1-5
>         libssl.so.0.9.6   is needed by python2-2.1-5
> D: ========== recording tsort relations
> D: ========== tsorting packages
> D:     0 (1,1) python2-2.1-5
> D: ========== successors only (presentation order)
> D: closed  db index       /var/lib/rpm/Depends
> D: closed  db index       /var/lib/rpm/Conflictname
> D: closed  db index       /var/lib/rpm/Providename
> D: closed  db index       /var/lib/rpm/Basenames
> D: closed  db index       /var/lib/rpm/Name
> D: closed  db index       /var/lib/rpm/Packages
> 
> -------------
> 
> You can see that it failed the dependencies for the files
> libcrypto.so.0.9.6, and libssl.so.0.9.6.
> 
> Just in case I was losing it, I checked for the RPMs the files would
> be in by running:
> 
> # rpm -qf /usr/lib/libssl.so.0.9.6
> openssl-0.9.6-3
> # rpm -qf /usr/lib/libcrypto.so.0.9.6
> openssl-0.9.6-3
> 
> ... which I'm assuming is telling me what RPMs the files exist in.  To
> double check, I ran the following:
> 
> # rpm -q openssl
> openssl-0.9.6-3
> 
> ... and verifying the openssl package gave me:
> 
> #rpm -V openssl
> 
> .. (nothing) - which I'm assuming means everything is well.
> 
> Please advise!
> 
> Thanks,
> 
> kc

*totally bewildered* Um. Have you checked to see if the libraries are on
your file system using ls? I'm suspecting that they would be. If they
are, it must be something to do with the dynamic loader, ld, but I've
never had to play with that seriously. If you get REALLY desperate, you
could always grab the source rpm and build using rpm --rebuild
python*src.rpm; rpm -U /usr/src/RPM/RPMS/i386/python*rpm.
-- 
      Joal Heagney is: _____           _____
   /\ _     __   __ _    |     | _  ___  |
  /__\|\  ||   ||__ |\  || |___|/_\|___] |
 /    \ \_||__ ||___| \_|! |   |   \   \ !



More information about the Python-list mailing list