Bitcomet: failed dependences for python although installed

deftone` · 12-20-2005, 02:59 AM

Hello. I´m trying to install BitComet from a rpm packet. This is what i get when i try to do it:

Code:

#rpm -ihv BitTorrent-4.2.2-1-Python2.3.noarch.rpm
error: Failed dependencies:
        /usr/bin/python is needed by BitTorrent-4.2.2-1
        python(abi) = 2.3 is needed by BitTorrent-4.2.2-1

But when i check if i have python installed this is what i get:

Code:

# python -V
Python 2.4.1
# which python
/usr/bin/python

if i try to force the installation with the --nodeps switch, after installation, but when I try to start bitcomet, i get this:

Code:

Traceback (most recent call last):
  File "/usr/bin/bittorrent", line 17, in ?
    from BitTorrent.platform import install_translation
ImportError: No module named BitTorrent.platform

Could anybody help me install properly and run this package? 10x.

-emil stanchev

sirclif · 12-21-2005, 11:54 AM

what does "rpm -q python" say? although i doubt this is the case, if python was not installed with rpm, then rpm will not be "aware" of it's installation. sometimes this can be done by forcing the rpm like you did with no dependencies, but if bittorrent is expecting python to be located in some location, like /usr/bin, but it's actually located in /usr/local/bin, then it will be calling something that is not there.

deftone` · 12-22-2005, 03:07 AM

Yes, python was not installed from rpm. If thats the problem, what should I do?
I asked a friend of mine and he said that I need the exact version of python, required by the bitcomet rpm, but I its kinda stupid if thats the case here.

sirclif · 12-22-2005, 10:23 AM

well, this is why a lot of people don't like rpm's. you can either:

install bittorrent from source, and try to work out any issues with being able to find python. the ./configure script will try to find it, if it can't there are things you can do to point it in the right direction

uninstall python, reinstall with rpm.

try to figure out where bittorrent is trying to look for python, and make sure the files it is trying to call at run time are where it is looking. i usually just make a symlink in the directory the program is looking that points to the actual file, but this can get ugly.

to find out where it is looking for your python executable, i would get a copy of a python rpm your distro, do '$ rpm -qlp python-xxx.rpm'. this will list all the files the rpm includes (in case you don't know -q means query the rpm, -l lists all files, and -p says to do the query on an actual rpm file, not an installed package.) from the list, which will be long, you can figure out what directory(s) the rpm would install python. then make sure that your installation is in the same place.

hope that made sense. unfortunatly, i don't think there is any real easy answer.

some distros have another layer of package managment that manage rpm's, Fedora has Yum, which will go get any dependancies that the package you're trying to install may have and installing them for you.

i use gentoo, and absolutly LOVE thier package management system...i've gone on too long.