From: Alexandre Hannud Abdo <abdo@member.fsf.org>
To: 47919@debbugs.gnu.org
Subject: bug#47919: Sourcing environment-variables may send to wrong directory
Date: Tue, 20 Apr 2021 22:37:09 +0200 [thread overview]
Message-ID: <db37b88c3d5fb402bb39efcb1163191cdff3b72d.camel@member.fsf.org> (raw)
Ni!
While debugging a package definition I met the following odd behavior:
On subsequent failed builds, if I go to build dir and source
'environment-variables', this is what happens:
/tmp/guix-build-[package].drv-1$ source environment-variables
/tmp/guix-build-[package].drv-0/[package]$
See how I source it in failed build '-1', but my cwd gets changed to
failed build '-0'!
Cheers,
ale
.~´
next reply other threads:[~2021-04-20 21:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 20:37 Alexandre Hannud Abdo [this message]
2021-04-20 21:20 ` bug#47919: Sourcing environment-variables may send to wrong directory Tobias Geerinckx-Rice via Bug reports for GNU Guix
2024-01-12 21:32 ` Alexandre Hannud Abdo
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=db37b88c3d5fb402bb39efcb1163191cdff3b72d.camel@member.fsf.org \
--to=abdo@member.fsf.org \
--cc=47919@debbugs.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).