GNU bug report logs - #63036
-v or --verbose CLI argument input is undocumented in the CLI

Previous Next

Package: guix;

Reported by: "jgart" <jgart <at> dismail.de>

Date: Sun, 23 Apr 2023 15:28:02 UTC

Severity: normal

To reply to this bug, email your comments to 63036 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-guix <at> gnu.org:
bug#63036; Package guix. (Sun, 23 Apr 2023 15:28:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to "jgart" <jgart <at> dismail.de>:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Sun, 23 Apr 2023 15:28:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: "jgart" <jgart <at> dismail.de>
To: bug-guix <at> gnu.org
Subject: -v or --verbose CLI argument input is undocumented in the CLI
Date: Sun, 23 Apr 2023 15:27:36 +0000
User story:

jgart tries to build a currently broken Python music package:

$ guix build -v 6 music21

Hmmm, what is the allowed input range for -v/--verbosity command line flag?

$ guix build --help
-v, --verbosity=LEVEL  use the given verbosity LEVEL

Hmmm, what is the type and/or range of inputs that are valid for LEVEL? 

Darn, I have to go find what the underlying implementation function takes as a valid verbosity level in the source code instead of just reading the documentation output of `guix build --help`. 

...but I just want to know everything that I need to know from just using the CLI and its help system as the user.

jgart adds TODO to document the valid levels in the CLI verbosity option itself

jgart thinks but what if the help message on the valid levels is too long once added?

jgart goes to get ice cream




Information forwarded to bug-guix <at> gnu.org:
bug#63036; Package guix. (Thu, 27 Apr 2023 13:21:02 GMT) Full text and rfc822 format available.

Message #8 received at 63036 <at> debbugs.gnu.org (full text, mbox):

From: Simon Tournier <zimon.toutoune <at> gmail.com>
To: jgart <jgart <at> dismail.de>, 63036 <at> debbugs.gnu.org
Subject: Re: bug#63036: -v or --verbose CLI argument input is undocumented
 in the CLI
Date: Tue, 25 Apr 2023 14:36:24 +0200
[Message part 1 (text/plain, inline)]
Hi,

On Sun, 23 Apr 2023 at 15:27, "jgart" via Bug reports for GNU Guix <bug-guix <at> gnu.org> wrote:

> Hmmm, what is the type and/or range of inputs that are valid for
> LEVEL?

What about this patch?

[p.patch (text/x-diff, inline)]
diff --git a/guix/scripts/build.scm b/guix/scripts/build.scm
index 72a24f91ac..35cb888c3b 100644
--- a/guix/scripts/build.scm
+++ b/guix/scripts/build.scm
@@ -452,8 +452,10 @@ (define (show-help)
   -r, --root=FILE        make FILE a symlink to the result, and register it
                          as a garbage collector root"))
   (display (G_ "
-  -v, --verbosity=LEVEL  use the given verbosity LEVEL"))
-  (display (G_ "
+  -v, --verbosity=LEVEL  use the given verbosity LEVEL, range 0-3
+                         0 = no output, 1 = quiet, 2 = 1 + download URLs,
+                         3 = all on standard error"))
+    (display (G_ "
   -q, --quiet            do not show the build log"))
   (display (G_ "
       --log-file         return the log file names for the given derivations"))
[Message part 3 (text/plain, inline)]

Cheers,
simon

This bug report was last modified 2 years and 49 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.