Bug#77487: marked as done (md5sum.txt file for disks-i386 doesn't match files on server)
Your message dated 04 Dec 2000 09:59:49 -0500
with message-id <oahf4kdyfu.fsf@arroz.fake>
and subject line Bug#77487: md5sum.txt file for disks-i386 doesn't match files on server
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Darren Benham
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 20 Nov 2000 00:48:43 +0000
>From olaf@epkowa.co.jp Sun Nov 19 18:48:43 2000
Return-path: <olaf@epkowa.co.jp>
Received: from epkowagw1.epkowa.co.jp [202.212.108.2]
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 13xf8V-0005YR-00; Sun, 19 Nov 2000 18:48:43 -0600
Received: from kowasv.epkowa.co.jp ([172.16.130.3])
by epkowagw1.epkowa.co.jp (8.9.3/3.7Wpl2-07/20/00) with ESMTP id JAA18263
for <submit@bugs.debian.org>; Mon, 20 Nov 2000 09:36:41 +0900 (JST)
Received: from nt1.epkowa.co.jp (nt1.epkowa.co.jp [172.16.130.15])
by kowasv.epkowa.co.jp (8.9.3/3.7W-11/27/99) with ESMTP id JAA50160
for <submit@bugs.debian.org>; Mon, 20 Nov 2000 09:32:57 +0900 (JST)
Received: from frodo.epkowa.co.jp ([172.16.142.101]) by nt1.epkowa.co.jp with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0)
id V7PWBJVM; Mon, 20 Nov 2000 09:49:13 +0900
Received: from olaf by frodo.epkowa.co.jp with local (Exim 3.12 #1 (Debian))
id 13xf8E-0006Om-00
for <submit@bugs.debian.org>; Mon, 20 Nov 2000 09:48:26 +0900
To: submit@bugs.debian.org
Subject: md5sum.txt file for disks-i386 doesn't match files on server
References: <87snore2tw.fsf@frodo.epkowa.co.jp> <oa4s155e9n.fsf@arroz.fake>
From: Olaf Meeuwissen <olaf@epkowa.co.jp>
Date: 20 Nov 2000 09:48:25 +0900
In-Reply-To: Adam Di Carlo's message of "18 Nov 2000 13:25:08 -0500"
Message-ID: <87r947o4di.fsf_-_@frodo.epkowa.co.jp>
Lines: 59
User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.7
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Delivered-To: submit@bugs.debian.org
Package: boot floppies
Version: N/A
Adam Di Carlo <adam@onshore.com> writes:
> Olaf Meeuwissen <olaf@epkowa.co.jp> writes:
>
> > I don't know if anyone noticed, but it looks like the md5sum.txt for
> > potato's disks-i386 directory doesn't match what's in there.
> >
> > I've pulled in 2.2.17-2000-11-11 last night and compared a locally
> > computed md5sum.txt with the one pulled down. Had to jump hoops to
> > get things sorted, but the diff says that all(?) files in lang/ have
> > different MD5sums as well as most/all *.txt files.
>
> Is there a script to compare the md5sum file with the actual files?
According to `man md5sum` the following should work (but doesn't)
olaf@bilbo:disks-i386/2.2.17-2000-11-11$ md5sum -c md5sum.txt
md5sum: can't open ./README.txt
md5sum: can't open ./READ-pl.txt
[...]
md5sum: can't open ./images-1.20/safe/README.txt
md5sum: no files checked
olaf@bilbo:disks-i386/2.2.17-2000-11-11$
Instead I did (something like) the following:
olaf@bilbo:disks-i386/2.2.17-2000-11-11$ for f in `find . -type f`; do
> md5sum $f; done | sort -k2 > /tmp/md5sum.local
olaf@bilbo:disks-i386/2.2.17-2000-11-11$ sort -k2 md5sum.txt |
> diff --unified=0 -b - /tmp/md5sum.local
Note, the `-b' is essential (and probably also explains why md5sum
doesn't work). Looks like you use some home-brewn recipe to generate
the md5sum.txt file that messes with white space (though I couldn't
find any). Consider using `md5sum' instead because then you could
just use `md5sum -c md5sum.txt` as in:
olaf@bilbo:disks-i386/2.2.17-2000-11-11$ md5sum -c /tmp/md5sum.local
olaf@bilbo:disks-i386/2.2.17-2000-11-11$
> > BTW, there are no MD5sums for doc/ and images-*/safe/.
> >
> > While it is reassuring that at least (most of) the binary files match,
> > I was wondering if there is a problem with the rest and, if so, where
> > and when it will be fixed.
>
> Can you please file a bug against boot-floppies 2.2.17 so we can track
> this problem?
Consider it done ;-)
-- System Information
Debian Release: 2.2
Kernel Version: Linux bilbo 2.2.17 #1 Sun Jun 25 09:24:41 EST 2000 i686 unknown
--
Olaf Meeuwissen Epson Kowa Corporation, Research and Development
---------------------------------------
Received: (at 77487-done) by bugs.debian.org; 4 Dec 2000 14:59:43 +0000
>From adam@onshore.com Mon Dec 04 08:59:43 2000
Return-path: <adam@onshore.com>
Received: from (burrito.onshore.com) [64.22.101.122] (postfix)
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 142x5i-0008Rw-00; Mon, 04 Dec 2000 08:59:42 -0600
Received: from arroz.fake (localhost [127.0.0.1])
by burrito.onshore.com (Postfix) with ESMTP
id 492BF93802; Mon, 4 Dec 2000 09:59:49 -0500 (EST)
Sender: apharris@burrito.onshore.com
To: Olaf Meeuwissen <olaf@epkowa.co.jp>
Cc: 77487-done@bugs.debian.org
Subject: Re: Bug#77487: md5sum.txt file for disks-i386 doesn't match files on server
References: <[🔎] oabsuufft1.fsf@arroz.fake> <[🔎] 87sno5lzjq.fsf@frodo.epkowa.co.jp>
From: Adam Di Carlo <adam@onshore.com>
Date: 04 Dec 2000 09:59:49 -0500
In-Reply-To: Olaf Meeuwissen's message of "04 Dec 2000 10:56:25 +0900"
Message-ID: <oahf4kdyfu.fsf@arroz.fake>
Lines: 20
User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Delivered-To: 77487-done@bugs.debian.org
Olaf Meeuwissen <olaf@epkowa.co.jp> writes:
> See the end of that third line, \r\n, hmmm, that looks very DOSish and
> is bound to trip up md5sum. Same thing in README.txt. Bet the other
> text files have the same problem. Oops, looks like I used an FTP URL
> and got bitten by the infamous binary/ascii download no-no courtesy of
> wget :-{
>
> Sorry for the false alarm!
No problem.
> > Is this bug closable?
>
> Yes. And thanks for making me do my homework ;-)
Heh.
--
.....Adam Di Carlo....adam@onShore.com.....<URL:http://www.onShore.com/>
Reply to: