While upgrading my laptop to OS X 10.9 Mavericks yesterday I finally took the plunge and upgraded Subversion 1.6.x to 1.8.3, using MacPorts. I had held off on the upgrade because of initial reports of working copy corruption when upgrading to the new Subversion 1.7 working copy format, especially when the working copy had been around for awhile, and I did not wish to have to recreate my MacPorts working copy, since it has years worth of uncommitted changes and half-finished updates in it. The working copy has about 20,000 files in about 13,000 directories, including innumerable unversioned items, and was originally checked out with some far-distant version of Subversion many years ago.
I discovered via a chance failed MacPorts build today that the execute bit had gotten lost on two files, even though they have the svn:executable property set to “*” like they should. I wondered if other files were also affected so I ran: find dports -type f -print0 | \ xargs -0 -n 1 svn pg -v svn:executable 2>/dev/null | \ sed -E -n "s/^Properties on '(.*)':$/\1/p" | \ xargs ls -l And I found that all files with the svn:executable property had indeed lost their executable bit. Is this loss-of-executable-bit-on-upgrade problem already known or should file a bug report? I did not immediately see a matching ticket in the issue tracker.
