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#58816 - [xcursor-bluecurve] wrong checksum
Attached to Project:
Community Packages
Opened by Andreas Baumann (andreas_baumann) - Friday, 01 June 2018, 05:04 GMT
Last edited by Kyle Keen (keenerd) - Saturday, 02 June 2018, 03:02 GMT
Opened by Andreas Baumann (andreas_baumann) - Friday, 01 June 2018, 05:04 GMT
Last edited by Kyle Keen (keenerd) - Saturday, 02 June 2018, 03:02 GMT
|
DetailsDescription:
==> Validating source files with md5sums... xcursor-bluecurve-0.1.1.tgz ... FAILED ==> ERROR: One or more files did not pass the validity check! Additional info: * package version(s): 0.1.1-6 * config and/or log files etc. Steps to reproduce: makepkg -s |
This task depends upon
Closed by Kyle Keen (keenerd)
Saturday, 02 June 2018, 03:02 GMT
Reason for closing: Fixed
Additional comments about closing: in SVN
Saturday, 02 June 2018, 03:02 GMT
Reason for closing: Fixed
Additional comments about closing: in SVN
Comment by Kyle Keen (keenerd) -
Saturday, 02 June 2018, 02:36 GMT
Ugh. There is something dynamic in the tarball and it has a different checksum every time.