Bug 15803

Summary: Unresolved dependencies *after* clicking "Install to satisfy..."
Product: [Retired] Red Hat Linux Reporter: Andrea Borgia <andrea.borgia>
Component: anacondaAssignee: Matt Wilson <msw>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: high    
Version: 7.1   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard: Winston gold
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-09-14 20:32:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Andrea Borgia 2000-08-09 13:06:35 UTC
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.

Comment 1 Glen Foster 2000-08-09 19:57:35 UTC
This defect is considered MUST-FIX for Winston Gold-release

Comment 2 Matt Wilson 2000-08-10 03:29:35 UTC
Already fixed

Comment 3 borgia 2000-08-17 05:47:54 UTC
Apparently not.

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.


Comment 4 Matt Wilson 2000-08-22 15:55:50 UTC
Oh, this was on the upgrade path?  That's deferred.


Comment 5 Michael Fulbright 2000-09-14 20:32:41 UTC

*** This bug has been marked as a duplicate of 14549 ***