I tried downloading whatever version of yum (along with anything else that looked "yummy") from here :
http://ftp.us.unixeria.com/fedora/li...4/os/Packages/

[root@skye yum]# rpm -i yum-3.2.28-5.fc14.noarch.rpm
package yum-3.2.28-5.fc14.noarch is already installed
[root@skye yum]# rpm -e yum
error: Failed dependencies:
yum is needed by (installed) python-meh-0.10-2.fc14.noarch
yum >= 3.0 is needed by (installed) PackageKit-yum-plugin-0.6.12-2.fc14.x86_64
yum >= 3.0 is needed by (installed) yum-langpacks-0.1.5-3.fc14.noarch
yum >= 3.2.23-10 is needed by (installed) createrepo-0.9.8-5.fc14.noarch
yum is needed by (installed) setroubleshoot-3.0.25-1.fc14.x86_64
yum is needed by (installed) anaconda-yum-plugins-1:1.0-5.fc12.noarch
yum >= 3.2.27 is needed by (installed) yum-utils-1.1.28-1.fc14.noarch
yum >= 3.2.19 is needed by (installed) PackageKit-yum-0.6.12-2.fc14.x86_64
yum >= 3.0 is needed by (installed) yum-presto-0.6.2-2.fc14.noarch
yum >= 2.9.2 is needed by (installed) anaconda-14.22-1.fc14.x86_64
[root@skye yum]# rpm -F yum-3.2.28-5.fc14.noarch.rpm
[root@skye yum]# rpm -F yum-metadata-parser-1.1.4-2.fc14.x86_64.rpm
[root@skye yum]# rpm -F yum-langpacks-0.1.5-3.fc14.noarch.rpm
[root@skye yum]# rpm -F yum-presto-0.6.2-2.fc14.noarch.rpm
[root@skye yum]# rpm -F yum-utils-1.1.28-1.fc14.noarch.rpm
[root@skye yum]# yum info
There was a problem importing one of the Python modules
required to run yum. The error leading to this problem was:

No module named yum

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.7 (r27:82500, Sep 27 2010, 17:57:21)
[GCC 4.5.1 20100924 (Red Hat 4.5.1-4)]

If you cannot solve this problem yourself, please go to
the yum faq at:
http://yum.baseurl.org/wiki/Faq
--------

Still no luck quite yet...

Maybe I need a different version of yum? I assume the yum rpm specific to Python 2.7 has to be on the distro... I may need to figure out how to pry it out of the iso file which is on the DVD I have... in case it matters.

I am attempting to install yum-3.2.28-5.fc14.noarch.rpm from the same download directory that I plucked python-2.7-8.fc14.3.x86_64.rpm - which is newer than the version you (wmakowski) mentioned in your suggestion (which was python-2.7-8.fc14.1.x86_64.rpm), so I probably need to either stick with this version level of software or try to locate these rpms from whatever Fedora 14 version I have on the DVD (which I cut several months ago).

I'm also wondering if shouldn't force these installs, rather than just freshen (-F)?

Thanks for all the help by the way!

This could be another case of the goofy path, causing it not to find yum even though it is installed. One of the q&a's from the link you provided had a suggestion I think may give you more information. Try running python from the command line, and type import yum.

yum-3.2.28-5.fc14.noarch.rpm is the version I have on my system. My python version, python-2.7-8.fc14.1, differs slightly from yours because you picked up python-2.7-8.fc14.3 from koji. This should not be an issue since there is no difference in the major and minor version numbers of python.

It looks like python is running better. At least you aren't getting the trace messages anymore.

[root@skye ~]# python
Python 2.7 (r27:82500, Sep 27 2010, 17:57:21)
[GCC 4.5.1 20100924 (Red Hat 4.5.1-4)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import yum
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ImportError: No module named yum
>>>

The problem thus far has been with lib64/python2.7 appearing in the path twice. I'm pretty sure the yum module it is looking for is in /usr/lib/python2.7/site-packages/sos/plugins/yum.py. I think it would be worth a shot to put a symlink in /usr/lib/python2.7 pointing to itself, much like we did for /usr/lib64/python2.7.

It works now.

OK, so I cheated and reinstalled [a newer version of] Fedora 14.

Not real sure what else to say on this...

So you listened to me then lol...

Yeah...

Hey, I know! Why not come over and help me reinstall three months worth of crap now?

(of course, I will admit that it's great having yum again!)

Glad to hear you are back in business, even if it took a reinstall to do it. There were some unusually mean gremlins in that system anyway. Plus with all the practice you'll be getting putting new/old crap on your box everything will be fresh in your mind when F15 comes out in less than three months.

Dude, I know how it feels... I used to do that on a daily basis

Oh well, it was a fun adventure anyway. Too bad it didn't quite work. Maybe someday Python and/or yum will be a little more flexible when it comes to AMD64.

As for Fedora 15, I would hope that I can simply "Upgrade", as opposed to having to "Reinstall" like I just had to do. I tried upgrading this time too, but it took a total of two seconds and obviously didn't do anything.

I mean, reinstalling Linux itself is a breeze - especially onto a new piece of hardware that you don't need to worry about. It's the reinstall of all of the layered products and associated data that can be a pain.

remove xulrunner-python
apparently it is a know bug. I cam across it when I could not run firefox after an upgrade.
yum remove xul-runner

I found this by googling "/usr/lib64/python2.7/site.py, line"

Hello,

This thread has been dead for quite some time now, and I don't know if what you posted is relevant to the OP's topic. If you need assistance with a different problem, let-a-lone trying to post information, I recommend highly that you create a new thread for it.

Cheers,

Josh