Emit standard sha512sum format in release checksums#769
Merged
Conversation
Surfaced during 0.42.0-incubating RC3 verification: the .sha512 files
shipped on dist.apache.org contain only the bare hex digest, so the
standard 'sha512sum -c file.sha512' recipe returns 'no properly
formatted checksum lines found'. Voters either have to work around it
with 'echo "$(cat ${F}.sha512) ${F}" | sha512sum -c -' (as the
README currently does) or compare digests by hand.
Switch _checksum_artifact() to emit the standard '<digest> <filename>'
layout that sha512sum -c and shasum -c both expect, and simplify the
verification recipe in scripts/README.md to plain
'sha512sum -c <file>.sha512'.
Both checksum readers in the repo (scripts/verify_apache_artifacts.py
and scripts/apache_release.py::_verify_artifact_checksum) already use
'.read().strip().split()[0]', so they accept both the old and the new
format -- verification of existing RCs on dist.apache.org keeps working
unchanged.
Vote thread:
https://lists.apache.org/thread/bhcwnjpbx7vhnql48z7vc3njpgrx9qmj
elijahbenizzy
approved these changes
May 9, 2026
Contributor
elijahbenizzy
left a comment
elijahbenizzy
left a comment
There was a problem hiding this comment.
This looks good, thank you!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Surfaced during 0.42.0-incubating RC3 verification: the
.sha512files shipped on dist.apache.org contain only the bare hex digest, so the standardsha512sum -c file.sha512recipe returns "no properly formatted checksum lines found". Voters either work around it withecho "$(cat ${F}.sha512) ${F}" | sha512sum -c -(as the README currently does, see lines 132–134) or compare digests by hand.Change
scripts/apache_release.py::_checksum_artifact()— emit the standard<digest> <filename>\nlayout thatsha512sum -candshasum -cboth expect.scripts/README.md— drop theecho "$(cat …)"workaround in the verification workflow and use plainsha512sum -c <file>.sha512.Compatibility
Both checksum readers in the repo already use
.read().strip().split()[0]:scripts/verify_apache_artifacts.py:113scripts/apache_release.py::_verify_artifact_checksum(line 310)So they accept both the old bare-digest format and the new standard format — verification of existing RCs on dist.apache.org keeps working unchanged.
Sanity test
Vote thread
https://lists.apache.org/thread/bhcwnjpbx7vhnql48z7vc3njpgrx9qmj
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.7) following the verification of 0.42.0-incubating RC3 on the IPMC vote thread.