From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from omta001.cacentral1.a.cloudfilter.net (omta001.cacentral1.a.cloudfilter.net [3.97.99.32]) by sourceware.org (Postfix) with ESMTPS id 490EE3858D38 for ; Mon, 3 Oct 2022 15:55:36 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 490EE3858D38 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=SystematicSw.ab.ca Authentication-Results: sourceware.org; spf=none smtp.mailfrom=systematicsw.ab.ca Received: from shw-obgw-4004a.ext.cloudfilter.net ([10.228.9.227]) by cmsmtp with ESMTP id fMM4o0u83S8WrfNn5oJ0ui; Mon, 03 Oct 2022 15:55:35 +0000 Received: from [10.0.0.5] ([184.64.124.72]) by cmsmtp with ESMTP id fNn5o4afrlQu6fNn5o4Uut; Mon, 03 Oct 2022 15:55:35 +0000 X-Authority-Analysis: v=2.4 cv=YfOuWidf c=1 sm=1 tr=0 ts=633b05f7 a=oHm12aVswOWz6TMtn9zYKg==:117 a=oHm12aVswOWz6TMtn9zYKg==:17 a=IkcTkHD0fZMA:10 a=CCpqsmhAAAAA:8 a=TSbVqHtbAAAA:8 a=NEAV23lmAAAA:8 a=24AZYWMyAAAA:8 a=uYT-Tk0qkVT609LjNaIA:9 a=QEXdDO2ut3YA:10 a=ul9cdbp4aOFLsgKbc677:22 a=NJcUIoPEKLAEIzHnl83t:22 a=bG88sKzkDEFeXWNnvthB:22 Message-ID: Date: Mon, 3 Oct 2022 09:55:35 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.13.1 From: Brian Inglis Subject: Re: Cygwin Mailing Lists Disabled? Blocking Package Uploads? Reply-To: Brian.Inglis@SystematicSw.ab.ca To: Cygwin Applications References: <6ad4f959-85d5-65f9-f412-853aeb4df46e@dronecode.org.uk> Content-Language: en-CA Organization: Systematic Software In-Reply-To: <6ad4f959-85d5-65f9-f412-853aeb4df46e@dronecode.org.uk> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4xfN4hbr4uEWS/rd/OwqCIK8w4ft3ZJwljdS4qOUtQgPnjgxsWeZt+iCAcKqcpMNlCFI9T7U6vG3jFhJan7jopyJ4UFWwJDbU5nb8J9I5nB9mkB/Zh3hig L0w5epzZ6NWxdouBHExFyKbgGqXFZKqYVaig00oArj8ylcJPoCBcLFn/U6mR44Cxk0wlDZ/6Q5OdPlHzbjeJAlhrYub06S1G2+A= X-Spam-Status: No, score=-1164.5 required=5.0 tests=BAYES_00,KAM_DMARC_STATUS,KAM_LAZY_DOMAIN_SECURITY,NICE_REPLY_A,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On 2022-10-02 14:37, Jon Turney wrote: > 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. Darn! ;^> >> 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... Wouldn't help me with Cygwin blocks ;^< Meant just append to a mbox file under ~ e.g. ~/.mbox? >> 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. These had to be commented out recently: ../fortune-mod/fortune-mod.cygport:#LICENSE=BSD-4-Clause ../unifont/unifont.cygport:#LICENSE="GPL-2.0-with-font-exception AND OFL-1.1" although after further checking, it should have been OR, and is now: LICENSE="(GPL-2.0-with-font-exception OR OFL-1.1) AND Public-Domain AND GPL-2.0-or-later" >> What are you using to validate licences in calm - PyPi spdx-tools? > > I'm using license_expression > > (See https://github.com/nexB/license-expression) Thanks - will see what I can do with that. >> 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. Great - will use. -- 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.]