On 1/22/2020 9:19 PM, Bruce Dubbs via blfs-support wrote:
On 1/22/20 9:23 PM, Alan Feuerbacher via blfs-support wrote:

On 1/22/20 7:26 PM, Douglas R. Reno via blfs-support wrote:

On 1/22/20 7:47 PM, Alan Feuerbacher via blfs-support wrote:
I'm going to post some emails detailing a few issues I've encountered building BLFS packages in the past several weeks. I believe some are real problems, others are probably the result of my ignorance of important things. Here we go:

I tried to build the updated xterm-352 in BLFS, but the
checksum for the tgz file did not match, and
"tar xf xterm-352.tgz" complained that this does not look
like a tar file. I checked the md5sum in the BLFS book
for this and it did not match.

I was able to find another download source:

https://fossies.org/linux/misc/xterm-352.tgz/

The checksum in the BLFS book matches with this file, and it
builds successfully. It works fine in X Windows.

Alan


Hi Alan,

I just downloaded it and extracted it to make sure that the link in the book worked. I didn't find any problems, and the MD5SUMs match. It was likely a transient problem upstream. Thank you for reporting though!

- Doug

Well something strange is going on, then. I just checked too, and the md5sums don't match. Here's what I did, with information from the latest edition of the BLFS book:


        Beyond Linux^® From Scratch (systemd Edition) - Version 2020-01-21


      Chapter 24. X Window System Environment


  xterm-352

  *

    Download (HTTP):
    http://invisible-mirror.net/archives/xterm/xterm-352.tgz

  *

    Download MD5 sum: 9d41798d035976715d532d38327f5e41


My commands for this latest tgz file:

alan [ ~ ]$ cat md5sums
9d41798d035976715d532d38327f5e41 xterm-352.tgz

alan [ ~ ]$ md5sum -c md5sums
xterm-352.tgz: FAILED
md5sum: WARNING: 1 computed checksum did NOT match

alan [ ~ ]$ ll xterm*
-rw-r--r-- 1 alan wheel 1402285 Jan 22 19:52 xterm-352.tgz


Files downloaded several days ago. Note that the xterm-352.tgz file is from https://fossies.org/linux/misc/xterm-352.tgz/ .

alan [ /sources/xc ]$ ll xterm*tgz
-rw-r--r-- 1 lfs wheel 1401009 Jan 16 00:53 xterm-351.tgz
-rw-r--r-- 1 lfs  1000 1405420 Jan 18 22:20 xterm-352.tgz

The size is different from the file downloaded from the BLFS book, and it matches to the checksum given in the BLFS book.

Evidently there is an issue in one of the xterm mirrors.  There is nothing we can do about that.  The reason we provide md5sums if so you can detect just these types of problems.

Ok.


You can always go to one of our file mirrors and get any BLFS package. It's just not from the upstream developer's primary location.

What do you mean by "upstream developer"?


http://www.linuxfromscratch.org/mirrors.html

I looked at the mirrors for North America. For xterm-352 each one gave a link to http://invisible-mirror.net -- exactly what is in the BLFS book. So they would not give the proper file.

So how does one decide which mirror to use? I've never run into this before.

Alan

--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to