Re: Xcode 3.1 SCM breaks after installing Subversion 1.6
Re: Xcode 3.1 SCM breaks after installing Subversion 1.6
- Subject: Re: Xcode 3.1 SCM breaks after installing Subversion 1.6
- From: Kyle McKay <email@hidden>
- Date: Wed, 18 Nov 2009 10:13:07 -0800
On Nov 18, 2009, at 09:33:21 PST, Jens Alfke <email@hidden> wrote:
I'm running Xcode 3.1.3 on OS 10.5.8. I've installed a newer version
of Subversion (1.6.6) via MacPorts because the build tools for the
project I'm working on require it.
Unfortunately svn 1.6 uses a newer repository format, and now
Xcode's SCM commands aren't working — they report "Error: 155021
(Unsupported working copy format) Description: This client is too
old to work with working copy ...; please get a newer Subversion
client".
Presumably Xcode is still calling /usr/bin/svn, not the new /opt/
subversion/bin/svn. Is there a way that I can override the path to
the Subversion tool that Xcode uses?
—Jens
See the email previously posted to this list. The instructions should
still work fine (although I have not yet tested them on Mac OS X
10.6.x). Be sure to use either subversion 1.5.7 if you need the 1.5.x
series (which apparently you do not) as earlier versions of the 1.5.x
series have a security issue or at least subversion 1.6.5 if you need
the 1.6.x series. Subversion versions 1.6.0 through 1.6.4 are
absolutely NOT compatible with Xcode. 1.6.5 is the first release of
the 1.6.x series to contain a fix for the bug introduced in 1.6.0 that
renders it unusable with Xcode.
You can find the email with detailed instructions here:
http://lists.apple.com/archives/Xcode-users/2009/Apr/msg00395.html
Kyle _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden