Re: Erratic Locking Behavior With TortoiseSVN

Larry Walker wrote:

> I’ve run into some strange locking behavior with TortoiseSVN. Server:
> Linux with Subversion 1.2.3 and Apache 2.0.54, Client: WinXP SP2. The
> test files have the needs-lock property set. When locking a file with
> TortoiseSVN, the icon shows the lock and the windows property changes
> from read-only to “writable”, but the file changes can’t be saved –

If the overlay changes, then that means that the "readonly" flag has
been removed. If the file is still not writable, then that would mean
some other program has the file open (virus scanner are known to behave
badly here), or that you don't have the right to write to that file
(NTFS permissions are different from the readonly flag).

> error: “Access to …/file was denied”. Cygwin shows the file is still
> read-only. Doing the same lock/write/commit operations works properly
> from the Cygwin command line. Changing the file to writable with Cygwin
> and doing the rest with TortoiseSVN also works. This strange behavior
> doesn’t occur with a fresh working copy but only after an area has been
> used for a while (sorry there is no better definition of when things go
> bad).

Maybe it's some interference with you using the cygwin svn client
together with TSVN. If you're working on windows, you should use the
windows SVN command line client. Or only the cygwin client and no other
Subversion clients.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
--