From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: Ivan Vilata i Balaguer <ivan@selidor.net>, help-guix@gnu.org
Subject: Re: Emacs not seeing newer packages after pull
Date: Tue, 31 Mar 2020 16:08:07 +0200 [thread overview]
Message-ID: <m18sjgipmg.fsf@ordinateur-de-catherine--konrad.home> (raw)
In-Reply-To: <20200331044752.GJ6131@sax.terramar.selidor.net>
Hi Ivan,
> Hi everyone! Recently it caught my attention that emacs-guix seems to
> always be on the *previous* generation of Guix, i.e. the one before
> the latest pull. That is, when I do a `guix pull` and check for new
...
> Is this behavior expected? Does it also happen to you?
No, and yes. Meaning that I most definitely didn't expect it, but I
confirm your observations. And I am running Guix System, so it's not
related to your Guix-under-Debian installation.
In fact, when I saw your mail, it reminded me of similar issues I had
noticed in the past but never taken the time to explore in more depth.
When trying to analyze this in more detail, I noticed that emacs-guix
runs guile 2.2, whereas guix itself used guile 3.0. That shouldn't make
a difference (my understanding is that the current Guix source code
works with both Guile releases), but it's a bit surprising as well.
Cheers,
Konrad.
next prev parent reply other threads:[~2020-03-31 14:08 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 [this message]
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
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=m18sjgipmg.fsf@ordinateur-de-catherine--konrad.home \
--to=konrad.hinsen@fastmail.net \
--cc=help-guix@gnu.org \
--cc=ivan@selidor.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).