unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 39993@debbugs.gnu.org
Subject: bug#39993: Guix report hash mismatch when underlying cause is ENOSPC
Date: Mon, 09 Mar 2020 17:53:29 +0100	[thread overview]
Message-ID: <878sk91ncm.fsf@gnu.org> (raw)
In-Reply-To: <8736ai5lp4.fsf@gmail.com> (Maxim Cournoyer's message of "Sun, 08 Mar 2020 22:03:19 -0400")

Hi,

Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:

> Guix should correctly report that it ran out of space instead of falsely
> mentioning hash mismatches and attempting alternative download sources,
> as demonstrated by the Guix output below:
>
> Session:
>
> building /gnu/store/dqzq8hbk8gqx5lhmnxsl5vl0c6s3i0a2-tcpdump-4.9.3.tar.gz.drv...
> downloading from https://www.tcpdump.org/release/tcpdump-4.9.3.tar.gz...

Could you post the log returned by ‘guix build --log-file
/gnu/store/dqzq8hbk8gqx5lhmnxsl5vl0c6s3i0a2-tcpdump-4.9.3.tar.gz.drv’?

The root cause is that ‘false-if-exception*’ as used in (guix build
download) is too coarse-grain.

Thanks,
Ludo’.

  reply	other threads:[~2020-03-09 16:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-09  2:03 bug#39993: Guix report hash mismatch when underlying cause is ENOSPC Maxim Cournoyer
2020-03-09 16:53 ` Ludovic Courtès [this message]
2020-03-11  3:26   ` Maxim Cournoyer
2020-03-11 14:00     ` Ludovic Courtès
2020-03-11 16:13       ` Maxim Cournoyer
2020-03-21 23:03   ` Ludovic Courtès
2020-03-23 17:59     ` Maxim Cournoyer
     [not found]       ` <87ftdy8x1v.fsf@gmail.com>
     [not found]         ` <87d092p03b.fsf@gnu.org>
     [not found]           ` <87wo79tixw.fsf@gmail.com>
     [not found]             ` <87h7ycglpi.fsf@gnu.org>
2020-04-18  4:17               ` Maxim Cournoyer

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=878sk91ncm.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=39993@debbugs.gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    /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).