FS#70361 - [bmake] use https, sha256

Attached to Project: Community Packages
Opened by T.J. Townsend (blakkheim) - Thursday, 08 April 2021, 03:39 GMT
Last edited by Ivy Foster (escondida) - Saturday, 23 October 2021, 22:29 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Ivy Foster (escondida)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Attached diff switches the bmake PKGBUILD to download the source over HTTPS and switches the checksum from SHA1 to SHA256.

Additional info:
The SHA1 of the file remains the same.
   bmake.diff (0.6 KiB)
This task depends upon

Closed by  Ivy Foster (escondida)
Saturday, 23 October 2021, 22:29 GMT
Reason for closing:  Implemented
Additional comments about closing:  Well, half-implemented. See https://bugs.archlinux.org/task/70361#co mment203201
Comment by T.J. Townsend (blakkheim) - Sunday, 23 May 2021, 17:00 GMT
Friendly ping.
Comment by T.J. Townsend (blakkheim) - Wednesday, 15 September 2021, 21:30 GMT
Ping again.
Comment by T.J. Townsend (blakkheim) - Saturday, 23 October 2021, 21:51 GMT
Ping number three.
Comment by Ivy Foster (escondida) - Saturday, 23 October 2021, 22:28 GMT
Thanks for pointing out that crufty.net is now using https! With the latest update to version 20211001, the PKGBUILD now uses https for sources and for upstream's url. It also takes advantage of the new addition of upstream PGP signatures for releases.

However, since upstream provides only md5sums and sha1sums, I will not be adding my own sha256sums; fortunately, we now have PGP verification as well as simple checksum verification.

Loading...