[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: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Fri, 12 Dec 2008 16:24:51 +0200 (Jerusalem Standard Time)

Stefan Sperling wrote on Fri, 12 Dec 2008 at 13:58 -0000:
> On Thu, Dec 11, 2008 at 06:44:01AM +0100, Neels Janosch Hofmeyr wrote:
> > 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.
>

There is a compile-time setting:

    /* Defining this conditional will result in a client that will refuse to
       upgrade working copies. This can be useful if you want to avoid
       problems caused by accidentally running a development version of SVN
       on a working copy that you typically use with an older version. */
    #ifndef SVN_DISABLE_WC_UPGRADE

> 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.
>

Yeah, some testing would be nice. Getting the script to support format
10 was a bit of a headache (just because 10 is more digits than 9).

Daniel

> 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].
>

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

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2008-12-12 20:05:34 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.