all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Cook, Malcolm" <MEC@stowers.org>
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: Sat, 11 Jul 2015 00:48:51 +0000	[thread overview]
Message-ID: <dbf9343635144f20888de6df35434630@exchsrv2.sgc.loc> (raw)
In-Reply-To: <87h9pce79t.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 4891 bytes --]

Ludovic, and Ricardo,

> Yes, one way to help would be by trying a simple setup using Guix as it
> currently exists, coupled with socat:
> 
>   http://debbugs.gnu.org/cgi/bugreport.cgi?bug=20381
> 
> If you could test this and provide feedback about the other options discussed
> there, that would be great (please email
> 20381@debbugs.gnu.org.)

Excellent.  That definitely looks testable by me, once I'm done with my basic site deployment.  I've been moving rather slowly but might be ready to contrast such approach with simply calling guix on guix-master over ssh.  I'll plan on it.  Maybe a week or two out.

Reading the thread, it sounds like Ricardo has today already had good success with socat.  Yay!

In that thread, you suggested "What about installing Guix in /gnu/bin (say) and sharing it over NFS?".  Is there a way to `./bootstrap ./configure ` this?  Something like -- exec_prefix=/gnu --localstatedir=/gnu/var?  

Also, you discussed need for setting NIX_STATE_DIR.  This should not be needed if guix was already installed with configuration of --localstatedir=/guix/var   (with /guix being nfs mounted), right?

Ricardo also wrote "For ‘guix package’ to work, /gnu/var/guix/profiles/per-user must be shared read-write (over NFS) with correct UID mapping." - I really don't understand this and tried to elicit feedback in http://lists.nongnu.org/archive/html/guix-devel/2015-07/msg00216.html -   Can anyone give me clarification on this.  I though the guix daemon is going to manage these profiles.

Honestly, much of my understanding of the above comes from reading the manual, archived IRC chats and mail threads, FOSDEM vids, and blog posts - which has been great.  But,  I've yet to succeed in my own site deploy, which will give me testbed to stretch my own understanding.  Today, I had the following failure....

Ricardo, et. al.,  would you mind sharing some details on your network sharing configuration as regards users/groups and privileges, for I seem to have painted myself into a corner with the following
          
	/gnu  is an NFS mount, owned by network user 'guix', group-owned by  guix-builder with mod of 1775 
 
	guix is being built from git configured with -- exec_prefix=/gnu --localstatedir=/gnu/var 

	`make check`  results are

============================================================================
Testsuite summary for GNU Guix 0.8.3
============================================================================
# TOTAL: 42
# PASS:  32
# SKIP:  0
# XFAIL: 0
# FAIL:  10
# XPASS: 0
# ERROR: 0

With details below....   I can submit all this to bug-guix@gnu.org, but I suspect (1) there is something fundamentally wrong with the way I am setting things up (2) your are reading this anyway ;)

Can you see any gotchas I haven't got yet?  Can you see the error in my ways and suggest a way through?

FWIW, I try to `make install` anyway, and, I pause.... I cannot complete a make install without "changing hats".  I find that it works to do the following

		sudo make install-data # as root on localhost
		sudo -u guix make install-exec ## since root on localhost is squashed on the NFS mount point, 

But I don't know if this is complete or not (the Makefile is complex!).

Anyway, "changing hats" feels very wrong, and I can feel more trouble coming when I want to run the daemon....

Thanks so much everyone, and, keep on guixing,

~Malcolm


PS - in case it helps - below are test results and attached are tarred logs - I have not yet taught myself how to read them with understanding.... - (have a great weekend!)

PASS: tests/base32.scm
PASS: tests/base64.scm
FAIL: tests/cpio.scm
PASS: tests/hash.scm
PASS: tests/pk-crypto.scm
PASS: tests/pki.scm
PASS: tests/sets.scm
PASS: tests/substitute.scm
FAIL: tests/builders.scm
FAIL: tests/derivations.scm
PASS: tests/ui.scm
PASS: tests/records.scm
PASS: tests/utils.scm
PASS: tests/build-utils.scm
FAIL: tests/packages.scm
PASS: tests/snix.scm
PASS: tests/hackage.scm
PASS: tests/elpa.scm
FAIL: tests/store.scm
PASS: tests/monads.scm
PASS: tests/gexp.scm
FAIL: tests/nar.scm
FAIL: tests/union.scm
PASS: tests/profiles.scm
FAIL: tests/syscalls.scm
PASS: tests/gremlin.scm
PASS: tests/lint.scm
PASS: tests/publish.scm
PASS: tests/size.scm
PASS: tests/guix-build.sh
PASS: tests/guix-download.sh
PASS: tests/guix-hash.sh
PASS: tests/guix-package.sh
FAIL: tests/guix-package-net.sh
PASS: tests/guix-system.sh
PASS: tests/guix-archive.sh
PASS: tests/guix-authenticate.sh
FAIL: tests/guix-environment.sh
PASS: tests/guix-lint.sh
PASS: tests/guix-register.sh
PASS: tests/guix-gc.sh
PASS: tests/guix-daemon.sh



> So no ETA, but once we have feedback from you, Ricardo, and other
> interested parties, it will be easier to make a choice and implement it.
> :-)
> 
> Thanks,
> Ludo’.

[-- Attachment #2: guixtests.log --]
[-- Type: application/octet-stream, Size: 1525760 bytes --]

  reply	other threads:[~2015-07-11  0:49 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 [this message]
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 (韋嘉誠)
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=dbf9343635144f20888de6df35434630@exchsrv2.sgc.loc \
    --to=mec@stowers.org \
    --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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.