SteveKing <steveking@gmx.ch> writes:
> A TSVN user reported that a commit of a property change on a locked
> file which has the svn:needs-lock property doesn't work.
> So I created a reproduction recipe with Subversion 1.2RC2:
>
> working copy, checked out from http:
> folder/file1
>
> inside folder:
> svn propset svn:needs-lock x file1
> svn ci -m ""
> svn lock file1
> svn propset custom:prop custvalue file1
> svn ci -m ""
> sending file1
> svn: commit failed (details follow):
> svn: At least one property change failed; repository is unchanged
>
> This all works with file:/// access, but it fails with http access to
> an 1.2RC2 server on windows XP Home.
Does this error still happen even without the svn:needs-lock propset?
What about without the 'svn lock' command too? I'm wondering if the
name "custom:prop" could be triggering issue #1971.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 6 19:00:43 2005