Re: svn add failing with svn: E200009: Can't set 'svn:eol-style': ... has binary mime type property and/or inconsistent newlines
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: E29: 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: E29: 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: E29: 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
Re: svn add failing with svn: E200009: Can't set 'svn:eol-style': ... has binary mime type property and/or inconsistent newlines
Probably caused by auto-props setting an svn:eol-style property. If tortoise actually crashed, please report that to http://tortoisesvn.net/support.html Andrew Reedick wrote on Tue, Jul 09, 2013 at 13:14:12 -0400: To add insult to injury, TortoiseSVN's add just died on a .css file: C:\temp\test18\foo\src\main\webapp\css C:\temp\test18\foo\src\main\webapp\css\jquery.fancybox-1.3.4.css File 'C:\temp\test18\foo\src\main\webapp\css\jquery.tooltip.css' has inconsistent newlines Inconsistent line ending style Additional errors: Inconsistent line ending style TortoiseSVN 1.8.0, Build 24401 - 32 Bit , 2013/06/17 18:15:59
RE: svn add failing with svn: E200009: Can't set 'svn:eol-style': ... has binary mime type property and/or inconsistent newlines
-Original Message- From: Daniel Shahaf [mailto:d...@daniel.shahaf.name] Sent: Tuesday, July 09, 2013 1:22 PM To: Andrew Reedick Cc: users@subversion.apache.org Subject: Re: svn add failing with svn: E29: Can't set 'svn:eol- style': ... has binary mime type property and/or inconsistent newlines 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 No joy. Setting *.png and enabling auto-props didn't work. The registry has no property settings (for both Tigris.org and Collabnet). And svn pg --show-inherited-props -R svn:auto-props returns nothing. However 'svn add --no-auto-props' does allow the add to work, but that's a bit drastic and inconvenient. That fact that 'svn add' fails on different files is really throwing me for a loop. I'm beginning to wonder if Something(tm) is borked with my workstation (anti-virus, some left-over DLL in the path, etc.)
Re: svn add failing with svn: E200009: Can't set 'svn:eol-style': ... has binary mime type property and/or inconsistent newlines
Andrew Reedick wrote on Tue, Jul 09, 2013 at 13:40:53 -0400: However 'svn add --no-auto-props' does allow the add to work, but that's a bit drastic and inconvenient. That fact that 'svn add' fails on different files is really throwing me for a loop. I'm beginning to wonder if Something(tm) is borked with my workstation (anti-virus, some left-over DLL in the path, etc.) Most likely you have an [auto-props] setting somewhere that's getting picked up.
RE: svn add failing with svn: E200009: Can't set 'svn:eol-style': ... has binary mime type property and/or inconsistent newlines
-Original Message- From: Daniel Shahaf [mailto:d...@daniel.shahaf.name] Sent: Tuesday, July 09, 2013 2:00 PM To: Andrew Reedick Cc: users@subversion.apache.org Subject: Re: svn add failing with svn: E29: Can't set 'svn:eol- style': ... has binary mime type property and/or inconsistent newlines Andrew Reedick wrote on Tue, Jul 09, 2013 at 13:40:53 -0400: However 'svn add --no-auto-props' does allow the add to work, but that's a bit drastic and inconvenient. That fact that 'svn add' fails on different files is really throwing me for a loop. I'm beginning to wonder if Something(tm) is borked with my workstation (anti-virus, some left-over DLL in the path, etc.) Most likely you have an [auto-props] setting somewhere that's getting picked up. Bingo. Somewhere was the operative word. The Collabnet config file was being read from my roaming profile instead of from my windows home dir. The roaming copy of config had * = svn:eol-style=LF, and that auto-prop seems to have been causing the breakage. (global-ignores = *.* * is a great way to narrow down what config file is being read.) And the reason why 'svn add' was failing on different files is because 'svn add' walks the directory tree in a different order each time. Thanks for the help! Now I must find a wall to quietly beat my head against.
RE: svn add failing with svn: E200009: Can't set 'svn:eol-style': ... has binary mime type property and/or inconsistent newlines
-Original Message- From: Branko Čibej [mailto:br...@wandisco.com] Sent: Tuesday, July 09, 2013 3:12 PM To: users@subversion.apache.org Subject: Re: svn add failing with svn: E29: Can't set 'svn:eol- style': ... has binary mime type property and/or inconsistent newlines On 09.07.2013 20:33, Andrew Reedick wrote: Bingo. Somewhere was the operative word. The Collabnet config file was being read from my roaming profile instead of from my windows home dir. You're aware that, on Windows, Subversion doesn't look for config files in %USERPROFILE%\.subversion at all but in %APPDATA%\Subversion? I'm aware now. (I've been using a Cygwin svn client for some time now, which reads from ~/.subversion.) The real question is why I had a %USERPROFILE%\.subversion tree in the first place (timestamps are from January.) *shrug*
