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

avoid auto-update of SVN meta files

From: Mark Thomas <mthomas_at_cmu.edu>
Date: Wed, 2 Jul 2008 16:28:10 -0400 (EDT)

My personal Subversion sandbox is located on a file system that is shared been machines running more-or-less stock releases of RHEL AS4 and RHEL5, with the RHEL AS 4 machines greatly outnumbering the RHEL5 machines. The Subversion releases on these machines are:

 $ cat /etc/redhat-release
 Red Hat Enterprise Linux AS release 4 (Nahant Update 6)
 $ svn --version --quiet

 $ cat /etc/redhat-release
 Red Hat Enterprise Linux Server release 5.2 (Tikanga)
 $ svn --version --quiet

The issue I am having is that running a Subversion command with svn-1.4.2 modifies the .svn "Working Copy Administration Area" files so that svn-1.3.2 no longer works:

 $ svn status
 svn: This client is too old to work with working copy '.'; please get a newer Subversion client

I know that for most users updating the administration files is probably the correct behavior most of the time. However, for me it is annoying, since an accidental "svn" on the wrong machine invalidates the .svn administration files for the machines I spend most of my time on.

What I would like is some value I could add to my ~/.subversion/config file that would prevent the automatic conversion of the .svn administration files to the newer format. I would prefer the svn-1.4.2 commands to fail with an appropriate message. There should be an explicit command I could give to svn to have it modify the .svn administration files to the newer version.



To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-07-02 22:36:22 CEST

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.