From: Stephen John Smoogen <smooge@gmail.com>
To: Takashi Yano <takashi.yano@nifty.ne.jp>
Cc: cygwin@cygwin.com
Subject: Re: I can no longer access newlib-cygwin.git via http.
Date: Thu, 12 Mar 2020 11:03:20 -0400 [thread overview]
Message-ID: <CANnLRdgX9ToTnL6BwzAC71ovFctRC4RkKG2=O-y4k5sMX7dSZw@mail.gmail.com> (raw)
In-Reply-To: <20200312212953.0fe1f53c4130b0c1e3529e7d@nifty.ne.jp>
On Thu, 12 Mar 2020 at 10:22, Takashi Yano via Cygwin <cygwin@cygwin.com>
wrote:
> On Thu, 12 Mar 2020 12:51:06 +0100
> Corinna Vinschen wrote:
> > > Is there any possibility that http access will be restored?
> >
> > I don't think so, http is a no-no these days. Just change over
> > to https, you can easily fix that in .git/config.
>
> https access also fails.
> git clone https://cygwin.com/git/newlib-cygwin.git
> Cloning into 'newlib-cygwin'...
> fatal: repository 'https://cygwin.com/git/newlib-cygwin.git/' not found
>
> Is there any mistake?
>
It turns out that this is due as part of a move on the server that Cygwin
and other Sourceware groups are on. It is being moved to a new datacenter
and hardware. They are in the process of getting various other services
going and it will take several days/weeks until everything is back. At the
moment they only have git available via git: protocol
I think there is a mirror on github of cygwin which you could use at this
time.
--
Stephen J Smoogen.
prev parent reply other threads:[~2020-03-12 15:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 11:15 Takashi Yano
2020-03-12 11:51 ` Corinna Vinschen
2020-03-12 12:29 ` Takashi Yano
2020-03-12 13:01 ` Corinna Vinschen
2020-03-12 13:30 ` Takashi Yano
2020-03-12 15:03 ` Stephen John Smoogen [this message]
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='CANnLRdgX9ToTnL6BwzAC71ovFctRC4RkKG2=O-y4k5sMX7dSZw@mail.gmail.com' \
--to=smooge@gmail.com \
--cc=cygwin@cygwin.com \
--cc=takashi.yano@nifty.ne.jp \
/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).