On Sep 8, 2008, at 18:31, Andy Levy wrote:
> On Mon, Sep 8, 2008 at 18:04, Arturo 'Buanzo' Busleiman wrote:
>
>> I know I have to svnadmin upgrade each repo after upgrading
>> subversion to 1.5+, I also know I have
>> to run svn-populate-node-origins-index, too.
>>
>> But... what do the clients (1.5 already) need to do? Is there any
>> need to re-checkout the project?
>
> Nothing. Unless your URLs or UUIDs changed, in which case you'd need
> to svn switch or svn switch --relocate on each WC.
If the URL *to* your repository changed (because you moved where the
repository is on the server disk, or you changed hostnames or
protocols or port numbers), you need to "svn switch --relocate"
If the URL to your project *within* your repository changed (because
you "svn mv"ed it in another working copy or with direct repository
URLs), you need to "svn switch"
If the repository UUID changed (because you dumped the repository and
then loaded the dumpfile into a new repository and used the --ignore-
uuid flag when loading, for example because the new repository will
not be identical to the old repository because you filtered out some
revisions with svndumpfilter), you need to throw away your working
copies and check out new ones.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-09-09 08:25:25 CEST