Re: erroneous cvs checksum failures?

[Larry Jones]

Stephen Degler writes:
> 
> I see the following problem, I'm not sure what to do (if anything) about
> it.  If there is a new revision of foo.c created with no diffs from the
> previous version, cvs update reports "checksum failure after patch to
> foo.c, will refetch" on a subsequent cvs update to a tree where foo.c is
> at the lower revision.  It also gives "cvs update: warning: `foo.c' was
> lost.", which is a disturbing message to see even if the results are
> innocuous.

I've tried everything I can think of to reproduce this problem and have
not succeeded.  The only thing I know of that will cause a patch
checksum failure is a user managing to update the working copy of a file
without changing its modification time, leading CVS to think it's
unmodified.  If you can provide an exact series of steps to reproduce
the problem, we'll be glad to look into it.  (Also, please let us know
exactly what version(s) of CVS you're using and whether you're using a
local repository or client/server mode.)

-Larry Jones

Everybody's a slave to routine. -- Calvin