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 12:20:51 +0100 [thread overview]
Message-ID: <f294d33d-9509-65db-866f-f584e43bf679@dronecode.org.uk> (raw)
In-Reply-To: <a24ac8d8-1e10-4b2b-83af-52b766dbdf6e@SystematicSw.ab.ca>
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.
> 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.
> 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]).
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
next prev parent reply other threads:[~2022-10-02 11:20 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 [this message]
2022-10-02 18:13 ` Brian Inglis
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=f294d33d-9509-65db-866f-f584e43bf679@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).