New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bitcoin: 0.20.0 -> 0.20.1 #94480
bitcoin: 0.20.0 -> 0.20.1 #94480
Conversation
@@ -40,7 +36,7 @@ stdenv.mkDerivation rec { | |||
"https://bitcoincore.org/bin/bitcoin-core-${version}/bitcoin-${version}.tar.gz" | |||
"https://bitcoin.org/bin/bitcoin-core-${version}/bitcoin-${version}.tar.gz" | |||
]; | |||
sha256 = "ec5a2358ee868d845115dc4fc3ed631ff063c57d5e0a713562d083c5c45efb28"; | |||
sha256 = "4bbd62fd6acfa5e9864ebf37a24a04bc2dcfe3e3222f056056288d854c53b978"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have verified that this hash, 4bbd62fd6acfa5e9864ebf37a24a04bc2dcfe3e3222f056056288d854c53b978
, is signed by Bitcoin Core binary release signing key
.
Anyone know what's up with this |
According to my reading of http://www.erisian.com.au/meetbot/bitcoin-core-dev/2020/bitcoin-core-dev.2020-05-14-19.00.log.html we are probably fine, but it would be much safer to engage that environment variable. (h/t to yoghurt for finding me those meeting notes). I would strongly encourage you to add |
Addressed in b5a5bf2f7949ce128eb5522af10efb79fe860bd8 |
(1) I think that export command has no effect. Based on (2) I'm not so sure anymore that it is worthwhile doing anything. |
Removed |
LGTM. Sorry for the back and forth. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Motivation for this change
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)