Thanks to those that responded so quickly to my question.
I am concerned that the default setup is to mangle EOL characters.
I compiled svn from subversion-1.2.3-1.tar.gz using an RPM spec file
based on the one from David Summers. I used the cvs2svn utility to
construct the initial repository. That is it. The rest is a default SVN
setup, I did not add any "auto-props" that I know of.
Here is my ~/.subversion/config (relevant section):
### The format of the entries is:
### file-name-pattern = propname[=value][;propname[=value]...]
### The file-name-pattern can contain wildcards (such as '*' and
### '?'). All entries which match will be applied to the file.
### Note that auto-props functionality must be enabled, which
### is typically done by setting the 'enable-auto-props' option.
# *.c = svn:eol-style=native
# *.cpp = svn:eol-style=native
# *.h = svn:eol-style=native
# *.dsp = svn:eol-style=CRLF
# *.dsw = svn:eol-style=CRLF
# *.sh = svn:eol-style=native;svn:executable
# *.txt = svn:eol-style=native
# *.png = svn:mime-type=image/png
# *.jpg = svn:mime-type=image/jpeg
# Makefile = svn:eol-style=native
I have no /etc/subversion, and I could not find anything relevant on the
server side. I would expect svn to leave my binaries alone by default,
but that is not the behavior I got. I have attached the spec file in
case there is something in there that did it which I do not understand.
How can I setup an auto-prop that turns off all mangling for binary
files? (Anything that svn puts (bin) next to on import). I will make
this the default so no one gets surprised.
I see in the manual 'svn:eol-style' property, but I don't see a setting
for "don't touch file".
Thank you for your help,
From: Ryan Schmidt [mailto:email@example.com]
Sent: Friday, September 23, 2005 3:21 PM
To: Sacerdoti, Federico
Subject: Re: svn corrupts binary files on import
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
> 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
Received on Fri Sep 23 22:44:12 2005
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com