Upgrade from 6.2, FTP install. 2 files were missing from our mirror, upon finding the installer trying to download a nonexistant file I went to the mirror and manually copied the file into the install tree. Unfortunatly the machine doing the install grabbed the file before it was entirly copied. The install then put up a window saying: The file /mnt/sysimage/var/tmpxxxxx.arch.rpm can not be installed due to the file missing, bad package, press <return> to try again (somewhat paraphrased). I pressed enter several times but it seems since the file was already present the installer did not bother to download it again. Instead it just kept trying to install the corrupt file. It struck me that the least the installer could do would be to delete the corrupt version and try downloading again.
*** This bug has been marked as a duplicate of 36540 ***
*** Bug 36540 has been marked as a duplicate of this bug. ***
The installer has to assume that the installation media is clean. If we start trying to catch all the errors that result from a corrupted download, we open up a real can of worms. Given all the files that are included in the distribution, checking and verifying each and every file creates way too much overhead.
*** Bug 36541 has been marked as a duplicate of this bug. ***
Retrying a download 2 or 3 times is to much effort? I'm not talking about checking every package as it comes down, just doing a retry if the file seems corrupt. How many retires do you do for a CD install?
We do one try for the cd install. We are not going to add more code to the installer just to check if the user has set up the ftp server correctly. That is the user's responsibility.