You are not logged in.
If I download the PKGBUILD for libpcap with ABS and attempt to compile it with makepkg, I get
libpcap-1.3.0.tar.gz.sig ... FAILED
for the integrity checks.
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?
Avatar by Ditey: https://twitter.com/phrobitey
Offline
Works fine here. Remove your libpcap-1.3.0.tar.gz.sig and try again? It's possibly gotten corrupted.
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..
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Also works fine here (libpcap-1.3.0-2 straight from abs). I'll second the suggestion of redownloading the sig file.
Last edited by tdy (2013-02-13 03:25:28)
Offline
When I redownload, now it's the patch failing the integrity checks, and SED still fails. Also, the sed error seems to be occuring in the configure file itself, not the patch operation.
Last edited by GourdCaptain (2013-02-13 06:09:14)
Avatar by Ditey: https://twitter.com/phrobitey
Offline
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.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
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.
Avatar by Ditey: https://twitter.com/phrobitey
Offline