"This client is too old to work with working copy" [SOLVED]

[Soren 'Frank' Munch <sm...@u5.com>]

Hi,

I got an error saying 'This client is too old to work with working copy'
when typing 'svn'.
It did not say what version the working copy was, though.
There was a link to a page which had a link to a python-script, but it
failed.
Sorry for not recording the error message.

The problem was easily solved. I did the following:

$ mv working_copy old_working_copy
$ find old_working_copy -name ".svn" | xargs rm -rf
$ svn checkout svn://myserver/path/trunk working_copy
$ cp -Rfp old_working_copy/* working_copy

Simple, and more reliable than any conversion script! :-) I had all my work
back, and 'svn' worked again.

I just post it in the hope that this, admitted: trivial,  idea may help
somebody else, e.g. if the python-script fails.

- - -

Must get around to upgrade one day...

-- 
Soren "Frank" Munch
CEO, U5com Co Ltd
~~~~~~~~~~~~~~~~~~~~~~~~
U5com Co Ltd
- productive corporate networks
 and web-systems since '97

2/22 Iyara Building 7th floor, #705
Chan Road
Thungwatdorn, Sathorn
10120 Bangkok
Thailand

web: www.u5.com
email: sfm@u5.com
phone: +66-2-678-7500(-1)
mobile: +66-81-431-3040
fax: +66-2-678-8400
~~~~~~~~~~~~~~~~~~~~~~~~

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2388789

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].

RE: "This client is too old to work with working copy" [SOLVED]

[Clyde Jones <cj...@exelixis.com>]

Soren 'Frank' Munch <> wrote:
> Hi,
> 
> I got an error saying 'This client is too old to work with
> working copy' when typing 'svn'.
> It did not say what version the working copy was, though.
> There was a link to a page which had a link to a
> python-script, but it failed.
> Sorry for not recording the error message.
> 
> The problem was easily solved. I did the following:
> 
> $ mv working_copy old_working_copy
> $ find old_working_copy -name ".svn" | xargs rm -rf $ svn
> checkout svn://myserver/path/trunk working_copy $ cp -Rfp
> old_working_copy/* working_copy
> 
> Simple, and more reliable than any conversion script! :-) I
> had all my work back, and 'svn' worked again.
> 
> I just post it in the hope that this, admitted: trivial,
> idea may help somebody else, e.g. if the python-script fails.
> 
> - - -
> 
> Must get around to upgrade one day...

I have had good luck with a script in the collabnet tools that will
change the version for you.

This fixes the error without having to remove the .svn and recheck out
the path 

http://svn.collab.net/repos/svn/trunk/tools/client-side/change-svn-wc-fo
rmat.py


usage: change-svn-wc-format.py WC_PATH SVN_VERSION [--verbose] [--force]
[--skip-unknown-format]
       change-svn-wc-format.py --help

Change the format of a Subversion working copy to that of SVN_VERSION.

  --skip-unknown-format    : skip directories with unknown working copy
                             format and continue the update

-- 
Clyde Jones
R&D Informatics
Senior Operations Developer
cjones@exelixis.com
Exelixis Inc
650 837 7085 Office
650 228 4699 Cell

This email (including any attachments) may contain material
that is confidential and privileged and is for the sole use of
the intended recipient. Any review, reliance or distribution by
others or forwarding without express permission is strictly
prohibited. If you are not the intended recipient, please
contact the sender and delete all copies.
Exelixis, Inc. reserves the right, to the extent and under
circumstances permitted by applicable law, to retain, monitor
and intercept e-mail messages to and from its systems.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2390742

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].