解决：Errors occurred while updating the change sets for SVNStatusSubscriber

FROM: http://www.bq69.com/toolbox/aptana-svn-subclipse-version.html

今天早上提早了快一个小时到公司，打开Aptana准备折腾一下，没想到Aptana的SVN插件subclipse彻底的罢-工了，提示：

Errors occurred while updating the change sets for SVNStatusSubscriber
org.tigris.subversion.javahl.ClientException: Unsupported working copy format
svn: This client is too old to work with working copy ‘F:\ecp’. You need
to get a newer Subversion client, or to downgrade this working copy.
See http://subversion.tigris.org/faq.html#working-copy-format-change
for details.

org.tigris.subversion.javahl.ClientException: Unsupported working copy format
svn: This client is too old to work with working copy ‘F:\ecp’. You need
to get a newer Subversion client, or to downgrade this working copy.
See http://subversion.tigris.org/faq.html#working-copy-format-change
for details.

回想了一下周末，我也没做过特别坏的事啊，怎么RP骤降了？！仔细看了看官方的FAQ:

Sometimes the working copy metadata format changes incompatibly between minor releases. For example, say you have a working copy created with Subversion 1.4.4, but one day you decide to try out Subversion 1.5.0. Afterwards, you attempt to switch back to 1.4.4, but it doesn’t work — it just gives the above error.
This is because 1.5.0 upgraded your working copy format to support some new features (in this case, changelists, the keep-local flag, and variable-depth directories). Although 1.4.4 doesn’t know anything about these new features, it can at least recognize that the working copy format has been upgraded to something higher than it can handle.
1.5.0 upgraded the working copy for a good reason: it realizes that 1.4.4 does not know about these new features, and that if 1.4.4 were to meddle with the working copy metadata now, important information might be lost, possibly causing corruption (see issue #2961, for example).
Subversion 1.7.0 and newer will not upgrade working copies unless you explicitly ask them to do so. (Upgrading the working copies is, however, required; Subversion 1.7.0 cannot operate on working copies created or used by earlier Subversions.)
Subversion 1.6.x and earlier automatically upgrade working copies when they first touch them. This behavior can be annoying, if you just want to try out a new release of Subversion without installing it permanently. For this reason, we distribute a script that can downgrade working copies when doing so is safe:

http://svn.apache.org/repos/asf/subversion/trunk/tools/client-side/change-svn-wc-format.py

Run that script with the “–help” option to see how to use it. (It can downgrade 1.6.x working copies to formats usable by Subversion 1.4.x and 1.5.x, but cannot downgrade 1.7.x working copies.)
As future versions of Subversion are released, we will try to keep this FAQ entry up-to-date with potential downgrade scenarios and their implications.

引自Apache Subversion FAQ

估计是上周五手痒惹的祸，回家前升级了一下公司电脑的SVN客户端TortoiseSVN，好吧，我Subclipse用的是1.4版本，貌似，再瞄一眼本机的TortoiseSVN，天煞的，都Version 1.6.14了，赶紧更新吧插件吧：

1. 工具栏>‘Window’->‘Preferences’,展开树‘Install/Update’->’Available Software Sites’,然后就是把Subclipse安装/更新地址改为http://subclipse.tigris.org/update_1.6.x ;
2. 工具栏->’help’->’Check for Updates’,然后就是和安装时一样的步骤了，全选，一路的next,然后restart Aptana;
3. 成功！