On 2009-04-12 20:56Z, David Christensen wrote:
> 
> md5sum computes the same checksum as what is contained in MD5SUMS, but
> prepends an asterisk to the filename on output.  So, the *.iso file is
> okay, but "md5sum -c MD5SUMS" is somehow broken (?).

The asterisk is okay; it should be ignored with '--check'.

> Nope.  Perhaps there is something wrong with my Cygwin (?) and/or md5sum
> (?).  Updating and trying again:
> 
> 2009-04-12 13:44:25 dpchr...@p43400e /cygdrive/h/data/iso/debian
> $ md5sum debian-live-500-i386-rescue.iso
> b02c3606a3f35f160a591fe1154aa362 *debian-live-500-i386-rescue.iso
> 
> 2009-04-12 13:45:09 dpchr...@p43400e /cygdrive/h/data/iso/debian
> $ grep 'rescue.iso$' MD5SUMS
> b02c3606a3f35f160a591fe1154aa362  debian-live-500-i386-rescue.iso
> 
> 2009-04-12 13:45:41 dpchr...@p43400e /cygdrive/h/data/iso/debian
> $ md5sum -c MD5SUMS 2>&1 | grep 'rescue\.iso'
> debian-live-500-i386-rescue.iso: FAILED
> debian-live-500-i386-rescue.iso.list: OK
> debian-live-500-i386-rescue.iso.log: OK
> debian-live-500-i386-rescue.iso.packages: OK

Try testing that file directly:

echo "b02c3606a3f35f160a591fe1154aa362  debian-live-500-i386-rescue.iso" \
 | md5sum --check --warn

And this (with an asterisk) should give the same result:

echo "b02c3606a3f35f160a591fe1154aa362 *debian-live-500-i386-rescue.iso" \
 | md5sum --check --warn

If those succeed, try adding '--warn' to the original command:

md5sum -cw MD5SUMS 2>&1 | grep 'rescue.iso'

just in case there's something strange in that file.

It would be interesting if this native 'md5sum' works as expected
where Cygwin's doesn't:

http://downloads.activestate.com/contrib/md5sum/Windows/md5sum.exe#!md5!eb574b236133e60c989c6f472f07827b

And I suppose it's worth showing the result of `which md5sum`,
just in case you've got a rogue copy on $PATH, even though you
seem not to.

A wild idea based on this report:
  http://bugs.centos.org/view.php?id=2961
would be to run the test repeatedly and see if the result changes.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Reply via email to