[holger krekel Mon, Oct 27, 2003 at 05:15:27PM +0100]

hello,

we will be upgrading the subversion server libraries and need to dump the old database and restore it to the new format. This will take some time so expect some downtime regarding svn-accesses. The rest of apache will probably continue to run as usual, though. We'll reply to this posting if everything is stable again.

We are pretty sure already, that you will need to run svn clients with at least version 0.30 (we'll also post some results for windows and linux clients which we will test the new server with).

OK, the update is complete, we are now running svn 0.32.1. Note that it is *highly recommended* to update your svn-client. See our usual page: http://codespeak.net/pypy/index.cgi?doc/devel/howtosvn.html Until subversion 1.0 is reached (probably end of this year) compatibility on the network layer is only guaranteed across two minor releases. For example, you should still be able to use a 0.31.x client with a 0.32.1 server. Although older clients may work in a lot of cases you may get strange errors in certain situations. It's also interesting to note that the new 'svn blame' command (similar to 'cvs annotate') does not always work on all PyPy files. We suspect this is so because when Armin and Holger merged the builtinrefactor branch to the trunk they actually swapped the 'trunk' and the 'branch' path to keep a linear history. However, we will communicate with the svn developers to resolve the issue. have fun, Holger & Jum