I just tried lein upgrade
and got this error message.
Downloading Leiningen to /Users/foo/.lein/self-installs/leiningen-2.9.2-standalone.jar now...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 618 100 618 0 0 2083 0 --:--:-- --:--:-- --:--:-- 2087
100 13.9M 100 13.9M 0 0 3152k 0 0:00:04 0:00:04 --:--:-- 3650k
shasum: /Users/foo/.lein/self-installs/leiningen-2.9.2-standalone.jar.pending.shasum: no properly formatted SHA1 checksum lines found
Failed to properly download <https://github.com/technomancy/leiningen/releases/download/2.9.2/leiningen-2.9.2-standalone.zip>
The checksum was mismatched. and we could not verify the downloaded
file. We expected a sha256 of
09805bd809656794cfe7d9155fd4b8bea2646092318690bf68e3c379574a2d3c and actually had
d1ac0284444a9a57f18c8bd41fa404598893a7ef0e5564934f35eeccbcc6ec4d.
Yes, I've been getting this problem consistently on CircleCI where I now switched everything over to 2.9.1 hardcoded...
Now, the .zip
file is there. But has a different SHA than lein expected. But the checksum is not 09805bd809656794cfe7d9155fd4b8bea2646092318690bf68e3c379574a2d3c
(baked into the version 2.9.2).
What happens in these circumstances? Does another binary get cut?
i've seen this mentioned elsewhere -- i don't know what the resolution is, but there the work-around was use 2.9.1. i think it was @borkdude who mentioned it.
Hmm, right. Is there somewhere to get the bash script? Or did he just manually change LEIN_VERSION
and LEIN_CHECKSUM
in said script?
See here: https://raw.githubusercontent.com/technomancy/leiningen/stable/bin/lein
not sure what he did, and i think it's likely he's not awake atm, sorry
No probs
@sogaiu FYI, you can get it thusly.
wget <https://raw.githubusercontent.com/technomancy/leiningen/2.9.1/bin/lein>
thanks for the clarification!