Merge bitcoin/bitcoin#33472: guix: documented shasum gathering command

ab649ce459450533ffdf068b00472259b72cf07a guix: documented shasum gathering command (janb84)

Pull request description:

  When a PR requires proof of Guix builds (sha256sums), the PR author or reviewer uses a not well documented command to collect the sha256sums of build outputs or manually gathers them from files.

  This pull request introduces a new section in the documentation, providing some documentation on the command's functionality and usage.

ACKs for top commit:
  willcl-ark:
    ACK ab649ce459450533ffdf068b00472259b72cf07a
  sedited:
    ACK ab649ce459450533ffdf068b00472259b72cf07a

Tree-SHA512: 0188663ad117b636c7d32a1b655db97610f558cfcffe4abd6f0fb097b3990db0dc6d23ab972926fefd2531b21f429742dcbea6b0fa579d22d5da7a7d6a4c753e
This commit is contained in:
merge-script 2026-01-28 17:31:40 +01:00
commit d9851f9a7c
No known key found for this signature in database
GPG Key ID: 9B79B45691DB4173

View File

@ -103,6 +103,18 @@ worktree to save disk space:
./contrib/guix/guix-clean
```
## Gathering shasums of build outputs
After a successful build, the shasums of the build outputs are gathered
into files named `SHA256SUMS`. These files are located in each of the
architecture-specific output directories.
To gather all shasums and output them together to console, for e.g.
inclusion in a Guix pull request comment, run:
``` sh
source contrib/shell/git-utils.bash && uname -m && find guix-build-$(git_head_version)/output/ -type f -print0 | env LC_ALL=C sort -z | xargs -r0 sha256sum
```
## Attesting to build outputs