[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: FC4



Alastair McKinley wrote:


On 20/09/06, *Robin Laing* <Robin Laing drdc-rddc gc ca <mailto:Robin Laing drdc-rddc gc ca>> wrote:

    Paul Howarth wrote:
     > Alastair McKinley wrote:
     >
     >> On 9/20/06, Paul Howarth <paul city-fan org
    <mailto:paul city-fan org>> wrote:
     >>
     >>>
     >>> Alastair McKinley wrote:
     >>> > On 9/20/06, David G. Miller <dave davenjudy org
    <mailto:dave davenjudy org>> wrote:
     >>> >>
     >>> >> "Alastair McKinley" < amckinley03 googlemail com
    <mailto:amckinley03 googlemail com>> wrote:
     >>> >>
     >>> >> >Hi Dave,
     >>> >> >
     >>> >> >Thanks for your help.  This is what I've got:
     >>> >> >
     >>> >> >
     >>> >> >[root d6173 alastair]# rpm -q --whatprovides
     >>> >> >/usr/lib/python2.4/site-packages/cElementTree.so
     >>> >> >python-elementtree-1.2.6-4
     >>> >> >[root d6173 alastair]# rpm -q --whatprovides `which python`
     >>> >> >python-2.4.3-8.FC4
     >>> >> >[root d6173 alastair]# rpm -q --whatprovides `which yum`
     >>> >> >yum-2.4.1-1.fc4
     >>> >> >[root d6173 alastair]# yum update
     >>> >> >There was a problem importing one of the Python modules
     >>> >> >required to run yum. The error leading to this problem was:
     >>> >> >
     >>> >> >   /usr/lib/python2.4/site-packages/cElementTree.so: undefined
     >>> symbol:
     >>> >> >PyUnicodeUCS4_DecodeUTF8
     >>> >> >
     >>> >> >Please install a package which provides this module, or
     >>> >> >verify that the module is installed correctly.
     >>> >> >
     >>> >> >It's possible that the above module doesn't match the
     >>> >> >current version of Python, which is:
     >>> >> >2.4.1 (#2, May  3 2005, 17:14:18)
     >>> >> >[GCC 3.2.2 20030222 (Red Hat Linux 3.2.2-5)]
     >>> >> >
     >>> >> >If you cannot solve this problem yourself, please go to
     >>> >> >the yum faq at:
     >>> >> >  http://wiki.linux.duke.edu/YumFaq
    <http://wiki.linux.duke.edu/YumFaq>
     >>> >> >
     >>> >> >
     >>> >> >
     >>> >> >I've been using yum with virtually no problems for a year.  As
     >>> far as
     >>> I
     >>> >> know
     >>> >> >(!) I havent changed any settings related to character sets, in
     >>> fact I
     >>> >> dont
     >>> >> >even know how to check.
     >>> >> >What should I do to check this out?
     >>> >> >
     >>> >> >Is it possible I have a corrupt shared object file?
     >>> >> >
     >>> >> >Thanks again,
     >>> >> >
     >>> >> >Alastair
     >>> >> >
     >>> >> >P.S. Apologies for the stupid subject line, I sent the email
     >>> before I
     >>> >> wrote
     >>> >> >anything descritive in there!
     >>> >> >
     >>> >> Sorry about the wild goose chase on the character set
    thing.  Its
     >>> >> something changeable through an environment variable so its
    something
     >>> >> that could easily be changed.  At least that would explain
    the sudden
     >>> >> change in behavior.  After I pursued this line for a little
    while it
     >>> >> dawned on me that the version of python being reported
    doesn't make
     >>> >> sense.
     >>> >>
     >>> >> It looks like the copy of python that's in yum's path has
     >>> regressed to
     >>> >> something REALLY old.  rpm -q showed python-2.4.3-8.FC4 but
    yum is
     >>> >> complaining about a problem with 2.4.1 compiled with gcc 3.2.2.
     >>> When I
     >>> >> run python from the command line on my FC4 box, I get:
     >>> >>
     >>> >> [root bend ~]# python
     >>> >> Python 2.4.3 (#1, Jun 13 2006, 16:41:18)
     >>> >> [GCC 4.0.2 20051125 (Red Hat 4.0.2-8)] on linux2
     >>> >>
     >>> >> The version number that python reports matches the version
    number for
     >>> >> the python rpm.  Also, the gcc version python was compiled with
     >>> matches
     >>> >> the current version of gcc for FC4.
     >>> >>
     >>> >> Try running python (if it will run) from the command line
    and see
     >>> what
     >>> >> it gives for a start-up message (ctrl-D to exit the python
    CLI).
     >>> If it
     >>> >> matches the error message you're getting then at least
    things are
     >>> >> consistent and you may need to just re-install python.  Not
    sure how
     >>> >> your system got into this state.  If you get the same thing
    I got
     >>> >> (matches what rpm says is the installed version) then something
     >>> really
     >>> >> strange is going on.  yum is somehow picking up an old copy of
     >>> python.
     >>> >>
     >>> >> Cheers,
     >>> >> Dave
     >>> >>
     >>> >> --
     >>> >> Politics, n. Strife of interests masquerading as a contest of
     >>> principles.
     >>> >> -- Ambrose Bierce
     >>> >>
     >>> >> --
     >>> >> fedora-list mailing list
     >>> >> fedora-list redhat com <mailto:fedora-list redhat com>
     >>> >> To unsubscribe:
    https://www.redhat.com/mailman/listinfo/fedora-list
     >>> >
     >>> >
     >>> >
     >>> >
     >>> > 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 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.
     >>> >>>>
     >>>
     >>> So which python is first in your PATH?
     >>>
     >>> $ which python
     >>>
     >>> > 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?
     >>>
     >>> Was the commercial app that you believe to be the culprit installed
     >>> using RPM?
     >>>
     >>> Paul.
     >>>
     >>> --
     >>> fedora-list mailing list
     >>> fedora-list redhat com <mailto:fedora-list redhat com>
     >>> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
     >>
     >>
     >>
     >>
     >> Hi Paul,
     >>
     >> [alastair d6173 alastair]# which python
     >> /usr/bin/python
     >> [alastair d6173 alastair]#
     >>
     >> The App I believe to be the culprit was installed with a shell
    script.  I
     >> didnt look at it closely and now its disappeared!
     >
     >
     > Earlier in the thread it appeared that root was getting python
    2.4.3 and
     > your regular user account was getting python 2.4.1. So what's the
    output
     > of "which python" when run from your regular account?
     >
     > Paul.
     >


    What do you get when you
      echo $PATH
    from a terminal window?

    If there is a "python" path listed, then you have to find where that is
    being added.  Check your local configuration files.  I do this with
       grep PATH ~/.*
    which only returns .bash_profile.

    The commercial application may work after changing the PATH if it hasn't
    written over your newer python some how.

    --
    Robin Laing

    --
    fedora-list mailing list
    fedora-list redhat com <mailto:fedora-list redhat com>
    To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
    <https://www.redhat.com/mailman/listinfo/fedora-list>



echo $PATH gives:

/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin

So there is no python path. I was about to no rpm -e --nodeps python but does rpm not use python?
Is there any other way I can force python to reinstall?

Best regards,

Alastair


This isn't getting you far is it.

I am not sure about rpm but I know yum uses python.

Taking a breath I would do an

   rpm -qa |grep python

to get a list of all the python packages installed. On my FC4 machine at work, I have 39 packages with python in the name.

Then I would run

   rpm -V {package name}

on the packages to see what packages have errors. This will narrow down what package is having issues. Them maybe you will only have to worry about repairing a few packages with force.

The last time I ran into a problem like this was moving from RH8 to FC1. The upgrade left a lot of little problems.

--
Robin Laing


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]