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#41591 - [yagf] md5sums mismatch
Attached to Project:
Community Packages
Opened by Eric Belanger (Snowman) - Sunday, 17 August 2014, 15:57 GMT
Last edited by Sergej Pupykin (sergej) - Thursday, 21 August 2014, 09:58 GMT
Opened by Eric Belanger (Snowman) - Sunday, 17 August 2014, 15:57 GMT
Last edited by Sergej Pupykin (sergej) - Thursday, 21 August 2014, 09:58 GMT
|
DetailsDescription:
$ makepkg --allsource ==> Making package: yagf 0.9.4-1 (Sun Aug 17 11:54:15 EDT 2014) ==> Retrieving sources... -> Downloading yagf-0.9.4.tar.gz... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 432k 0 432k 0 0 18316 0 --:--:-- 0:00:24 --:--:-- 22590 ==> Validating source files with md5sums... yagf-0.9.4.tar.gz ... FAILED ==> ERROR: One or more files did not pass the validity check! |
This task depends upon
Comment by Eric Belanger (Snowman) -
Thursday, 21 August 2014, 05:16 GMT
The md5sums change every time the source is downloaded. Should be fixed by placing a source tarball on ftp.archlinux.org or using 'SKIP' for md5sums.