RE: svn 1.8 causing locks to be broken on update
From: Bert Huijben <bert_at_qqmail.nl>
Date: Thu, 15 Aug 2013 10:19:07 +0200
Do you have access to the repository configuration at the server?
Things we are most interested in is how exactly your authentication is setup. E.g. do you allow anonymous acces, and if yes in what way?
Posting your server configuration (with passwords and private information changed) would really help.
I don’t think the serf debug log is really giving much more information here, as there are (as far as I can tell) no requests that fail. The default server side logging (if not disabled) provides most likely more than enough information to look into this.
Last night (EU time) we spend some time with different scenarios in an attempt to reproduce your issue, but we were unable to.
From: Felipe Alvarez [mailto:felipe.alvarez_at_gmail.com]
As of 1.8 SVN only uses the serf library for http communication, and
Unfortunately there is no runtime-switch (yet) to enable debug output
You can enable debug logging with serf by rebuilding (see ).
With your combined input, this issue really starts to look like a
To double check that it's serf-related, perhaps one of you could try
Perhaps it's time to open an issue in the issue tracker for this.
Subversion client 1.7 using serf cause the lock to break! But it does not break when using neon (default)
C:\tmp>svn --username will --password will co http://svntest.freshcomp.com.au/svn/repos --config-option servers:global:http-library=serf wc
C:\tmp\wc\Trunk\Lettus\lbin>svn lock test.txt --config-option servers:global:http-library=serf
C:\tmp\wc\Trunk\Lettus\lbin>svn st --config-option servers:global:http-library=serf
Updated to revision 4.
C:\tmp\wc>svn st --config-option servers:global:http-library=serf
-- FelipeReceived on 2013-08-15 10:20:05 CEST
This is an archived mail posted to the Subversion Users mailing list.