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#55527 - [dtkcore] checksum mismatch
Attached to Project:
Community Packages
Opened by Erich Eckner (deepthought) - Wednesday, 06 September 2017, 06:48 GMT
Last edited by Eli Schwartz (eschwartz) - Monday, 25 December 2017, 14:54 GMT
Opened by Erich Eckner (deepthought) - Wednesday, 06 September 2017, 06:48 GMT
Last edited by Eli Schwartz (eschwartz) - Monday, 25 December 2017, 14:54 GMT
|
DetailsDescription:
The checksum of the source does not match: ==> Retrieving sources... -> Downloading dtkcore-2.0.0.tar.gz... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 126 0 126 0 0 126 0 --:--:-- --:--:-- --:--:-- 249 100 66021 0 66021 0 0 66021 0 --:--:-- 0:00:01 --:--:-- 118k ==> Validating source files with sha512sums... dtkcore-2.0.0.tar.gz ... FAILED ==> ERROR: One or more files did not pass the validity check! Additional info: * package version(s) dtkcore-1:2.0.0-2 (git revision 60b0e8e9e47c306645542d89ebb874d04eff0641) Steps to reproduce: > makepkg --verifysource |
This task depends upon
Closed by Eli Schwartz (eschwartz)
Monday, 25 December 2017, 14:54 GMT
Reason for closing: Fixed
Additional comments about closing: automatically fixed when the package was updated to a new version (dtkcore 1:2.0.1-1)
Monday, 25 December 2017, 14:54 GMT
Reason for closing: Fixed
Additional comments about closing: automatically fixed when the package was updated to a new version (dtkcore 1:2.0.1-1)
Comment by Felix Yan (felixonmars) -
Monday, 25 December 2017, 04:39 GMT
Is it still an issue? I could not reproduce.