GNU bug report logs - #47919
Sourcing environment-variables may send to wrong directory

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Alexandre Hannud Abdo <abdo <at> member.fsf.org>
Subject: bug#47919: closed (Sourcing environment-variables may send to
 wrong directory)
Date: Fri, 12 Jan 2024 21:33:02 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#47919: Sourcing environment-variables may send to wrong directory

which was filed against the guix package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 47919 <at> debbugs.gnu.org.

-- 
47919: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=47919
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Alexandre Hannud Abdo <abdo <at> member.fsf.org>
To: 47919-done <at> debbugs.gnu.org
Subject: Sourcing environment-variables may send to wrong directory
Date: Fri, 12 Jan 2024 22:32:20 +0100

Ni! I see. Thanks for the explanation. .~´

[Message part 3 (message/rfc822, inline)]

From: Alexandre Hannud Abdo <abdo <at> member.fsf.org>
To: bug-guix <at> gnu.org
Subject: Sourcing environment-variables may send to wrong directory
Date: Tue, 20 Apr 2021 22:37:09 +0200

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
.~´

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.