Thanks for the response. I'm using Apache 2.2.2 so that shouldn't be a problem.
Still not sure about the modules. From what I can tell the SVN
binaries don't come up with Apache modules. Maybe the ones that come
with 2.2.2 will work fine with SVN 1.6.
The svn docu seems to indicate that I don't have to do the svndump and
re-import thing when upgrading to 1.6. I'll of course back up the
repositories regardless. Apparently the repositories don't get
upgraded automatically on upgrade and you have to use "svnadmin
upgrade" to manually upgrade the repositories to a 1.6 format.
On Mon, Apr 6, 2009 at 7:05 PM, Andrey Repin <anrdaemon_at_freemail.ru> wrote:
> Greetings, Bradley Wagner!
>> I'm wondering what I have to upgrade a SVN 1.3.2 server to the latest
>> 1.6 when running with apache's SVN modules.
>> Am I going to have to recompile apache to use these new binaries? Are these
>> modules dynamically loaded and easily replaceable?
> You have answer in your question. Apache modules could be easily replaced.
> They are shared libraries.
> However, true question is, what the version of Apache server you're using?
> If it's not Apache 2.2, you'll need to upgrade Apache server too.
> And for SVN database upgrade, you better "svnadmin dump" your repository(es)
> using current server installation, then prepare an upgrade, make test
> repository, check that it working fine, then restore your actual repos.
> Andrey Repin (anrdaemon_at_freemail.ru) 07.04.2009, <3:01>
> Sorry for my terrible english...
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-04-07 01:17:19 CEST