Guix deploy does not properly error report

  • Open
  • quality assurance status badge
Details
2 participants
  • wolf
  • Tomas Volf
Owner
unassigned
Submitted by
wolf
Severity
normal

Debbugs page

wolf wrote 1 years ago
(address . bug-guix@gnu.org)
ZS2BbyX_aOq1NL5_@ws
Hi,

when I run `guix deploy' that ends in an error, the report does not include all
information required to debug the issue.

guix deploy: error: failed to deploy test: failed to switch systems while deploying '192.168.0.130':
system-error "symlink" "~A" ("File exists") (17)

Would be somewhat useful to have the details about what file already exists. If
I run `guix system switch-generation' directly on the target system, the output
is better:

building /gnu/store/jqnxwfq6f5gvyjz0avqaakkd0ljbzglj-grub.cfg.drv...
building /gnu/store/vjgyb6j36idxzdm8g6hgjsa75wmdbr7f-install-bootloader.scm.drv...
switched from generation 83 to 83
WARNING: (guile-user): imported module (guix build utils) overrides core binding `delete'
making '/gnu/store/m71zy9yd38pm4mlwk7a7wp79053iiy5s-system' the current system...
WARNING: (guile-user): imported module (guix build utils) overrides core binding `delete'
setting up setuid programs in '/run/setuid-programs'...
populating /etc from /gnu/store/inl5dmrhrdxxkch06mp1hvpv45abgkic-etc...
guix system: error: symlink: File exists: "/etc/guix"

The information seems to be available, just not propagated via the `guix
deploy'.

Have a nice day,
W.

--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEt4NJs4wUfTYpiGikL7/ufbZ/wakFAmUtgW8ACgkQL7/ufbZ/
wamDIxAAs8rsFtajoA2plCGfIAtqTTks+H8sqL0WisgctrqrLFP1SBzDtIMr7Py/
HTNY3ypMnTTWjPPUnEUIYEmbFKB87pdDQx8u4qbr0K+dl6ydk2c7/RlGvK3DlsE3
CCDIgv2Wpqn45bb4VgfB9aqBrGR1hvrgAWc9CYitEW4Kx0Nyu/gJSYuRM9570Sqd
qlh8jK4ZHKAXY747QFo3aHipn5m6WjgGgIWOcslSg5Y9YM1hcM86HLyTH3BXgUZF
AX7DvrdOLtMxWTxqrSa4qHi7M758+oWz4JFEG6Bq4hjOgWu1VuWcQaih4r78fNJV
J2Rp3+LB9I/RdGRpKhwtkc0ZlxNkfc7nsINP/COvjyDHS4IB/FUpA72gm7Z8UNvO
IDgI9s1OTEdAhLPV48+mv4Gr3TtJiV+56j2klcrDJGGS75CI2zpcFCxuDPb7I2j2
it9z6z+0k3CUt+ovaSz5wGE6di5qK+Qo2Wt0OcTQ8CBYeT6WlOnzv4F8HSA9CIOd
rxHqm5JNTKAwtHO61EBkdUDmiqgi85vv0Ws7RkroykJCYpcRmu3y6m32xgxXzSwJ
8R4ZgajbiEFUf3+cOQcLnzEFqnXuAF8MdRTkHCdNJyPjQY1me+XzRVz9jkyTv0zY
j6zGwzzw3KHsaZiSeX5s6lXIa+7DbZswXoDg/8djMVVT9y4irro=
=OUAw
-----END PGP SIGNATURE-----


Tomas Volf wrote 1 years ago
control message for bug #66580
(address . control@debbugs.gnu.org)
6003c419c0ca5df58f8d67059245ce83@wolfsden.cz
submitter 66580 !
quit
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 66580@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 66580
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
You may also tag this issue. See list of standard tags. For example, to set the confirmed and easy tags
mumi command -t +confirmed -t +easy
Or, remove the moreinfo tag and set the help tag
mumi command -t -moreinfo -t +help