> On Jul 14, 2026, at 06:30, David H. Gutteridge <david%gutteridge.ca@localhost> wrote: > > Looks like this is a parallelism issue, as I suspected. My example above > is with "-j 8", where these checksums are spun up in parallel quite > quickly. So something would have to deal with this. Yes, indeed a parallelism issue. That is now fixed. I believe this now fixes all the issues with creating hashes for multiple, compressed release files in the same directory, and does the same for all (that I know of) uses in the tree. Please review the patch below. Once this is committed, the mkhashes script will become an integral part of the release process. Therefore, I am particularly interested that it be as portable as possible. I believe I have picked up all the relevant tools that might differ among build environments, but more eyes would be helpful. Thanks for any suggestions on offer. Cheers, Brook
Attachment:
mkhashes.patch
Description: Binary data