From mboxrd@z Thu Jan 1 00:00:00 1970 From: swedebugia Subject: Re: guix fail to reconfigure the system Date: Mon, 30 Apr 2018 12:44:38 +0200 Message-ID: References: <877eov2pqj.fsf@gmx.com> <87tvrzow3s.fsf@gnu.org> <87tvrzq946.fsf@gmx.com> <87h8nyc2g0.fsf@lassieur.org> <87bme6ejy2.fsf@gmail.com> <87604d2sxi.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="------------4FBA73D2E97ECB57F99A1AFD" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:54951) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fD6Fz-00066a-D9 for help-guix@gnu.org; Mon, 30 Apr 2018 06:42:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fD6Fw-0000m5-2y for help-guix@gnu.org; Mon, 30 Apr 2018 06:42:07 -0400 Received: from mx1.riseup.net ([198.252.153.129]:57200) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fD6Fv-0000ko-N4 for help-guix@gnu.org; Mon, 30 Apr 2018 06:42:04 -0400 Received: from cotinga.riseup.net (cotinga-pn.riseup.net [10.0.1.164]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.riseup.net (Postfix) with ESMTPS id D40531A0906 for ; Mon, 30 Apr 2018 03:42:01 -0700 (PDT) Received: from [127.0.0.1] (localhost [127.0.0.1]) by cotinga.riseup.net with ESMTPSA id 47FDFA7001 for ; Mon, 30 Apr 2018 03:42:01 -0700 (PDT) In-Reply-To: <87604d2sxi.fsf@gmail.com> Content-Language: sv-FI List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: help-guix@gnu.org This is a multi-part message in MIME format. --------------4FBA73D2E97ECB57F99A1AFD Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hi On 2018-04-27 06:07, Chris Marusich wrote: > Pierre Neidhardt 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 --------------4FBA73D2E97ECB57F99A1AFD Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit 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

--------------4FBA73D2E97ECB57F99A1AFD--