[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn 1.8 causing locks to be broken on update

From: Felipe Alvarez <felipe.alvarez_at_gmail.com>
Date: Fri, 6 Sep 2013 10:06:17 +1000

I have upgraded my tortoiseSVN to 1.8.2 which includes svn version 1.8.3
(r1516576). The problem is still there (locks broken on update).

I have not seen any progress on the bug report <
http://subversion.tigris.org/issues/show_bug.cgi?id=4412>

Cheers,
Felipe

On Fri, Aug 23, 2013 at 11:21 AM, Felipe Alvarez
<felipe.alvarez_at_gmail.com>wrote:

>
>
>
> Johan Corveleyn <jcorvel_at_gmail.com> writes:
>>
>> > Now, playing "user's advocate": is there still something useful to do
>> > here? I.e. apparently ra_neon worked fine with the broken servers.
>> > Should ra_serf also be able to handle this, so 1.8 clients can still
>> > work fine with servers < 1.6.17?
>>
>> It appears to be related to a path handling bug in code that is supposed
>> to handle old servers, the obvious fix makes the problem worse. I've
>> raised http://subversion.tigris.org/issues/show_bug.cgi?id=4412
>>
>> --
>> Philip Martin | Subversion Committer
>> WANdisco // *Non-Stop Data*
>>
>
> Hi Philip
>
> How is this bug fix progressing?
>
>
> Cheers,
> Felipe
>
>
Received on 2013-09-06 02:07:31 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.