[SOLVED] Yaourt: trying to install leiningen - validity check fails.

Question

Here's what I get:
==> Building and installing package
==> Making package: leiningen 1:2.2.0-1 (Fri Aug 16 19:48:01 EDT 2013)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Downloading lein...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 11440 100 11440 0 0 65861 0 --:--:-- --:--:-- --:--:-- 66127
==> Validating source files with sha1sums...
lein ... FAILED
==> ERROR: One or more files did not pass the validity check!
==> ERROR: Makepkg was unable to build leiningen.
Now, I did do some research, and it seems that if I do:
makepkg -g
That will give me the current sha, but I'm reluctant to use it:
If the github repo is trusted (which seems to be the case), why isn't the PKGBUILD updated automatically?
I'm guessing there must be a good reason, and I would like to clear that up before I continue.
Thanks.
Last edited by Goran (2013-08-17 03:50:31)

Answer 1

Trilby wrote:I cringed on seeing a 'curl' in the build function that bypasses makepkg's checksum
Yea, and also, dependencies are not defined, so it's not really a good alternative to leiningen.
In either case, leiningen is what really needs to be fixed, in my view, because that's what the github wiki points to: https://github.com/technomancy/leiningen/wiki/Packaging
And I think I know the perfect way to do it: Instead of drawing from the floating stable, why not simply draw from a specific commit in stable?
That seems like a perfect solution, because that's essentially a snap-shot, which won't change until the package maintainer decides to update the pkgbuild.
What do you think?