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#3532 - lib/lzo: invalid MD5sums
Attached to Project:
Arch Linux
Opened by Jürgen Hötzel (juergen) - Sunday, 27 November 2005, 22:21 GMT
Last edited by Jürgen Hötzel (juergen) - Monday, 28 November 2005, 13:38 GMT
Opened by Jürgen Hötzel (juergen) - Sunday, 27 November 2005, 22:21 GMT
Last edited by Jürgen Hötzel (juergen) - Monday, 28 November 2005, 13:38 GMT
|
Details[juergen@epia lzo]$ makepkg
==> Entering fakeroot environment ==> Making package: lzo 1.08-4 (Sun Nov 27 23:20:12 CET 2005) ==> Checking Runtime Dependencies... ==> Checking Buildtime Dependencies... ==> Retrieving Sources... ==> Found lzo-1.08.tar.gz in build dir ==> Found nasm-gcc3.patch in build dir ==> Validating source files with MD5sums lzo-1.08.tar.gz ... Passed nasm-gcc3.patch ... FAILED ==> ERROR: One or more files did not pass the validity check! Jürgen 
PKGBUILD.diff
(0.6 KiB)
|
This task depends upon
Strange thing. The (old) md5sums match on my up-to-date copy of nasm-gcc3.patch. Care to attach yours so we can see what's different?
really strange. My working dir is uptodate:
cvs update: Updating .
cvs update: warning: nasm-gcc3.patch was lost
U nasm-gcc3.patch
bash-3.00$ md5sum nasm-gcc3.patch
43fb13762383b572d22152f8815ea4a5 nasm-gcc3.patch
Jürgen