unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Greg Hogan <code@greghogan.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Substitute not downloading
Date: Wed, 10 May 2023 11:35:08 +0200	[thread overview]
Message-ID: <ZFtlTCgjUbA6VNjN@jurong> (raw)
In-Reply-To: <CA+3U0ZmKsH0MLYLrGAWjtgiD_VvUg78JAGmvmW7AwhvQxO0ZUA@mail.gmail.com>

Am Tue, May 09, 2023 at 11:43:01AM -0400 schrieb Greg Hogan:
> I have an up-to-date Guix but am unable to fetch the substitute from
>   http://ci.guix.gnu.org/build/1332269/details

So the link indicates that the build has succeeded "19 hours ago",
which would mean on May 9 around 14:30 UTC, which was about an hour
before you wrote this message.

> Are substitutes only available after the evaluation has completed?
> --8<---------------cut here---------------start------------->8---
> $ guix describe
> Generation 9    May 09 2023 15:18:11    (current)
>   guix c1ffe2f
>     repository URL: https://git.savannah.gnu.org/git/guix.git
>     branch: master
>     commit: c1ffe2f21bd1b9ba6bd527bbabe130144a69af71
> --8<---------------cut here---------------end--------------->8---

I think the substitute not being available may have to do with the
difference between the package being available in the store, and as a
nar file for substitution. As I understand it, the first request for a nar
can fail, then it is built in the background, and a later request after
a timeout will succeed. Hopefully offload specialists can correct potential
misconceptions on my side ;-)

Andreas



  reply	other threads:[~2023-05-10  9:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-09 15:43 Substitute not downloading Greg Hogan
2023-05-10  9:35 ` Andreas Enge [this message]
2023-05-10 15:02   ` Greg Hogan

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=ZFtlTCgjUbA6VNjN@jurong \
    --to=andreas@enge.fr \
    --cc=code@greghogan.com \
    --cc=guix-devel@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).