From: swedebugia <swedebugia@riseup.net>
To: help-guix@gnu.org
Subject: Re: guix fail to reconfigure the system
Date: Mon, 30 Apr 2018 12:44:38 +0200 [thread overview]
Message-ID: <a87d9b5d-29d6-d3f9-9431-c2256da448c0@riseup.net> (raw)
In-Reply-To: <87604d2sxi.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]
Hi
On 2018-04-27 06:07, Chris Marusich wrote:
> Pierre Neidhardt <ambrevar@gmail.com> writes:
>
>> In general I think `guix system` error feedback tends to be a tad too
>> shy. Are there some plans to make them more explicit and precise?
> Did you know that you can ask for more verbose feedback with the
> --on-error option? See (guix) Invoking guix system for details.
>
According to the manual this is the default strategy:
|nothing-special|
Report the error concisely and exit. This is the default strategy.
Which in the case of Matija reports:
guix system: error: stat: No such file or directory: "system"
Maybe we should add to this error message an information about the
ability to choose another error strategy (to have more information about
what went wrong), e.g.:
guix system: error: stat: No such file or directory: "system"
Note: More information on the error is availiable by choosing another error strategy.
See (guix) Invoking guix system for details.
Cheers
Swedebugia
[-- Attachment #2: Type: text/html, Size: 1807 bytes --]
next prev parent reply other threads:[~2018-04-30 10:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 16:52 guix fail to reconfigure the system Maitja Obid
2018-04-25 20:43 ` Ludovic Courtès
2018-04-25 21:17 ` Matija Obid
2018-04-25 23:05 ` Clément Lassieur
2018-04-26 3:16 ` Pierre Neidhardt
2018-04-27 4:07 ` Chris Marusich
2018-04-27 9:07 ` Pierre Neidhardt
2018-04-30 10:44 ` swedebugia [this message]
2018-04-30 16:31 ` Ludovic Courtès
2018-04-30 20:21 ` Clément Lassieur
2018-05-05 13:42 ` Pierre Neidhardt
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a87d9b5d-29d6-d3f9-9431-c2256da448c0@riseup.net \
--to=swedebugia@riseup.net \
--cc=help-guix@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.