all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
	24083-done@debbugs.gnu.org, zimoun <zimon.toutoune@gmail.com>
Subject: bug#24083: guix lint doesn't actually fail on some errors
Date: Fri, 31 Mar 2023 12:57:12 -0400	[thread overview]
Message-ID: <87edp4x3iv.fsf@gmail.com> (raw)
In-Reply-To: <20210713122021.258f00f7@scratchpost.org> (Danny Milosavljevic's message of "Tue, 13 Jul 2021 12:20:21 +0200")

Hi,

Danny Milosavljevic <dannym@scratchpost.org> writes:

> On Tue, 13 Jul 2021 11:05:49 +0200
> zimoun <zimon.toutoune@gmail.com> wrote:
>
>> On Wed, 27 Jul 2016 at 22:57, ludo@gnu.org (Ludovic Courtès) wrote:
>> > Danny Milosavljevic <dannym@scratchpost.org> skribis:
>> >  
>> >> guix lint doesn't actually fail on some errors.  
>> >
>> > It never pretended to exit with non-zero when warnings are emitted.  :-)
>> > (These are warnings, not errors.)  
>
> Sure, it makes sense.  I'm just doing " |wc -l" now.
>
>> Because of that, I propose to close without modifying the returned code.
>> WDYT?
>
> Agreed.
>
> But I would suggest to document in the manual that the exit status is
> not set,  though.

Acting on the proposed and agreed closing action :-).

-- 
Thanks,
Maxim




      reply	other threads:[~2023-03-31 16:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-26 22:25 bug#24083: guix lint doesn't actually fail on some errors Danny Milosavljevic
2016-07-27 20:57 ` Ludovic Courtès
2016-07-27 21:12   ` Danny Milosavljevic
2021-03-24 22:19     ` zimoun
2021-06-09 21:41   ` zimoun
2021-07-13  9:05   ` zimoun
2021-07-13 10:20     ` Danny Milosavljevic
2023-03-31 16:57       ` Maxim Cournoyer [this message]

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=87edp4x3iv.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=24083-done@debbugs.gnu.org \
    --cc=dannym@scratchpost.org \
    --cc=ludo@gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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.