uninstall yum repository
 

Hi

I am facing lots of trouble with a yum repository that I think might be corrupted. I don't want to disable it (yum-config-manager --disable repository) I want to remove it so that I can reinstall it with the file that I downloaded:

yum-3.4.3.tar.gz

once I uncompress it shows me the next(I suppose that I have to "make install"):

AUTHORS callback.py cli.py docs FAQ Makefile PLUGINS README shell.py TODO yum yummain.py yum-updatesd.py
bin ChangeLog COPYING etc INSTALL output.py po rpmUtils test utils.py yumcommands.py yum.spec

But I don't know how to unistall it properly

DO NOT!!!!!!

do not install a source tar ball


first WHY do you think a repo that many many users use is corrupt ?

next WHAT operating system are you using ?
you have yum so it is ether
RHEL 6 or 7
CentOS 6 or 7
ScientificLinux 6 or 7

so what os and what minor version

Hi

The server is a RedHat 6.9, and the reason I think the repository is corrupted is because nobody can use it. Everytime I type for example:

yum repolist or yum install package_name, I get an error that says:

"There was a problem importing one of the Python modules
required to run yum. The error leading to this problem was:

No module named sqlite"

It's possible that the above module doesn't match the
current version of Python, which is:
2.6.6"

Here it says that the yum uses python 2.6.6, but when I check the python version with python --version it gives me the 2.7 version. So what can I make yum to use python 2.7 instead of 2.6.6.(The sqlite3 is indeed installed)

The sqlite3 is located in the following directories:

/usr/lib64/python2.6/sqlite3
/usr/local/src/php-5.6.30/ext/sqlite3
/usr/local/include/php/ext/sqlite3
/usr/local/lib/python2.7/sqlite3
/usr/local/bin/sqlite3
/usr/bin/Python-2.7/Lib/sqlite3
/usr/bin/Python-2.7/Doc/includes/sqlite3

When was the last time you did an update of your system?

I can't update either, it throws me the same error. Do you know if I can have two versions of Sqlite installed?? I was thinking that the problem might be with the Sqlite version 3.20.1