Red Hat Bugzilla – Bug 15803
Unresolved dependencies *after* clicking "Install to satisfy..."
Last modified: 2008-05-01 11:37:57 EDT
I did not choose to customize packages, got unresolved dependencies (yes, I've read
about this being due to an incomplete tree), chose "Install to satisfy" and got some more
(different) unresolved dependencies, which is odd.
This defect is considered MUST-FIX for Winston Gold-release
It just got worse: unresolved dep -> satisfy -> unr. -> satisfy -> about to upgrade.
This on a 6.2->RC1 upgrade test, albeit with a custom selection of packages. Anyway, whether the user customizes or not
the list should not matter at all, we should be doing a transitive closure of the dependencies and get them right in a single shot.
Oh, this was on the upgrade path? That's deferred.
*** This bug has been marked as a duplicate of 14549 ***