MD5SUM mismatch
I have 2 versions of the same file (md5sums): 65aab7a568bd8ebb4cfcdd97ea9e2944 debian-30r1-i386-binary-1_NONUS.iso 9fa969a779faec5c8d242924457e31b6 debian-30r1-i386-binary-1_NONUS.iso.ok Where the last one matches the digitally signed MD5SUM package. Can you clarify what happened in the phase of release since I now have two files with the same name, but differing in sum? I will keep the 2nd version for forensics if that is desired. The wrong file is date-stamped at Feb 14 15:22:19 2003 which might help to clarify things. (CC the message, I am not reading debian-cd at a daily basis). Diff of files follow from after loopback mounting both files and wreaking havoc with a diff -uNr (bad is the first file from above, good is the second): Binary files bad/dists/frozen/main/disks-i386/3.0.23-2002-05-21/images-1.20/driv er-1.bin and good/dists/frozen/main/disks-i386/3.0.23-2002-05-21/images-1.20/dri ver-1.bin differ Binary files bad/dists/frozen/main/disks-i386/3.0.23-2002-05-21/images-1.20/safe /driver-1.bin and good/dists/frozen/main/disks-i386/3.0.23-2002-05-21/images-1.2 0/safe/driver-1.bin differ Binary files bad/dists/frozen/main/disks-i386/current/images-1.20/driver-1.bin a nd good/dists/frozen/main/disks-i386/current/images-1.20/driver-1.bin differ Binary files bad/dists/frozen/main/disks-i386/current/images-1.20/safe/driver-1. bin and good/dists/frozen/main/disks-i386/current/images-1.20/safe/driver-1.bin differ Binary files bad/dists/stable/main/disks-i386/3.0.23-2002-05-21/images-1.20/driv er-1.bin and good/dists/stable/main/disks-i386/3.0.23-2002-05-21/images-1.20/dri ver-1.bin differ Binary files bad/dists/stable/main/disks-i386/3.0.23-2002-05-21/images-1.20/safe /driver-1.bin and good/dists/stable/main/disks-i386/3.0.23-2002-05-21/images-1.2 0/safe/driver-1.bin differ Binary files bad/dists/stable/main/disks-i386/current/images-1.20/driver-1.bin a nd good/dists/stable/main/disks-i386/current/images-1.20/driver-1.bin differ Binary files bad/dists/stable/main/disks-i386/current/images-1.20/safe/driver-1. bin and good/dists/stable/main/disks-i386/current/images-1.20/safe/driver-1.bin differ Binary files bad/dists/testing/main/disks-i386/3.0.23-2002-05-21/images-1.20/dri ver-1.bin and good/dists/testing/main/disks-i386/3.0.23-2002-05-21/images-1.20/d river-1.bin differ Binary files bad/dists/testing/main/disks-i386/3.0.23-2002-05-21/images-1.20/saf e/driver-1.bin and good/dists/testing/main/disks-i386/3.0.23-2002-05-21/images-1 .20/safe/driver-1.bin differ Binary files bad/dists/testing/main/disks-i386/current/images-1.20/driver-1.bin and good/dists/testing/main/disks-i386/current/images-1.20/driver-1.bin differ Binary files bad/dists/testing/main/disks-i386/current/images-1.20/safe/driver-1 .bin and good/dists/testing/main/disks-i386/current/images-1.20/safe/driver-1.bi n differ Binary files bad/dists/unstable/main/disks-i386/3.0.23-2002-05-21/images-1.20/dr iver-1.bin and good/dists/unstable/main/disks-i386/3.0.23-2002-05-21/images-1.20 /driver-1.bin differ Binary files bad/dists/unstable/main/disks-i386/3.0.23-2002-05-21/images-1.20/sa fe/driver-1.bin and good/dists/unstable/main/disks-i386/3.0.23-2002-05-21/images -1.20/safe/driver-1.bin differ Binary files bad/dists/unstable/main/disks-i386/current/images-1.20/driver-1.bin and good/dists/unstable/main/disks-i386/current/images-1.20/driver-1.bin differ Binary files bad/dists/unstable/main/disks-i386/current/images-1.20/safe/driver- 1.bin and good/dists/unstable/main/disks-i386/current/images-1.20/safe/driver-1. bin differ Binary files bad/dists/woody/main/disks-i386/3.0.23-2002-05-21/images-1.20/drive r-1.bin and good/dists/woody/main/disks-i386/3.0.23-2002-05-21/images-1.20/drive r-1.bin differ Binary files bad/dists/woody/main/disks-i386/3.0.23-2002-05-21/images-1.20/safe/ driver-1.bin and good/dists/woody/main/disks-i386/3.0.23-2002-05-21/images-1.20/ safe/driver-1.bin differ Binary files bad/dists/woody/main/disks-i386/current/images-1.20/driver-1.bin an d good/dists/woody/main/disks-i386/current/images-1.20/driver-1.bin differ Binary files bad/dists/woody/main/disks-i386/current/images-1.20/safe/driver-1.b in and good/dists/woody/main/disks-i386/current/images-1.20/safe/driver-1.bin di ffer Binary files bad/pool/main/g/gs/gs_6.53-3_i386.deb and good/pool/main/g/gs/gs_6. 53-3_i386.deb differ Binary files bad/pool/main/i/isdnutils/isdnlog_3.1pre4-4_i386.deb and good/pool/ main/i/isdnutils/isdnlog_3.1pre4-4_i386.deb differ Binary files bad/pool/main/k/kdebase/kdebase_2.2.2-14_i386.deb and good/pool/mai n/k/kdebase/kdebase_2.2.2-14_i386.deb differ Binary files bad/pool/main/t/tar/tar_1.13.25-2_i386.deb and good/pool/main/t/tar /tar_1.13.25-2_i386.deb differ -- Jesper Java skal drikkes - ikke kodes i -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: MD5SUM mismatch
Hi Jesper, On Tue, Mar 11, 2003 at 04:34:18PM +0100, Jesper Louis Andersen wrote: > 65aab7a568bd8ebb4cfcdd97ea9e2944 debian-30r1-i386-binary-1_NONUS.iso Where did you get the bad file from? > Binary files bad/pool/main/t/tar/tar_1.13.25-2_i386.deb and > good/pool/main/t/tar > /tar_1.13.25-2_i386.deb differ Can you upload the "bad" file somewhere (or mail it to me, but I'd prefer if you could upload it, I'm on a dialup...). The md5sum of the good one is 465e2223807d64e217f13af988541192. Cheers, Richard -- __ _ |_) /| Richard Atterer | CS student at the Technische | GnuPG key: | \/¯| http://atterer.net | Universität München, Germany | 0x888354F7 ¯ '` ¯ pgp0.pgp Description: PGP signature
Re: MD5SUM mismatch
On Tue, 11 Mar 2003 16:34:18 +0100 Jesper Louis Andersen <[EMAIL PROTECTED]> wrote: > Binary files bad/pool/main/t/tar/tar_1.13.25-2_i386.deb and > good/pool/main/t/tar > /tar_1.13.25-2_i386.deb differ You could pull these two files out (for example), calculate their md5sum and see see which is wrong. Or unpack the contents of the deb (dpkg-deb -X ) and compare it on a file by file bases. Glenn -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: MD5SUM mismatch
On Tue, Mar 11, 2003 at 10:27:08PM +0100, Richard Atterer wrote: > Hi Jesper, > > On Tue, Mar 11, 2003 at 04:34:18PM +0100, Jesper Louis Andersen wrote: > > 65aab7a568bd8ebb4cfcdd97ea9e2944 debian-30r1-i386-binary-1_NONUS.iso > > Where did you get the bad file from? >From our squid log (lines broken): 1045232539.837 1242406 130.225.96.227 TCP_MISS/200 678396169 GET ftp://mirror.pudas.net/debian-iso/3.0_r1/ i386/debian-30r1-i386-binary-1_NONUS.iso sarah$ date -r 1045232539 Fri Feb 14 14:22:19 UTC 2003 which exactly matches the creation time of the file. > > Binary files bad/pool/main/t/tar/tar_1.13.25-2_i386.deb and > > good/pool/main/t/tar > > /tar_1.13.25-2_i386.deb differ > > Can you upload the "bad" file somewhere (or mail it to me, but I'd prefer > if you could upload it, I'm on a dialup...). The md5sum of the good one is > 465e2223807d64e217f13af988541192. Of course! To where should I upload it and how? Our publically available ftp and webspace is very limited, so I can not place it there[1]. [1] Read: it is driven by an old HPUX11 box and thus uses some old 4gb disks all to stressed out to have any space left. -- Jesper An algorithm a day, keeps the bugs away -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
MD5SUM mismatch
I have 2 versions of the same file (md5sums): 65aab7a568bd8ebb4cfcdd97ea9e2944 debian-30r1-i386-binary-1_NONUS.iso 9fa969a779faec5c8d242924457e31b6 debian-30r1-i386-binary-1_NONUS.iso.ok Where the last one matches the digitally signed MD5SUM package. Can you clarify what happened in the phase of release since I now have two files with the same name, but differing in sum? I will keep the 2nd version for forensics if that is desired. The wrong file is date-stamped at Feb 14 15:22:19 2003 which might help to clarify things. (CC the message, I am not reading debian-cd at a daily basis). Diff of files follow from after loopback mounting both files and wreaking havoc with a diff -uNr (bad is the first file from above, good is the second): Binary files bad/dists/frozen/main/disks-i386/3.0.23-2002-05-21/images-1.20/driv er-1.bin and good/dists/frozen/main/disks-i386/3.0.23-2002-05-21/images-1.20/dri ver-1.bin differ Binary files bad/dists/frozen/main/disks-i386/3.0.23-2002-05-21/images-1.20/safe /driver-1.bin and good/dists/frozen/main/disks-i386/3.0.23-2002-05-21/images-1.2 0/safe/driver-1.bin differ Binary files bad/dists/frozen/main/disks-i386/current/images-1.20/driver-1.bin a nd good/dists/frozen/main/disks-i386/current/images-1.20/driver-1.bin differ Binary files bad/dists/frozen/main/disks-i386/current/images-1.20/safe/driver-1. bin and good/dists/frozen/main/disks-i386/current/images-1.20/safe/driver-1.bin differ Binary files bad/dists/stable/main/disks-i386/3.0.23-2002-05-21/images-1.20/driv er-1.bin and good/dists/stable/main/disks-i386/3.0.23-2002-05-21/images-1.20/dri ver-1.bin differ Binary files bad/dists/stable/main/disks-i386/3.0.23-2002-05-21/images-1.20/safe /driver-1.bin and good/dists/stable/main/disks-i386/3.0.23-2002-05-21/images-1.2 0/safe/driver-1.bin differ Binary files bad/dists/stable/main/disks-i386/current/images-1.20/driver-1.bin a nd good/dists/stable/main/disks-i386/current/images-1.20/driver-1.bin differ Binary files bad/dists/stable/main/disks-i386/current/images-1.20/safe/driver-1. bin and good/dists/stable/main/disks-i386/current/images-1.20/safe/driver-1.bin differ Binary files bad/dists/testing/main/disks-i386/3.0.23-2002-05-21/images-1.20/dri ver-1.bin and good/dists/testing/main/disks-i386/3.0.23-2002-05-21/images-1.20/d river-1.bin differ Binary files bad/dists/testing/main/disks-i386/3.0.23-2002-05-21/images-1.20/saf e/driver-1.bin and good/dists/testing/main/disks-i386/3.0.23-2002-05-21/images-1 .20/safe/driver-1.bin differ Binary files bad/dists/testing/main/disks-i386/current/images-1.20/driver-1.bin and good/dists/testing/main/disks-i386/current/images-1.20/driver-1.bin differ Binary files bad/dists/testing/main/disks-i386/current/images-1.20/safe/driver-1 .bin and good/dists/testing/main/disks-i386/current/images-1.20/safe/driver-1.bi n differ Binary files bad/dists/unstable/main/disks-i386/3.0.23-2002-05-21/images-1.20/dr iver-1.bin and good/dists/unstable/main/disks-i386/3.0.23-2002-05-21/images-1.20 /driver-1.bin differ Binary files bad/dists/unstable/main/disks-i386/3.0.23-2002-05-21/images-1.20/sa fe/driver-1.bin and good/dists/unstable/main/disks-i386/3.0.23-2002-05-21/images -1.20/safe/driver-1.bin differ Binary files bad/dists/unstable/main/disks-i386/current/images-1.20/driver-1.bin and good/dists/unstable/main/disks-i386/current/images-1.20/driver-1.bin differ Binary files bad/dists/unstable/main/disks-i386/current/images-1.20/safe/driver- 1.bin and good/dists/unstable/main/disks-i386/current/images-1.20/safe/driver-1. bin differ Binary files bad/dists/woody/main/disks-i386/3.0.23-2002-05-21/images-1.20/drive r-1.bin and good/dists/woody/main/disks-i386/3.0.23-2002-05-21/images-1.20/drive r-1.bin differ Binary files bad/dists/woody/main/disks-i386/3.0.23-2002-05-21/images-1.20/safe/ driver-1.bin and good/dists/woody/main/disks-i386/3.0.23-2002-05-21/images-1.20/ safe/driver-1.bin differ Binary files bad/dists/woody/main/disks-i386/current/images-1.20/driver-1.bin an d good/dists/woody/main/disks-i386/current/images-1.20/driver-1.bin differ Binary files bad/dists/woody/main/disks-i386/current/images-1.20/safe/driver-1.b in and good/dists/woody/main/disks-i386/current/images-1.20/safe/driver-1.bin di ffer Binary files bad/pool/main/g/gs/gs_6.53-3_i386.deb and good/pool/main/g/gs/gs_6. 53-3_i386.deb differ Binary files bad/pool/main/i/isdnutils/isdnlog_3.1pre4-4_i386.deb and good/pool/ main/i/isdnutils/isdnlog_3.1pre4-4_i386.deb differ Binary files bad/pool/main/k/kdebase/kdebase_2.2.2-14_i386.deb and good/pool/mai n/k/kdebase/kdebase_2.2.2-14_i386.deb differ Binary files bad/pool/main/t/tar/tar_1.13.25-2_i386.deb and good/pool/main/t/tar /tar_1.13.25-2_i386.deb differ -- Jesper Java skal drikkes - ikke kodes i
Re: MD5SUM mismatch
Hi Jesper, On Tue, Mar 11, 2003 at 04:34:18PM +0100, Jesper Louis Andersen wrote: > 65aab7a568bd8ebb4cfcdd97ea9e2944 debian-30r1-i386-binary-1_NONUS.iso Where did you get the bad file from? > Binary files bad/pool/main/t/tar/tar_1.13.25-2_i386.deb and > good/pool/main/t/tar > /tar_1.13.25-2_i386.deb differ Can you upload the "bad" file somewhere (or mail it to me, but I'd prefer if you could upload it, I'm on a dialup...). The md5sum of the good one is 465e2223807d64e217f13af988541192. Cheers, Richard -- __ _ |_) /| Richard Atterer | CS student at the Technische | GnuPG key: | \/¯| http://atterer.net | Universität München, Germany | 0x888354F7 ¯ '` ¯ pgpIjveZ9I9Yx.pgp Description: PGP signature
Re: MD5SUM mismatch
On Tue, 11 Mar 2003 16:34:18 +0100 Jesper Louis Andersen <[EMAIL PROTECTED]> wrote: > Binary files bad/pool/main/t/tar/tar_1.13.25-2_i386.deb and > good/pool/main/t/tar > /tar_1.13.25-2_i386.deb differ You could pull these two files out (for example), calculate their md5sum and see see which is wrong. Or unpack the contents of the deb (dpkg-deb -X ) and compare it on a file by file bases. Glenn
Re: MD5SUM mismatch
On Tue, Mar 11, 2003 at 10:27:08PM +0100, Richard Atterer wrote: > Hi Jesper, > > On Tue, Mar 11, 2003 at 04:34:18PM +0100, Jesper Louis Andersen wrote: > > 65aab7a568bd8ebb4cfcdd97ea9e2944 debian-30r1-i386-binary-1_NONUS.iso > > Where did you get the bad file from? >From our squid log (lines broken): 1045232539.837 1242406 130.225.96.227 TCP_MISS/200 678396169 GET ftp://mirror.pudas.net/debian-iso/3.0_r1/ i386/debian-30r1-i386-binary-1_NONUS.iso sarah$ date -r 1045232539 Fri Feb 14 14:22:19 UTC 2003 which exactly matches the creation time of the file. > > Binary files bad/pool/main/t/tar/tar_1.13.25-2_i386.deb and > > good/pool/main/t/tar > > /tar_1.13.25-2_i386.deb differ > > Can you upload the "bad" file somewhere (or mail it to me, but I'd prefer > if you could upload it, I'm on a dialup...). The md5sum of the good one is > 465e2223807d64e217f13af988541192. Of course! To where should I upload it and how? Our publically available ftp and webspace is very limited, so I can not place it there[1]. [1] Read: it is driven by an old HPUX11 box and thus uses some old 4gb disks all to stressed out to have any space left. -- Jesper An algorithm a day, keeps the bugs away
