public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
Cc: cygwin-apps@cygwin.com
Subject: Re: package uploads not being processed again - calm failed or stuck?
Date: Sun, 14 Apr 2024 22:10:49 +0100	[thread overview]
Message-ID: <ab3bc77b-4a99-4055-abc6-7ab6b24a57aa@dronecode.org.uk> (raw)
In-Reply-To: <39c0924a-9abc-4311-83ab-62cd99a8e4b5@SystematicSW.ab.ca>

On 14/04/2024 22:01, Brian Inglis via Cygwin-apps wrote:
> On 2024-04-14 13:53, Brian Inglis via Cygwin-apps wrote:
>> Not seeing any progress hours after package upload - master setup.ini 
>> not updated and no calm emails received - has calm failed or is it stuck?
>>
>> `ssh` commands /help/, /alive/, /info/ work okay - could do with a 
>> /status/ command to show us what calm is doing!

Sorry, this isn't going to happen for various reasons.

>> Achim - none of your announced releases appear to have been processed 
>> yet!
> 
> Thanks to whoever got the process going again a half hour ago!
> I could see from curl -I the setup.ini last-modified date updated.

No problem.  sourceware overseers have re-arranged things so it won't be 
automatically killed by systemd for lols, and I am assured it should 
carry on running now...

Some emails reporting uploads that had been processed have been lost 
during the confusion.

We apologize for the inconvenience.


  reply	other threads:[~2024-04-14 21:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-14 19:53 Brian Inglis
2024-04-14 21:01 ` Brian Inglis
2024-04-14 21:10   ` Jon Turney [this message]
2024-04-14 21:39     ` 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=ab3bc77b-4a99-4055-abc6-7ab6b24a57aa@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).