I am opening this bug to seperate one of the issues out of bug #50899.

Prior relevant text:
------- Additional comments from pzb 2001-08-05 11:46:53 -------
This also showed up on my laptop during the upgrade from Zoot to Roswell.  The
unresolved deps screen was caused by foreign (non-Red Hat provided) packages
being installed on my system.  

All the packages listed had 'no suggestion' listed under 'Requirement'.  Even
though there were not any packages to potentially install, there was still an
option to 'Install packages to satisfy dependencies'.  Choosing this option has
the same result as choosing 'Ignore package dependencies': unsatisified deps on
the machine post-install.  Additionally, the option 'Do not install packages
that have dependencies' does not make sense, as the listed packages are already
installed on the system.

I realize that this screen has existed as long as anaconda has existed, but it
could be confusing to users who are not familiar with RPM dependencies.  This
screen seems unnecessary unless the user has selected 'Customize packages to be
 upgraded' or 'Select individual packages' as there is never an option for the
end user -- if they want a functional system, the dependencies must be
resolved.
 The only time it seems reasonable to show the screen is when the user has
chosen to select individual packages.

Could anaconda not show the 'Unresolved Dependencies' screen unless the
user has
manually selected packages?  Otherwise it would just automatically choose
'Install packages to satisfy dependencies' and skip the screen.


------- Additional comments from bfox 2001-08-10 18:24:06 -------
Ok, we're talking about a few different issues here. One is that the package
dependency screen needs some work. That can't be done in the current release
time frame, but perhaps in the future.