From: Loic Dachary <loic@gnu.org>
To: Jeff Bailey <jbailey@nisa.net>
Cc: Mathieu Roy <yeupou@gnu.org>,
Brad Lucier <lucier@math.purdue.edu>,
system-hackers@gnu.org, savannah-hackers@gnu.org,
dje@watson.ibm.com, gcc@gcc.gnu.org
Subject: Re: subversions.gnu.org not being updated (fwd)
Date: Sun, 13 Oct 2002 11:23:00 -0000 [thread overview]
Message-ID: <15785.16858.79802.232483@gargle.gargle.HOWL> (raw)
In-Reply-To: Jeff Bailey's message of 11 October 2002 09:05:45 -0700
> > > David Edelsohn believes that you should be notified if there's
> > > a problem with subversion.gnu.org not updating its cvs
> > > directories from gcc.gnu.org. In fact, this doesn't seem to
> > > have been done for about two days for the mainline development
> > > version of gcc.
That is correct. Here is the source of the problem:
unknown host: sourceware.cygnus.com
The mirroring command line is:
rsync --archive --delete --checksum --compress rsync://sourceware.cygnus.com/gcc-cvs /home/rsync/gcc
(in the rsync user crontab on subversions.gnu.org)
and should be changed to accomodate the fact that the domain
name is no longer valid.
Any suggestion ? Help from gcc people on the best way to fix this ?
--
Loic Dachary http://www.dachary.org/ loic@dachary.org
12 bd Magenta http://www.senga.org/ loic@senga.org
75010 Paris T: 33 1 42 45 07 97 loic@gnu.org
GPG Public Key: http://www.dachary.org/loic/gpg.txt
next prev parent reply other threads:[~2002-10-13 9:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-10 13:25 Brad Lucier
2002-10-11 5:04 ` Mathieu Roy
2002-10-11 10:01 ` Jeff Bailey
2002-10-13 11:23 ` Loic Dachary [this message]
2002-10-13 12:30 ` Fergus Henderson
2002-10-13 14:00 ` Loic Dachary
2002-10-15 14:51 ` Gerald Pfeifer
2002-10-15 17:49 ` Joseph S. Myers
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=15785.16858.79802.232483@gargle.gargle.HOWL \
--to=loic@gnu.org \
--cc=dje@watson.ibm.com \
--cc=gcc@gcc.gnu.org \
--cc=jbailey@nisa.net \
--cc=lucier@math.purdue.edu \
--cc=savannah-hackers@gnu.org \
--cc=system-hackers@gnu.org \
--cc=yeupou@gnu.org \
/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).