All geek questions in one place

Xcode: Error & # 8594; Build failed & # 8594; Upgrade your Subversion client to use this working copy.

I am using Xcode 4.2.1. and I have this problem with running an existing application on an iOS simulator:

svn: The path '.' appears to be part of a Subversion 1.7 or greater working copy. Please upgrade your Subversion client to use this working copy. /Users/me/Library/Developer/Xcode/DerivedData/myproject-dxfzldckuqdmlrghowwkdrbgoigy/Build /Intermediates/myproject.build/Debug-iphonesimulator/MyProject.build/Script-9567AEA113C59633000AA291.sh: No Subversion revision found at /Users/me/Library/Developer/Xcode/DerivedData/myproject-dxfzldckuqdmlrghowwkdrbgoigy/Build/Intermediates/myproject.build/Debug-iphonesimulator/MyProject.build/Script-9567AEA113C59633000AA291.sh line 32. Building revision Command /bin/sh failed with exit code 1

I have a Subversion 1.7.1 server installed, and on the client side I upgraded to 1.7.1. I did svn upgrade and then get this error in Xcode.

If I repeat svn upgrade on the terminal, I get the message Can't upgrade '...' as it is not a pre-1.7 working copy directory .

So what's wrong? How do I solve the problem?

Regards Tim

+6
source share
3 answers

Xcode does not yet support SVN 1.7. Only 1.6 is supported. To fix your problem, you need to switch to a working copy compatible with SVN 1.6.

Since the client of SVN 1.7 cannot work with 1.6 working copies at all, you need to remove SVN 1.7.x from your client and return to 1.6. (Or maybe just adjust your PATH so that the SVN 1.6 tools are first.) As soon as 1.6 returns, delete or move aside the existing working copy and check the new copy with SVN 1.6. Xcode should now work with your working copy.

Please note that you can freely use the SVN 1.6 client with the SVN 1.7 server. Some of the new features will not be available, but they will work. There is no need to downgrade the server or server repositories.

Stay tuned for updates to Xcode releases as updates as I'm sure Apple will notice when Xcode is able to use SVN 1.7. When the 1.7-compatible release of Xcode becomes available, then you should be safe to upgrade the client to version 1.7 and transfer the working copy again.

+7
source

There is a message that apparently means that you can trick Xcode into using the svn 1.7 client by changing PATH and creating a couple of free links in strategic places. Sorry, the message is in Chinese. Fortunately, Google translate , and the presence of UNIX commands, allows you to decrypt what the message says. I will try it in the next few days and update the answer if anything useful comes out of this exercise.

EDIT: I tried the steps from the post and it worked. Here is what I did:

  • Downloaded and installed svn 1.7.2 client in /opt/subversion
  • Added / opt / subversion / bin to my PATH in .bash_profile
  • Backup directory /Developer/usr/bin/orig.svn
  • Moved /Developer/usr/bin/svn* to /Developer/usr/bin/orig.svn
  • Ran ln -s /opt/subversion/bin/svn* /Developer/usr/bin/

After that I restarted Xcode, went to Organizer and was able to attach a working copy of the check created by the svn 1.7.2 client. The organizer showed a green dot next to the repository, displayed a list of revisions, etc., Therefore, at this moment I believe that the trick worked.

+8
source

You can download and install the binary package from http://www.wandisco.com/subversion/download#osx

The package will be installed on /opt/subversion , while the SVC version for xcode is installed on /usr/bin . If you add /opt/subversion/bin to the path variable, it will be selected instead of the xcode version.

If you do not want to get confused with your path, you can simply use the alias of one or the other version. man alias for details.

0
source

Source: https://habr.com/ru/post/902384/

More articles:


All Articles