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

Re: locking a file renders repos unusable with older clients

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2005-03-28 19:44:32 CEST

Ben Collins-Sussman <sussman@collab.net> wrote on 03/28/2005 12:20:50 PM:

> After another hour of discussion, cmpilato, fitz and I are in favor of
> this idea.
> What we'd like to see:
> * upgrading to 1.2 libraries doesn't make locking appear, doesn't
> affect existing repositories in any way. Attempts to use locking APIs
> against the repository result in unsupported-feature errors.
> * admin runs 'svnadmin upgrade', which:
> - bumps the repos format number (thus blocking older ra_local
> clients)
> - creates 4 new locking-related hook templates
> * subsequent attempts to use locking APIs against the repository are

> successful; the fs implementations notice that the the format number
> is "high enough", and therefore auto-create the new locking tables
> and/or dirs.

Sounds good.

What is the behavior of svnadmin create? Does it create a repository with
locking enabled, or do you still have to run svnadmin upgrade?


Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Mar 28 19:46:12 2005

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

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