From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marius Bakke Subject: Re: guixbuild does not exist??? Date: Tue, 27 Feb 2018 17:26:16 +0100 Message-ID: <87efl6v1p3.fsf@fastmail.com> References: Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:57746) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eqi59-0000lt-DV for help-guix@gnu.org; Tue, 27 Feb 2018 11:26:24 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eqi56-0004CV-6I for help-guix@gnu.org; Tue, 27 Feb 2018 11:26:23 -0500 Received: from out2-smtp.messagingengine.com ([66.111.4.26]:56797) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1eqi55-0004Bh-TL for help-guix@gnu.org; Tue, 27 Feb 2018 11:26:20 -0500 In-Reply-To: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Konrad Hinsen , help-guix@gnu.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Konrad Hinsen writes: > Hi Guixers, > > Today guix greeted me with a strange error message when I tried to=20 > install a package: > > guix package: error: build failed: the group `guixbuild' specified in= =20 > `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=20 > nothing spectacular happened since the last use. > 3) I cannot find any trace of this error message in the Guix source cod= e. > 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: . The workaround is to either install 'nscd', or update nsswitch.conf to include 'files' (or similar) as a fallback (for "group" in this case). --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAlqVhqgACgkQoqBt8qM6 VPqmvAf/Xqp3AqGOguzFZzsA1qcMAnhnzc+ODMLlIyLFoPdOftrO/Hwxi+A6Z6lT c+aWEwxnTDD9AFjB4JhDWhxljyryPp0XS8r/XQymPP9zFVKHb0QsbgN5K1QJEEQ/ tMa5TwHarV/J8JjEhg1RT6zr/FNbXnyV4hXxTB81P9ueWVl9tSaLRKY61IbAr799 fj/IvBlk90Ax2hmq7l/gM5Jt3xc4EjiSPdNa1zsN/TRTey0oGHSbhuj7JiL+I/2i 9dtLhnegqqIElEMKu7jSa+CD7iEWm/5bRyq6nult0KfpWBghKadfCB0p8sTXER6Z vgReU2NlMt77kXdTSRnfpy6tqgyzAw== =Ush2 -----END PGP SIGNATURE----- --=-=-=--