Re: Problems with update -C

[Jim Hyslop]

Mark E. Hamilton wrote:
> Hi,
>
> We're having some odd problems with 'cvs update -C'; it reports as 
> locally modified (and hence backs up) files that are not modified in the 
> working directory. If I diff the '.#' backup of the file with the 
> version updated from the repository there area no differences. 
> (Additionally, I had done a 'cvs -qn update' in the same working 
> directory just prior to the update that had this error, and no files 
> were reported as being out-of-date.)
>
> It also reports as locally modified files that were updated in a 
> previous commit, even though they were not modified in the working 
> directory either. (They were committed from somewhere else.)

This sounds like something might have changed the timestamp of the file, 
without changing the contents. If this happens again, compare the 
timestamp on the file with the timestamp stored in CVS/Entries. A simple 
"cvs update" usually sets everything right.

--
Jim