[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Windows 10 November 2019 security updates affecting file:// to Win2003 shares?

From: Branko Čibej <brane_at_apache.org>
Date: Thu, 21 Nov 2019 08:10:00 +0100

On 20.11.2019 18:57, Nathan Hartman wrote:
> On Wed, Nov 20, 2019 at 10:59 AM jimbobmcgee
> <users~subversion.apache.org_at_jimbobmcgee.com
> <mailto:subversion.apache.org_at_jimbobmcgee.com>> wrote:
>
> HI all;
>
> Appreciating the woefully out-of-date/unsupported nature of my
> setup, I thought it might be worth dropping a line to see if
> anyone else out there might be experiencing issues since this
> month's Patch Tuesday release.
>
> Prior to the November 2019 updates, our Windows 10 users were
> successfully using Subversion and/or TortoiseSVN to commit to some
> old v1.6 repositories stored on a Windows Server 2003 R2 file
> share, using the file:// protocol. 
>
>
> 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

No, just pointing to the new URL will be enough.

> svn switch --relocate (or through TortoiseSVN).

  2. The '--relocate' option is deprecated. This syntax is equivalent to
     'svn relocate FROM-PREFIX TO-PREFIX [PATH]'.

So, 'svn relocate', not 'svn switch --relocate'. :)

-- Brane
Received on 2019-11-21 08:10:07 CET

This is an archived mail posted to the Subversion Users mailing list.