[Yum-devel] Installed unresolved dependencies

Florian Festi ffesti at redhat.com
Tue Jun 5 14:44:30 UTC 2007


rpm allows unresolved dependencies to persist during updates. If pkg A-1 
with an unresolved requires:b=2.1 is installed an update to A-2 succeeds 
even if it also requires:b=2.1 which is still not provided anywhere. This is 
a wanted behavior because it avoids using --force/--nodeps over and over 
again. But if the requires of the update pkg is not exactly the same rpm 
issues an error - so this short cut is only of limited range.

With oldreqs and newpoprovs in Depsolve._checkInstall and ._checkRemove yum 
has the same behavior as rpm.

The question is if this is also the wanted or if it wouldn't be better to at 
least try to resolve these dependencies and pull in new packages if 
available? Should there be a cmd line switch and should it enable the new or 
the old behavior?


More information about the Yum-devel mailing list