You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Neels Janosch Hofmeyr <ne...@elego.de> on 2008/12/11 05:44:01 UTC
blocking newer client on older WC?
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?
Thanks
~Neels
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=982688
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: blocking newer client on older WC?
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
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@subversion.tigris.org].
>
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=983418
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: blocking newer client on older WC?
Posted by Stefan Sperling <st...@elego.de>.
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@subversion.tigris.org].
Re: blocking newer client on older WC?
Posted by Stefan Sperling <st...@elego.de>.
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@subversion.tigris.org].
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=988274
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].