dragontale wrote:
I just woke up from bed and I'm ready.
After reading about your use of rpm --nodeps, I suggest in the future
you either use
yum remove myrpm
instead. There are a few occasions where --nodeps is valuable, but
mostly it is dangerous.
One instance fro reading your post, you have the libglade2-devel package
but not libglade.
Your system is most likely hosed from all of the occasions where you
used rpm -e package --nodeps. To recover, you most likely need to review
your history from the terminal and reinstall the packages again.
Check out your system to see if it works for things that you use, then use
yum remove myrpm
in the future and either allow yum to remove all dependent packages or
cancel the action and live with the rpm installed on your system.
As you can see with your system state, the dependencies are there for
real reasons, they need the other packages. There are some trivial
dependencies but not a large amount to my knowledge.
Regarding getting libglade2 installed again, either grab the rpm from
the disk, load it on a USB drive from a working computer or log in at a
terminal CTL-ALT-F1 through F6 should allow you to login at text mode.
When logged in try to grab the rpm and install it. If it needs any deps,
also install them.
If you have a working Internet connection, running
yum install libglade2 and answering yes to the prompt should pull in the
library and all its deps.
Jim
--
A debugged program is one for which you have not yet found the conditions
that make it fail.
-- Jerry Ogdin
