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#3673 - md5 validity failure on lirc as-is in cvs
|
Details==> Entering fakeroot environment
==> Making package: lirc 0.7.2-5 (Thu Dec 29 20:33:26 EST 2005) ==> Checking Runtime Dependencies... ==> Checking Buildtime Dependencies... ==> Retrieving Sources... ==> Using local copy of lirc-0.7.2.tar.bz2 ==> Found 2.6.14.patch in build dir ==> Found lircd in build dir ==> Found lircmd in build dir ==> Validating source files with MD5sums lirc-0.7.2.tar.bz2 ... Passed 2.6.14.patch ... FAILED lircd ... Passed lircmd ... Passed ==> ERROR: One or more files did not pass the validity check! |
This task depends upon
Comment by Jan de Groot (JGC) -
Friday, 30 December 2005, 11:33 GMT
The patchfile contains CVS IDs, After commiting to CVS, it won't even apply anymore since the CVS headers in the patchfile have changed.