erroneous cvs checksum failures?

[Stephen Degler]

Hello,

 

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.

 

The server is indicating 0 length patch and the client's checksum
differs due to keyword expansion.  I believe that the repository was put
in this state from a developer manually copying a version from a branch
and commtting it to the head.  The keywords stored in the text of the
revision in the repository do not match either the current revision or
the previous one (they reflect the revision of the branch).

 

On the client side of things, I see the message at line 1621 of client.c
with version 1.12.9.

Is there a bug in the server or client handling of this case?  And is it
the problem the handling of the commit or the subsequent update?

 

Please CC me as I'm not subscribed to the list.

 

Thanks,

skd