[Clfs-support] md5sum mismatches

[Andrew Bradford]

On Tue, Jun 7, 2011 at 7:31 PM,  <bailongom at aol.com> wrote:
> My md5sum computations differ from values reported in the CLFS book for the
> following package and patch:
>
> patch-2.6.1.tar.gz
> md5sum computed by me:          d758eb96d3f75047efc004a720d33daf      md5sum
> reported in CLFS book: 0818d1763ae0c4281bcdc63cdac0b2c0

I just downloaded patch-2.6.1.tar.bz2 and its md5sum is
0818d1763ae0c4281bcdc63cdac0b2c0 (same as the book but for the wrong
file).
The .tar.gz version gives me the same md5 as you're getting for the
.tar.gz: d758eb96d3f75047efc004a720d33daf.

I think there's just a mixup in matching the md5sum to the correct
tarball.  You should be fine using the .tar.gz version of patch (or
grab the .tar.bz2 version).

> perl-5.14.0-libc-1.patch
> md5sum computed by me:          6efb1ffa5a6961c239024c445e0adc9a
> md5sum reported in CLFS book:  d572b0cc87b35f1806fd84f88803fb66

I also compute the md5sum you've gotten for the perl patch.  Possibly
the md5sum didn't get updated when the patch changed?

This patch was changed on May 18th (commit
279277d27c9cda5abda3b9f50f30132585f18303) but may not have had the
md5sum updated (I don't see a commit changing the md5sum but I've only
looked quickly thru the web interface [I'm on a Windows box right now
and don't have the git repo local]).

> Can I trust the copies of files mentioned above and continue following the
> book's instructions of the linux system build process?

You should be fine trusting the files.

-Andrew

PS: This email to the list, being delivered to my gmail, got marked as
spam by gmail.  That's strange...