Arch Linux

Please read this before reporting a bug:

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
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To No-one
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


[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!

This task depends upon

Closed by  Judd Vinet (judd)
Monday, 05 December 2005, 18:35 GMT
Reason for closing:  Fixed
Comment by Judd Vinet (judd) - Monday, 28 November 2005, 19:18 GMT
Hi Jürgen,

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?
Comment by Jürgen Hötzel (juergen) - Monday, 28 November 2005, 20:21 GMT
Hi Judd,

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