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#57767 - [supercollider] source checksum mismatch
Attached to Project:
Community Packages
Opened by Erich Eckner (deepthought) - Friday, 09 March 2018, 12:37 GMT
Last edited by David Runge (dvzrv) - Friday, 09 March 2018, 18:12 GMT
Opened by Erich Eckner (deepthought) - Friday, 09 March 2018, 12:37 GMT
Last edited by David Runge (dvzrv) - Friday, 09 March 2018, 18:12 GMT
|
DetailsDescription:
The checksum of the source does not match: ==> Making package: supercollider 3.9.1-2 (Fr 9. Mär 13:34:44 CET 2018) ==> Retrieving sources... -> Downloading SuperCollider-3.9.1-Source-linux.tar.bz2... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 629 0 629 0 0 1221 0 --:--:-- --:--:-- --:--:-- 1218 100 10.5M 100 10.5M 0 0 2756k 0 0:00:03 0:00:03 --:--:-- 4357k ==> Validating source files with sha512sums... SuperCollider-3.9.1-Source-linux.tar.bz2 ... FAILED ==> ERROR: One or more files did not pass the validity check! Additional info: * package version(s) supercollider 3.9.1-2 (git revision fb7e305d812fd08a5312731e9a6ec655020867ca) Steps to reproduce: > git checkout fb7e305d812fd08a5312731e9a6ec655020867ca > cd supercollider/repos/community-x86_64 > makepkg --verifysource |
This task depends upon
Closed by David Runge (dvzrv)
Friday, 09 March 2018, 18:12 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in 3.9.1-3.
Friday, 09 March 2018, 18:12 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in 3.9.1-3.
However, it is possible, that upstream has changed their assets for that release without notification in the meantime!
Rebuilding as we speak.