From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Vivien Kraus <vivien@planete-kraus.eu>
Cc: 30890@debbugs.gnu.org
Subject: bug#30890: Hash mismatch for /gnu/store/bvbs19jg8497ca73i82xmrjspd83lvs2-usb.ids
Date: Wed, 21 Mar 2018 18:24:00 +0100 [thread overview]
Message-ID: <bfcebf1f36f4b2924718efd1c010b55d@tobias.gr> (raw)
In-Reply-To: <1521615280.1118.15.camel@planete-kraus.eu>
Vivien,
On 2018-03-21 7:54, Vivien Kraus wrote:
> I don't know on what the hash depends; maybe it also depends on the
> URL?
It depends only on the contents. This allows us to use a list of
different URIs (see the lsof package for an example) or try many
different mirror://s as long as they serve the right file.
> Should I change the hash in virtualization.scm?
In general: yes, but not without prior investigation.
The server might be serving a temporary error page instead of a usable
tarball (SF.net is currently notorious for doing so), or the tarball
might have been updated in-place (and you'll have to manually diff the
contents to make sure it's legitimate), or it might just be a problem
with your network, or...
Pushing a hash update without explanation in the commit message will
result in lots of spam from people like me. Avoid that.
Kind regards,
T G-R
Sent from a Web browser. Excuse or enjoy my brevity.
next prev parent reply other threads:[~2018-03-21 17:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 23:10 bug#30890: Hash mismatch for /gnu/store/bvbs19jg8497ca73i82xmrjspd83lvs2-usb.ids Vivien Kraus
2018-03-21 0:19 ` Danny Milosavljevic
2018-03-21 6:54 ` Vivien Kraus
2018-03-21 17:24 ` Tobias Geerinckx-Rice [this message]
2018-03-21 7:27 ` Ricardo Wurmus
2018-03-21 10:35 ` Vivien Kraus
2018-03-21 11:10 ` Ricardo Wurmus
2018-03-21 11:05 ` Vivien Kraus
2018-03-21 15:46 ` Tobias Geerinckx-Rice
2018-03-21 16:08 ` Tobias Geerinckx-Rice
2018-03-21 17:01 ` Vivien Kraus
2018-03-21 17:05 ` 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=bfcebf1f36f4b2924718efd1c010b55d@tobias.gr \
--to=me@tobias.gr \
--cc=30890@debbugs.gnu.org \
--cc=vivien@planete-kraus.eu \
/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).