[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: File corruption

From: Ryan Schmidt <subversion-2006Q1_at_ryandesign.com>
Date: 2006-02-03 11:17:34 CET

On Feb 3, 2006, at 09:11, Lakshman Srilakshmanan wrote:

> I found that "xdocs/Sensis_Classifieds_J2EE_Framework.doc" on my
> branch
> was corrupted.
> Since I had changed the Meta data on this file on the branch I
> wanted to
> merge it back to the trunk (Don't worry JUST testing).
> In step 0 I listed the file.
> In step 1 I ran a dry-run.
> In step 2 I ran the merge.
> In step 3 I listed the file.
> In step 4 I commit the file to trunk
> In step 5 I listed the file again.
> The strange behaviour is that the file size changed between step 3 and
> step 5 and that file is now corrupted.
> Why did the file size change after a commit. I would have expected
> it to
> change after the merge...!!

Perhaps you have set the svn:eol-style property on this file, and
Subversion dutifully converted the newlines for you. Since this is a
binary file, not a text file, this obviously corrupts the file.
Therefore you should not set the svn:eol-style property on binary
files. Perhaps you have an auto-props rule that sets svn:eol-style
indiscriminately on all kinds of files? If so, you should change your
auto-props to only set the property on files you know to be plain text.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 3 11:19:15 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.