unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 29814@debbugs.gnu.org
Subject: bug#29814: impossible to pass spaces in GUIX_BUILD_OPTIONS
Date: Fri, 22 Dec 2017 22:36:45 -0500	[thread overview]
Message-ID: <87fu82m7xu.fsf@netris.org> (raw)
In-Reply-To: <87a7ya79s3.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Fri, 22 Dec 2017 22:06:04 +0100")

ludo@gnu.org (Ludovic Courtès) writes:

> Martin Castillo <castilma@uni-bremen.de> skribis:
>
>> guix/util.scm:(arguments-from-envirenment-variable) uses
>> char-set:graphic to split the string. this makes it impossible to pass
>> spaces in the arguments.
>>
>> This makes it impossible to pass more than one substitute-url via the
>> environment.
>
> Yes, this is annoying.  I think --substitute-urls (plural) was
> misguided.  Instead we should instead have --substitute-url (singular),
> which could be repeated several times.  That would solve the troubles
> with spaces.
>
> During a transition period we could keep accepting --substitute-urls.

I require a way to clear the list of substitute urls, because last I
checked --no-substitutes doesn't fully inhibit use of the substitute
servers.  For example, I found that when grafting, substitute servers
were queried even when --no-substitutes is passed to the daemon.  I
guess that's to determine the set of references found in the build
outputs, to optimize the grafting process.  However, a compromised
substitute server (or a man-in-the-middle in possession of our signing
key) could send me the wrong set of references, and thus cause my system
to perform incomplete grafts, with some dependencies omitted from the
list of rewrites.

My current method to avoid trusting the substitute servers is to pass
both --no-substitutes and --substitute-urls "" to the daemon.  If we
deprecate the use of --substitute-urls, how will I clear the list?

       Mark

  reply	other threads:[~2017-12-23  3:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-22 17:58 bug#29814: impossible to pass spaces in GUIX_BUILD_OPTIONS Martin Castillo
2017-12-22 21:06 ` Ludovic Courtès
2017-12-23  3:36   ` Mark H Weaver [this message]
2017-12-23 14:14     ` Ludovic Courtès
2017-12-27 16:37   ` Martin Castillo

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=87fu82m7xu.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=29814@debbugs.gnu.org \
    --cc=ludo@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).