public inbox for
 help / color / mirror / Atom feed
From: Brian Inglis <>
Subject: calm 'license key' upload failures and cygport requirements
Date: Mon, 18 Jul 2022 10:21:59 -0600	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi folks,

Could we maybe turn the calm "license key" error messages causing 
failing uploads down to warnings for now, until we get a handle on what 
we need to change to make it valid and accurate!

It was not obvious to me that these messages were referring to the 
cygport script variable LICENSE value I provide for some packages.

I commented out the values for now, but had to re-package and re-upload 
the four package related builds, to release the upgrades.

As it is summer, and many of us will have other things to do in our free 
time, if in doubt, I will be commenting these out in future builds, to 
avoid redos, which will not improve licence traceability or support.
For the same reason, this may not be the best time to make these 
changes, or ask for the related support below. ;^>

Could we perhaps also provide either cygport prep integrated warnings 
about these LICENSE values, similar to DEPEND/BUILD_REQUIRES checks.

Perhaps cygport commands could be added like check-dep and 
check-license, and/or a standalone interface or spdx package built with 
the calm licence check.

A more comprehensive description of what is required and allowed to be 
specified would be appreciated over and above that linked in the page:

For example, I have some packages with alternate and/or multiple 
licences for different bits e.g.


Is it sufficient to just replace the slashes with spaces (and add 
quotes) for now, until we get a handle on what we need to change to make 
it valid and accurate?
Or do slashes have to be replaced with AND/OR/WITH operators to make 
valid expressions, or split for each subpackage, so each subpackage has 
an explicit valid SPDX licence expression?
Are parentheses also supported as in the specification?

I also normally set a LICENSE_SPDX variable with a value prefixed by the 
recommended SPDX-License-Identifier: tag, and also in a # script comment 
as recommended in the spec, as well as a LICENSE_URI variable with a 
list of the src/doc file names containing the licence text(s).

What are the expectations for the information provided in the variable?

Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

      parent reply	other threads:[~2022-07-18 16:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-16 17:48 Is calm running or upset with me? Brian Inglis
2022-07-16 20:26 ` Jon Turney
2022-07-17 21:38   ` Brian Inglis
2022-07-17 22:25     ` Brian Inglis
2022-07-18 16:21     ` Brian Inglis [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:

* 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).