• Changing Subversion working copy version using Windows and Python 3

    by  • July 30, 2009 • java, subclipse, subversion, windows • 4 Comments

    Made a bit of a boo-boo today… I used the Subclipse plugin regularly within Eclipse to manage my code checkins on my SVN repositories, but I’ve also got TortoiseSVN installed and checked in some modifications to this code using TortoiseSVN, which consequentially upgraded by working copy from Subversion 1.4 to 1.6.

    When I attempted to check in some further code changes using Subclipse, it complained with an error This client is too old to work with working copy. Turns out its pretty easy to downgrade your working copy without having to check out a fresh copy, using a Python file provided on the Subversion FAQ here.

    So I installed Python 3.1 for Windows, and the py file would not compile, complaining about a syntax error. It seems that the file in the main distribution is not compatible with Python 3 but you can grab a copy of the appropriate py file from the python-3-compatibility branch at https://svn.collab.net/repos/svn/branches/python-3-compatibility/tools/client-side/change-svn-wc-format.py.

    Using it was a sinch to convert the working copy back to v1.4 (n.b. python was on the path and associated with .py files):

    change-svn-wc-format.py checked_out_dir 1.4

    Took no longer than about a minute and I was back to checking in files via the Subclipse plugin.

    About

    .NET developer at thetrainline.com, previously web developer at MRM Meteorite. Awarded a PhD in misbehaviour detection in wireless ad-hoc networks.A keen C# ASP.net developer bridging the gap with APIs and JavaScript frameworks, one web app at a time.

    http://www.paulkiddie.com

    4 Responses to Changing Subversion working copy version using Windows and Python 3

    1. Lex Robin
      July 31, 2009 at 7:35 am

      SmartSVN, like any other SVN client, updates the working copy format automatically, too, when performing some operations. But if offers a separate menu item to downgrade the working copy format. No need to mess around with Python and a script.

      BTW, why you are not upgrading your Subclipse plug-in, too?

    2. July 31, 2009 at 8:25 am

      Thanks for the information – have been using TortoiseSVN for years so not been on the lookout for a new SVN client, but SmartSVN looks pretty good.

      On the Subclipse plug-in, the reason i’ve not moved over to 1.6 yet is more to do with legacy than anything, got the code checked out on a few client PCs all running the same, or similar versions of Subclipse – need to get around to it!

    3. Michael Kopinsky
      November 2, 2010 at 5:58 pm

      Note that the link you included is a Python 3 script. If you don’t have Python 3 installed, you can use this one instead:

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

    4. Michael Kopinsky
      November 2, 2010 at 5:59 pm

      Note that the link you included is a Python 3 script. If you don’t have Python 3 installed, you can use this one instead:

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

      (I got an error when submitting last time, let’s try again…)

    Leave a Reply

    Your email address will not be published. Required fields are marked *