GNU bug report logs - #35561
Fresh install, guix pull exits with error, hash mismatch

Previous Next

Full log

Message #17 received at 35561 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Calle Kabo <calle <at> kabo.nu>
Cc: 35561 <at> debbugs.gnu.org, Tobias Geerinckx-Rice <me <at> tobias.gr>
Subject: Re: bug#35561: Fresh install, guix pull exits with error,
 hash mismatch
Date: Tue, 07 May 2019 10:13:04 +0200

Hello,

Calle Kabo <calle <at> 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’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.