Re: Windows 10 November 2019 security updates affecting file:// to Win2003 shares?
From: jimbobmcgee <users~subversion.apache.org_at_jimbobmcgee.com>
Date: Wed, 20 Nov 2019 19:20:51 +0000
We did not go down that route -- we simply moved our repositories to a newer-edition Windows file server, and used a DNS alias so that the end-users weren't affected for too long. It is part of our ongoing server refresh plan to move to a svn://- or https://-based solution in the near future, but we needed a short-term fix
The email to users@ was more a PSA than request for help, and also to see if my findings wre matched by anyone else.
----- Original message -----
On Wed, Nov 20, 2019 at 10:59 AM jimbobmcgee <users~subversion.apache.org_at_jimbobmcgee.com> wrote:
Have you considered running svnserve on that Windows Server 2003 box and then accessing the repository from your client machines via the svn:// protocol?
This will require either re-checking-out working copies on the client machines or updating their URLs with svn switch --relocate (or through TortoiseSVN).
This is an archived mail posted to the Subversion Users mailing list.