unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Yoshinori Arai <kumagusu08@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Alex Kost <alezost@gmail.com>, help-guix <help-guix@gnu.org>
Subject: Re: emacs-guix error
Date: Mon, 28 Jan 2019 20:22:59 +0900	[thread overview]
Message-ID: <20190128112259.hs5xcn7oz4f77cj3@WaraToNora> (raw)
In-Reply-To: <87sgxft8kn.fsf@elephly.net>

On Sat, Jan 26, 2019 at 10:25:44PM +0100, Ricardo Wurmus wrote:
> 
> Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
> 
> > Hello,
> >
> > Yoshinori Arai <kumagusu08@gmail.com> writes:
> >
> >> On Fri, Jan 25, 2019 at 08:48:21PM +0300, Alex Kost wrote:
> >>  
> >>> Hello, do you use Guix on a foreign system (not GuixSD)?  If so, please
> >>> look at:
> >>> 
> >>>   https://github.com/alezost/guix.el#important-note-for-non-guixsd-users
> >>> 
> >>> Try the workaround described there and let me know if it works or not.
> >>> 
> >>> -- 
> >>> Alex
> >>
> >> Hello, I use both, foreign system and GuixSD. There is problem on GuixSD.
> >> I followed the link you pointed but I can't recover. 
> >
> > I'm also experiencing the problem reported earlier:
> >
> > --8<---------------cut here---------------start------------->8---
> > ,m (emacs-guix)
> > scheme@(emacs-guix)> (process-package-actions "/var/guix/profiles/per-user/mcournoyer/guix-profile" #:install '((62110912 "out")) #:upgrade '() #:remove '() #:use-substitutes? #t #:dry-run? #f)
> > The process begins ...
> > ERROR: Wrong type to apply: #<syntax-transformer nix-server-version>
> >
> > Entering a new prompt.  Type `,bt' for a backtrace or `,q' to continue.
> > scheme@(emacs-guix) [1]> ,bt
> > In emacs-guix/actions.scm:
> >     118:8  1 (process-package-actions "/var/guix/profiles/per-user/mcournoyer/guix-profile" #:install _ #:upgrade _ #:remove _ #:use-substitutes? _ # _)
> > In unknown file:
> >            0 (_ #<store-connection 256.99 24c73c0>)
> > scheme@(emacs-guix) [1]>
> > --8<---------------cut here---------------end--------------->8---
> >
> > Maybe a system reconfigure (daemon update) would fix it -- I haven't
> > tried it yet.
> 
> Are you using Guix from a git checkout?  In that case you’ll need to
> recompile as there has been an ABI change.
> 
> -- 
> Ricardo
> 

Hello,

I have checked out guix repository but installed guix-daemon to /usr/local.
$ ls /usr/local/bin
guix  guix-daemon
$ which guix-daemon
/gnu/store/75x1as0ff5100d5mxji0i2dxkg77zhqc-profile/bin/guix-daemon

In this cace, is recompilation of guix related with this issue?

  reply	other threads:[~2019-01-28 11:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-24  0:20 emacs-guix error 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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-01-24  2:34 brettg
2019-01-25 17:48 ` Alex Kost
2019-01-28  1:30 brettg
2019-01-28  1:39 ` brettg
2019-01-28  7:50   ` Ricardo Wurmus
2019-01-28  1:49 ` Maxim Cournoyer
2019-01-28 11:56   ` Alex Kost
2019-01-30  7:29     ` 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

  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=20190128112259.hs5xcn7oz4f77cj3@WaraToNora \
    --to=kumagusu08@gmail.com \
    --cc=alezost@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=rekado@elephly.net \
    /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.
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).