David Timms wrote:
Gerry Reno wrote:
David Timms wrote:
If you don't want to uninstall orphans, I think you could rpm -e
--justdb (from memory), so that they stay installed during the
upgrade, but then rpm reinstall --justdb afterwards.
I was just considering 'rpm -e --justdb --nodeps PKGS' if I can
figure out the list of packages.
Never heard of rpm reinstall.
No that was a bit of oversimplification ;-)
Perhaps more like:
$ rpm -q glglobe
$ yumdownloader glglobe (same version hopefully)
# rpm -e --nodeps --justdb glglobe
---
# rpm -Uvh --justdb glglobe-x-y-x.arch.rpm
$ rpm -V glglobe
DaveT.
Ok, I was finally able to get this upgrade to complete using this
technique of 'hiding' some of the problem packages and 'unhiding' them
after the upgrade. Thanks.
This also brings up another question though.
Whenever I've run into some type of 'yum upgrade' dependency problems
that were very involved or too complex to solve I've noticed that if I
do an 'anaconda upgrade' that for whatever reason these problems don't
seem to get in the way of anaconda being able to upgrade the system. So
what is different about how anaconda does it's upgrade. It almost seems
that it is doing the equivalent of 'rpm -Uvh --force PKGLIST' to power
it's way through all the dependency hell. Is this how it can succeed at
upgrading where doing a 'yum upgrade' cannot?
Regards,
Gerry
_______________________________________________
Yum mailing list
Yum@xxxxxxxxxxxxxxxxx
http://lists.baseurl.org/mailman/listinfo/yum
