Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] utils/check-package: add a check for the new spacing convention
Date: Tue, 2 Jun 2020 23:24:25 +0200	[thread overview]
Message-ID: <20200602232425.57210c9c@windsurf.home> (raw)
In-Reply-To: <20200531204233.31866-1-heiko.thiery@gmail.com>

On Sun, 31 May 2020 22:42:31 +0200
Heiko Thiery <heiko.thiery@gmail.com> wrote:

> The seperation of the fields in the hash file should be 2 spaces for
> consistency.
> 
> Signed-off-by: Heiko Thiery <heiko.thiery@gmail.com>
> Cc: Yann E. MORIN <yann.morin.1998@free.fr>

I'm not sure how to proceed with this: it causes a huge number of
warnings, because there are many packages still not fixed.

So, two options:

 (1) We merge this and live for warnings for the next few weeks until
 all packages are fixed. The advantage is that people will notice that
 packages need to be fixed.

 (2) We wait until all packages are fixed, and then we merge the
 check-package change to make sure we don't regress on this.

I'm not sure which is best. Perhaps we need to do (2) for a little
while in order to reduce the number of warnings, and then go for (1) ?
I'm not sure.

In any case, I'm also getting some weird Python exceptions while
running "make check-package":

Traceback (most recent call last):
  File "./utils/check-package", line 194, in <module>
    __main__()
  File "./utils/check-package", line 177, in __main__
    nwarnings, nlines = check_file_using_lib(fname)
  File "./utils/check-package", line 146, in check_file_using_lib
    nwarnings += print_warnings(cf.check_line(lineno + 1, text))
  File "/home/thomas/projets/buildroot/utils/checkpackagelib/lib_hash.py", line 56, in check_line
    if not re.match("^{}  {}  {}.*$".format(htype, hexa, filename), text):
  File "/usr/lib64/python3.8/re.py", line 191, in match
    return _compile(pattern, flags).match(string)
  File "/usr/lib64/python3.8/re.py", line 304, in _compile
    p = sre_compile.compile(pattern, flags)
  File "/usr/lib64/python3.8/sre_compile.py", line 764, in compile
    p = sre_parse.parse(p, flags)
  File "/usr/lib64/python3.8/sre_parse.py", line 948, in parse
    p = _parse_sub(source, state, flags & SRE_FLAG_VERBOSE, 0)
  File "/usr/lib64/python3.8/sre_parse.py", line 443, in _parse_sub
    itemsappend(_parse(source, state, verbose, nested + 1,
  File "/usr/lib64/python3.8/sre_parse.py", line 671, in _parse
    raise source.error("multiple repeat",
re.error: multiple repeat at position 50
make: *** [Makefile:1203: check-package] Error 1


Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2020-06-02 21:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-31 20:42 [Buildroot] [PATCH v2 1/1] utils/check-package: add a check for the new spacing convention Heiko Thiery
2020-06-02 21:24 ` Thomas Petazzoni [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=20200602232425.57210c9c@windsurf.home \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox