[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: blocking newer client on older WC?

From: Stefan Sperling <stsp_at_elego.de>
Date: Fri, 12 Dec 2008 13:58:22 +0000

On Thu, Dec 11, 2008 at 06:44:01AM +0100, Neels Janosch Hofmeyr wrote:
> Hi all,
>
> during subversion development, I sometimes accidentally use a client built
> from trunk on a working copy that I'm actually handling with a trusted,
> older build of svn.
>
> When I do that, the working copy is instantly upgraded to the trunk version
> and I end up checking out a whole new working copy to get it back to the old
> version, eliminating possible artifacts from the whacko trunk build.
>
> Is there a local setting I can apply to fixate the working copy version, so
> that any newer clients say "sorry, this working copy is older" instead of
> upgrading it?

I don't think there is such a setting.

What about using trunk/tools/client-side/change-svn-wc-format.py to
switch the WC back to 1.5 instead of getting a fresh WC?

Bonus: If that script fails, it's likely that trunk has severely broken
the WC, and there is a bug we need to fix anyway. Or the script needs
to be updated. Or both.

Stefan

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=983400

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2008-12-12 14:59:25 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.