bug#36614: rust@1.36's hash is incorrect.

[Ivan Petkov]

> On Jul 12, 2019, at 10:26 AM, Tobias Geerinckx-Rice <address@hidden> 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