Currently, the sha256sums files are assembled by hand (copy-pasting the hash results from the Gitian build).
This patch introduces make-sha256sums.sh to do this automatically.
Details
- Reviewers
deadalnix Fabien - Group Reviewers
Restricted Project - Commits
- rSTAGINGb2c7043ba97e: Add a script to generate sha256sums from Gitian output
rABCb2c7043ba97e: Add a script to generate sha256sums from Gitian output
make-sha256sums.sh -h make-sha256sums.sh # errors as expected make-sha256sums.sh [path to some gitian output] make-sha256sums.sh path/to/0.20.9 > jasonbcox-sha256sums.0.20.9
Diff Detail
- Repository
- rABC Bitcoin ABC
- Branch
- make-sha256sums
- Lint
Lint Passed - Unit
No Test Coverage - Build Status
Buildable 8862 Build 15699: Default Diff Build & Tests Build 15698: arc lint + arc unit
Event Timeline
contrib/release/make-sha256sums.sh | ||
---|---|---|
33 ↗ | (On Diff #15324) | Since there is no version number in the res.yml anymore the wildcard is not required. |
contrib/release/make-sha256sums.sh | ||
---|---|---|
33 ↗ | (On Diff #15324) | On the contrary, I wanted this script to work for old releases until we get one or two new ones out. It allows me to easily test the script, etc. I can make it less greedy though. |
contrib/release/make-sha256sums.sh | ||
---|---|---|
33 ↗ | (On Diff #15324) | Also note that the pattern you gave will greedily match, so not really working as intended: |
While I don't have anything against that patch per se, it seems somewhat questionable that the signing process that core used was ditched in favor of something that clearly requires work.
Core's process makes many assumptions that do not patch over to ours well. It will take some time to reconcile these before our process closely matches theirs. In the mean time, this saves us time on every release.