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

Re: Vendor Branches from Foreign Repositories: svn: E200009: Can't set 'svn:eol-style'

From: Ben Reser <ben_at_reser.org>
Date: Fri, 31 Jan 2014 17:31:44 -0800

On 1/31/14, 5:49 AM, Uwe Tropp wrote:
> I'm trying to import a vendor branch from a foreign repository by:
>
> d:\foo>svn copy http://svn.boost.org/svn/boost/tags/release/Boost_1_55_0
> Boost
>
> svn starts copying, but aborts with E200009: Can't set 'svn:eol-style':
>
> --- Copying from foreign repository URL
> 'http://svn.boost.org/svn/boost/tags/release/Boost_1_55_0':
> :
> :
> A Boost\tools\quickbook\test\html\images
> svn: E200009: Can't set 'svn:eol-style': file
> 'D:\foo\Boost\tools\quickbook\test\html\images\open_clipart_library_logo.svg
> ' has binary mime type property
>
> Since I have no control over the foreign repository I can't fix this issue
> and am now stuck and unable to complete the import.
> I think SVN should either skip the properties for this file and place a
> warning or mark it as a conflict but continue to import instead of abort.
>
> Can anybody add this to the issue tracker?
>
> Is there a workaround to solve this?

I agree, this isn't very useful as it stands.

Fixed on trunk with:
http://svn.apache.org/r1563361

Don't think we'll backport this to 1.8 since I ended up adding an API. We
probably could though with some effort of switch the foreign copy from using
the svn_wc_add_from_disk2() into using the other functions that can do all the
same things, just can't do them all at once and ultimately end up using
svn_wc_prop_set4() which already has the argument to skip the property
canonicalization.

You could workaround this locally by modifying subversion/libsvn_wc/adm_ops.c
to change the skip_some_checks argument to the svn_wc__canonicalize_props()
call in svn_wc_add_from_disk2(). That's at line 1016 in the current 1.8.x
branch. However, that will disable those checks for all adds (including those
done via svn add, svn merge, and svn patch) which I wouldn't recommend for
daily usage. But that sort of patch might get you past this issue temporarily.
Received on 2014-02-01 02:32:19 CET

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.