Can't satisfy wxpython python2.4 dependencies - rpm database problem?

My goal was to intall Boa constructor, the Python debugger.

1) Running Fedora Core 4 (?):
$ cat /etc/redhat-release
Red Hat Enterprise Linux WS release 4 (Nahant Update 2)

2) Original version of Python was 2.2 (i think)
3) Had already installed Python 2.3 many months ago for another project
3) Recently installed Python 2.4 in preperation for wxpython (without erasing Python 2.3)

* With Python 2.4 installations, I get the following warnings:

$ sudo rpm -i -v python2.4-2.4.1-1pydotorg.i386.rpm
warning: python2.4-2.4.1-1pydotorg.i386.rpm: V3 DSA signature: NOKEY, key ID 95ccbcff
Preparing packages for installation...
python2.4-2.4.1-1pydotorg

$ sudo rpm -i -v python2.4-devel-2.4.1-1pydotorg.i386.rpm
warning: python2.4-devel-2.4.1-1pydotorg.i386.rpm: V3 DSA signature: NOKEY, key ID 95ccbcff
Preparing packages for installation...
python2.4-devel-2.4.1-1pydotorg

Are these NOKEY warnings significant? If so, how to overcome them?

$ rpm -q -p python*
warning: python2.4-2.4.1-1pydotorg.i386.rpm: V3 DSA signature: NOKEY, key ID 95ccbcff
python2.4-2.4.1-1pydotorg
python2.4-devel-2.4.1-1pydotorg

$ rpm -i -v wxPython-common-gtk2-ansi-2.8.0.1-fc4_py2.4.i386.rpm
error: Failed dependencies:
python(abi) = 2.4 is needed by wxPython-common-gtk2-ansi-2.8.0.1-fc4_py2.4.i386

Removal of the python 2.4 packages, still shows V4 is installed when issuing '$ rpm -q -p python*'

Thanks for any help!
Mike

Originally Posted by mfurnanz 1) Running Fedora Core 4 (?): $ cat /etc/redhat-release Red Hat Enterprise Linux WS release 4 (Nahant Update 2)

You are running RHEL4 (not Fedora).

$ sudo rpm -i -v python2.4-2.4.1-1pydotorg.i386.rpm warning: python2.4-2.4.1-1pydotorg.i386.rpm: V3 DSA signature: NOKEY, key ID 95ccbcff Preparing packages for installation... python2.4-2.4.1-1pydotorg Are these NOKEY warnings significant? If so, how to overcome them?

This tells that you have not installed the proper key to verify the RPM signature.

Removal of the python 2.4 packages, still shows V4 is installed when issuing '$ rpm -q -p python*'

rpm -p does not query the installed packages, but the RPMs you have effectively downloaded in the current directory. Probably you are issuing the rpm -qp command against the RPMs saved on your hard disk. Try simply 'rpm -q python'.

Anyway, it sounds strange to me the "pydotorg" suffix in the above python RPMs. Are you sure you are installing the packages built for your system?

Thanks alot for pointing out my mistakes--i'm obviously a newbie!
Since you pointed out that I have RHEL4 rather than FC4, apprently I have the wrong packages downloaded.

I have downloaded the source and will try (again) at builing and installing. I had tried this earlier and the install didn't seem to work, so I'll have to pay closer attention to the README instructions.

Will I have NOKEY problems if I build from souce? If so, where/how do I obtain these and fix it?

Also, I have a build environment which uses python 2.3 (currently installed over the system version). Should I remove 2.3 before installing 2.4, or can they co-exist? It wouldn't be too much trouble to remove 2.3 and update my build (boost) environment if necessary.

Thanks again for the quick reply and help.
Mike

Originally Posted by mfurnanz Will I have NOKEY problems if I build from souce? If so, where/how do I obtain these and fix it?

No problem with the source. The signature is generally associated to the RPM packages. When you download RPM from a website, generally you will find instructions on how to import the proper key into your PGP keys database. But I think there is no problem if you do not.

Also, I have a build environment which uses python 2.3 (currently installed over the system version). Should I remove 2.3 before installing 2.4, or can they co-exist?

Multiple versions of Python can coexist, since each version of the interpreter can find its associated library files. One can install a separate, customized version elsewhere without disturbing the pre-installed version, which may be used for many system configuration tasks, and probably shouldn't be overwritten. Be careful to not install the python executables over the pre-installed ones and change their name accordingly.

You're welcome!
Alex