unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Ivan Vilata i Balaguer <ivan@selidor.net>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>
Cc: help-guix@gnu.org
Subject: Re: Emacs not seeing newer packages after pull
Date: Tue, 7 Apr 2020 15:44:05 -0400	[thread overview]
Message-ID: <20200407194405.GG9908@sax.terramar.selidor.net> (raw)
In-Reply-To: <m1k12r4so3.fsf@khs-macbook.home>

Konrad Hinsen (2020-04-07 10:16:28 +0200) wrote:

> > and behold, the files are under my pulled Guix.  Yay!  However, `guix-pull` in
> > Emacs still fails with a bunch of "incompatible bytecode kind" errors then
> > "guix: pull: command not found".
> 
> The "incompatible byte code" messages are due to emacs-guix using Guile
> 2.2 whereas Guix is using Guile 3. They will disappear in the ongoing
> transition of everything to Guile 3. And they don't signal any real
> problem. It's the last message that is critical.

Indeed.  I see that someone already reported Guile 3 incompatibilities in
<https://github.com/alezost/guix.el/issues/37>.  I'll keep an eye on that.

> > So I guess the proper way to go now is to report why `emacs-guix` on a foreign
> > distro doesn't really work.  I'll look at the archives and open a new thread
> > if needed.
> 
> Emacs-guix is a project separate from Guix, so it's best to open an
> issue at https://gitlab.com/emacs-guix.

Thanks for the pointer!  I see that after GitHub issues #28 and #29, Alex
added an explicit warning for foreign distro users here:
<https://github.com/alezost/guix.el#important-note-for-non-guixsd-users>.
I'll report that they result in `emacs-guix` seeing packages from the previous
pull instead.

Thanks again!

-- 
Ivan Vilata i Balaguer -- https://elvil.net/

  reply	other threads:[~2020-04-07 19:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-31  4:47 Emacs not seeing newer packages after pull Ivan Vilata i Balaguer
2020-03-31 14:08 ` Konrad Hinsen
2020-03-31 18:25   ` Konrad Hinsen
2020-04-01  0:04     ` Ivan Vilata i Balaguer
2020-04-02  7:20       ` Konrad Hinsen
2020-04-07  0:44         ` Ivan Vilata i Balaguer
2020-04-07  8:16           ` Konrad Hinsen
2020-04-07 19:44             ` Ivan Vilata i Balaguer [this message]
2020-04-09  1:25               ` Ivan Vilata i Balaguer

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=20200407194405.GG9908@sax.terramar.selidor.net \
    --to=ivan@selidor.net \
    --cc=help-guix@gnu.org \
    --cc=konrad.hinsen@fastmail.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).