From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "brettg@posteo.net" <brettg@posteo.net>
Cc: Alex Kost <alezost@gmail.com>, help-guix <help-guix@gnu.org>
Subject: Re: emacs-guix error
Date: Sun, 27 Jan 2019 20:49:04 -0500 [thread overview]
Message-ID: <87zhrly2jz.fsf@gmail.com> (raw)
In-Reply-To: <p4cs9j33scb20btjt6uiajj4.1548639014638@email.lge.com> (brettg@posteo.net's message of "Sun, 27 Jan 2019 19:30:34 -0600")
Hello!
[...]
> Are you using Guix from a git checkout? In that case you’ll need to
> recompile as there has been an ABI change.
My normal Guix run from guix pull, but I do have a Guix checkout that I
use with the pre-inst-env wrapper.
I have this set in my ~/.emacs.
--8<---------------cut here---------------start------------->8---
(setq guix-directory "~/src/guix")
--8<---------------cut here---------------end--------------->8---
IIUC, that doesn't cause Emacs-Guix to use that Guix, only locate
package definition.
In any case, running make clean-go and rebuilding my guix source tree
didn't make the issue go away, but I got a different error when using
C-c . b (guix-devel-build-package-definition); it was failing to find
the module (guix build utils), which led me to the bug 28144.
The suggested workaround by Ludovic to delete the file guix/profiles.go
made the problem go away.
So this might be related.
HTH,
Maxim
next prev parent reply other threads:[~2019-01-28 1:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 1:30 emacs-guix error brettg
2019-01-28 1:39 ` brettg
2019-01-28 7:50 ` Ricardo Wurmus
2019-01-28 1:49 ` Maxim Cournoyer [this message]
2019-01-28 11:56 ` Alex Kost
2019-01-30 7:29 ` Yoshinori Arai
-- strict thread matches above, loose matches on Subject: below --
2019-01-24 2:34 brettg
2019-01-25 17:48 ` Alex Kost
2019-01-24 0:20 Yoshinori Arai
2019-01-25 17:48 ` Alex Kost
2019-01-26 3:31 ` Yoshinori Arai
2019-01-26 17:29 ` Alex Kost
2019-01-26 20:50 ` Maxim Cournoyer
2019-01-26 21:25 ` Ricardo Wurmus
2019-01-28 11:22 ` Yoshinori Arai
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=87zhrly2jz.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=alezost@gmail.com \
--cc=brettg@posteo.net \
--cc=help-guix@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 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.