[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: Philip Martin <philip.martin_at_wandisco.com>
Date: Thu, 15 Dec 2011 12:04:31 +0000

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.
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.)

The most likely thing to be missing is the root URL. You only need to
add this for the single entry that represents the root of the working
copy and you will find that in the .svn/entries file in the root of the
working copy. If your .svn/entries file is XML then locate the root
entry:

<entry
    ...
    name=""
    ...
    url="http://example.com/some/repos/trunk"
    ...
    revision="6">

and add a repos element:

<entry
    ...
    name=""
    ...
    url="http://example.com/some/repos/trunk"
    repos="http://example.com/some/repos"
    ...
    revision="6">

If your .svn/entries file is not XML then it should start something like:

   10

   dir
   6

   http://example.com/some/repos/trunk

   2011-12-15T10:15:25.161943Z

Change the blank line after the checkout URL to define the root URL:

   10

   dir
   6

   http://example.com/some/repos/trunk
   http://example.com/some/repos

   2011-12-15T10:15:25.161943Z

Make sure you change the blank line, do not insert a new line.

-- 
Philip
Received on 2011-12-15 13:05:15 CET

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.