guix time-machine does not have a verbosity option

  • Open
  • quality assurance status badge
Details
3 participants
  • Greg Hogan
  • Richard Sent
  • Simon Tournier
Owner
unassigned
Submitted by
Richard Sent
Severity
wishlist
R
R
Richard Sent wrote on 31 May 23:42 +0200
(address . bug-guix@gnu.org)
87r0dh8xpo.fsf@freakingpenguin.com
Hi Guix!

guix time-machine does not have a verbosity option.

Toggle snippet (4 lines)
~/code/projects/srht-readme $ guix time-machine -q --verbosity 0 -- describe
guix time-machine: error: verbosity: unrecognized option

This is unfortunate because it hurts it's usability as part of a CI
system. Pipelines using time-machine are filled with excess logging
messages that aren't always needed and can't be disabled unless output
redirection is available.

--
Take it easy,
Richard Sent
Making my computer weirder one commit at a time.
G
G
Greg Hogan wrote on 25 Jul 17:44 +0200
(name . Richard Sent)(address . richard@freakingpenguin.com)(address . 71297@debbugs.gnu.org)
CA+3U0ZkECm7nwaWC+VpBT-qj2BQxW_dd8aJP7h-_O7bJwGtEiQ@mail.gmail.com
On Fri, May 31, 2024 at 5:44?PM Richard Sent
<richard@freakingpenguin.com> wrote:
Toggle quote (15 lines)
>
> Hi Guix!
>
> guix time-machine does not have a verbosity option.
>
> --8<---------------cut here---------------start------------->8---
> ~/code/projects/srht-readme $ guix time-machine -q --verbosity 0 -- describe
> guix time-machine: error: verbosity: unrecognized option
> --8<---------------cut here---------------end--------------->8---
>
> This is unfortunate because it hurts it's usability as part of a CI
> system. Pipelines using time-machine are filled with excess logging
> messages that aren't always needed and can't be disabled unless output
> redirection is available.

This is also an annoyance when one has set verbosity in the
environment variable GUIX_BUILD_OPTIONS.
S
S
Simon Tournier wrote on 29 Aug 18:34 +0200
control message for bug #71297
(address . control@debbugs.gnu.org)
87frqnthie.fsf@gmail.com
severity 71297 wishlist
quit
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 71297@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 71297
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch