Sign in to follow this  
gamelife

svn "unrecognized line ending style"

Recommended Posts

Hi, I am using TortoiseSVN. Recently, I updated all .txt files to have svn:mime-type = application/octet-stream. After that, when some other colleagues do svn update on their computers, they got error: "unrecognized line ending style". Any clues? Thanks in advance!

Share this post


Link to post
Share on other sites
When you change a text file to be treated as a binary, then you don't get newline translations done. On different platforms the character(s) for line endings are different.

Share this post


Link to post
Share on other sites
But when a colleague do SVN update again, he got the same error; and he cannot commit the file.
"unrecognized line ending style" should be an warning instead of an error, right?

Share this post


Link to post
Share on other sites
I cannot set eol-style to native since it pops up an error: File xxx has binary mime type property.

My client is TortoiseSVN 1.6.2. I am not sure what's the server's version.

I just want SVN to treat my files as binary, that's why I set svn:mime-type to application/octet-stream. I don't know why it bothers with line ending style. It should be a bug.

Share this post


Link to post
Share on other sites
What happens if your colleagues attempt a fresh checkout of the directory containing the text files with application/octet-stream MIME type? I'm wondering if the errors aren't due to switching from a previous revision having been a purely text file (meaning SVN would try to merge commits) and the subsequent revision being binary (meaning it wouldn't). I can't be certain, but it's worth investigating.

SVN shouldn't care about the line ending style in a binary file, so it's a truly odd error.

Share this post


Link to post
Share on other sites
Fresh checkout has no problem.
Btw, apparently only the first update(s) after changing mime-type would raise the error, after that no problem occurs now.

Share this post


Link to post
Share on other sites
Quote:
Original post by gamelife
Fresh checkout has no problem.
Btw, apparently only the first update(s) after changing mime-type would raise the error, after that no problem occurs now.

Yeah, that's what I thought. For future reference, you could probably dropped to the command line and done an svn update --force to override the error.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this