|
"The system goes through a dependency check then stops with a message that it can't find certain versions of a dependent rpm's."
"I've been using yum to keep the system current with updates from the Fedora Legacy project. If I query my system I find that I alread have the dependent packages installed. In fact, I have newer versions than the Add/Remove Applications routine is looking for."
When a rpm is dependent on a specific version of a dependency and refuses to accept newer versions that can mean one of two things:
1. It could be true. I have seen KDE packages that were dependent on a specific version of Qt. Neither higher or lower would do.
2. Somebody goofed. I have seen cases where somebody set a rpm dependency version number and forgot to include "or higher".
"How can I add some of the base Redhat packages from Add/Remove Applications now that yum has placed newer versions of certain rpm's on my system?"
When a high level package manager won't do what you want the solution is usually to drop down into the command line package manager which is far more flexible. In your case you should use rpm to install the packages using the --nodeps option. If you have run into a rpm package missing the "or higher" version test then:
rpm --nodeps -i /pathname/packagename.rpm
should work OK. If it turns out that the dependency restriction really were correct then you can remove the package with:
rpm --nodeps -e packagename
--------------------------
Steve Stites
Last edited by jailbait; 05-19-2005 at 07:08 PM.
|
