mika.karkkainen_at_tietolaite.com wrote:
> Hi,
>
> While doing some merge-related testing, I stumbled into a text file that
> had gone corrupt. The signs of corruption are:
>
> 1) A 0x0B char followed by two slashes appeared twice in a line that I
> added, the corrupt line looks like:
>
> // 0x3b// svn150devtest3-branch mod #1 0x3b//
>
> 2) Two null bytes were appended to the end of the file
>
> The whole scenario was:
> - create a fsfs repo
> - using TSVN, import a std VC 6 project into it
> - using TSVN, checkout the trunk
> - using TSVN, create a branch
> - using TSVN, checkout the branch
> - modify a file in the branch (as discussed above)
> - using TSVN, check-in the branch (this is the step were the corruption
> occurred)
Is the file corrupted on your branch working copy? If that's the case,
then it's unlikely that svn is the reason for the corruption: on
import/commit/... files are not modified at all by Subversion, only
during update/merge/...
> - using TSVN, merge from branch to trunk
>
>
> Since we have a self-compiled 150-dev subversion on the server side, my
> guesses tend to fall into that direction (even though the subversion
> test-suite succeeded, except for one blame-related test). But anyhow,
> _any_ ideas/experiences about what might be causing this, are most
> certainly gladly received.
If you can reproduce the corruption of the file, I suggest you report
this to the subversion mailing list (users at subversion tigris org).
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-01-16 20:24:32 CET