Re: Can't md5-check 2.2_rev0/binary-i386-2.iso

["J.A. Bezemer" <costar@panic.et.tudelft.nl>]

On Wed, 23 Aug 2000, Stephan A Suerken wrote:

>  I am just trying to build the Original Debian 2.2 Rev 0 (binary i386)
> iso images with pseudo disk kit. Everything seems fine:
> 
> $ helsing: ~/pseudo-image-kit-2.0/2.2_i386_orig 
> $ absurd? l -h binary-i386-*.iso
> -rw-r--r--    1 absurd   absurd       639M Aug 22 21:33 binary-i386-1_NONUS.iso
> -rw-r--r--    1 absurd   absurd       642M Aug 23 01:55 binary-i386-2.iso
> -rw-r--r--    1 absurd   absurd       502M Aug 22 22:46 binary-i386-3.iso
> 
> But, when testing the images with the MD5SUM form cdimage.debian.org:
> 
> $ helsing: ~/pseudo-image-kit-2.0/2.2_i386_orig 
> $ absurd? md5sum -v -c ../contrib/MD5SUMS.2.2_rev0-i386.cdimage.debian.org
> binary-i386-1.iso md5sum: can't open binary-i386-1.iso
> binary-i386-1_NONUS.iso OK
> binary-i386-2.iso       FAILED
> binary-i386-3.iso       OK
> md5sum: 1 of 3 file(s) failed MD5 check
> 
> I have rsynced -2.iso three times, and (at least) in the last run, 
> file size was == matched data.
> 
> I am either missing something, or the MD5SUMS file (refetched it, gpg
> checked it twice) is false. Maybe the corrupt files i've heard of
> being in image 2 have been silently corrected, but not the md5sum?

I think it's the other way around. Try the repair program from
  http://cdimage.debian.org/lastmin.html
and md5sum again.


Regards,
  Anne Bezemer