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: Mon, 6 Apr 2020 20:44:49 -0400	[thread overview]
Message-ID: <20200407004449.GF9908@sax.terramar.selidor.net> (raw)
In-Reply-To: <m17dyymjz9.fsf@khs-macbook.home>

Konrad Hinsen (2020-04-02 09:20:58 +0200) wrote:

> Hi Ivan,
> 
> […] Interesting. That looks very different for me on Guix System! But then,
> I don't have "guix" in my profile. Not sure it's a good idea.
> 
> > If I run `guix package -s guix`, the version of the `guix` package (which I
> > assume is the same that I got after the last `guix pull`, but I may be wrong)
> > is `1.0.1-15…`.
> 
> If you have "guix" in your profile, you'd have to update your profile
> after a pull to run the latest version.
> 
> > Maybe I should just `guix package -u` this time and check if the problem
> > repeats with the next pull…
> 
> That sounds like a good experiment to do.

So I did `guix package -u` and `emacs-guix` continued to show the list of
packages and references to package definitions from the previous pull.  I then
confirmed that definitions belonged to the `guix` package *in my profile*
while, for instance, `guix package -s whatever` showed references to files *in
my pulled Guix*.

Anyway, that kinda confirmed what a bad idea keeping `guix` in my profile was
(it landed there in some of my first generations).  So I removed it, pulled
and upgraded packages again.

However (as I had tested before), `emacs-guix` now shows a lot of "unknown"
pink packages in my installed list.  Some of the few green ones can't be
opened because of unbound variables, others can be opened but have empty
descriptions with just a link to their store directory… but some do have
descriptions and a valid reference (absolute path) to their definition and, lo
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".

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.

Thanks anyway Konrad for your help!

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

  reply	other threads:[~2020-04-07  0: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 [this message]
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=20200407004449.GF9908@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).