Re: problem with cvs

> I'm looking into this, but it would be easier if I could reproduce the
> error case consistently.  I'm guessing this isn't possible due to the
> fact that you can recommit your changes without encountering the error.
> If you know how to reproduce the case consistently, please let me know.

I agree it doesn't seem easy to reproduce the problem. I can, however, 
explain better the context: this happens only when I do a very large
commit, with many files. In that case the commit takes a lot of time, at
least 10/15 minutes.

> Meanwhile, I will attempt to copy the repository, back out your changes
> from the copy, and reproduce the problem with your commit.

I fear you won't be able to reproduce the bug easily. My guess (but I 
may be wrong) is that it happens because there is a race condition 
somewhere. If you can't reproduce it, and if you still want to debug it, 
maybe we could set up a virtual project such that I can test massive 
and controlled commits ?

Another information: here is my client version:

[dumas@zeus texi2html]$ cvs --version

Concurrent Versions System (CVS) 1.11.2 (client/server)

Pat