#19 Checksums of release 0.3.111 and 0.3.112 don't match
Closed 2 years ago by benjamin.antal.memgraph. Opened 2 years ago by benjamin.antal.memgraph.

Hi! I downloaded the latest tarballs and I found out none of the checksums are valid:

user@mylaptop:~/tmp/libaio$ ls -la
total 104
drwxrwxr-x 2 kovi kovi  4096 Dec 13 16:09 .
drwxrwxr-x 8 kovi kovi  4096 Dec 13 16:09 ..
-rw-rw-r-- 1 kovi kovi   554 Dec 13 16:08 CHECKSUMS
-rw-rw-r-- 1 kovi kovi 44590 Dec 13 15:26 libaio-0.3.111.tar.gz
-rw-rw-r-- 1 kovi kovi 46391 Dec 13 15:22 libaio-0.3.112.tar.gz
user@mylaptop:~/tmp/libaio$ sha512sum -c CHECKSUMS 
libaio-0.3.111.tar.gz: FAILED
libaio-0.3.112.tar.gz: FAILED
sha512sum: WARNING: 2 lines are improperly formatted
sha512sum: WARNING: 2 computed checksums did NOT match
user@mylaptop:~/tmp/libaio$ sha256sum -c CHECKSUMS 
libaio-0.3.111.tar.gz: FAILED
libaio-0.3.112.tar.gz: FAILED
sha256sum: WARNING: 2 lines are improperly formatted
sha256sum: WARNING: 2 computed checksums did NOT match

And here are the hashes I got:

user@mylaptop:~/tmp/libaio$ sha256sum libaio-0.3.111.tar.gz 
e6bc17cba66e59085e670fea238ad095766b412561f90b354eb4012d851730ba  libaio-0.3.111.tar.gz
user@mylaptop:~/tmp/libaio$ sha512sum libaio-0.3.111.tar.gz 
af29584ff45119bf238e0ee03577c2c217d29e40a1e73536bad1801fb9f137acf59df228706d62990c88efd24250eef497e6c9d527896226c1f16788b60ca4b2  libaio-0.3.111.tar.gz
user@mylaptop:~/tmp/libaio$ sha256sum libaio-0.3.112.tar.gz 
b7cf93b29bbfb354213a0e8c0e82dfcf4e776157940d894750528714a0af2272  libaio-0.3.112.tar.gz
user@mylaptop:~/tmp/libaio$ sha512sum libaio-0.3.112.tar.gz 
1fe56c3ec1908f4c05bb777f03e2398014d79c290650c599123d2a72d23a42cc3097af015cb2bc5dd21cc5f8181946fab54c79a54a4d21a7a5029bb7f912697b  libaio-0.3.112.tar.gz

Am I doing something wrong, or the tarballs/checksums are not okay?


I was doing something wrong. I downloaded the packages from the Releases page not from release folder.

Metadata Update from @benjamin.antal.memgraph:
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata