If you may be aware, all Mac machines come pre-loaded with Subversion. You can find out which version is pre-installed on your machine by typing the following in terminal :
svn --version
Well, my default version was 1.6.x. And recently I decided to upgrade it to the latest current version v1.8.8. I also created a repository and a corresponding working copy using Cornerstone client for Mac. However it supports the older version 1.4, 1.5, 1.6 & 1.7 clients. It does not support yet v.1.8.8 client.
So if you try to see the logs from the Terminal or perform any svn operation from the command line on your working copy, you will get an error like :
The working copy at "x-x-x-x-location" is too old (format 10) to work with client version '1.8.8 (r1568071)' (expects format 31). You need to upgrade the working copy first.
This message can be taken care of by simply typing svn upgrade in the command line.
However, if you return to working with Cornerstone, you simply won't be able to access the working copy. It pops up an annoying message, something like :
It leads me to believe that Cornerstone works fine with Apple- supplied Subversion v1.6. However, if you upgrade it to v1.7 or v1.8 this can result in annoying errors. It seems like Cornerstone automatically detects which Subversion to use while creating the repos and working copies. There's no way to customize it on this front - I mean you can't define the svn location if you upgraded it to v1.8.
Though the Cornerstone 2.7 upgrade provides support for subversion 1.7 as described in its release notes, it is not possible to downgrade 1.7 to 1.6 or lower, if needed. Plus it doesn't support the newer subversion version 1.8.x as yet. Sure it does plan to integrate Svn v1.8 in a future update. But I feel isn't this a bit annoying, having to wait for Cornerstone to update after subversion updates theirs.
Guys, do post your comments if you think any good workaround or a fix to this annoyance is available. For now, am contemplating a switch to Versions. Ping in your views about it's strengths and weaknesses folks. You have a good day. Take care.
svn --version
Well, my default version was 1.6.x. And recently I decided to upgrade it to the latest current version v1.8.8. I also created a repository and a corresponding working copy using Cornerstone client for Mac. However it supports the older version 1.4, 1.5, 1.6 & 1.7 clients. It does not support yet v.1.8.8 client.
So if you try to see the logs from the Terminal or perform any svn operation from the command line on your working copy, you will get an error like :
The working copy at "x-x-x-x-location" is too old (format 10) to work with client version '1.8.8 (r1568071)' (expects format 31). You need to upgrade the working copy first.
This message can be taken care of by simply typing svn upgrade in the command line.
However, if you return to working with Cornerstone, you simply won't be able to access the working copy. It pops up an annoying message, something like :
Description : "Working_Copy_Example" the working copy's format is not supported.
Suggestion : The working copy must be downgraded to a compatible version before it can be used.
Technical Information
=====================
Error : V4UnsupportedWorkingCopyFormatError
Exception : ZSVNUnsupportedWorkingCopyFormatException
Causal Information
==================
working copy. Please upgrade your Subversion client to use this
working copy.
Status : 155021
It leads me to believe that Cornerstone works fine with Apple- supplied Subversion v1.6. However, if you upgrade it to v1.7 or v1.8 this can result in annoying errors. It seems like Cornerstone automatically detects which Subversion to use while creating the repos and working copies. There's no way to customize it on this front - I mean you can't define the svn location if you upgraded it to v1.8.
Though the Cornerstone 2.7 upgrade provides support for subversion 1.7 as described in its release notes, it is not possible to downgrade 1.7 to 1.6 or lower, if needed. Plus it doesn't support the newer subversion version 1.8.x as yet. Sure it does plan to integrate Svn v1.8 in a future update. But I feel isn't this a bit annoying, having to wait for Cornerstone to update after subversion updates theirs.
Guys, do post your comments if you think any good workaround or a fix to this annoyance is available. For now, am contemplating a switch to Versions. Ping in your views about it's strengths and weaknesses folks. You have a good day. Take care.
No comments:
Post a Comment