On Fri, Jun 3, 2011 at 8:04 AM, Stefan Sperling <s...@elego.de> wrote: > 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?
I do not get the impression that 1.4 is the relevant fact here. It seems like the issue is just that svn upgrade needs to contact the repository? So you cannot upgrade a WC that needs to be relocated? This does not sound like a real world problem. -- Thanks Mark Phippard http://markphip.blogspot.com/
