> -----Original Message-----
> From: Stefan Sperling [mailto:s...@elego.de]
> Sent: vrijdag 3 juni 2011 14:05
> To: Bert Huijben
> Cc: dev@subversion.apache.org
> Subject: Re: Stuck between relocate and upgrade
>
> 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.
Yes, we do support this.
And even in 1.6 we can't be sure uuid and repos_root are available.
As this working copy might have been upgraded (1.0-1.3), upgraded(1.3-1.5)
and upgraded (1.5-1.6).
That is why our upgrade contacts the repository to fetch the missing
information.
Bert
