>> We could just display some sort of warning here, but this seems like a pretty >> big error. It could indicate media read errors or network problems getting in >> the way, and either of those will likely lead to additional errors later on. > self.progress.processEvents() >> > > Would you consider letting the person doing the install decide? I.e., > if the package that is showing the error would not prevent the > installation booting to a usable configuration and letting the user > downloada a good rpm, why not let the installation proceed? I > understand the consequence of another package depending on the failed > rpm. Yeah, we could probably allow this to be user-controlled. I have a related bug (511801 - restricted visibility, sorry) that's going to require some more error handling code in the RPM callback, too. At that point I think it'll make sense to offer both an abort/continue/continue all option on the error dialog in this patch, and perhaps also a %packages option in kickstart. My original thought was that if you're getting cpio errors when installing an RPM, it likely points to a very serious problem with the media and you're almost certainly not going to get a valid install out of this. - Chris _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
