OSGeo
doc: use the correct release tarball, which includes generated content
With the 8.4.2 release, the wrong tarball ended up on the server. One that is missing the generated files from this part:
https://github.com/OSGeo/grass/blob/a0b61664ad13688cf3abaf012295b8db9583df48/.github/workflows/create_release_draft.yml#L50-L61
(But for 8.4.2. this is too late, we cannot/mustn't replace the tarball now, that will lead to problems. )
Where do you think the md5sum should come from? Now it is locally generated, but there is one uploaded from the CI.
Where do you think the md5sum should come from? Now it is locally generated, but there is one uploaded from the CI.
I was thinking of adding an instruction of downloading the md5sum file and compare with a sum check on the downloaded tarball (a bit of a security check). After that it doesn't matter which file,
Now I added a instructions for download of *.sha256 file and running sha256sum with it. The *.sha256 file will, and should, be uploaded to server (along with the *.md5sum file).
Please test on a Linux machine.