From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27041 invoked by alias); 1 Jun 2004 15:29:33 -0000 Mailing-List: contact overseers-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: , Sender: overseers-owner@sources.redhat.com Received: (qmail 27025 invoked from network); 1 Jun 2004 15:29:31 -0000 Received: from unknown (HELO yosemite.airs.com) (209.128.65.135) by sourceware.org with SMTP; 1 Jun 2004 15:29:31 -0000 Received: (qmail 12625 invoked by uid 10); 1 Jun 2004 15:29:31 -0000 Received: (qmail 26530 invoked by uid 500); 1 Jun 2004 15:29:21 -0000 From: Ian Lance Taylor To: Volker Reichelt Cc: overseers@gcc.gnu.org, gcc@gcc.gnu.org Subject: Re: Trouble with rsync-access References: <200406011512.i51FCCKp005530@relay.rwth-aachen.de> Date: Tue, 01 Jun 2004 15:57:00 -0000 In-Reply-To: <200406011512.i51FCCKp005530@relay.rwth-aachen.de> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2004-q2/txt/msg00466.txt.bz2 Volker Reichelt 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