From: Ivan Petkov <ivanppetkov@gmail.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 36614-done@debbugs.gnu.org
Subject: bug#36614: rust@1.36's hash is incorrect.
Date: Fri, 12 Jul 2019 17:59:29 -0700 [thread overview]
Message-ID: <4F732059-C44D-45CA-B077-7CDB5C8C5569@gmail.com> (raw)
In-Reply-To: <87k1cn411s.fsf@nckx>
> On Jul 12, 2019, at 10:26 AM, Tobias Geerinckx-Rice <me@tobias.gr> wrote:
>
> Yes, this is exactly what happened. I consider this is a feature of Guix, even though it can feel like a gotcha sometimes. :-)
>
> We often tend to think of the source URL(s) as an ‘identifier’ of the source file. However, it is nothing more than a hint about its *location*. The only authoritative identifier of its *content* is the hash: to get *this file* (content hash), try looking *here* (location: URL).
>
> One origin may have 0 or more source URLs: Guix will try them all until it downloads something matching the hash (and if even that fails it will try some implicit ones like tarballs.nixos.org).
>
> ‘Unique’ identifier (hash)
> ├ maybe you can *find* it here (URL)
> ├ or here (another URL)
> ├ hell maybe here I don't know (yet another URL)
> ⋮
> Guix cares only about the content of the file; it doesn't care or even remember how it got it. Or: if you change the download hint (release URL in this case), Guix won't care, because you didn't change the hash.
>
> I hope that makes some sense,
This is a wonderful explanation, thanks! Will keep this in mind for the future :)
—Ivan
next prev parent reply other threads:[~2019-07-13 1:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 9:41 bug#36614: rust@1.36's hash is incorrect Pierre Langlois
[not found] ` <handler.36614.B.156292453627169.ack@debbugs.gnu.org>
2019-07-12 13:11 ` bug#36614: Acknowledgement (rust@1.36's hash is incorrect.) Pierre Langlois
2019-07-12 13:16 ` bug#36614: rust@1.36's hash is incorrect Tobias Geerinckx-Rice
2019-07-12 16:33 ` Ivan Petkov
2019-07-12 17:23 ` Leo Famulari
2019-07-12 17:26 ` Tobias Geerinckx-Rice
2019-07-13 0:59 ` Ivan Petkov [this message]
2019-07-12 17:27 ` Tobias Geerinckx-Rice
2019-07-12 17:34 ` Tobias Geerinckx-Rice
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=4F732059-C44D-45CA-B077-7CDB5C8C5569@gmail.com \
--to=ivanppetkov@gmail.com \
--cc=36614-done@debbugs.gnu.org \
--cc=me@tobias.gr \
/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).