[Release] .sha{256,512} for .jar related files should use relative path not absolute path for easy to use #592

Activity

1. kou

   added

   Type: enhancementNew feature or requestNew feature or request

   on Feb 7, 2025
2. jbonofre

   self-assigned this

   on Feb 12, 2025
3. jbonofre commented on Feb 12, 2025

   

   jbonofre

   on Feb 12, 2025

   Member

   More actions

   Yes, agree, related path is preferred 😄
4. kou commented on Apr 15, 2025

   

   kou

   on Apr 15, 2025

   MemberAuthor

   More actions

   @yyossy5 You may be interested in this.

   We must provide checksums for release artifacts based on the Apache Software Foundation policy: https://infra.apache.org/release-distribution.html#sigs-and-sums

   We generate checksums for binary artifacts by

   arrow-java/ci/scripts/jni_full_build.sh

   Lines 100 to 103 in 4b4d928

   	for artifact in "${dist_dir}"/*; do
   	sha256sum "${artifact}" >"${artifact}.sha256"
   	sha512sum "${artifact}" >"${artifact}.sha512"
   	done

   but it uses absolute paths not relative paths. It's inconvenient because we can't use sha512sum -c to verify the checksums.

   FYI: We can use $(basename "${artifact}") to get basename in shell.

   ❤️React with ❤️1Reacted by yysd
5. yysd5 commented on Apr 15, 2025

   

   yysd5

   on Apr 15, 2025

   More actions

   Thank you @kou , I'll check this when I have a moment.
6. kou

   added a commit that references this issue on Oct 8, 2025

   apacheGH-592: [Release] Use relative path in .sha*

   41804f7
7. lidavidm

   added a commit that references this issue on Oct 8, 2025

   GH-592: [Release] Use relative path in .sha* (#879)

   ...

   37e9ba6
8. lidavidm

   closed this as completedin #879on Oct 8, 2025