unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <ng0@crash.cx>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: offloading trouble on GuixSD->Debian
Date: Sat, 24 Feb 2018 22:53:16 +0000	[thread overview]
Message-ID: <20180224225316.ojocbdmf2u4fvxxt@abyayala> (raw)
In-Reply-To: <878tbiovs0.fsf@gmail.com>

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

Chris Marusich transcribed 2.7K bytes:
> ng0 <ng0@crash.cx> writes:
> 
> > user@abyayala ~$ guix offload test
> > guix offload: testing 1 build machines defined in '/etc/guix/machines.scm'...
> > guix offload: 'yt' is running guile (GNU Guile) 2.2.3
> > offload: error: Guile modules not found on remote host 'yt'
> > hint: Make sure `GUILE_LOAD_PATH' includes Guix' own module directory.  Run
> > `ssh yt env | grep GUILE_LOAD_PATH' to check.
> >
> > On the serer itself, the Guix modules are in the path.
> > Guile-ssh, guile, and guile-readline are installed in the profile of the
> > offloading user on the build node.
> > guix pull has been run at least once for the user profile.
> > 
> > ...
> >
> > I have experimented with the content of files and what is exported.
> >
> > ssh yt env | grep GUILE_
> > GUILE_LOAD_COMPILED_PATH=/gnu/store/63p2z4sx3j6y8xs4sff423fl12qh1m0p-profile/lib/guile/2.2/site-ccache:/gnu/store/63p2z4sx3j6y8xs4sff423fl12qh1m0p-profile/share/guile/site/2.2
> > GUILE_LOAD_PATH=/gnu/store/63p2z4sx3j6y8xs4sff423fl12qh1m0p-profile/share/guile/site/2.2
> 
> Are the Guix modules actually present at those paths in
> "/gnu/store/63p2z4sx3j6y8xs4sff423fl12qh1m0p-profile"?  You can find out
> by running this command on the Debian host:
> 
> find -L /gnu/store/63p2z4sx3j6y8xs4sff423fl12qh1m0p-profile -name guix

indeed, this returned an empty result.

> If they aren't present, then according to the "guix offload" hint,
> you'll need to add the Guix modules to it.  One way to accomplish that
> might be to add either the system installation or the build user's
> installation of Guix (the latter should be at ~/.config/guix/latest) to
> the GUILE_LOAD_PATH in your build user's ~/.bashrc on the Debian host.

None of the above worked,

> Another way might be to run "guix package -i guix" as the build user on
> the Debian host.

but this did. Too bad, I wanted avoid installing guix into the profile.

> Hope that helps!  Good luck.
> 
> -- 
> Chris



-- 
ng0 ::  https://n0.is | https://crash.cx
A88C8ADD129828D7EAC02E52E22F9BBFEE348588

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-02-24 22:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-24 21:37 offloading trouble on GuixSD->Debian ng0
2018-02-24 21:52 ` Marius Bakke
2018-02-24 21:57   ` ng0
2018-02-25 10:35     ` Ricardo Wurmus
2018-02-25 11:16       ` ng0
2018-02-24 22:41 ` Chris Marusich
2018-02-24 22:53   ` ng0 [this message]
2018-02-25 23:40     ` Chris Marusich

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=20180224225316.ojocbdmf2u4fvxxt@abyayala \
    --to=ng0@crash.cx \
    --cc=cmmarusich@gmail.com \
    --cc=guix-devel@gnu.org \
    /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).