unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: YOANN P <yoann_mac_donald@hotmail.com>
Cc: "30768@debbugs.gnu.org" <30768@debbugs.gnu.org>
Subject: bug#30768: Gettext : test-copy-file-1.sh fail if --with-store-dir=/var/tmp/xxxxx/gnu/store
Date: Mon, 12 Mar 2018 14:47:25 +0100	[thread overview]
Message-ID: <87y3ixpfrm.fsf@gnu.org> (raw)
In-Reply-To: <DB6P18901MB0022308B270EB51633D14D13DBDC0@DB6P18901MB0022.EURP189.PROD.OUTLOOK.COM> (YOANN P.'s message of "Sun, 11 Mar 2018 20:01:12 +0000")

Hello Yoann,

YOANN P <yoann_mac_donald@hotmail.com> skribis:

> --- a/nix/libstore/build.cc
> +++ b/nix/libstore/build.cc
> @@ -1849,6 +1849,11 @@ void DerivationGoal::startBuilder()
>          createDirs(chrootTmpDir);
>          chmod_(chrootTmpDir, 01777);
>  
> +        /* Create a writable /var/tmp in the chroot. */
> +        Path chrootVarTmpDir = chrootRootDir + "/var/tmp";
> +        createDirs(chrootVarTmpDir);
> +        chmod_(chrootVarTmpDir, 01777);

We won’t apply this patch because in general there’s no reason for build
processes to require /var/tmp (we’ve never encountered that.)

That said, are you sure you want to use
--with-store-dir=/var/tmp/xxxxx/gnu/store?

You probably got a ‘configure’ warning already that certain things may
not work, for instance that the shebang max length may be exceeded.

Also using a store other than /gnu/store means you won’t be able to use
substitutes, nor to compare build results with other machines.

Thanks,
Ludo’.

  reply	other threads:[~2018-03-12 13:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-11 16:08 bug#30768: Gettext : test-copy-file-1.sh fail if --with-store-dir=/var/tmp/xxxxx/gnu/store YOANN P
2018-03-11 20:01 ` YOANN P
2018-03-12 13:47   ` Ludovic Courtès [this message]
2018-03-12 19:18     ` YOANN P
2018-03-12 21:08       ` Ludovic Courtès
2018-03-13 23:48         ` YOANN P
2018-03-14  9:33           ` 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=87y3ixpfrm.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=30768@debbugs.gnu.org \
    --cc=yoann_mac_donald@hotmail.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 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).