From: Tobias Geerinckx-Rice <me@tobias.gr>
To: b.woodcroft@uq.edu.au, help-guix@gnu.org
Subject: Re: downloading a tarball
Date: Fri, 24 Mar 2017 14:14:20 +0100 [thread overview]
Message-ID: <70f61b82-be0d-e493-6841-cb2d121f3051@tobias.gr> (raw)
In-Reply-To: <cf786b3f-15b9-5e54-424a-1d2afd1347d1@uq.edu.au>
[-- Attachment #1.1: Type: text/plain, Size: 1180 bytes --]
Ben (can I trust you now?),
On 24/03/17 13:26, Ben Woodcroft wrote:
> The correct hash is 0py8hsspvwjlckg2xi7jcpj0frrp2qbmsy9x55fx0knnwbhdg5d2.
I'm afraid it's the other way round. ;-)
> `/gnu/store/7mfyynbzzi15265z92bdb00j7lxfa70y-libxls-1.4.0.zip' should
> have sha256 hash `0py8hsspvwjlckg2xi7jcpj0frrp2qbmsy9x55fx0knnwbhdg5d2',
> instead has `1g8ds7wbhsa4hdcn77xc2c0l3vvz5bx2hx9ng9c9n7aii92ymfnk'
The first hash is what's expected, the second is what was actually
received. What's ‘correct’ is of course not always clear.
‘guix hash’ on my manually downloaded copy returns
1g8ds7wbhsa4hdcn77xc2c0l3vvz5bx2hx9ng9c9n7aii92ymfnk.
I did no further checking.
> HTH - speaking from experience making the same mistake here..
I suspect most people have. The message isn't as clear as it could be.
It doesn't help that IIRC Nix and Guix differ(ed) in which hash they
place first. So much fun when dual-'ixing.
I considered changing the wording of this a long time ago to say
something more like ‘expecting ..., got ...’. Like most people, I just
got used to it. Perhaps I should have sent that patch anyway.
Kind regards,
T G-R
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 476 bytes --]
next prev parent reply other threads:[~2017-03-24 13:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 12:06 downloading a tarball Catonano
2017-03-24 12:26 ` Ben Woodcroft
2017-03-24 13:14 ` Tobias Geerinckx-Rice [this message]
2017-03-24 14:33 ` Hartmut Goebel
2017-03-24 22:10 ` Ludovic Courtès
2017-03-25 16:43 ` Hartmut Goebel
2017-03-25 8:47 ` Catonano
2017-03-25 10:30 ` Ben Woodcroft
2017-03-24 12:50 ` Ricardo Wurmus
2017-03-24 13:16 ` Catonano
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=70f61b82-be0d-e493-6841-cb2d121f3051@tobias.gr \
--to=me@tobias.gr \
--cc=b.woodcroft@uq.edu.au \
--cc=help-guix@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.
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).