From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23520 invoked by alias); 17 Dec 2001 18:02:39 -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 23483 invoked from network); 17 Dec 2001 18:02:34 -0000 To: angela@releasedominatrix.com Cc: overseers@gcc.gnu.org Subject: Re: cvs cache corrupt again References: <20011217173740.EE3831D2F@dragaera.ReleaseDominatrix.com> From: Ian Lance Taylor Date: Fri, 09 Nov 2001 12:49:00 -0000 In-Reply-To: <20011217173740.EE3831D2F@dragaera.ReleaseDominatrix.com> Message-ID: User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2001-q4/txt/msg00200.txt.bz2 Angela Marie Thomas writes: > > cvs [server aborted]: head attribute does not match file for `/cvs/gcc/gcc/gc > c/ChangeLog,v' > > I was told once that this happened when non-fileattr-aware versions of > cvs were used to make commits. If that's the case, this will happen a > lot (which it seems to). I can't think of any reason why the client would > have to know about it, so maybe it's a bug? > > Chris, when you were looking at the local hacks, did you notice anything > that would indicate the client needed support for fileattr as well? The client doesn't need to know about the fileattrs patch. Only the CVS which is modifying the actual repository. This problem can happen if a commit is interrupted at the wrong time, or more generally if the commit fails for some reason at the wrong time. Ian From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Lance Taylor To: angela@releasedominatrix.com Cc: overseers@gcc.gnu.org Subject: Re: cvs cache corrupt again Date: Mon, 17 Dec 2001 10:02:00 -0000 Message-ID: References: <20011217173740.EE3831D2F@dragaera.ReleaseDominatrix.com> X-SW-Source: 2001-q4/msg00425.html Message-ID: <20011217100200.Wk_YCdlSHuo8TdWcOoLQKGCJu7t98DPcIVw37dcyZ0A@z> Angela Marie Thomas writes: > > cvs [server aborted]: head attribute does not match file for `/cvs/gcc/gcc/gc > c/ChangeLog,v' > > I was told once that this happened when non-fileattr-aware versions of > cvs were used to make commits. If that's the case, this will happen a > lot (which it seems to). I can't think of any reason why the client would > have to know about it, so maybe it's a bug? > > Chris, when you were looking at the local hacks, did you notice anything > that would indicate the client needed support for fileattr as well? The client doesn't need to know about the fileattrs patch. Only the CVS which is modifying the actual repository. This problem can happen if a commit is interrupted at the wrong time, or more generally if the commit fails for some reason at the wrong time. Ian