I saw the SHA256SUM file published for release 1.3.1.
I think there is a problem with current file:
ef29def5d0ffed54fe1f8b48049be939ff24b04082a683406bc4d29859a360cc linux x86_64
e934507c885a2818cd3e7ded1155a8505f762409b094752d41913c80a119fd92 linux arm aarch_64
fef126513c3b1a1f1ce29673f596547b16e31103cbc31007297f77b92e91b0eb windows installable
9332eb4183e61022981b2779d7e2ce82187a9a933a72683bb69729305ee1e28b windows portable
cb62e5921c058844d8b0a2900ae3316f86d8baacbb00d1b7c89d5e4dc40185d1 macos zip
The right-hand part of every line should contain the actual filename of the binary (e.g.:
Gitnuro-linux-x86_64-1.3.1.jar) not those explanation words like linux x86_64 -- please note there are 2 (two) spaces between the two words:
@JetpackDuba
I saw the SHA256SUM file published for release 1.3.1.
I think there is a problem with current file:
The right-hand part of every line should contain the actual filename of the binary (e.g.:
Gitnuro-linux-x86_64-1.3.1.jar
) not those explanation words likelinux x86_64
-- please note there are 2 (two) spaces between the two words:For comparison, here is the
SHA512SUM
file for Debian.iso
images: