public inbox for
help / color / mirror / Atom feed
From: Jon TURNEY <>
Subject: [calm - Cygwin server-side packaging maintenance script] branch master, updated. 20220704-6-g81315ae
Date: Sat, 16 Jul 2022 20:04:03 +0000 (GMT)	[thread overview]
Message-ID: <> (raw);h=81315aef01a137bce51f636d96c3066b5cb4bb0b

commit 81315aef01a137bce51f636d96c3066b5cb4bb0b
Author: Jon Turney <>
Date:   Sat Jul 16 20:50:20 2022 +0100

    Workaround unexpected exceptions from license_expression.validate()
      File "/home/cygwin/.local/lib/python3.6/site-packages/license_expression/", line 1214, in __init__
        'Invalid license key: the valid characters are: letters and '
    license_expression.ExpressionError: Invalid license key: the valid characters are: letters and numbers, underscore, dot, colon or hyphen signs and spaces: 'LGPLv3+/GPLv2+/GPLv3+/GFDLv1.3+'
    During handling of the above exception, another exception occurred:
      File "/home/cygwin/.local/lib/python3.6/site-packages/license_expression/", line 780, in validate
    AttributeError: 'ExpressionError' object has no attribute 'token_string'

 calm/ | 1 +
 1 file changed, 1 insertion(+)

diff --git a/calm/ b/calm/
index d464bbc..1e9d717 100755
--- a/calm/
+++ b/calm/
@@ -297,6 +297,7 @@ def hint_file_parse(fn, kind, strict=False):
                     # license must be a valid spdx license expression
                     if key == 'license' and licensing:
+                            licensing.parse(value, strict=True)
                             le = licensing.validate(value, strict=True)
                         except (license_expression.ExpressionParseError, license_expression.ExpressionError) as e:
                             errors.append('value for key %s not a valid license expression: %s' % (key, e))

                 reply	other threads:[~2022-07-16 20:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).