On Friday 03 June 2011 05:47 PM, Bert Huijben wrote:
-----Original Message-----
From: Mark Phippard [mailto:markp...@gmail.com]
Sent: vrijdag 3 juni 2011 14:13
To: Bert Huijben; dev@subversion.apache.org
Subject: Re: Stuck between relocate and upgrade
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.
What the old version is, is not relevant. (See other reply: Before 1.7 we
can never be sure if we have all the information in the working copy
or not)
The question is more: Is this problem relevant enough to support this
scenario on 'svn upgrade'.
For my test suite it isn't... But we have millions of Subversion users
that
will upgrade over the next few years. Some of those will have the same
problem.
And if one of those users doesn't manage its own installed applications
(Read: typical corporate environment), then the only thing a user could do
is delete all relevant working copies and perform a new checkout.
Bert
If it's simple matter of adding the uuid and repos_root_url, can't we
teach one of our existing scripts like change-svn-wc-format.py to simply
add them?
