On Thu, Oct 24, 2013 at 7:33 AM, Ryan Schmidt <
subversion-2012c_at_ryandesign.com> wrote:
> 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.
>
Then, Ryan, you've got a lot more problems than just a need to upgrade, and
I really hope you made a full tarball of that repository before you copied
it, or that you have your work backed up by other means. Because this kind
of stunt is dangerous, even with upgrade paths that have previously worked
well. It's difficult indeed to test the upgrade tools from, say, a working
copy in Subversion 1.4.1, which may have had bugs fixed during the 1.4
series, to Subversion 1.8.3 without the intervening steps. Some surprises
are not shocking.
> 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.
>
> What happens if you delete or move aside the file, then check it out
again? And what are the permissions of the local copy in the ".svn"
directory? And what shows up in a completely clean checkout? It should be
possible to do a clean checkout and then copy all the files from a backup,
excluding the ".svn" subdirectory, right on top and get back as close as
possible to the old state.
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.
>
> It's new to me, but I'm not using a Mac right now.
Received on 2013-10-24 13:47:55 CEST