[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Emacs on a reMarkable

From: Simon Tournier
Subject: Re: Emacs on a reMarkable
Date: Thu, 21 Sep 2023 09:14:03 +0200


On Wed, 20 Sep 2023 at 20:25, Sébastien Lerique <> wrote:

> root@vm-remarkable2:~# guix pull -l
> guix pull: error: profile '/var/guix/profiles/per-user/root/current-guix' 
> does not exist
> root@vm-remarkable2:~# guix pack -RR -S /emacsbin=bin emacs-no-x
> [... substitutes, grafts, builds ...]
> /gnu/store/wpxqqdcslxxx9g9l9j847ifgh0xdlsfl-emacs-no-x-tarball-pack.tar.gz

Here, you are using the “old” Guix revision packaged by Debian and
installed as /usr/bin/guix.  Well, “which guix“ or “type -P guix” should
confirm or infirm this assumption…

> root@vm-remarkable2:~# guix pull -l
> guix pull: error: profile '/var/guix/profiles/per-user/root/current-guix' 
> does not exist
> root@vm-remarkable2:~# guix describe
> guix describe: error: failed to determine origin
> hint: Perhaps this `guix' command was not obtained with `guix pull'? Its 
> version
> string is 1.4.0.

…and this output is a first clue that confirms the assumption above.

> root@vm-remarkable2:~# guix pull
> [... substitutes and builds ...]
> root@vm-remarkable2:~# guix pull -l
> Generation 1 Sep 20 2023 13:50:04 (current)
>   guix 6bd17a0
>     repository URL:
>     branch: master
>     commit: 6bd17a0806ad32d1493ac51a7443276f719c4224

Now, the “new” Guix revision is around.  The question is…

> root@vm-remarkable2:~# guix pack -RR -S /emacsbin=bin emacs-no-x
> /gnu/store/wpxqqdcslxxx9g9l9j847ifgh0xdlsfl-emacs-no-x-tarball-pack.tar.gz

…what the Guix revision that this “guix pack” refers to?  What is the
output of “which guix” or “type -P guix”?  I guess it is /usr/bin/guix,
isn’t it?

Other said, it seems something about “hash guix“ as probably recommended
by the message ending “guix pull”. :-)

>> root@arm-vm:~# /usr/bin/guix pack -R -S /emacsbin=bin emacs-no-x
>> /gnu/store/wpxqqdcslxxx9g9l9j847ifgh0xdlsfl-emacs-no-x-tarball-pack.tar.gz
>> root@arm-vm:~# guix time-machine 
>> --commit=65dcfb3f3865d08467da747041263fd22460d393 \
>>                -- pack -R -S /emacsbin=bin emacs-no-x
>> /gnu/store/pszvzh7917kkf1cisxd46bx8vlac25zh-emacs-no-x-tarball-pack.tar.gz

In these two commands, the Guix revision used for producing the tarball
is explicitly set.  Commit 65dcfb3 is just a recent one – pick the one
you prefer :-) – the point was to verify you get a different tarball for
another revision than the “old” one and thus check if the issue is about
an incorrect configured “guix” command.  Does it make sense?

> So no, the tarball after guix pull is the same as the one from before,
> unless I reboot the VM.

I think that’s because the Guix revision when typing “guix“ had not been
refreshed after “guix pull”.  IIRC, it needs to be after the first “guix

>                         After rebooting the VM, running the same guix
> pack gives a different tarball (the actual one under guix 6bd17a0 I
> guess):

Well, I guess reboot acts as “hash guix” here. :-)

> Could this just be due to a need for reboot after the first `guix pull`?

Well, my guess is that the command “guix” points to the same executable
(/usr/bin/guix) before and after “guix pull”.  Something like:

    # apt install guix
    # type -P guix

    # guix pull
    # type -P guix

    # hash guix
    # type -P guix

If not, also check that PATH is correctly configured, before and after


reply via email to

[Prev in Thread] Current Thread [Next in Thread]