From: Leo Famulari <leo@famulari.name>
To: Dmitry Matveyev <greenfork.lists@yandex.com>
Cc: 47786@debbugs.gnu.org
Subject: bug#47786: Several build --keep-failed result in wrong env variables
Date: Thu, 15 Apr 2021 13:06:47 -0400 [thread overview]
Message-ID: <YHhyp4v/7g7Gfujo@jasmine.lan> (raw)
In-Reply-To: <87r1jc5ld1.fsf@yandex.com>
On Thu, Apr 15, 2021 at 08:31:54AM +0600, Dmitry Matveyev wrote:
> Hello,
>
> I use guix on Arch Linux, version
> 050be36cbf3a42199f64f2e44c59f1cb1b3afab5.
>
> Several invocations of guix build --keep-failed creates directories in
> /tmp like this one guix-build-hello-2.10.drv-0 for 1st build and then
> guix-build-hello-2.10.drv-1 for 2nd and so on (with last digit
> increasing). But environment variables for all of them are set to point
> to the very 1st directory.
>
> Reproduce:
>
> $ guix build --check --keep-failed hello
> ^C
> $ guix build --check --keep-failed hello
> ^C
> $ cd /tmp/guix-build-hello-2.10.drv-1/
> $ grep PWD environment-variables
> export OLDPWD
> export PWD="/tmp/guix-build-hello-2.10.drv-0/hello-2.10"
>
> Here although we are in directory /tmp/guix-build-hello-2.10.drv-1/, PWD
> is set to .drv-0 directory.
I see, thanks for the report.
This is probably because, within the build environment, the directory is
always named '/tmp/guix-build-$name-$version.drv-0/', for
reproducibility.
We should see about changing the PWD variable after the build fails.
next prev parent reply other threads:[~2021-04-15 17:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-15 2:31 bug#47786: Several build --keep-failed result in wrong env variables Dmitry Matveyev
2021-04-15 17:06 ` Leo Famulari [this message]
2021-04-15 20:24 ` Mark H Weaver
2021-04-16 4:49 ` Dmitry Matveyev
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=YHhyp4v/7g7Gfujo@jasmine.lan \
--to=leo@famulari.name \
--cc=47786@debbugs.gnu.org \
--cc=greenfork.lists@yandex.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).