X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org From: "David Christensen" To: Cc: "'Greg Chicares'" References: <5029335BDC474F6FAF2AECE45CF4F72F AT p43400e> <49E1A62F DOT 90703 AT debian DOT org> <49E27B29 DOT 8010800 AT sbcglobal DOT net> Subject: RE: debian-live-500-i386-rescue.iso: FAILED Date: Sun, 12 Apr 2009 22:03:28 -0700 Message-ID: <1B4ED130E4864E2D9F85B9A5070102B4@p43400e> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit In-Reply-To: <49E27B29.8010800@sbcglobal.net> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Greg Chicares wrote: > The asterisk is okay; it should be ignored with '--check'. Thanks for the help. :-) > Try testing that file directly: > echo "b02c3606a3f35f160a591fe1154aa362 debian-live-500-i386-rescue.is > o" \ > | md5sum --check --warn 2009-04-12 21:20:57 dpchrist AT p43400e /cygdrive/h/data/iso/debian $ echo "b02c3606a3f35f160a591fe1154aa362 debian-live-500-i386-rescue.is o" | md5sum --check --warn debian-live-500-i386-rescue.iso: FAILED md5sum: WARNING: 1 of 1 computed checksum did NOT match > And this (with an asterisk) should give the same result: > echo "b02c3606a3f35f160a591fe1154aa362 *debian-live-500-i386-rescue.is > o" \ > | md5sum --check --warn 2009-04-12 21:21:22 dpchrist AT p43400e /cygdrive/h/data/iso/debian $ echo "b02c3606a3f35f160a591fe1154aa362 *debian-live-500-i386-rescue.is o" | md5sum --check --warn debian-live-500-i386-rescue.iso: OK So, the asterisk does matter to Cygwin md5sum when checking. > 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 H:\data\iso\debian>h:\data\download\a\activestate\md5sum.exe -c MD5SUMS ... debian-live-500-i386-rescue.iso: OK debian-live-500-i386-rescue.iso.list: OK debian-live-500-i386-rescue.iso.log: OK debian-live-500-i386-rescue.iso.packages: OK > 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. 2009-04-12 21:23:13 dpchrist AT p43400e /cygdrive/h/data/iso/debian $ which md5sum /usr/bin/md5sum > 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. http://www.quotationspage.com/quote/26032.html I wonder if line endings of the MD5SUMS file has anything to do with it? 2009-04-12 21:27:42 dpchrist AT p43400e /cygdrive/h/data/iso/debian $ file MD5SUMS MD5SUMS: ASCII text 2009-04-12 21:29:44 dpchrist AT p43400e /cygdrive/h/data/iso/debian $ cp MD5SUMS MD5SUMS.dos 2009-04-12 21:30:18 dpchrist AT p43400e /cygdrive/h/data/iso/debian $ unix2dos MD5SUMS.dos MD5SUMS.dos: done. 2009-04-12 21:43:48 dpchrist AT p43400e /cygdrive/h/data/iso/debian $ file MD5SUMS.dos MD5SUMS.dos: ASCII text, with CRLF line terminators 2009-04-12 21:43:54 dpchrist AT p43400e /cygdrive/h/data/iso/debian $ md5sum --check --warn MD5SUMS.dos 2>&1 | grep rescue 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 Nope. I wonder if it's because my Cygwin is installed to use DOS line endings? Switch it to Unix line endings and try again: 2009-04-12 21:51:39 dpchrist AT p43400e /cygdrive/h/data/iso/debian $ md5sum --check --warn MD5SUMS 2>&1 | grep rescue debian-live-500-i386-rescue.iso: OK debian-live-500-i386-rescue.iso.list: OK debian-live-500-i386-rescue.iso.log: OK debian-live-500-i386-rescue.iso.packages: OK Yup. I wonder if this is a bug or a feature? David -- 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/