public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>,
	Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
Subject: Re: Cygwin Mailing Lists Disabled? Blocking Package Uploads?
Date: Sun, 2 Oct 2022 21:37:47 +0100	[thread overview]
Message-ID: <6ad4f959-85d5-65f9-f412-853aeb4df46e@dronecode.org.uk> (raw)
In-Reply-To: <c10c9dde-024f-1def-5c3f-0a6a704e9cc7@SystematicSw.ab.ca>

On 02/10/2022 19:13, Brian Inglis wrote:
> On 2022-10-02 05:20, Jon Turney wrote:
>> On 02/10/2022 08:23, Brian Inglis wrote:
>>> Also I don't seem to be able to get on to any mailing list interface 
>>> to re-enable email to perhaps check status via email in public inbox.
>>
>> I don't understand what this means.
> 
> Email retries are often visible under Sourceware Public Inbox e.g.
> 
> https://inbox.sourceware.org/cygwin-apps/202209252042.28PJfcQU021984-28PKg7eC017324-6W6R+pMrZmcI6pMNW8xKTw@public.gmane.org/T/#u

It was unintentional that email bounces were ending up there, and has 
been fixed.

> Any chance of maybe just appending to an mbox cleared after 24 hours old?

It would probably just be easier to arrange for upload reports to go to 
a new mailing list, if we that something that is really wanted...

> I keep having to comment out LICENSE after updates to the latest SPDX 
> keys, as it seems to block uploads!

The current situation is that a 'license:' key is not required in the 
package hint, but if present, it's value must validate.

If you're having problems, please give an example of a something you 
think is a valid SPDX license expression, but isn't accepted.

> What are you using to validate licences in calm - PyPi spdx-tools?

I'm using license_expression

(See https://github.com/nexB/license-expression)

> Finally, do you have any advice on what to do about various US Public 
> Domain sources like tz{code,data} about which SPDX.org is still having 
> discussions?
> I have submitted input asking them to add a tz/tzdb/zoneinfo PD licence 
> instance, and/or also something for other generic US.gov PD sources, 
> like they currently have for NIST, CC, Open Data Commons, Sax, and 
> libselinux.
> But they closed an issue from a US.gov entity asking for a generic 
> US.gov PD licence for their documents!
For our purposes, you may use the string 'Public-Domain', in cases where 
no license applies because the material has been placed in the public 
domain.

  reply	other threads:[~2022-10-02 20:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-02  7:23 Brian Inglis
2022-10-02 11:20 ` Jon Turney
2022-10-02 18:13   ` Brian Inglis
2022-10-02 20:37     ` Jon Turney [this message]
2022-10-03 15:55       ` 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:
  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=6ad4f959-85d5-65f9-f412-853aeb4df46e@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=Brian.Inglis@SystematicSw.ab.ca \
    --cc=cygwin-apps@cygwin.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).