Summary
If you get
==> ERROR: One or more files did not pass the validity check!
then either:
- a file did not download correctly; remove it and try again.
- there is an issue with the AUR package and you should report it via the associated packaging page.
Details
All packaging files include a section to determine whether the downloaded source file(s) have downloaded correctly and have not been tampered with.
An upstream project usually publishes checksums for the artefacts, whether MD5, SHA1, or otherwise.
When you build a package, makepkg
will validate each file against the checksum contained in the PKGBUILD
file.
If the files have the same checksum the process will succeed. If the files have a different checksum the process will fail.
In the following example one file passes its validation, but the other fails:
$ makepkg -sr
==> Making package: clarity-icon-theme 0.4.7-2 (Sat 31 Mar 14:36:19 BST 2018)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Downloading clarity-icon-theme_0.4.7.tar.gz...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 248 100 248 0 0 359 0 --:--:-- --:--:-- --:--:-- 2234
100 391k 0 391k 0 0 138k 0 --:--:-- 0:00:02 --:--:-- 365k
-> Found fix-blueberry-icons.patch
==> Validating source files with md5sums...
clarity-icon-theme_0.4.7.tar.gz ... FAILED
fix-blueberry-icons.patch ... Passed
==> ERROR: One or more files did not pass the validity check!
If on removing the clarity-icon-theme_0.4.7.tar.gz
file and re-downloading it still fails validation, that means there is an issue with the PKGBUILD and I should report it on the AUR package page.