From: "Ludovic Courtès" <ludo@gnu.org>
To: Karrick McDermott <kmcdermott@linkedin.com>
Cc: "35623-done@debbugs.gnu.org" <35623-done@debbugs.gnu.org>
Subject: bug#35623: FW: bug#35623: guix pull failed on RHEL7
Date: Sat, 11 May 2019 20:12:08 +0200 [thread overview]
Message-ID: <87d0kox3lz.fsf@gnu.org> (raw)
In-Reply-To: <526B5A3B-EEDB-4C57-8582-C47B583D780F@linkedin.biz> (Karrick McDermott's message of "Fri, 10 May 2019 22:47:38 +0000")
Hello,
Karrick McDermott <kmcdermott@linkedin.com> skribis:
> 1. Glad you identified why `HOME` was unset, due to the `with-clean-environment` function. I am surprised a few environment variables are not conveyed through the code path, as `ssh` does for variables it deems safe, including `HOME`, `LOGNAME`, `TZ`, and `USER`.
In this case this is done on purpose, to make sure that the execution
environment of this program is well under control.
Commit 48d498c2c3984784336b27ba5e261319f3ac6a3a lets HOME pass through,
which should sidestep the problem you encountered.
> 2. My RHEL7 machine is _not_ running `nscd` as you surmised. This machine was configured to use LDAP for user account management.
Yes, as the manual explains, you’ll really need to run nscd for proper
operation.
Thank you,
Ludo’.
next prev parent reply other threads:[~2019-05-11 18:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 18:03 bug#35623: guix pull failed on RHEL7 Karrick McDermott
2019-05-07 19:53 ` david.larsson
2019-05-07 21:39 ` Mark H Weaver
[not found] ` <9245F115-A7B5-4DA1-944F-8A510659019E@linkedin.biz>
2019-05-10 18:49 ` bug#35623: FW: " Karrick McDermott
2019-05-10 22:23 ` Ludovic Courtès
2019-05-10 22:47 ` Karrick McDermott
2019-05-11 18:12 ` Ludovic Courtès [this message]
2019-05-11 19:07 ` Tobias Geerinckx-Rice
2019-05-11 21:42 ` Tobias Geerinckx-Rice
2019-05-12 22:19 ` Ludovic Courtès
2019-05-12 22:47 ` Tobias Geerinckx-Rice
2019-05-12 23:09 ` Tobias Geerinckx-Rice
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d0kox3lz.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=35623-done@debbugs.gnu.org \
--cc=kmcdermott@linkedin.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.