Quoting Barbara Pennacchi <b.pennacchi@xxxxxxxxxxx>:
To sum it up, both yums, when called upon, keep spitting this:
I had a similar problem once when I updated via yum/apt across versions.
The problem was, at least in my case, I ended up with multiple pythons
on my system. For example:
% ls /usr/bin/python*
/usr/bin/python /usr/bin/python2 /usr/bin/python2.2
(That's just an example).
Now, the first line of /usr/bin/yum is something like:
#!/usr/bin/python
Which may be pointing at the "wrong" python version. So, to get it to
work
for me, I changed that line to something like (this is from memory, so you
may have to experiment)
#!/usr/bin/python2
Anyone has ideas or pointers ? :(
Try the above; it can't hurt, and if you are lucky it may help.
I feel that somewhere, hidden or simply-not-mentioned-explicitly, there
is
a config file or something similar (environment variables?) that had been
overlooked by me and by rpm.
If my memory is correct, it was just as simple as changing the version
of python yum was using, as above... But then, my memory may be off some,
so your milage may vary...
--
Eric Rostetter
--
fedora-legacy-list mailing list
fedora-legacy-list@xxxxxxxxxx
http://www.redhat.com/mailman/listinfo/fedora-legacy-list
