From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: 17122@debbugs.gnu.org
Subject: bug#17122: More problems with --no-substitutes
Date: Fri, 28 Mar 2014 10:17:12 +0100 [thread overview]
Message-ID: <874n2ismw7.fsf@gnu.org> (raw)
In-Reply-To: <8738i3ipsh.fsf@yeeloong.lan> (Mark H. Weaver's message of "Thu, 27 Mar 2014 12:12:30 -0400")
Mark H Weaver <mhw@netris.org> skribis:
> What disturbs me the most is that 'substitute-binary' is being called at
> all. I'm 100% certain that I passed '--no-substitutes' to guix-daemon.
> I use a script to start guix-daemon with the options I prefer, to avoid
> mistakes. I also just checked with 'ps', and indeed '--no-substitutes'
> is there on the command line.
Can you check with current master? (See in particular commits 968e84a
and c9e2b0b.) Does tests/guix-daemon.sh pass?
Make sure to use the “right” daemon code, but updating the nix-upstream
module and running nix/sync-with-upstream.
> I'm surprised and concerned that we seem to be having so much trouble
> making '--no-substitutes' work reliably. How hard can it be?
The issue is that guix-daemon.cc glues into Nix’s code, and Nix changed
the way it handles substituter settings in the last update.
Specifically, in Nix commit dcaea042, the Settings::update method is
made to re-read $NIX_SUBSTITUTERS:
<https://github.com/NixOS/nix/commit/dcaea042fc895667bf6f529471ff9f449629774c>;
then in Guix commit 89faa5c I adjusted guix-daemon.cc accordingly, but
inadvertently removed the ‘if’ branch that clears the substituter list.
Commit c9e2b0b augments tests/guix-daemon.sh to test guix-daemon
--no-substitutes.
Ludo’.
next prev parent reply other threads:[~2014-03-28 9:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 16:12 bug#17122: More problems with --no-substitutes Mark H Weaver
2014-03-27 16:51 ` Sree Harsha Totakura
2014-03-27 17:22 ` Mark H Weaver
2014-03-28 9:20 ` Ludovic Courtès
2014-03-28 9:17 ` Ludovic Courtès [this message]
2014-03-31 22:59 ` Mark H Weaver
2014-04-01 9:51 ` 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=874n2ismw7.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=17122@debbugs.gnu.org \
--cc=mhw@netris.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).