http://qa.mandrakesoft.com/show_bug.cgi?id=3156





------- Additional Comments From [EMAIL PROTECTED]  2003-03-26 20:20 -------
On Wed, 2003-03-26 at 10:47, jamesl wrote:


Don't know if this will help you but what I do is.

Mount the cd

cd to the RPMS directory

at the command line.

rpm -K *.rpm | grep NOT


The grep reports to me only the rpms that have a bad md5 or gpg sig.  if
you don't have the gpg key installed on the box you are checking from
then 

rpm -K *.rpm --nogpg | grep NOT 

checks only the md5 of all the rpms.

(the other) James




------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: UNCONFIRMED
creation_date: 
description: 
9.1 release candidiate 2:

During numerous attempts at installing RC2, I have encountered a point most of
the way through the install where the installer becomes unable to read many of
the packages it is attempting to install.  The particular packages are never the
same from one try to the next.  I have re-created the CDs from the ISO files,
using different brands of disks, and tried installing from the CD-RW drive in
the system rather than the CD-ROM drive.  The ISO files passed md5sum tests. 
8.2 & 9.0 install CDs have worked flawlessly on this system.

What would make this easier to troubleshoot is if there were a way to verify the
 CD has been written correctly.  Not a utility that checks at install time, but
a way to validate from the system that wrote the disks.

Reply via email to