From: Marius Bakke <mbakke@fastmail.com>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>, help-guix@gnu.org
Subject: Re: guixbuild does not exist???
Date: Tue, 27 Feb 2018 17:26:16 +0100 [thread overview]
Message-ID: <87efl6v1p3.fsf@fastmail.com> (raw)
In-Reply-To: <bc4a9359-26be-3776-81de-c80bf0b4425f@fastmail.net>
[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]
Konrad Hinsen <konrad.hinsen@fastmail.net> writes:
> Hi Guixers,
>
> Today guix greeted me with a strange error message when I tried to
> install a package:
>
> guix package: error: build failed: the group `guixbuild' specified in
> `build-users-group' does not exist
>
> I call this strange because
> 1) The group exists, as do the users guixbuilder01 to guixbuilder10.
> 2) Guix has been working for quite a while on this machine, and
> nothing spectacular happened since the last use.
> 3) I cannot find any trace of this error message in the Guix source code.
> 4) The guix daemon is running without any sign of trouble.
>
> Any idea of what could be going wrong here?
This has to do with the recent update to glibc 2.26. It no longer
builds the "nss_compat" library, which causes problems on distributions
that only has 'compat' in /etc/nsswitch.conf.
There is some discussion about it here: <https://bugs.gnu.org/30298>.
The workaround is to either install 'nscd', or update nsswitch.conf to
include 'files' (or similar) as a fallback (for "group" in this case).
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2018-02-27 16:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 15:44 guixbuild does not exist??? Konrad Hinsen
2018-02-27 16:25 ` Ricardo Wurmus
2018-02-27 19:59 ` Konrad Hinsen
2018-03-02 13:46 ` Ludovic Courtès
2018-02-27 16:26 ` Marius Bakke [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=87efl6v1p3.fsf@fastmail.com \
--to=mbakke@fastmail.com \
--cc=help-guix@gnu.org \
--cc=konrad.hinsen@fastmail.net \
/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.
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).