From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: 30298@debbugs.gnu.org
Subject: bug#30298: core-updates: Failure to find the guixbuild group
Date: Wed, 31 Jan 2018 23:52:23 +0100 [thread overview]
Message-ID: <87k1vxr68o.fsf@gnu.org> (raw)
In-Reply-To: <20180131224913.GA29149@jasmine.lan> (Leo Famulari's message of "Wed, 31 Jan 2018 17:49:13 -0500")
Leo Famulari <leo@famulari.name> skribis:
> On Wed, Jan 31, 2018 at 11:38:35PM +0100, Ludovic Courtès wrote:
>> I suppose it works if you start nscd on this Debian machine (as is the
>> case on GuixSD), right?
>
> Yes, `apt-get install nscd` does everything necessary to set up and
> start nscd, and then guix-daemon works.
OK. (Note that running nscd is recommended anyway when using Guix on
foreign distros anyway.)
>> The question is why isn’t guix-daemon falling back to loading
>> libnss_files and reading /etc/groups directly.
>>
>> How is this guix-daemon built? What libc is it linked against?
>> Does /etc/nsswitch.conf exist and what does it contain?
>
> This guix-daemon is based on core-updates commit 76ef53eb828 (gnu:
> glslang: Update to commit b5b084624), on x86_64-linux.
If you stop nscd again and “strace -f” guix-daemon entirely, can you
check if it ever tries to open libnss_*?
Ludo’.
next prev parent reply other threads:[~2018-01-31 22:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 2:56 bug#30298: core-updates: Failure to find the guixbuild group Leo Famulari
2018-01-31 3:03 ` Leo Famulari
2018-01-31 3:29 ` Leo Famulari
2018-01-31 22:38 ` Ludovic Courtès
2018-01-31 22:49 ` Leo Famulari
2018-01-31 22:52 ` Ludovic Courtès [this message]
2018-01-31 23:07 ` Leo Famulari
2018-01-31 23:28 ` Ludovic Courtès
2018-01-31 23:47 ` Leo Famulari
2018-02-01 9:06 ` Ludovic Courtès
2018-02-01 20:10 ` Leo Famulari
2018-01-31 22:54 ` Leo Famulari
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=87k1vxr68o.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=30298@debbugs.gnu.org \
--cc=leo@famulari.name \
/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).