Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
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
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
|
DetailsDescription:
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. |
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
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
bmake.diff
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.