During a network install, if an rpm to be installed isn't found (like with
the situation described in bugzilla #12804), anaconda fails very
ungracefully. No traceback on the gui screen and can't get to tty1 to
check for a traceback there, but it's a package I know is on the second cd
and thus not there
verified ... a traceback occurs using TUI ... thanks for the report!
This defect is considered MUST-FIX for Winston Release-Candidate #1
We are in a UI freeze so we cannot add screens/dialogs at this time - hopefully
the original issue of installing an RPM which is on another CDROM does not occur
in post-beta5 builds.
I will add 'better exception handling' to our feature list for the next release.
*** This bug has been marked as a duplicate of 16038 ***