[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: Bert Huijben <bert_at_qqmail.nl>
Date: Fri, 3 Jun 2011 14:17:47 +0200

> -----Original Message-----
> From: Mark Phippard [mailto:markphip_at_gmail.com]
> Sent: vrijdag 3 juni 2011 14:13
> To: Bert Huijben; dev_at_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

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.

Received on 2011-06-03 14:18: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.