sebastianliebscher commented on issue #25333:
URL: https://github.com/apache/superset/issues/25333#issuecomment-1725832376
I noticed that too. The checksums are valid, but the file content format is
off, so it is hard to compare the checksums.
If you look at the content of `source.tar.gz.sha512` you will notice that it
is not a format `shasum` (or `sha512sum`) recognizes. This is because
`source.tar.gz.sha512` is generated via
```bash
gpg --print-md SHA512 "${NAME}" > "${NAME}".sha512
```
so instead you would have to compare the checksums with:
```bash
gpg --print-md SHA512 apache-superset-3.0.0-source.tar.gz | diff -
apache-superset-3.0.0-source.tar.gz.sha512
```
but unfortunately this shows you a diff as the full path is included:
```bash
➜ /tmp gpg --print-md SHA512 apache-superset-3.0.0-source.tar.gz | diff -
apache-superset-3.0.0-source.tar.gz.sha512
1,4c1,3
< apache-superset-3.0.0-source.tar.gz: 13ACE0D3 B24D150E 3E4462F3 BA235397
< 72B754C2 EAAF7FB4 013792BB 0552B0E2
< 679A4000 5A29ADE2 74340F33 69F6E2E7
< D04F56CF 1CDF85B1 82B7A5A0 38C7D874
---
>
/Users/michael_molina/svn/superset_dev/3.0.0rc4/apache-superset-3.0.0rc4-source.tar.gz:
> 13ACE0D3 B24D150E 3E4462F3 BA235397 72B754C2 EAAF7FB4 013792BB 0552B0E2
> 679A4000 5A29ADE2 74340F33 69F6E2E7 D04F56CF 1CDF85B1 82B7A5A0 38C7D874
```
I don't think there is a standard file format for `.sha512` files, but if
you look at how other Apache projects publish their checksums I'd suggest
replacing
```bash
gpg --print-md SHA512 "${NAME}" > "${NAME}".sha512
```
with
```bash
shasum -a 512 "${NAME}" > "${NAME}.sha512"
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
