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

RE: Locking & V1.4

From: Shakespeare, Simon \(Pensions\) <Simon.Shakespeare_at_capita.co.uk>
Date: 2006-09-18 17:41:58 CEST

> -----Original Message-----
> From: Mark Phippard [mailto:markp@softlanding.com]
> Sent: 18 September 2006 16:20
> To: Shakespeare, Simon (Pensions)
> Cc: users@subversion.tigris.org
> Subject: Re: Locking & V1.4
>
>
> "Shakespeare, Simon \(Pensions\)"
> <Simon.Shakespeare@capita.co.uk> wrote
> on 09/18/2006 11:14:11 AM:
>
> > Hi - Can anyone tell me if locking has changed in the latest 1.4
> release.
> > I guess it has as I'm no longer able to do "svn help lock"
> this gives
> > "unknown command".
> > I can't find any documentation on what's changed - If I try to lock
> > a file via my client (Tortoise) I get "server doesn't
> support the lock
> command".
> > The repository was created using the latest release i.e. 1.4 & the
> > server was started using svnserve -d -r /pathtorep.
> >
> > Thanks for any help & can you cc me in on any replies - Simon
>
> I just tried it with the Windows 1.4 binaries and it worked:
>
> C:\svn-win32-1.4.0\bin>svn help lock
> lock: Lock working copy paths or URLs in the repository, so that
> no other user can commit changes to them.
> usage: lock TARGET...
>
> Use --force to steal the lock from another user or working copy.
>
> Valid options:
> --targets arg : pass contents of file ARG as
> additional args
> -m [--message] arg : specify lock comment ARG
> -F [--file] arg : read lock comment from file ARG
> --force-log : force validity of log message source
> --encoding arg : treat value as being in charset
> encoding ARG
> --username arg : specify a username ARG
> --password arg : specify a password ARG
> --no-auth-cache : do not cache authentication tokens
> --non-interactive : do no interactive prompting
> --config-dir arg : read user configuration files
> from directory
> ARG
> --force : force operation to run
>
> Are you sure a pre 1.2 version of the binaries is not in your PATH or
> something? Try svn --version.
>
> Mark
>
Thanks Mark - It's *nix but I think that you might be right.
I also have the installation for v1.3 in my path while I test out 1.4.
I've fiddled about with paths & such like & re-started the server but I
still get the problem. If no one else has this problem then I guess it will
sort itself out when I release to the standard installation directory.
Simon

**********************************************************************************
This email and any files transmitted with it are confidential, and may be subject to legal privilege, and are intended solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error or think you may have done so, you may not peruse, use, disseminate, distribute or copy this message. Please notify the sender immediately and delete the original e-mail from your system.

Computer viruses can be transmitted by e-mail. Recipients should check this e-mail for the presence of viruses. The Capita Group and its subsidiaries accept no liability for any damage caused by any virus transmitted by this e-mail.
***********************************************************************************

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Sep 18 17:44:16 2006

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.