unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: 24140@debbugs.gnu.org
Subject: bug#24140: Substitute hash mismatches not properly reported
Date: Wed, 03 Aug 2016 11:50:21 +0200	[thread overview]
Message-ID: <87ziou5ggy.fsf@gnu.org> (raw)

Hello,

When using ‘guix package’, upon a substitute hash mismatch, all we see
is something like this:

--8<---------------cut here---------------start------------->8---
Found valid signature for /gnu/store/cpw9yca1mcqhqfq450dr3rz2jzr95l69-glib-2.48.0
From https://mirror.hydra.gnu.org/nar/cpw9yca1mcqhqfq450dr3rz2jzr95l69-glib-2.48.0
Downloading cpw9yc...-glib-2.48.0 (13.5MiB installed)...
 glib-2.48.0                                                                                    744KiB/s 00:04 | 2.9MiB transferred
killing process 11821
guix system: error: build failed: some substitutes for the outputs of derivation `/gnu/store/lkvlm17z8qm1v6r4n5ja5vcmsp7d860i-graphviz-2.38.0.drv' failed (usually happens due to networking issues); try `--fallback' to build derivation from source 
--8<---------------cut here---------------end--------------->8---

The error message from build.cc:

--8<---------------cut here---------------start------------->8---
      if (expectedHash != actualHash)
          throw SubstError(format("hash mismatch in downloaded path `%1%': expected %2%, got %3%")
              % storePath % printHash(expectedHash) % printHash(actualHash));
--8<---------------cut here---------------end--------------->8---

… is only visible when we set-build-options #:print-build-trace? #t
(like ‘guix build’ does, but ‘guix package’ and others do not.)

The message should always be displayed, regardless of
#:print-build-trace?.

Ludo’.

             reply	other threads:[~2016-08-03  9:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-03  9:50 Ludovic Courtès [this message]
2020-07-09 13:56 ` bug#24140: Substitute hash mismatches not properly reported Ludovic Courtès

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=87ziou5ggy.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=24140@debbugs.gnu.org \
    /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).