FC4

[David G. Miller]

"Alastair McKinley" <amckinley03 at googlemail.com> wrote:

>Ok I've still got a problem I dont quite understand!
>
>So i did this:
>
>rpm -i --force ~alastair/python-2.4.3-8.FC4.i386.rpm
>
>However, python still does this:
>
>[alastair at d6173 sh]$ python Python 2.4.1 (#2, May  3 2005, 17:14:18)
>[GCC 3.2.2 20030222 (Red Hat Linux 3.2.2-5)] on linux2
>Type "help", "copyright", "credits" or "license" for more information.
>  
>
>>>>>>>
>>>>        
>>>>
>
>[alastair at d6173 sh]$ ls -l /usr/bin/python*
>-rwxr-xr-x  2 root root 3348 Jun 13 21:41 /usr/bin/python
>lrwxrwxrwx  1 root root    6 Sep 20 15:00 /usr/bin/python2 -> python
>-rwxr-xr-x  2 root root 3348 Jun 13 21:41 /usr/bin/python2.4
>[alastair at d6173 sh]$
>
>
>So the only thing that looks like it has been changed is the symlink
>/usr/bin/python2
>
>Is there another rpm command I should be using for this?
>
>Best regards,
>
>Alastair
>
Very strange.  The dates for the files are correct but the sizes are not:

[dave at bend FC6-test3]# ls -l /usr/bin/python*
-rwxr-xr-x  2 root root 5568 Jun 13 14:41 /usr/bin/python*
lrwxrwxrwx  1 root root    6 Jun 27 07:14 /usr/bin/python2 -> python*
-rwxr-xr-x  2 root root 5568 Jun 13 14:41 /usr/bin/python2.4*

You could try removing the existing copy of python (something like "rpm 
-e --nodeps python"), confirm that the files were actually removed and 
then re-install python.  I'm not sure if rpm is smart enough to detect 
that the python files currently in your /usr/bin directory aren't the 
ones from the rpm package when you either remove or install. 

The rpm verify function (rpm -V python) will do these compares if that's 
of any interest to you.  The output from running verify should be 
something like:

[root at bend ~]# rpm -V python
........C   /usr/lib/libpython2.4.so.1.0
..?......   /usr/lib/python2.4/bsddb/test/__init__.py
..?......   /usr/lib/python2.4/email/test/__init__.py
........C   /usr/lib/python2.4/lib-dynload/_bisect.so
........C   /usr/lib/python2.4/lib-dynload/_bsddb.so
...(lots of files with "........C")

If you get anything else, there's a problem but we already knew that. 

How important is the commercial package that you installed?  Does it 
have an "uninstall?"  You may need to uninstall it, get python back to 
working order and then see if there is a way to either have the package 
use your current copy of python or at least not step on the current copy.

Cheers,
Dave

-- 
Politics, n. Strife of interests masquerading as a contest of principles.
-- Ambrose Bierce