From: Ivan Vilata i Balaguer <ivan@selidor.net>
To: help-guix@gnu.org
Subject: Emacs not seeing newer packages after pull
Date: Tue, 31 Mar 2020 00:47:52 -0400 [thread overview]
Message-ID: <20200331044752.GJ6131@sax.terramar.selidor.net> (raw)
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 packages and versions in
`guix pull --news`, when I go to the emacs-guix packages list, these packages
and versions are not there; the ones from the previous Guix generation are
instead.
Actually, if I upgrade or install such new packages from the command line,
some packages under emacs-guix appear as "from the future".
Restaring Emacs or pulling from it doesn't seem to fix things. I also came
across the `guix-repl-use-latest` variable, but it's already `t` (in fact,
`ps` shows the right `~/.config/guix/current` paths being passed to `guile`).
I'm running Guix on top of Debian, and I also have package `guix` installed in
my profile (if I remove it, it gets even worse: the Emacs installed package
list shows most packages as "unknown").
Is this behavior expected? Does it also happen to you? (Hint: do you see
many blue packages "from the future" in the Emacs list.) Maybe I'm doing
something wrong?
Thanks in advance for your help!
--
Ivan Vilata i Balaguer -- https://elvil.net/
next reply other threads:[~2020-03-31 4:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 4:47 Ivan Vilata i Balaguer [this message]
2020-03-31 14:08 ` Emacs not seeing newer packages after pull 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
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=20200331044752.GJ6131@sax.terramar.selidor.net \
--to=ivan@selidor.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.
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).