On Tue, Apr 11, 2006 at 12:01:43PM -0700, Justin Erenkrantz wrote:
> On 4/11/06, Malcolm Rowe <malcolm-svn-dev@farside.org.uk> wrote:
> > Er, no. The cleanup comment was just that when the development version
> > errors out (instead of borking the working copy), it exits with a lock on
> > the wc, which isn't strictly necessary (it hasn't actually modified the
> > wc, so it could remove the lock). But it should be a rare occurrence,
> > so I don't see that as a big problem.
>
> If you're intending to use this 'not-WC-upgradable' version, doesn't
> it mean that everytime you see this error that the WC will no longer
> be usable? You won't be able to run cleanup (or any read-only ops)
> with the version you have because it'll need to open the WC, right?
That's true, but it's not a problem. Yes, if I try to run 'svn up' using
a trunk svn on my svn-trunk working copy, it will error and leave a wc
lock around, so I won't be able to access it with a trunk svn until I
clean up the lock (and as you correctly point out, I can't do that with
the trunk svn).
But the reason that I don't want to use a trunk svn on my working copy
is because I've got a 1.3.1 svn installed that I use for my day-to-day
use, and running a write operation on my (format 4) working copy was a
mistake in the first place.
So I unalias svn or fix my PATH (i.e. fix whatever caused me to make
the mistake in the first place), and just run 'svn cleanup' using my
installed 1.3.1 client and continue with my life (versus: work out how
to downgrade my working copy from format 6 to format 4).
Regards,
Malcolm
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Apr 12 10:25:30 2006