Re: is 'svn lock' possible for replication?

On Sunday 22 Aug 2010, Andy Levy wrote:
> On Sun, Aug 22, 2010 at 14:16, Steven Woody <narkewoody_at_gmail.com> wrote:
> > On 20 August 2010 23:19, Steven Woody <narkewoody_at_gmail.com> wrote:
> >> Hi,
> >>
> >> With a replication/write-through setup, can a user execute 'svn lock'
> >> on master/slaver nodes? Thanks.
> >
> > Hey folks, no one can gives me a hint?
>
> You asked at the beginning of a weekend and no one is obligated to
> reply within a set timeframe (or at all, for that matter). If you need
> an answer that fast, it costs you nothing to set up a master/slave
> pair to test it for yourself (and you'd be done by now if you'd
> started Friday).

I mentioned in your previous thread their isn't support in svnsync and this
would require a third party script to maintain the locks. I've not looked
into it further though. To answer your specific question, yes. A user can
issue a svn lock on a write through setup, but it won't work in a consistent
and symmetric manner.

The results may differ as I have a 1.4 master repository and a 1.6.12 write
through mirror but locks on the master will not be passed through to the
mirror. Further, trying to force a lock/unlock fails as the mirror does not
think the file is locked but when trying to obtain a lock it will still fail
because it is locked.

If a lock on the mirror is obtained then the master can see it but it's in a
strange state depending on whether the -u flag is used when running svn
status.

#svn status svn-proxy
     K svn-proxy/test.xml

#svn status -u svn-proxy
     B 70801 svn-proxy/test.xml

#svn status -u svn-server
     O 70801 svn-server/test.xml

-- 
__________________________________________________________________________________
Sword Ciboodle is the trading name of ciboodle Limited (a company 
registered in Scotland with registered number SC143434 and whose 
registered office is at India of Inchinnan, Renfrewshire, UK, 
PA4 9LH) which is part of the Sword Group of companies.
This email (and any attachments) is intended for the named
recipient(s) and is private and confidential. If it is not for you, 
please inform us and then delete it. If you are not the intended 
recipient(s), the use, disclosure, copying or distribution of any 
information contained within this email is prohibited. Messages to 
and from us may be monitored. If the content is not about the 
business of the Sword Group then the message is neither from nor 
sanctioned by us.
Internet communications are not secure. You should scan this
message and any attachments for viruses. Under no circumstances
do we accept liability for any loss or damage which may result from
your receipt of this email or any attachment.
__________________________________________________________________________________