cvs problems ...

[Dave Korn]

> -----Original Message-----
> From: gcc-owner On Behalf Of Zack Weinberg
> Sent: 08 October 2004 21:26

> Since it doesn't look like a fix for the underlying bug is coming in
> short order, I'd like to suggest a custom for ensuring that the
> repository gets restored to a usable state as fast as possible.
> 
> Whenever anyone does a merge of any kind, or hits ^C on a commit
> operation, they should IMMEDIATELY AFTERWARD perform a cvs update from
> a separate checkout of the trunk.  If this fails, they should
> immediately notify overseers

  Think that's a good idea.  In fact, it's always a good idea to do an
update after a commit, and preferably a rebuild (and even re-test) if
possible, since CVS commits aren't atomic and there's always the danger of
some kind of collision.  It's good to verify that what ended up in the
repository actually matches what you were trying to put in there!

> Fixing CVS requires shell access to gcc.gnu.org/sources.redhat.com and
> write privileges on the repository that's busted.  I will outline what
> one does, but caution everyone that this is fiddly and somewhat
> dangerous - if you're not confident that you will not clobber the
> wrong files, please leave it to the sysadmins.

  I think this could be a good job for a bot/script:

> The error message indicates the directory with a broken fileattr
> cache, e.g.
> 
> > > cvs [update aborted]: branch attribute does not match file 
> > > for `/cvs/gcc/gcc/boehm-gc/NT_STATIC_THREADS_MAKEFILE,v'
> 
> The specific ,v file is irrelevant - it's just the first file that CVS
> tried to access in the directory with the bad cache.  What you do when
> you see this is
> 
> sourceware $ cd /cvs/gcc/gcc/boehm-gc
> sourceware $ : > CVS/fileattr

  How about setting up a script, and a mail-alias that forwards to it, so
that anyone who gets one of those error messages can email it in, and the
script will parse out the directory path and fix up the fileattr
automagically?  [Naturally there are security issues to consider, but it
should be entirely possible to do in a robust fashion].

    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....