all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: lichengtai@gmail.com, 52591@debbugs.gnu.org
Subject: bug#52591: downloading from software archives as default even if version is wrong
Date: Sat, 18 Dec 2021 01:06:48 +0100	[thread overview]
Message-ID: <874k76n55q.fsf@nckx> (raw)
In-Reply-To: <6c18852ca39e53a40cf6cdf0f3c661354d762907.camel@telenet.be>

[-- Attachment #1: Type: text/plain, Size: 728 bytes --]

Maxime Devos 写道:
> You forgot to update the sha256 hash.

That's it, in a nutshell!

> which at this time shall fail as I have not updated the hash 
> checksum.

No, that's the reason it *succeeds*!

Guix is mostly content-addressed, meaning that the hash identifies 
a file.  If you don't change the hash, you're not asking for a new 
file, by definition.  URLs are like directions (hence: ‘locator’), 
not identifiers.

You can easily generate a bogus-but-valid hash by negating the 
first digit, which (in nix-base32 at least), can only be either 0 
or 1.  Guix will then print the correct hash of whatever it found 
at the URI you specified.

OK to close as NOTABUG?

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 243 bytes --]

  reply	other threads:[~2021-12-18  0:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-17 23:40 bug#52591: downloading from software archives as default even if version is wrong Andy Tai
2021-12-17 23:58 ` Maxime Devos
2021-12-18  0:06   ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2021-12-18  0:23     ` Andy Tai
2021-12-18  1:51       ` Leo Famulari
2021-12-18  1:57         ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-12-18  0:06 ` Leo Famulari
2021-12-18  0:07 ` raingloom

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874k76n55q.fsf@nckx \
    --to=bug-guix@gnu.org \
    --cc=52591@debbugs.gnu.org \
    --cc=lichengtai@gmail.com \
    --cc=maximedevos@telenet.be \
    --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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.