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

Re: svn corrupts binary files on import

From: Ryan Schmidt <subversion-2005_at_ryandesign.com>
Date: 2005-09-23 21:20:30 CEST

On Sep 23, 2005, at 20:52, Sacerdoti, Federico wrote:

> I have seen this happen a few times. I have just started using SVN,
> so I
> may be doing something wrong. Steps to recreate:
> 1. svn import mydir/, where there is a non-text file "mybin" somewhere
> under mydir
> 2. checkout mydir to some other location.
> 3. inspect "mybin". It is not good.
> Attached is an example of an rpm that was mangled in this way. SVN
> cannot even tell the difference between a good version and the bad
> one.
> 1. cp known-good "mybin" over existing mybin-BAD
> 2. svn status -> nothing


> Diff from an octal dump "od -x Good" and "od -x Bad". Seems like the
> difference is always between an 0xa and 0xd.

So you've got auto-props enabled in your client's config file, and
you've told Subversion to mangle line endings on all files. And
Subversion is doing so.

Don't Do That. :-) Instead, tell Subversion to mangle line endings
only on the file types whose line endings you actually want it to

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Sep 23 21:25:21 2005

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.