From: Volker Reichelt <reichelt@igpm.rwth-aachen.de>
To: ian@wasabisystems.com
Cc: overseers@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: Trouble with rsync-access
Date: Tue, 01 Jun 2004 21:28:00 -0000 [thread overview]
Message-ID: <200406011552.i51FqvKp010933@relay.rwth-aachen.de> (raw)
On 1 Jun, Ian Lance Taylor wrote:
> Volker Reichelt <reichelt@igpm.rwth-aachen.de> writes:
>
>> since a couple of days rsync-access to the gcc sources doesn't
>> work as it used to. Rsyncing my local archive and then checking
>> out from there results in an error message:
>>
>> cvs checkout: Updating gcc
>> cvs [checkout aborted]: cannot stat /sourceware/cvs-lockdir/gcc:
>> No such file or directory
>>
>> The culprit seems to be the line
>>
>> LockDir=/sourceware/cvs-lockdir/gcc
>>
>> which got added to CVSROOT/config recently:
>>
>> date 2004.05.30.01.29.28; author root; state Exp;
>>
>> After deleting this line manually, the check-out works fine.
>> But that's only a work-around since the next rsync will break things again.
>>
>> Can the change be reverted or be worked around in some other way?
>
> We made that change intentionally. I don't know that we have ever
> promised that you can rsync our CVS repository and then use it
> locally. It's great if it works, but I don't think we're going to
> accept responsibility for having it always work.
Well, but it is desirable to make it work as rsync.html states:
In an ongoing effort to accelerate development of GCC and provide an open development
environment, we are offering our CVS repository and various other data through anonymous
rsync access.
That way you can make local copies of the GCC CVS repository to ease the burden on the
GCC main site, and browse the source locally using cvs.
So, making rsync difficult to use seems to be counter-productive, since
it puts more load on GCC's CVS.
In addition bugs/reghunt.html states:
Using rsync to get a local copy of the GCC CVS repository is highly recommended for
regression hunts. You'll be checking out the tree used for the regression search over
and over again and won't want to affect access times for other GCC developers
who are using the real repository, and it will also be faster for you.
That's why I would appreciate rsync-access to be as easy as possible.
However, if there's no chance of going back to the old version we should
at least document the new behavior in rsync.html.
> That said, you can make it continue to work in a straightforward
> manner by creating the directory /sourceware/cvs-lockdir/gcc on your
> system, possibly using symlinks.
Not everybody has write permissions outside his/her home directory :-(
(I'll have to use a shell script that does the patching after the
rsync.)
> Ian
Regards,
Volker
next reply other threads:[~2004-06-01 15:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-01 21:28 Volker Reichelt [this message]
2004-06-01 21:46 ` Christopher Faylor
2004-06-01 23:40 ` Alexandre Oliva
2004-06-03 12:33 ` Marc Espie
2004-06-04 16:21 ` Ian Lance Taylor
-- strict thread matches above, loose matches on Subject: below --
2004-06-02 14:19 Volker Reichelt
2004-06-01 15:48 Volker Reichelt
2004-06-01 15:57 ` Ian Lance Taylor
2004-06-01 17:17 ` Frank Ch. Eigler
2004-06-01 20:23 ` Andreas Schwab
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=200406011552.i51FqvKp010933@relay.rwth-aachen.de \
--to=reichelt@igpm.rwth-aachen.de \
--cc=gcc@gcc.gnu.org \
--cc=ian@wasabisystems.com \
--cc=overseers@gcc.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).