Hi,
We're looking to use Subversion to replace VSS (doesn't
everyone say that?). Regardless of whether I can resolve
the philosophical battles over exclusive locking, we will
need the locking to work for binary files, e.g. Word
documents, etc.
I saw a reference to the problem that I'm having:
> Using Tortoise SVN 1.20 and Subversion 1.20rc2 I keep getting
> "incomplete lock data returned" in the box when I try to get a
> lock on a file.
And the corresponding reply:
> Show us a transcript. Or better yet, try it with 1.2.0-rc3.
At the time, I thought "Great! I'm using rc2!". Problem is,
I went to the current revision, rc4, and am having the exact
same problem.
Since 'svn lock' doesn't support --verbose, a transcript is
not particularly illuminating:
[toolset@svn test]$ svn lock d
svn: Incomplete lock data returned
I've spent some time in the debugger, but the flow is not
something that's easy to pop in and follow.
Anyone else seeing this and/or have any pointer about where
to look to track this one down? The Apache logs are not
particularly illuminating (I'm using http to access the
Subversion repository), and there's no other logs that I
can find.
- [17:05:06] "PROPFIND /svn/test/d HTTP/1.1" 207 644
- [17:05:06] "PROPFIND /svn/test/!svn/vcc/default HTTP/1.1" 207 398
- [17:05:06] "PROPFIND /svn/test/!svn/bln/2 HTTP/1.1" 207 449
- [17:05:06] "LOCK /svn/test/d HTTP/1.1" 401 578
toolset [17:05:06] "LOCK /svn/test/d HTTP/1.1" 200 371
Perhaps there's some hidden way to turn on Double Secret Logging
in either the client or the Apache modules? The thing is, I'm
inclined to think it's not really a problem, just a mismatch
somewhere, as the lock *seems* to complete correctly, it just
returns that bogus error message.
Other commands work just dandy, it's just lock that's choking.
thanks,
-burt
David Bryant wrote:
> Hi,
>
> I have noticed an issue with svn move on a working/local copy. It
> will produce the following output:
>
> svn: Working copy 'dir1/testing/testing' is missing or not
> locked
>
> However, if you run the same command directly against the repository,
> it work fine. The only case where this seems to happen is when you are
> trying to move one directory that has the same directory name two names
> deep to another directory. Example:
>
> dir1/
> testing/testing/README
>
> svn move testing/ dir1/
> svn: Working copy 'dir1/testing/testing' is missing or not
> locked
>
> Has anyone else run into this?
>
> Thanks,
> Dave
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue May 31 23:14:37 2005