[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: Philip Martin <philip.martin_at_wandisco.com>
Date: Thu, 15 Aug 2013 10:41:12 +0100

Felipe Alvarez <felipe.alvarez_at_gmail.com> writes:

>> I'm using a 1.8.x client and a 1.6.x server and I can't reproduce it. I
>> tried this
>>
>> svnadmin create repo --compatible-version 1.6
>> svn co http://localhost:8888/obj/repo wc
>> svn mkdir --parents wc/A/B/C
>> touch wc/A/B/C/f
>> svn add wc/A/B/C/f
>> svn ci -mm wc
>> svn up wc
>> svn lock wc/A/B/C/f
>> cd wc/A
>> svn up
>> cd ..
>> svn up
>> cd ..
>> svn st wc
>>
>> and the final status shows wc/A/B/C/f still locked.
>>
>> --
>> Philip Martin | Subversion Committer
>> WANdisco // *Non-Stop Data*
>>
> ​Hi Philip
>
> Pardon my ignorance. We are using an authentic 1.6.15 client, not a 1.8.1
> in 1.6 "mode" (If I am interpreting your --compatible-version option
> correctly). Further, we are using Apache 2.2 with the following config <
> http://pastebin.com/ZefLnHA9>
>
> We followed the exact same steps as you have, but not localhost, we used a
> remote host. Should it matter?

I have determined that the the lock gets broken when I use a 1.6.16
server but it is not broken when I use a 1.6.17 server. It was fixed by
r1124173.

-- 
Philip Martin | Subversion Committer
WANdisco // *Non-Stop Data*
Received on 2013-08-15 11:41:52 CEST

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