There should be a wiki page describing the manual steps to generate/verify a SHA 512 checksum for PKI source tarball.
The compose script should be modified to generate the checksum automatically and store it in a separate file. The checksum files should be linked from the official download page.
Metadata Update from @mharmsen: - Custom field component adjusted to None - Custom field feature adjusted to None - Custom field origin adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None - Issue set to the milestone: 0.0 NEEDS_TRIAGE
Metadata Update from @vakwetu: - Issue priority set to: major - Issue set to the milestone: 10.6 (was: 0.0 NEEDS_TRIAGE)
The tarball is now generated by GitHub and the checksum is stored in Fedora package repository:
See also http://pki.fedoraproject.org/wiki/PKI_Fedora_Development.
Metadata Update from @edewata: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @edewata: - Issue set to the milestone: 10.6.0 (was: 10.6)
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/2911
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.