From: "Claes Wallin (韋嘉誠)" <clacke+gmail@lysator.liu.se>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>,
Pjotr Prins <pjotr.public66@thebird.nl>,
"bio-packaging@mailman.open-bio.org"
<bio-packaging@mailman.open-bio.org>
Subject: Re: Using a shared Guix store (was RE: [Bio-packaging] testing out guix)
Date: Sun, 19 Jul 2015 11:18:34 +0200 [thread overview]
Message-ID: <CAGv_=BrgdvH32Wma4noSZqu5Hb3y12pvdJv_E1UvXfZKNQRCnw@mail.gmail.com> (raw)
In-Reply-To: <87fv4lo5xc.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]
On Jul 18, 2015 5:13 PM, "Ludovic Courtès" <ludo@gnu.org> wrote:
> "Cook, Malcolm" <MEC@stowers.org> skribis:
>
> > However
> >
> > ./pre-inst-env guix package -i hello
> >
> > Gives me
> >
> > guix package: error: build failed: the build users group
`guix-builder' has no members
> >
> > But, but, I do have a group `guix-builder`
> >
> > I think the problem may be that my guix-builder group was defined in
NIS whereas its members are not in NIS.
>
> What does ‘getenv group guix-builder’ return? It should show something
> like:
Typo: getent, not getenv.
>
guixbuild:x:30000:guixbuilder01,guixbuilder02,guixbuilder03,guixbuilder04,guixbuilder05,guixbuilder06,guixbuilder07,guixbuilder08,guixbuilder09,guixbuilder10
>
> Each build account must have ‘guix-builder’ in its supplementary group
list.
>
> > The daemon is running as user `guix` on host ${GUIXHOST}
>
> The daemon really needs to run as root, if possible:
>
>
http://www.gnu.org/software/guix/manual/html_node/Build-Environment-Setup.html
[-- Attachment #2: Type: text/html, Size: 1524 bytes --]
next prev parent reply other threads:[~2015-07-19 9:18 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 20:22 Using a shared Guix store (was RE: [Bio-packaging] testing out guix) Cook, Malcolm
2015-06-19 8:06 ` Ricardo Wurmus
2015-06-19 11:34 ` Ludovic Courtès
2015-06-25 6:40 ` Ricardo Wurmus
2015-06-19 11:40 ` Ludovic Courtès
2015-07-08 19:20 ` Cook, Malcolm
2015-07-08 19:43 ` Ricardo Wurmus
2015-06-19 17:48 ` Cook, Malcolm
2015-06-24 19:57 ` Ludovic Courtès
2015-07-08 18:03 ` Cook, Malcolm
2015-07-08 19:53 ` Ricardo Wurmus
2015-07-10 8:39 ` Ludovic Courtès
2015-07-11 0:48 ` Cook, Malcolm
2015-07-13 16:45 ` Test suite failures Ludovic Courtès
2015-07-18 3:04 ` Cook, Malcolm
2015-07-18 15:02 ` Ludovic Courtès
2015-07-11 0:54 ` Using a shared Guix store (was RE: [Bio-packaging] testing out guix) Cook, Malcolm
2015-07-15 15:45 ` Ricardo Wurmus
2015-07-15 19:49 ` Cook, Malcolm
2015-07-15 20:28 ` Pjotr Prins
2015-07-18 9:26 ` Cook, Malcolm
2015-07-18 15:13 ` Ludovic Courtès
2015-07-19 9:18 ` Claes Wallin (韋嘉誠) [this message]
2015-07-19 9:33 ` Andreas Enge
2015-07-20 22:37 ` Cook, Malcolm
2015-07-21 20:23 ` Cook, Malcolm
2015-07-21 20:29 ` Ricardo Wurmus
2015-07-23 22:52 ` Ludovic Courtès
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='CAGv_=BrgdvH32Wma4noSZqu5Hb3y12pvdJv_E1UvXfZKNQRCnw@mail.gmail.com' \
--to=clacke+gmail@lysator.liu.se \
--cc=bio-packaging@mailman.open-bio.org \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=pjotr.public66@thebird.nl \
/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).