[cvsnt] BUG: Corrupted binary files

[Kevin]

Actually it was manifested in a strange way:

My collegue had a working copy in sync with the repository. I checked out
the same branch and some binary files were not working. After some
investigation we discovered that his working copy had the same revision
numbers but the file contents were different.

By the way the files we are dealing with were *removed* on the HEAD version
but are still alive on the branch.

I can hand you a problematic file that you may take a look at and the
'original' file that was committed, should I attach it to the mailing list?
The file at the tip of the branch is not the same as the committed file.



P.S. The related thread was "[cvsnt] Alert: Binary files are corrupted when
you do a cvs remove", I did not see it before! (Thanks Bo for pointing it
out).

--
Kevin Agius

"Tony Hoyle" <tmh at nodomain.org> wrote in message
news:d8mb9n$tk$1 at paris.nodomain.org...
> Kevin wrote:
>
> > Tony, do you recall fixing this problem?  The history page mentions "Fix
> > problem with deleting then resurrecting binary files" in build 1969 (the
> > stable version that I am using); can this be related?
>
> Doesn't sound related.
>
> Lots of people use binary files all the time without issue.  The problem
> that was found before related to a relatively infrequent usage pattern,
> where they were deleted then resurrected.
>
> Can you tell us exactly what you were doing to cause the problem?
>
> Tony