guix deploy failed with exit code 1

  • Done
  • quality assurance status badge
Details
One participant
  • Jack Hill
Owner
unassigned
Submitted by
Jack Hill
Severity
normal

Debbugs page

J
J
Jack Hill wrote on 25 Aug 2021 15:05
(address . bug-guix@gnu.org)
alpine.DEB.2.21.2108251745210.2109@marsh.hcoop.net
Hi Guix,

I'm using Guix from commit 68b22a85419a52dcdb47422c10f9575b5d332790. When
I try to run `guix deploy` using the attatched configuration, I receive
the following error:

```
$ guix deploy -v3 config.scm
The following 1 machine will be deployed:
kiosk

guix deploy: deploying to kiosk...
guix deploy: sending 0 store items (0 MiB) to 'kiosk.jackhill.us'...
guix deploy: sending 0 store items (0 MiB) to 'kiosk.jackhill.us'...
guix deploy: sending 0 store items (0 MiB) to 'kiosk.jackhill.us'...
guix deploy: sending 2 store items (0 MiB) to 'kiosk.jackhill.us'...
guix deploy: error: program `/gnu/store/3lig4b2i1qaisg9yx8nbl0xp8hgh40a7-guix-1.0.1-15.0984481/bin/guix' failed with exit code 1
```

The error would appear to occur when creating the grub configuration,
because both /run/current-system and the list reported by `guix system
list-generations` show the newly created generation, but it is not present
in the grub configuration.

The last time I sucessfully used guix deploy on this host was with Guix
830dab870ab1d4a4ec1127a877a43d19f86c4f7f on March 20th, 2020 (yes, the
pandemic has kept me away from working on this host for some time).

Best,
Jack
;; This is an operating system configuration generated ;; by the graphical installer. (use-modules (gnu)) (use-service-modules desktop networking ssh xorg) (define kiosk-example (operating-system (locale "en_US.utf8") (timezone "America/New_York") (bootloader (bootloader-configuration (bootloader grub-bootloader) (target "/dev/sda"))) (swap-devices (list "/dev/sda1")) (file-systems (cons* (file-system (mount-point "/") (device (file-system-label "guix-root")) (type "ext4")) %base-file-systems)) (host-name "kiosk") (users (cons* (user-account (name "jackhill") (comment "Jack Hill") (group "users") (home-directory "/home/jackhill") (supplementary-groups '("wheel" "netdev" "audio" "video"))) %base-user-accounts)) (packages (append (list (specification->package "nss-certs")) %base-packages)) (services (append (list (service openssh-service-type (openssh-configuration (permit-root-login 'prohibit-password))) (service network-manager-service-type) (service wpa-supplicant-service-type)) %base-services)))) (list (machine (operating-system kiosk-example) (environment managed-host-environment-type) (configuration (machine-ssh-configuration (host-name "kiosk.jackhill.us") (host-key "ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIEk3vY6QSwYtHpmsKTIGHJd508k3n1uCe3K3cpidUrzS") (system "x86_64-linux")))))
J
J
Jack Hill wrote on 26 Nov 2021 22:51
Can't fix past error with upgrading from old versions
(address . control@debbugs.gnu.org)
alpine.DEB.2.21.2111270147390.13935@marsh.hcoop.net
tag 50206 wontfix
close 50206

Thanks

I worked around this problem by stepping through an intermediate commit.
It seems that going over a year between updates was not something that
these particular versions of Guix can handle. Hopefully we'll be a little
bit more stable in the future, but there's nothing we can do about the
history now. I should note that this was never a bug in `guix deploy` as
reconfiguring locally ran into the problem as well.

Best,
Jack
?
Your comment

This issue is archived.

To comment on this conversation send an email to 50206@patchwise.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 50206
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch