all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: George Clemmer <myglc2@gmail.com>
Cc: 33262@debbugs.gnu.org
Subject: bug#33262: guix fails to find and use some available substitutes
Date: Mon, 05 Nov 2018 19:45:54 +0100	[thread overview]
Message-ID: <D79A075E-AB72-498C-8DFB-9BCD6B7F2C32@lepiller.eu> (raw)
In-Reply-To: <cucpnvj4ez2.fsf@gmail.com>

Exactly!

Le 5 novembre 2018 18:21:53 GMT+01:00, George Clemmer <myglc2@gmail.com> a écrit :
>
>Julien Lepiller <julien@lepiller.eu> writes:
>
>> I think guix' message is a bit confusing: the .drv file is always
>> created by guix, it's the derivation. The derivation is built, which
>> results in a new store path. It can be built locally or by using a
>> substitute. What you see in your store is the derivation (.drv), not
>> its result. You can open that file to find where the result will be
>> stored and check if it exists on your machine.
>
>Hi Julien,
>
>Thank you. You are right, the .drv "out" substitute is not on my
>local server. So this is not a bug. SORRY for the noise ;-)
>
>After re-reading (guix) Derivations, I see I had a wrong impression:
>that the presence of a .drv indicates a successful build. But AIUI now
>it only means that at some point in the past we attempted to build the
>.drv. IOW, we will also have .drv files for all failed builds.
>
>Is that correct?
>
>Thanks! - George

      reply	other threads:[~2018-11-05 18:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-05  1:09 bug#33262: guix fails to find and use some available substitutes George Clemmer
2018-11-05  1:29 ` George Clemmer
2018-11-05  8:26 ` Julien Lepiller
2018-11-05 17:21   ` George Clemmer
2018-11-05 18:45     ` Julien Lepiller [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D79A075E-AB72-498C-8DFB-9BCD6B7F2C32@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=33262@debbugs.gnu.org \
    --cc=myglc2@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.