[cvsnt] repeateable ,v file corruption in 2.02, 2.03

[Jean-Francois Lamy]

Contrary to what is claimed in my previous message, :pserver: fails in the 
same fashion as the other two protocols.

So we have no workaround...

jfl

"Jean-Francois Lamy" <jeanfrancois_lamy at videotron.ca> wrote in message 
news:efbtg0$18s$1 at paris.nodomain.org...
> Context:  We have found about 40 files (out of tens of thousands) for 
> which we can repeatably produce a corrupt ,v file.  One of them is 
> included as attachment. The problem occurs with :ext: and :local: 
> protocols, using cvs.exe shipped with the server.
>
> *** the problem does not occur with :pserver: ***
>
> Recipe:
> - add enclosed binary file, with -kb or -kB option
> - commit the file
> - tag the file
> *** at this point, all is fine, ,v file is well-formed.
> - update the directory (nothing is retrieved)
> - commit the directory --> RCS error, end of file
>
>
> The file is systematically corrupted with DF (hexa) at the end (shows up 
> as beta / German "double-S" character).
>
> This is repeatable with both 2.02.2115 and the 2.03.2382 versions, with 
> :local: and :ext: protocols.
>
> We have absolutely no clue as to why a commit of a non-modified file would 
> cause this problem.
>
> Specifics:  Server is running on Windows 2000, fully patched.  Repository 
> is on a file system with NTFS file compression enabled.
>
> Mail followup in addition to newgroup would be appreciated.
>
> Jean-François Lamy
> Teximus Technologies inc.
> Montreal, Canada.
>
>