From: Martin via web <issues.guix.gnu.org@elephly.net>
To: 44493@debbugs.gnu.org
Subject: [bug#44493] [PATCH 0/1] gnu: bitcoin-core: Update to 0.20.1.
Date: Sun, 6 Dec 2020 08:18:40 +0100 [thread overview]
Message-ID: <7f4c4d580230.10f738a92840912a@guile.gnu.org> (raw)
In-Reply-To: <cover.1604701819.git.simon@simonsouth.net>
The SHA256 checksum is not the hexadecimal one output by sha256sum, and I cannot recompute it as follows `cat bitcoin-0.20.1.tar.gz | sha256sum | xxd -r -p | base32`
How is this base32 value `0y5rad68b398arh0abr2wgiwybdw0i5a4dxz9s3fk9fgdbyn5gab` computed?
Thanks!
next prev parent reply other threads:[~2020-12-06 7:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 23:06 [bug#44493] [PATCH 0/1] gnu: bitcoin-core: Update to 0.20.1 Simon South
2020-11-06 23:15 ` [bug#44493] [PATCH 1/1] " Simon South
2020-11-18 8:48 ` bug#44493: [PATCH 0/1] " Christopher Baines
2020-12-06 7:18 ` Martin via web [this message]
2020-12-06 8:43 ` [bug#44493] " Guillaume Le Vaillant
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7f4c4d580230.10f738a92840912a@guile.gnu.org \
--to=issues.guix.gnu.org@elephly.net \
--cc=44493@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).