Bug 61372

From Bugzilla Helper:
User-Agent: Mozilla/4.6 [en] (WinNT; I)

Description of problem:
For any of a number of reasons, a package instilation may need to be redone. In particular, some files in a package may have been deleted or corrupted. (The 
notorious 'rm -rR /' is a good example of this.) Assuming the RPM database has survived and you have
access to a package distribution, it
should be fairly easy to verify which files are missing or corrupt and reinstall them. The current implementation makes locating the missing/corrupted file possible, but 
it 
is NOT easy to do the update. Either add a 'fixit' option to 'verify' mode, or add a seperate 'fixit' mode. Interactive confirmation and batch mode would be useful 
options. 
On the other hand, if this already exists, I couldn't find anything on the subject in the documentation.


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.rm -fR /
2.^C (quickly!)
3.rpm -Va (or whatever...)
  Now what do you do?
	

Actual Results:  You're SOL and probably out on the street looking for a new job.

Expected Results:  4.mount /mnt/cdrom
5./mnt/cdrom/.../rpm -Va --fixit -interactive

Additional info:

This would be useful wien a machine has had a security compromise.