How to fix CentOS-Yum says a package is installed, and not?
~ $> sudo yum reinstall glibc-common-2.12-1.149.el6 Loaded plugins: fastestmirror, presto Setting up Reinstall Process Loading mirror speeds from cached hostfile No Match for argument: glibc-common-2.12-1.149.el6 Package (s) glibc-common-2.12-1.149.el6 available, but not installed. Nothing to do How can I resolve this? The RPM DB is confused.
Why does my computer say this software is already installed?
“This software already installed on your system” when trying to install a progarm. I am unable to install a software on my computer. it shows the error message that ” this software already installed on your system.”
Why do I get borked install on setup.py?
To be clear, if your module’s name is “foo”: If you try to run setup.py from any other directory by calling out its path, you end up with a borked install. I encountered this while trying to use keyring which I installed via sudo pip install keyring. As mentioned in the other answers, it’s a permissions issue in my case.
Why is my env unable to import a module that is definitely installed?
After that the dependencies that I installed were getting added to the global site-packages instead of the one inside venv folder. So the code running inside this env was not able to access those dependencies. Solution: Just removed the venv folder and recreated it again.
What does it mean when Yum says install else re-install?
I ended up detecting if the package has been installed, if not, install it else re-install: Yum can return a non-zero exit status for things that are not really errors, causing higher-level systems such as Elastic Beanstalk to think the script has failed.
Is there a glibc package in CentOS-Yum?
But glibc-common-2.12-1.149.el6_6.5.x86_64 is listed as being available. I would think that yum would happily install it. Unforunately, yum didn’t install it. So I tried to do it myself.
What’s the best way to ignore a Yum error?
A simpler way is just to ignore all errors by appending a true or exit 0 command – however, this is eventually going to bite you when the Yum repo is unreachable, or Yum has out of date metadata, etc.