unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: wolf <wolf@wolfsden.cz>
To: 66580@debbugs.gnu.org
Subject: bug#66580: Guix deploy does not properly error report
Date: Mon, 16 Oct 2023 20:31:11 +0200	[thread overview]
Message-ID: <ZS2BbyX_aOq1NL5_@ws> (raw)

[-- Attachment #1: Type: text/plain, Size: 1374 bytes --]

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.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

                 reply	other threads:[~2023-10-16 18:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=ZS2BbyX_aOq1NL5_@ws \
    --to=wolf@wolfsden.cz \
    --cc=66580@debbugs.gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).