Red Hat Bugzilla – Bug 68376
Bad rpms during install handled badly - want SKIP option
Last modified: 2007-04-18 12:44:00 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.0 (X11; Linux i686; U;) Gecko/20020408
Description of problem:
During install, while extracting from disk3, there was no more progress for
almost 30 minutes; no change of rpm to be inflated. The mouse was active. But
there was no chance to stop the current rpm from being installed.
Agreed, disk3 turned out to 'fail' the media test.
Though, I propose that when an error occurs, the user should have more
alternatives than power-off. An erroneous rpm could be skipped (and installed
later, after reboot), e.g. instead of freezing all inputs (except mouse), which
means start from scratch.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. insert install disk containing errors
Actual Results: a program that cannot be inflated will be skipped.
Expected Results: The users can continue on their own; and have some control
over the procedure (skip current, pause, etc)
PLEASE do this. I've wanted this on the RH install since back in 4.2. If there
is a scratch on the CD or anything, the whoe thing starts over with the same
problem next time. Just add a "SKIP" optin and a warning that you must install
be hand to avoid dependency problems, maybe even give a command line to run
*** Bug 71487 has been marked as a duplicate of this bug. ***
*** Bug 74139 has been marked as a duplicate of this bug. ***
Deferring to a future release. We should allow for ejecting and replacing the
CD with a new one if you hit a problem package during the installation now, though.
*** Bug 30029 has been marked as a duplicate of this bug. ***
A skip option requires significant changes in many ways and doesn't make sense
for many packages (eg, if glibc fails to install a skip button isn't going to
help at all). We now catch every case that we can of a package failure before
trying to install the package and allow you to replace the CD in cases where you
*** Bug 109734 has been marked as a duplicate of this bug. ***
*** Bug 118206 has been marked as a duplicate of this bug. ***