Re: debian-live-500-i386-rescue.iso: FAILED
David Christensen wrote: >> When I attempt to verify the checksums related to the "rescue" disk, >> the ISO image appears corrupt: >>2009-04-11 21:00:35 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 >> I've downloaded MD5SUMS and debian-live-500-i386-rescue.iso twice, >> with the same results. > I ran more some more tests: > > 2009-04-12 08:13:07 dpchr...@p43400e /cygdrive/h/data/iso/debian > $ md5sum debian-live-500-i386-rescue.iso > b02c3606a3f35f160a591fe1154aa362 *debian-live-500-i386-rescue.iso > > 2009-04-12 08:13:39 dpchr...@p43400e /cygdrive/h/data/iso/debian > $ grep 'rescue.iso$' MD5SUMS > b02c3606a3f35f160a591fe1154aa362 debian-live-500-i386-rescue.iso > > 2009-04-12 08:42:26 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 > > 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 means that md5sum has detected the file is binary and opened it in binary mode. The lack of an asterisk on the other files means that md5sum has identified them as text and opened and summed them in text mode. This is deliberate, it means that the same text document checksums the same regardless of line-end style, which is generally what you want when verifying download integrity - e.g. in case ftp text mode translation has been in effect. The reason this situation is causing surprise on the Debian list is because in Linux, there's no distinction between text and binary mode. I don't know if it even supports binary mode, because I would have expected it to use binary mode everywhere rather than nowhere. As to whether md5sum is right to fail, well I think it has to draw your attention to the fact that the modes don't match even though the checksums do, because that means "something weird is going on and I don't understand why". I'm pretty sure your download is good though! cheers, DaveK -- 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/
RE: debian-live-500-i386-rescue.iso: FAILED
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 dpchr...@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 dpchr...@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 dpchr...@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 dpchr...@p43400e /cygdrive/h/data/iso/debian $ file MD5SUMS MD5SUMS: ASCII text 2009-04-12 21:29:44 dpchr...@p43400e /cygdrive/h/data/iso/debian $ cp MD5SUMS MD5SUMS.dos 2009-04-12 21:30:18 dpchr...@p43400e /cygdrive/h/data/iso/debian $ unix2dos MD5SUMS.dos MD5SUMS.dos: done. 2009-04-12 21:43:48 dpchr...@p43400e /cygdrive/h/data/iso/debian $ file MD5SUMS.dos MD5SUMS.dos: ASCII text, with CRLF line terminators 2009-04-12 21:43:54 dpchr...@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 dpchr...@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/
Re: debian-live-500-i386-rescue.iso: FAILED
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/
Re: debian-live-500-i386-rescue.iso: FAILED
On 4/12/2009 4:56 PM, 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 (?).
I think it's behaving exactly as documented ("man md5sum"). See also
http://www.cygwin.com/ml/cygwin/2005-08/msg00361.html
--
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/
Re: debian-live-500-i386-rescue.iso: FAILED
David Christensen wrote: > Any suggestions? no idea, never used cygwin. -- Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: daniel.baum...@panthera-systems.net Internet: http://people.panthera-systems.net/~daniel-baumann/ -- 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/
RE: debian-live-500-i386-rescue.iso: FAILED
cygwin: I wrote on debian-live (http://lists.debian.org/debian-live/2009/04/msg00068.html): > I've downloaded several files from: >http://cdimage.debian.org/cdimage/release/current-live/i386/iso-cd/ > When I attempt to verify the checksums related to the "rescue" disk, > the ISO image appears corrupt: >2009-04-11 21:00:35 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 > I've downloaded MD5SUMS and debian-live-500-i386-rescue.iso twice, > with the same results. Daniel Baumann wrote (http://lists.debian.org/debian-live/2009/04/msg00069.html): > i don't think so. ... > dan...@debian:/mnt/daniel1/srv/debian-unofficial/live/cdimage/release/5. 0.0/i386/iso-cd$ grep "rescue.*iso$" MD5SUMS > b02c3606a3f35f160a591fe1154aa362 debian-live-500-i386-rescue.iso > dan...@debian:/mnt/daniel1/srv/debian-unofficial/live/cdimage/release/5. 0.0/i386/iso-cd$ md5sum debian-live-500-i386-rescue.iso > b02c3606a3f35f160a591fe1154aa362 debian-live-500-i386-rescue.iso ... > make sure both your computer and network work correctly Thank you for your help. :-) I ran more some more tests: 2009-04-12 08:13:07 dpchr...@p43400e /cygdrive/h/data/iso/debian $ md5sum debian-live-500-i386-rescue.iso b02c3606a3f35f160a591fe1154aa362 *debian-live-500-i386-rescue.iso 2009-04-12 08:13:39 dpchr...@p43400e /cygdrive/h/data/iso/debian $ grep 'rescue.iso$' MD5SUMS b02c3606a3f35f160a591fe1154aa362 debian-live-500-i386-rescue.iso 2009-04-12 08:42:26 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 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 (?). Attempting to force binary mode: 2009-04-12 08:43:47 dpchr...@p43400e /cygdrive/h/data/iso/debian $ md5sum -b -c MD5SUMS md5sum: the --binary and --text options are meaningless when verifying checksums Try `md5sum --help' for more information. 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 Nope. cygcheck.out attached. Any suggestions? TIA, David cygcheck.out Description: Binary data -- 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/
