From mboxrd@z Thu Jan 1 00:00:00 1970 From: swedebugia@riseup.net Subject: bug#33673: "guix system --help" does not detail how to use --on-error=strategy Date: Sat, 08 Dec 2018 00:30:54 -0800 Message-ID: <2a004926090617e0227252136dc35dab@riseup.net> References: <87pnuccuk2.fsf@gmail.com> <74aa65394c92165fbf4c2f777099eab3@riseup.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:51545) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gVY1u-00070u-Ul for bug-guix@gnu.org; Sat, 08 Dec 2018 03:32:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gVY1q-0002WN-EX for bug-guix@gnu.org; Sat, 08 Dec 2018 03:32:06 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:33315) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gVY1q-0002WG-Aj for bug-guix@gnu.org; Sat, 08 Dec 2018 03:32:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gVY1q-0002Tp-79 for bug-guix@gnu.org; Sat, 08 Dec 2018 03:32:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: Received: from eggs.gnu.org ([2001:4830:134:3::10]:51375) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gVY0q-0006x5-30 for bug-guix@gnu.org; Sat, 08 Dec 2018 03:31:00 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gVY0l-0001wr-Qq for bug-guix@gnu.org; Sat, 08 Dec 2018 03:31:00 -0500 Received: from mx1.riseup.net ([198.252.153.129]:36001) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gVY0l-0001wP-Jh for bug-guix@gnu.org; Sat, 08 Dec 2018 03:30:55 -0500 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 95B361A046C for ; Sat, 8 Dec 2018 00:30:54 -0800 (PST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by cotinga.riseup.net with ESMTPSA id 545DBE9AAE for ; Sat, 8 Dec 2018 00:30:54 -0800 (PST) In-Reply-To: <74aa65394c92165fbf4c2f777099eab3@riseup.net> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: 33673@debbugs.gnu.org Hi The current output is: --on-error=STRATEGY apply STRATEGY when an error occurs while reading FILE Also the manual currently lacks a cindex for on-error (I had to search with 's' through multiple false positives to find the relevant section) Additionally we now have so many commands in the help pages of guix system and guix build that it would be nice to present them in a more readable/categorized way. Would a patches for improvement in these areas be accepted? -- Cheers Swedebugia -------- Original Message -------- Subject: Re: error: rmdir: Device or resource busy Date: 2018-12-08 09:24 From: swedebugia@riseup.net To: Fredrik Salomonsson Cc: help-guix , Help-Guix Hej! On 2018-12-08 09:05, Fredrik Salomonsson wrote: > Hello, > > tried installing GuixSD 0.16. But hitting a cryptic error. > > guix system init /mnt/etc/config.scm /mnt > --substitute-urls="http://berlin.guixsd.org http://mirror.hydra.gnu.org" > ... > /gnu/store/sh9x3mhl5q60yxhl861kpk6vm70l3w81-bootloader-installer > > initializing operating system under '/mnt'... > guix system: error: rmdir: Device or resource busy > > This was working fine with 0.15. > > Is there a way to get a better backtrace from system init? Yes! >From the manual: '--on-error=STRATEGY' Apply STRATEGY when an error occurs when reading FILE. STRATEGY may be one of the following: 'nothing-special' Report the error concisely and exit. This is the default strategy. 'backtrace' Likewise, but also display a backtrace. 'debug' Report the error and enter Guile's debugger. From there, you can run commands such as ',bt' to get a backtrace, ',locals' to display local variable values, and more generally inspect the state of the program. *Note (guile)Debug Commands::, for a list of available debugging commands. Actually the --help to "guix system" hints about this but it is not telling how to use it, which is a bug I think. (i'm going to report it and send a patch) > Or does anyone > know what the error might be? I never saw it before.