GNU bug report logs - #24083
guix lint doesn't actually fail on some errors

Previous Next

Package: guix;

Reported by: Danny Milosavljevic <dannym <at> scratchpost.org>

Date: Tue, 26 Jul 2016 22:26:01 UTC

Severity: normal

Tags: moreinfo

Done: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


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

From: zimoun <zimon.toutoune <at> gmail.com>
To: Danny Milosavljevic <dannym <at> scratchpost.org>
Cc: Ludovic Courtès <ludo <at> gnu.org>, 24083 <at> debbugs.gnu.org
Subject: Re: bug#24083: guix lint doesn't actually fail on some errors
Date: Wed, 24 Mar 2021 23:19:04 +0100
Hi,

On Wed, 27 Jul 2016 at 23:12, Danny Milosavljevic <dannym <at> scratchpost.org> wrote:
> On Wed, 27 Jul 2016 22:57:15 +0200 ludo <at> gnu.org (Ludovic Courtès) wrote:
>> Danny Milosavljevic <dannym <at> 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.)
>
> Too bad :)
>
> I wrote a little helper script which was supposed to prevent me from posting
> packages that don't build or lint. Then I found out that the lint actually
> doesn't fail on warnings. So now my script is only half as useful (the builder
> does fail on build error).
>
> It would be nice to have a way to also check the lint status.

The good news is that the initial example ’perl-io-socket-inet6’ now
does not report any linting error. :-)

Well, on the other side, it is still the same behaviour.

--8<---------------cut here---------------start------------->8---
$ guix lint julia ; echo $?
gnu/packages/julia.scm:301:0: julia <at> 1.5.3: line 301 is way too long (107 characters)
gnu/packages/julia.scm:303:0: julia <at> 1.5.3: line 303 is way too long (106 characters)
gnu/packages/julia.scm:226:13: julia <at> 1.5.3: can be upgraded to 1.6.0
gnu/packages/julia.scm:227:12: julia <at> 1.5.3: source not archived on Software Heritage
0
--8<---------------cut here---------------end--------------->8---

What do we do.  On one hand, «it never pretended to exit with non-zero
when warninf» and on the other hand it could be annoying.

Well, since it is 4 years and 34 weeks, I consider it is not a big deal
and so we can close.  WDYT?


All the best,
simon




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

Previous Next


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