unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Adroit <adroit1@proton.me>
Cc: 62023-done@debbugs.gnu.org, control@debbugs.gnu.org
Subject: bug#62023: compute-guix-derivation failed to compute the derivation for Guix
Date: Thu, 09 Mar 2023 00:21:16 -0500	[thread overview]
Message-ID: <87jzzqts8j.fsf@gmail.com> (raw)
In-Reply-To: <PUPl8JN9lKcs6d0kR4k45Ipi8gkGqAV3sOWycMm3vtFm_kRDuJg6xbGczEgCLxpDEAcg7MaHeMOZNFiYehSjnsgmSp3Hwc_z_1ykivdkLHM=@proton.me> (Adroit's message of "Thu, 09 Mar 2023 02:15:42 +0000")

Hi,

Adroit <adroit1@proton.me> writes:

> The output explicitly says "you found a bug".

Yes, thanks for reaching out.  Sadly this is something that comes up
often; a user with a failing connection can end up receiving such
advice.  We should open another bug to track this (there are many such
reports but I don't think there's a report about improving the message).

> Are you suggesting that a crash, with backtrace, is the intended
> behavior when a substitute server happens to be offline?

That's indeed a bug.  Error messages should be clear, not a backtrace
soup :-).  It seems the real underlying error is a network timeout; it's
already been reported in https://issues.guix.gnu.org/60547.

> The problem also occurs when using --no-substitutes and --fallback, so
> I'm not even sure the server is the root cause - you can see from
> first few lines (where I curl) of output that the server is indeed
> online. I also checked the web interface. The only issue I can think
> of is Guix not respecting the Gnome proxy, but in that case all of the
> servers would be seen as offline.

I'm not sure what's going on with the network, but what tipped me that
the problem was caused by a channel was this:

--8<---------------cut here---------------start------------->8---
substitutes.nonguix.org: host not found: Name or service not
--8<---------------cut here---------------end--------------->8---

But looking more closely it seems no substitutes could be fetched at all
even from the official build farms, so it looks like your networking was
not working at that time.  Did you retry it since?  Did it work?

-- 
Thanks,
Maxim




      reply	other threads:[~2023-03-09  5:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-07  2:30 bug#62023: compute-guix-derivation failed to compute the derivation for Guix Adroit via Bug reports for GNU Guix
2023-03-07 21:15 ` Maxim Cournoyer
2023-03-09  2:15   ` Adroit via Bug reports for GNU Guix
2023-03-09  5:21     ` Maxim Cournoyer [this message]

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=87jzzqts8j.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=62023-done@debbugs.gnu.org \
    --cc=adroit1@proton.me \
    --cc=control@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).