From: "Sébastien Lerique" <sl@eauchat.org>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Emacs on a reMarkable
Date: Wed, 20 Sep 2023 20:25:30 +0200 [thread overview]
Message-ID: <87pm2c1wos.fsf@eauchat.org> (raw)
In-Reply-To: <87o7hzsw4t.fsf@gmail.com>
Hi!
On 18 Sep 2023 at 10:50, Simon Tournier <zimon.toutoune@gmail.com> wrote:
> Re-reading, I am missing one point…
>
> [...]
>
> This wpxqqdcslxxx9g9l9j847ifgh0xdlsfl-emacs-no-x-tarball-pack.tar.gz is
> what you get before “guix pull”. It means, it used the Guix revision
> packaged by Debian (Guix v1.4 I guess).
>
> Then after “guix pull”, I read
> pszvzh7917kkf1cisxd46bx8vlac25zh-emacs-no-x-tarball-pack.tar.gz which
> seems different. This had been produced using Guix revision 65dcfb3.
>
Yes, but there's been a mix of `-R` and `-RR` in the summary I might
have made.
So I tried out from scratch to be sure, and I'm still surprised: On a
clean ARM VM made following
https://www.willhaley.com/blog/debian-arm-qemu/ here is my full setup
(apologies for the details):
1) Get Debian all up to date
--8<---------------cut here---------------start------------->8---
root@vm-remarkable2:~# nano /etc/sources.list
root@vm-remarkable2:~# cat /etc/sources.list
deb http://deb.debian.org/debian bookworm main
deb-src http://deb.debian.org/debian bookworm main
deb http://deb.debian.org/debian-security/ bookworm-security main
deb-src http://deb.debian.org/debian-security/ bookworm-security main
deb http://deb.debian.org/debian bookworm-updates main
deb-src http://deb.debian.org/debian bookworm-updates main
root@vm-remarkable2:~# apt update && apt upgrade
[...]
--8<---------------cut here---------------end--------------->8---
Copy the new vmlinuz and initrd.gz to the host's folder (as they're in
the launch code described in
https://www.willhaley.com/blog/debian-arm-qemu/ , so just in case), then
power off the VM and boot it again. Then:
root@vm-remarkable2:~# apt install guix
Then reboot once more as the terminal would not give new lines. Then
build and check the file name before and after updating guix:
--8<---------------cut here---------------start------------->8---
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
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.
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: https://git.savannah.gnu.org/git/guix.git
branch: master
commit: 6bd17a0806ad32d1493ac51a7443276f719c4224
root@vm-remarkable2:~# guix pack -RR -S /emacsbin=bin emacs-no-x
/gnu/store/wpxqqdcslxxx9g9l9j847ifgh0xdlsfl-emacs-no-x-tarball-pack.tar.gz
--8<---------------cut here---------------end--------------->8---
> Is it not the case? Well, I guess you get:
>
> 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
>
> No? Do you see something different?
>
So no, the tarball after guix pull is the same as the one from before,
unless I reboot the VM. After rebooting the VM, running the same guix
pack gives a different tarball (the actual one under guix 6bd17a0 I
guess):
--8<---------------cut here---------------start------------->8---
root@vm-remarkable2:~# guix pack -RR -S /emacsbin=bin emacs-no-x
/gnu/store/0cam5691zqp1r8wlv741c8im2rmhk2v1-emacs-no-x-tarball-pack.tar.gz
--8<---------------cut here---------------end--------------->8---
(Sorry for not having reused 65dcfb3, but the problem is independent of
that version.)
Could this just be due to a need for reboot after the first `guix pull`?
Cheers!
Sébastien
next prev parent reply other threads:[~2023-09-20 19:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 13:26 Emacs on a reMarkable Sébastien Lerique
2023-09-05 14:18 ` Simon Tournier
2023-09-07 9:52 ` Sébastien Lerique
2023-09-11 16:26 ` Simon Tournier
2023-09-15 20:56 ` Sébastien Lerique
2023-09-18 8:50 ` Simon Tournier
2023-09-20 18:25 ` Sébastien Lerique [this message]
2023-09-21 7:14 ` Simon Tournier
2023-09-22 7:14 ` Sébastien Lerique
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=87pm2c1wos.fsf@eauchat.org \
--to=sl@eauchat.org \
--cc=help-guix@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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).