On Jun 25, 2011, at 14:38, davmar wrote: > I've upgraded from 10.6's native version of 1.6.15 to 1.6.17 using .dmg as > well as using MacPorts. > I've followed the installers directions to update the envvars file on my > remote server, as well .profile on the client side and vice, versa If I run > snvserv --version on the server I get the correct version and if I run svn > --version on the client side, I get the right version. > > However, when I navigate through a browser to http://myserver/svn ... the > page shows 1.6.15 instead of 1.6.17. Does anybody know why and how to fix > this? Am I really running 1.6.17 or is there something I am missing?
According to what you've told us, you're running the Subversion command line client 1.6.17, the Subversion svnserve server 1.6.17, and the Subversion mod_dav_svn Apache module 1.6.15. If you installed a new mod_dav_svn, you need to restart Apache for it to load that new version. If you've already restarted Apache and it still says 1.6.15, then you have not installed a new mod_dav_svn in a place where your Apache is looking for it. I don't know how the Subversion dmg installers work. I do know how Subversion works in MacPorts. It only installs mod_dav_svn if you ask for it (sudo port install subversion +mod_dav_svn), and it only works with the MacPorts apache2 server. It does not work with the Apache server built into Mac OS X.
