public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: Cygwin Applications <cygwin-apps@cygwin.com>
Subject: Re: Cygwin Mailing Lists Disabled? Blocking Package Uploads?
Date: Sun, 2 Oct 2022 12:13:51 -0600	[thread overview]
Message-ID: <c10c9dde-024f-1def-5c3f-0a6a704e9cc7@SystematicSw.ab.ca> (raw)
In-Reply-To: <f294d33d-9509-65db-866f-f584e43bf679@dronecode.org.uk>

On 2022-10-02 05:20, Jon Turney wrote:
> On 02/10/2022 08:23, Brian Inglis wrote:
>> Hi folks,
>>
>> Tried uploading package cpuid with and without LICENSE.
>> Neither seems to work (checked master setup.ini).
> 
> It seems like I broke calm when I updated it a couple of days ago. :(
> 
> Thanks for pointing this out.
> 
> I've repaired it, and your upload seems to have succeeded.

Thanks Jon,

>> 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@mx1.webnames.ca/T/#u

and I am now also monitoring the Cygwin lists via Atom Feeds in Chromium 
Foxish RSS/Atom Feed reader extension.

>> Has the Cygwin mailing lists being disabled now blocking package uploads?
> 
> No.
> 
>> Can someone please see if they can have a look and give me some hints 
>> via DM.
>>
>> Are there any other ways I can see any issues with package uploads?
> 
> If your ISP is blocking email from sourceware, I can only suggest 
> getting a free webmail from somewhere else, and arranging for upload 
> reports be sent there as well (see [1]).

Thanks for that reminder, I've added Direct ISP and Gmail - hopefully 
one succeeds!

> I'd did think that it would be nice to add a "recent uploads" report to 
> the web pages, but I'm unlikely to have any time to work on that.
> 
> [1] https://cygwin.com/package-upload.html#reports

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

P.S.
I keep having to comment out LICENSE after updates to the latest SPDX 
keys, as it seems to block uploads!
What are you using to validate licences in calm - PyPi spdx-tools?

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!

-- 
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-10-02 18:13 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 [this message]
2022-10-02 20:37     ` Jon Turney
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=c10c9dde-024f-1def-5c3f-0a6a704e9cc7@SystematicSw.ab.ca \
    --to=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).