Hi! On 18 Sep 2023 at 10:50, Simon Tournier <[email protected]> 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
