On 4/24/20 2:21 PM, Bruce Dubbs via blfs-support wrote:
On 4/24/20 9:32 AM, Richard via blfs-support wrote:
On 4/23/20 2:08 PM, Bruce Dubbs via blfs-support wrote:
On 4/23/20 10:51 AM, Richard via blfs-support wrote:
I've downloaded xterm-353.tgz from two different
locations, and in each case I get the following
md5sum, which doesn't match the value given
in the blfs-9.1 book:
fd3c8948475b53044a72a10ba04e8088
I don't know where you got your version, but I get:
$ wget http://invisible-mirror.net/archives/xterm/xterm-353.tgz
--2020-04-23 13:02:35--
http://invisible-mirror.net/archives/xterm/xterm-353.tgz
Resolving invisible-mirror.net... 160.153.42.69
Connecting to invisible-mirror.net|160.153.42.69|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1407183 (1.3M) [application/x-tar]
Saving to: ‘xterm-353.tgz’
xterm-353.tgz 100%[================================>] 1.34M
1.67MB/s in 0.8s
2020-04-23 13:02:36 (1.67 MB/s) - ‘xterm-353.tgz’ saved
[1407183/1407183]
$ md5sum xterm-353.tgz
247c30ebfa44623f3a2d100e0cae5c7f xterm-353.tgz
The mirror master has the same md5sum.
-- Bruce
Here is something I don't understand. If I use wget
to fetch xterm-353.tgz, as you did, then I get the
same md5sum as you, which is also in the book.
However if I paste the link to the file in the
Firefox address bar and press enter, then request
to save the file, I get a xterm-353.tgz file that
has a slightly different size and the different
md5sum that I reported above. I have been using
the latter method (pasting links in the Firefox
address bar) to download all the files, and
all the other md5sums are correct. Do you have
any idea why that method doesn't seem to
work for the xterm-353.tgz file?
The only thing I can think of is that there is some DNS forwarding
going on and actually downloading from a different site. What happens
if you use:
http://160.153.42.69/archives/xterm/xterm-353.tgz
Also you can try unpacking both files and doing a diff. You will have
to rename the directory xterm-353/ after untarring the first tarball
to, say, xterm-353-bad/ and then doing:
diff -Naur xterm-353-bad xterm-353
If you get no output then the contents of the files are identical and
there is some timestamps that are different.
If there are changes, please post them here. The files being
different sizes is an indication that there will be something
different. It may be innocent but depends on the actual differences.
-- Bruce
If I put the following link in the FF address bar:
http://160.153.42.69/archives/xterm/xterm-353.tgz
I get the error:
File not found (404 error)
I was able to verify what Pierre Labastie found, namely that
FF applies an extra gzip to the downloaded file. The
directory xterm_bad has the FF downloaded file, and
xterm_good has the correct file obtained using wget:
rkm:~/xterm_bad$ ls -l
total 1376
-rw-rw-r-- 1 rkm rkm 1403484 Apr 25 10:53 xterm-353.tgz
rkm:~/xterm_bad$ md5sum xterm-353.tgz
fd3c8948475b53044a72a10ba04e8088 xterm-353.tgz
rkm:~/xterm_bad$ tar xzf xterm-353.tgz
tar: This does not look like a tar archive
tar: Skipping to next header
tar: Exiting with failure status due to previous errors
rkm:~/xterm_bad$ gunzip xterm-353.tgz
rkm:~/xterm_bad$ ls -l
total 1380
-rw-rw-r-- 1 rkm rkm 1407183 Apr 25 10:53 xterm-353.tar
rkm:~/xterm_bad$ md5sum xterm-353.tar
247c30ebfa44623f3a2d100e0cae5c7f xterm-353.tar
rkm:~/xterm_bad$ mv xterm-353.tar xterm-353.tgz
rkm:~/xterm_bad$ tar xzf xterm-353.tgz
rkm:~/xterm_bad$ ls
xterm-353 xterm-353.tgz
rkm:~/xterm_bad$ diff -Naur xterm-353 ../xterm_good/xterm-353
rkm:~/xterm_bad$
Also, you may be right about DNS forwarding in some cases.
When I used FF to download the file:
mypaint-brushes-v1.3.0.tar.gz
FF downloaded a file that had the correct md5sum, but the
file name was slightly different:
mypaint-brushes-1.3.0.tar.gz
i.e. the "v" was missing. Maybe that indicates that FF got
the file from a different location?
Richard
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
