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

Re: Stuck between relocate and upgrade

From: Stefan Sperling <stsp_at_elego.de>
Date: Fri, 3 Jun 2011 14:04:46 +0200

On Fri, Jun 03, 2011 at 01:53:45PM +0200, Bert Huijben wrote:
> Hi,
> I'm trying to get SharpSvn working compiled against Subversion 1.7. After
> fixing a few minor compilation problems I found a problem that other users
> might find as well.
> In our test suite (which is based on the old AnkhSVN test suite) we have a
> few tarballs of working copies created with some pre subversion 1.4 client.
> These working copies were created on a unix system and expect their
> repository in file:///tmp/...<something>.
> In Subversion 1.4-1.6 we just performed a 'svn switch --relocate' directly
> after checkout and then we did the rest of the test.
> For Subversion 1.7 I tried to simply tried to add a 'svn upgrade' before the
> relocate.
> But:
> svn upgrade needs to contact the repository in this case to get a uuid
> and/or repos_root_url.
> So to get this working I have to perform a relocate before the upgrade...
> but also an upgrade before the relocate.
> I haven't found a good solution yet..

Do we really support upgrading 1.4 working copies with 1.7?
I thought that users would have to upgrade their working copies
to 1.6 before upgrading to 1.7.

In which case your test scenario is simply not supported.

Maybe you could workaround it by hacking the .entries files so that
they contain UUID/repos_root_rul before the upgrade.
Or upgrade those working copies using a 1.6 client, then upgrade
them to 1.7, and save them for use in your tests?
Received on 2011-06-03 14:05:24 CEST

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

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