Bug 124286 - Errors installing an RPM are handled inflexibly
Summary: Errors installing an RPM are handled inflexibly
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 2
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
Depends On:
TreeView+ depends on / blocked
Reported: 2004-05-25 13:33 UTC by Dave Shield
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2004-10-07 18:35:11 UTC

Attachments (Terms of Use)

Description Dave Shield 2004-05-25 13:33:00 UTC
Description of problem:
  During the installation of a clean system, if an RPM fails to
unpack correctly, then a dialog box appears to report this problem,
and offer the possibility of trying again.  There are two flaws
with this:

  a) Having clicked "OK", the dialog box stays up, making it
difficult to tell whether/when the second attempt has also failed.

  b) If the installation media is indeed corrupted, then there
is no way to skip this RPM and continue.  It's not even possible
to cleanly abort the installation and return to the configuration
screens.   The only option appears to be to reboot the system
and start the installation right from scratch.

Expected results:
  a)  The dialog box should be removed before starting to retry
installing the RPM
  b)  The dialog box should have an option to skip this particular
RPM, and continue with the installation.

Comment 1 Jeremy Katz 2004-05-26 03:48:50 UTC
Unfortunately, there's not much we can do in this case.  There's no
good way to tell the "importance" of a package and whether we can skip
it and still have a reasonably sane system.

Comment 2 Dave Shield 2004-05-26 08:31:29 UTC
You probably can't do so automatically, no.
But the person doing the installation might be able to.
Why not at least offer them the *option* of continuing?
(with suitable warnings about a broken system)
If nothing else, they could make a note of the missing
RPM and install it manually later.

And what about the other half of this bug report -
taking down the dialog box before retrying?

Note You need to log in before you can comment on or make changes to this bug.