So it seems that as part of our changes to the working copy library in
trunk we changed some behavior with regard to how we deal with
inconsistent eols. Previously if you managed to get inconsistent eols
checked into the repository along with an svn:eol-style of native you
could at least check out the file, remove the svn:eol-style, and get
on with your life. Now, we fail on checkout with an error about the
text base having inconsistent newlines:
svn: In directory 'whatever'
svn: File 'whatever/.svn/tmp/text-base/something-or-other.dia.svn-base'
has inconsistent newlines
svn: Inconsistent line ending style
This isn't especially friendly, since without the ability to check out
the working copy there isn't actually any way to remove the property,
since propdel doesn't work on URLs.
Now in a perfect world we wouldn't have files like this in the
repository, but it seems that they do get there. I wouldn't be
surprised to see them as the result of some cvs2svn mess ups, and in
the case I actually observed it was through addition via an old client
that apparently didn't check for such things.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Mar 16 02:50:48 2006