I suggest that you run a fsck on the partition that you're running makepkg on (if applicable) and do a memtest. It's possible that these integrity check failures and sed errors are symptoms caused by a more serious problem, like filesystem corruption and/or a faulty RAM module.
If those checks come back clean, check your internet connection and keep deleting/redownloading things until you get no integrity failures.
Okay, turned out I was downloading the file off the Arch site incorrectly - the browser was stripping out a space at the end for some reason which using abs didn't cause, and trying it with Firefox on other machines did the same thing.
]]>If those checks come back clean, check your internet connection and keep deleting/redownloading things until you get no integrity failures.
]]>As for the sed error, I don't know what to tell you. Like I said, the package builds fine for me, so the patch is fine..
]]>If I bypass this (or if I just try to compile it from source from http://www.tcpdump.org/ as well) it fails at the configuration step with about twenty repititions of the error:
sed: -e expression #1, char 447: unknown option to `s'
just varied by the specific character number.
Any ideas?
]]>