On Tue, Aug 22, 2017 at 7:38 PM, Stefan Hett <stefan_at_egosoft.com> wrote:
> Hi Pavel,
> On 8/22/2017 5:44 PM, Pavel Lyalyakin wrote:
>> It seems that I've reproduced a bug:
>> 1. svn lock foo.txt
>> 2. svn rename foo.txt bar.txt
>> 3. svn commit -m MyCommit
>> No errors or other symptoms on client side, but there is an error in
>> Apache logs:
>> No lock on path '/foo.txt' in filesystem 'f8388469-131a-5745-bb04-c2e5033b8b08'
>> (160040) APR does not understand this error code[client 192.168.0.1]
>> Tested with SVN 1.9.7 command line client and mod_dav_svn via HTTP and HTTPS:
>> Subversion 1.8.18
>> Apache HTTP Server 2.4.26
>> (Subversion Edge 5.2.1)
>> Subversion 1.9.7
>> Apache HTTP Server 2.2.34
>> (VisualSVN Server 3.6.4)
>> With best regards,
>> Pavel Lyalyakin
>> VisualSVN Team
> This sounds highly similiar to the issue described in https://issues.apache.org/jira/browse/SVN-2534.
> While the (repro-)case is slightly different (uses pre-commit hooks to demonstrate the problem) to me it sounds like basically the same underlying problem. Do you agree?
> Stefan Hett
I see that both issues are about locks and involve `svn rename` / `svn
move`. However, I'm not sure whether that's the same problem. I do not
understand why the reproduction script in SVN-2534 includes hook
scripts. It seems to me that the reproduction script in SVN-2534 is
overcomplicated and could be reduced. If it really is the same
problem, then my repro could be helpful.
With best regards,
Received on 2017-08-24 17:52:54 CEST