Bug 15803 - Unresolved dependencies *after* clicking "Install to satisfy..."
Summary: Unresolved dependencies *after* clicking "Install to satisfy..."
Status: CLOSED DUPLICATE of bug 14549
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
(Show other bugs)
Version: 7.1
Hardware: i386 Linux
high
medium
Target Milestone: ---
Assignee: Matt Wilson
QA Contact:
URL:
Whiteboard: Winston gold
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-08-09 13:06 UTC by Andrea Borgia
Modified: 2008-05-01 15:37 UTC (History)
0 users

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: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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 ***
Note You need to log in before you can comment on or make changes to this bug.