From: "Buchbinder, Barry (NIH/NIAID) [E]" <BBuchbinder@niaid.nih.gov>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: something is wrong with cygwin's mirror checker
Date: Wed, 13 Nov 2013 23:20:00 -0000 [thread overview]
Message-ID: <6CF2FC1279D0844C9357664DC5A08BA21B66C1@MLBXV06.nih.gov> (raw)
In-Reply-To: <20131112182947.GA7911@ednor.casa.cgf.cx>
Christopher Faylor sent the following at Tuesday, November 12, 2013 1:30 PM
>On Tue, Nov 12, 2013 at 01:08:37PM -0500, Christopher Faylor wrote:
>>I don't know why but the mirror checker is screwed up. The last email I
>>got from the system said that the mirrors were in good shape but
>>http://cygwin.com/mirrors.html tells another story.
>>
>>Just a heads up. I'm investigating.
>
>Problem identified and (I hope) fixed. It will take a few hours for the
>system to correct itself so mirrors will be scarce until that happens.
This list has recovered a bit but is still very sparse.
It is probably just a coincidence, but my usual mirror,
<ftp://mirror.mcs.anl.gov/pub/cygwin/>, has disappeared, not just from
<http://cygwin.com/mirrors.html>, but when accessed directly with Firefox,
not setup. Usually it is very reliable. I doubt that there's anything
that you can do, but I wonder if anl.gov cannot find something that it is
looking for at the cygwin/sourceware end and that that has contributed to
this problem at anl.gov and at least some of the other mirrors.
Best wishes,
- Barry
Disclaimer: Statements made herein are not made on behalf of NIAID.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2013-11-13 23:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 18:08 Christopher Faylor
2013-11-12 18:29 ` Christopher Faylor
2013-11-13 23:20 ` Buchbinder, Barry (NIH/NIAID) [E] [this message]
2013-11-13 23:36 ` Wm. David Bentlage
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=6CF2FC1279D0844C9357664DC5A08BA21B66C1@MLBXV06.nih.gov \
--to=bbuchbinder@niaid.nih.gov \
--cc=cygwin@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).