From: "Ludovic Courtès" <ludo@gnu.org>
To: Christine Lemmer-Webber <cwebber@dustycloud.org>
Cc: 50441@debbugs.gnu.org
Subject: bug#50441: Wrong build directory number shown in environment-variables file
Date: Tue, 14 Sep 2021 09:47:01 +0200 [thread overview]
Message-ID: <87y27z7g5m.fsf@gnu.org> (raw)
In-Reply-To: <874kawcvey.fsf@dustycloud.org> (Christine Lemmer-Webber's message of "Tue, 07 Sep 2021 10:26:48 -0400")
Hi,
Christine Lemmer-Webber <cwebber@dustycloud.org> skribis:
> Tobias Geerinckx-Rice <me@tobias.gr> writes:
[...]
>>> #+BEGIN_SRC sh
>>> export TEMP=\
>>> "/tmp/guix-build-u-boot-mnt-reform2-2021.06.drv-0"
>>
>> Part of the build environment isolation/reproducibility is that
>> processes inside it always see a build directory ending in ‘-0’,
>> regardless of the file name on the host system.
>>
>> Kind regards,
>>
>> T G-R
>>
>> [[End of PGP Signed Part]]
>
> This makes sense in general, though I wonder if when using --keep-failed
> if environment-variables should dump out something different, since
> that file is around for debugging, and sourcing it might set up the
> wrong paths I guess? What do you think?
There’s no good solution I’m afraid. Directory names within the build
environment must be fixed to ensure reproducibility, as Tobias writes;
yet, the daemon shouldn’t overwrite directories that happen to already
exist in the “real” /tmp.
Thanks,
Ludo’.
next prev parent reply other threads:[~2021-09-14 7:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 21:22 bug#50441: Wrong build directory number shown in environment-variables file Christine Lemmer-Webber
2021-09-07 4:34 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-09-07 14:26 ` Christine Lemmer-Webber
2021-09-14 7:47 ` Ludovic Courtès [this message]
2021-09-07 4:44 ` Sarah Morgensen
2021-09-07 14:25 ` Christine Lemmer-Webber
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=87y27z7g5m.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=50441@debbugs.gnu.org \
--cc=cwebber@dustycloud.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).