From: "Ludovic Courtès" <ludo@gnu.org>
To: Calle Kabo <calle@kabo.nu>
Cc: 35561@debbugs.gnu.org
Subject: bug#35561: Fresh install, guix pull exits with error, hash mismatch
Date: Tue, 07 May 2019 10:13:04 +0200 [thread overview]
Message-ID: <87d0kuadin.fsf@gnu.org> (raw)
In-Reply-To: <LeERazl--3-1@kabo.nu> (Calle Kabo's message of "Tue, 7 May 2019 01:20:04 +0200 (CEST)")
Hello,
Calle Kabo <calle@kabo.nu> skribis:
> I tried running guix pull again, but still didn't work
> https://paste.debian.net/1081770
This shows that substitutes were not used:
--8<---------------cut here---------------start------------->8---
41 building /gnu/store/2bahavdikdgvznc7yn1qmnpbw4pz0jnr-letsencryptauthorityx4.pem.drv...
42 downloading from https://letsencrypt.org/certs/letsencryptauthorityx4.pem...
43 |sha256 hash mismatch for /gnu/store/rrjqsmxk40fza2gra7pr9pbsdhbcbp0g-letsencryptauthorityx4.pem:
44 expected hash: 003dc94c8qwj634h0dq743x7hqv9rdcfaisdksprkmi2jd107xq4
45 actual hash: 0giiixknr0mls2ir6qqzb42mq7x9a7vz79gbn7fjszbf87pqhpzm
--8<---------------cut here---------------end--------------->8---
That’s why you get the exact same result as before.
The reason substitutes were not used is that Guix cached the fact that
substitutes weren’t available. They became available in the meantime
but the cached entry hasn’t expired yet.
To work around it, you could wait some more :-), or you can do:
guix pull --substitute-urls=https://berlin.guixsd.org
berlin.guixsd.org provides the same contents as ci.guix.gnu.org.
However, that will trick Guix into building a fresh cache for that
machine.
Let us know how it goes!
Ludo’.
next prev parent reply other threads:[~2019-05-07 8:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-04 7:43 bug#35561: Fresh install, guix pull exits with error, hash mismatch Calle Kabo
2019-05-06 22:33 ` Ludovic Courtès
2019-05-06 22:59 ` Tobias Geerinckx-Rice
2019-05-06 23:20 ` Calle Kabo
2019-05-07 8:13 ` Ludovic Courtès [this message]
2019-05-07 8:39 ` Calle Kabo
2019-05-07 16:13 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d0kuadin.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=35561@debbugs.gnu.org \
--cc=calle@kabo.nu \
/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.