public inbox for
 help / color / mirror / Atom feed
From: Brian Inglis <>
Subject: Re: Is calm running or upset with me?
Date: Sun, 17 Jul 2022 16:25:42 -0600	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 2022-07-17 15:38, Brian Inglis wrote:
> On 2022-07-16 14:26, Jon Turney wrote:
>> On 16/07/2022 18:48, Brian Inglis wrote:
>>> Uploaded mingw/libidn packages, no emails, no change in setup.ini.
>> Thanks for pointing this out.  I'd managed to break the alert which 
>> tells me when calm stops :(
>> There was a problem with validating the value of the license: key, 
>> which was preventing this upload from happening.  I've fixed that and 
>> set it to be retried, which seems to have succeeded...
> Thanks very much Jon, calm failure and also then success messages 
> received, and evything now looking more normal.
> Chill out and stay cool over there! ;^>

Hi folks,

Could we maybe turn down the licence messages 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.

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.]

  reply	other threads:[~2022-07-17 22:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-16 17:48 Brian Inglis
2022-07-16 20:26 ` Jon Turney
2022-07-17 21:38   ` Brian Inglis
2022-07-17 22:25     ` Brian Inglis [this message]
2022-07-18 16:21     ` calm 'license key' upload failures and cygport requirements Brian Inglis

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