unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: Vincent Rouvreau <vincent.rouvreau@inria.fr>
Cc: 34573@debbugs.gnu.org
Subject: bug#34573: Backtrace of guix pull failed
Date: Mon, 04 Mar 2019 23:02:36 +0100	[thread overview]
Message-ID: <875zsynvr7.fsf@gnu.org> (raw)
In-Reply-To: <87ftsjvk1i.fsf@elephly.net> (Ricardo Wurmus's message of "Tue, 19 Feb 2019 17:08:55 +0100")

Hi Vincent,

Ricardo Wurmus <rekado@elephly.net> skribis:

>> I wanted to install python, numpy and conda on plafrim as explained here : https://www.plafrim.fr/en/guix/
>> And guix pull failed :
> […]
>> In ./guix/profiles.scm:
>>   1773:23  2 (_)
>> In ./guix/utils.scm:
>>    661:47  1 (xdg-directory _ "/.config" #:ensure? _)
>> In unknown file:
>>            0 (getpw 10837)
>>
>> ERROR: In procedure getpw:
>> In procedure getpw: entry not found
>
> This looks like nscd is not running.

Actually nscd *is* running but it’s been misconfigured on these machines
since a couple of weeks or so—the sysadmins are aware of it and will
take a look shortly.

What happens is that nscd returns nothing for “passwd” database lookups
and as a result, the application (in this case Guile) falls back to its
local NSS implementation, which in turns tries to load an incompatible
libnss*.so file, leading to this lookup failure.

Anyway, this really looks like a setup issue on this machine, so I’m
closing this bug and we can discuss it further with the admins if
needed, Vincent.

Thanks,
Ludo’.

      reply	other threads:[~2019-03-04 22:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-19  9:55 bug#34573: Backtrace of guix pull failed Vincent Rouvreau
2019-02-19 15:42 ` Andreas Enge
2019-02-19 16:48   ` Vincent Rouvreau
2019-02-19 16:56     ` Leo Famulari
2019-02-19 16:08 ` Ricardo Wurmus
2019-03-04 22:02   ` Ludovic Courtès [this message]

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=875zsynvr7.fsf@gnu.org \
    --to=ludovic.courtes@inria.fr \
    --cc=34573@debbugs.gnu.org \
    --cc=vincent.rouvreau@inria.fr \
    /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).