Yes it was solved for me. All I did is build your apache with -enable-
pie option. Without this some special characters will go with lock
files, and during commit your locks will not match.
Thanks
Srini
On Dec 11, 2009, at 7:06 AM, Mark Blokpoel <blokpoelmark_at_hotmail.com>
wrote:
> Hi, I seem to have the same symptoms with my svn setup. Have you had
> any luck solving your problem?
>
> I recently migrated two (large) repositories from one server to
> another. Now users cannot commit files they have locked. Only by
> unlocking the files they can commit. The error message we receive is
> below. I suspect something is preventing subversion to modify the
> locks even when the committer is the lock's owner. Any help is
> greatly appreciated, because I'm out of ideas...
>
> Description : An error occurred while contacting the repository.
> Suggestion : The server may be unreachable or the URL may be
> incorrect.
>
> Description : Commit failed (details follow):
> Status : 175002
> File : subversion/libsvn_client/commit.c, 867
>
> Description : CHECKOUT of '/svn/programmers/testrepo/!svn/ver/1/
> test.txt': Could not read status line: Secure connection truncated
> Status : 175002
> File : subversion/libsvn_ra_neon/util.c, 604
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2429762
Please start new threads on the <users_at_subversion.apache.org> mailing list.
To subscribe to the new list, send an empty e-mail to <users-subscribe_at_subversion.apache.org>.
Received on 2009-12-11 13:37:08 CET