This is an automated email from the ASF dual-hosted git repository.
GGraziadei pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/storm.git
The following commit(s) were added to refs/heads/master by this push:
new f67e6d4a2 verify-release-file.sh: check .sha512 files with sha512sum
-c (#8906)
f67e6d4a2 is described below
commit f67e6d4a2c3c921f5a277eda361d62216cea4144
Author: Gianluca Graziadei <[email protected]>
AuthorDate: Sun Jul 19 14:40:42 2026 +0200
verify-release-file.sh: check .sha512 files with sha512sum -c (#8906)
The script compared the output of 'gpg --print-md SHA512' textually
against the published .sha512 file, but release .sha512 files are
generated in sha512sum format, so the diff always failed and the script
reported 'SHA file is not correct' even when the hash matched.
Verified against the apache-storm-2.8.9-rc1 artifacts: the script now
reports 'SHA file is correct' for a valid file.
Co-authored-by: Claude Fable 5 <[email protected]>
---
dev-tools/rc/verify-release-file.sh | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/dev-tools/rc/verify-release-file.sh
b/dev-tools/rc/verify-release-file.sh
index 3e6a8690b..933990f42 100755
--- a/dev-tools/rc/verify-release-file.sh
+++ b/dev-tools/rc/verify-release-file.sh
@@ -35,12 +35,10 @@ else
fi
# checking SHA
-GPG_SHA_FILE="/tmp/${TARGET_FILE}_GPG.sha512"
-gpg --print-md SHA512 ${TARGET_FILE} > ${GPG_SHA_FILE}
SHA_TARGET_FILE="${TARGET_FILE}.sha512"
echo ">> checking SHA file... (${SHA_TARGET_FILE})"
-diff /tmp/${TARGET_FILE}_GPG.sha512 ${SHA_TARGET_FILE}
+sha512sum -c ${SHA_TARGET_FILE}
if [ $? -eq 0 ];
then
