From: ng0 <ng0@crash.cx>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: offloading trouble on GuixSD->Debian
Date: Sat, 24 Feb 2018 21:57:15 +0000 [thread overview]
Message-ID: <20180224215715.ldzevt7t7lfe6zh6@abyayala> (raw)
In-Reply-To: <87h8q68397.fsf@fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]
Marius Bakke transcribed 1.4K bytes:
> ng0 <ng0@crash.cx> writes:
>
> > Hi,
> >
> > I have run into yet another familar(?) problem with offloading.
> >
> > My build host for the first time is Debian, so instead of GuixSD master offloading
> > to an GuixSD build node I'm offloading from GuixSD master to an Debian build
> > node.
> > This is a minimal, basic Debian install in the Hetzner cloud.
> >
> > I've come as far as:
> >
> > 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.
>
> The "guix" package must be available on GUILE_LOAD_PATH.
>
> Does 'guile -c "(use-modules (guix))"' work for the offloading user?
As I've written, yes, locally it works (guix is available when I log in via ssh and
execute the command for guile to use the module). via remote non-interactive shell
it doesn't.
--
ng0 :: https://n0.is | https://crash.cx
A88C8ADD129828D7EAC02E52E22F9BBFEE348588
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-02-24 21:57 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 [this message]
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
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=20180224215715.ldzevt7t7lfe6zh6@abyayala \
--to=ng0@crash.cx \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.com \
/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).