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#1390 - pacman won't build with bad MD5sum
Attached to Project:
Arch Linux
Opened by Steven J. Slizewski (slyski) - Monday, 06 September 2004, 19:29 GMT
Opened by Steven J. Slizewski (slyski) - Monday, 06 September 2004, 19:29 GMT
|
Details[root@eclip pacman]# makepkg -cb
==> Making package: pacman (Mon Sep 6 14:28:39 UTC 2004) ==> Checking Runtime Dependencies... ==> Checking Buildtime Dependencies... ==> Retrieving Sources... ==> Using local copy of pacman-2.8.4.tar.gz ==> Using local copy of sortmirrors.pl ==> Found supfile.arch in build dir ==> Found supfile.extra in build dir ==> Found supfile.unstable in build dir ==> Found abs in build dir ==> Found abs.conf in build dir ==> Validating source files with MD5sums pacman-2.8.4.tar.gz ... Passed sortmirrors.pl ... FAILED supfile.arch ... Passed supfile.extra ... Passed supfile.unstable ... Passed abs ... Passed abs.conf ... Passed ==> ERROR: One or more files did not pass the validity check! [root@eclip pacman]# it's been like this for the last few builds. finally got around filing this |
This task depends upon
Comment by Judd Vinet (judd) -
Monday, 06 September 2004, 19:39 GMT
It's likely your local copy. The md5sums match up fine for me. The correct sum is '005d82a4832b5273450e556f30010414'.