Anyone else encounter this discrepancy?
Did Elastic forget to update the SHA512 hash text for comparison with the Oct. 2nd release?
Or has the download been corrupted?
I just downloaded the tarball and it checks out for me:
$ curl -O https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-6.4.2.tar.gz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 93.3M 100 93.3M 0 0 1149k 0 0:01:23 0:01:23 --:--:-- 2248k
$ shasum -a512 elasticsearch-6.4.2.tar.gz
23c610a8cd33d4229e8b79b0dc5e1f106e5f186d45c83e9994bb15708d2ce4e763fcb7c9be0f652ebdf12905be7f4ced14e1d8e18f6240dfe5ccb4a064239f86 elasticsearch-6.4.2.tar.gz
$ curl https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-6.4.2.tar.gz.sha512
23c610a8cd33d4229e8b79b0dc5e1f106e5f186d45c83e9994bb15708d2ce4e763fcb7c9be0f652ebdf12905be7f4ced14e1d8e18f6240dfe5ccb4a064239f86 elasticsearch-6.4.2.tar.gz
I think your download is corrupt and you should retry.
Your screenshot was clear enough to me but please in future could you include the relevant information as text too? Text makes it clearer what's going on, improves accessibility for those of us using screenreaders etc, and makes it easier for others to search for similar issues.
Oh, I think I see the difference. The copy I have is not compressed. Maybe Mac OS uncompressed it.
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.