This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Trouble with rsync-access
- From: Ian Lance Taylor <ian at wasabisystems dot com>
- To: Volker Reichelt <reichelt at igpm dot rwth-aachen dot de>
- Cc: overseers at gcc dot gnu dot org, gcc at gcc dot gnu dot org
- Date: 01 Jun 2004 11:29:21 -0400
- Subject: Re: Trouble with rsync-access
- References: <200406011512.i51FCCKp005530@relay.rwth-aachen.de>
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.
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.
Ian