Andrew Reedick wrote on Tue, Jul 09, 2013 at 13:03:10 -0400:
> "svn add" is having trouble with *.png files. This is with a 1.8 and a 1.7.9 client.
>
> I create a new test repository, copy in some vender code, then when I run "svn add" I get the following error on 1.8:
> svn add build-pipeline-plugin-1.3.3
> ...
> A build-pipeline-plugin-1.3.3\src\main\resources\index.jelly
> A build-pipeline-plugin-1.3.3\src\main\webapp
> A build-pipeline-plugin-1.3.3\src\main\webapp\images
> svn: E200009: Can't set 'svn:eol-style': file 'C:\temp\1.8\test18\tags\build-pipeline-plugin-1.3.3\src\main\webapp\images\gear.png' has binary mime type property
>
> When I revert and re-run the add, the add will sometimes fail on a different *.png file, which is odd.
>
> Under 1.7.9, I get one of two errors, either:
> svn: E200009: File 'C:\temp\test18\build-pipeline-plugin-1.3.3\src\main\webapp\images\application-small-list-blue.png' has binary mime type property
> or
> svn: E200009: File 'C:\temp\test18\build-pipeline-plugin-1.3.3\src\main\webapp\css\redmond\images\ui-icons_f9bd01_256x240.png' has inconsistent newlines
> svn: E135000: Inconsistent line ending style
>
> This is on Windows 7 32-bit with "svn, version 1.7.9 (r1462340)" or "svn, version 1.8.0 (r1490375)" clients from Collabnet.
>
> 'svn import' imports the files without issue. Enabling auto-props and uncommenting the '*.png' auto-prop in the client's config file made no difference either.
>
> Anyone have any ideas?
Can you try setting "*.png =" in the auto-props section? Perhaps
your registry has a setting that that will override. That said,
perhaps your registry has a setting for "*.pn*" which that will _not_
override; so check your registry:
" REGISTRY:HKLM\\Software\\Tigris.org\\Subversion\\Config"
" REGISTRY:HKCU\\Software\\Tigris.org\\Subversion\\Config"
For the archives, if this hadn't been a new repository, I'd have
suggested to look for inherited svn:auto-props properties too:
% svn pg --show-inherited-props -R svn:auto-props
Received on 2013-07-09 19:22:22 CEST