From: Chris Marusich <cmmarusich@gmail.com>
To: guix-devel@gnu.org
Subject: Re: offloading trouble on GuixSD->Debian
Date: Mon, 26 Feb 2018 00:40:05 +0100 [thread overview]
Message-ID: <87y3jg4p0q.fsf@gmail.com> (raw)
In-Reply-To: <20180224225316.ojocbdmf2u4fvxxt@abyayala> (ng0@crash.cx's message of "Sat, 24 Feb 2018 22:53:16 +0000")
[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]
ng0 <ng0@crash.cx> writes:
>> 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.
Glad it worked. To figure out precisely why only the last method worked
for you, I guess it would be necessary to debug the exact logic that is
importing the modules. It's probably somewhere in
guix/scripts/offload.scm, maybe?
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2018-02-25 23:40 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
2018-02-25 23:40 ` Chris Marusich [this message]
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=87y3jg4p0q.fsf@gmail.com \
--to=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).