On 09/02/17 14:21, Daniel James via Boost wrote:
On 9 Feb 2017 11:54, "Jonathan Wakely via Boost"
wrote: Checking the hash is a manual process that should be done by the maintainer, it can't cause updating the Fedora servers to fail (the infrastructure can't check the hash because it doesn't know what to compare it to). I screwed that up for the first cycle of rebuilds I did for Boost 1.63.0.
If you want the download info in a machine readable format, let me know. For example, I wrote a little script to generate a csv file:
The actions required from this, as I see them are: 1. eliminate the forwarding of the URL to snapshots. This may require altering the filename of the archive based on earlier discussions about the source forge forwarding logic. Perhaps include snapshot and date in the archive name? 2. produce a well-known download location for the hash, so that our release archives are able to be validated by scripts. I'd help do these if I had the access to do so. Are these actions correct, and are they assigned? Neil Groves