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

Re: why does svn upgrade contact the server?

From: Stefan Sperling <stsp_at_elego.de>
Date: Thu, 15 Dec 2011 13:25:57 +0100

On Thu, Dec 15, 2011 at 12:04:31PM +0000, Philip Martin wrote:
> Stefan Sperling <stsp_at_elego.de> writes:
>
> > You will likely be better
> > of with a new checkout, given that such old working copies often exhibit
> > problems during or after an upgrade to the 1.7.x format anyway.
>
> That's not possible as the repository effectively no longer exists.

Ah, I realise that now. Sorry, I skimmed the initial email too fast.

> However it is possible to manually add enough information to make the
> client attempt the upgrade. (If the working copy has any of the
> corruption Stefan mentioned then the upgrade may still fail.)

I would recommend to use a 1.6 client instead of trying to upgrade the WC.
And above all import the data into a new repository so it can be versioned
properly again. Having a working copy as the only copy of the data
was bound to cause a dead-end situation at some point.
Received on 2011-12-15 13:26:38 CET

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