On 02/20/15 10:21, Philip Martin wrote:
You are making things very hard for yourself by running 1.6.11, it is
very old and no longer maintained, unless your distribution is
backporting fixes. A newer version will have fewer bugs and better
performance.
You'll get no disagreement from me on tha
> On Feb 20, 2015, at 8:21, Branko Čibej wrote:
>
>> On 20.02.2015 13:59, Nico Kadel-Garcia wrote:
>> On Fri, Feb 20, 2015 at 5:50 AM, Philip Martin
>> wrote:
>>> "Andreas Stieger" writes:
>>>
In addition to what Philip wrote, for initializing a sync to a target
created via hotcopy
On 20.02.2015 13:59, Nico Kadel-Garcia wrote:
> On Fri, Feb 20, 2015 at 5:50 AM, Philip Martin
> wrote:
>> "Andreas Stieger" writes:
>>
>>> In addition to what Philip wrote, for initializing a sync to a target
>>> created via hotcopy, you will find "svnsync init --allow-non-empty"
>>> very useful
On Fri, Feb 20, 2015 at 5:50 AM, Philip Martin
wrote:
> "Andreas Stieger" writes:
>
>> In addition to what Philip wrote, for initializing a sync to a target
>> created via hotcopy, you will find "svnsync init --allow-non-empty"
>> very useful.
>
> But only after upgrading as that is not present i
"Andreas Stieger" writes:
> In addition to what Philip wrote, for initializing a sync to a target
> created via hotcopy, you will find "svnsync init --allow-non-empty"
> very useful.
But only after upgrading as that is not present in 1.6.
--
Philip Martin | Subversion Committer
WANdisco // *No
> Tony Sweeney writes:
> > running under Apache. I set the svn:sync-last-merged-rev revprop on
> > r0 to reflect the newest revision on the hotcopy.
In addition to what Philip wrote, for initializing a sync to a target created
via hotcopy, you will find "svnsync init --allow-non-empty" very u
You are making things very hard for yourself by running 1.6.11, it is
very old and no longer maintained, unless your distribution is
backporting fixes. A newer version will have fewer bugs and better
performance.
1.6 has a hotcopy bug
http://subversion.tigris.org/issues/show_bug.cgi?id=3596
t
Hi,
Mise en scene:
We have three Subversion servers, version 1.6.11 running on CentOS6.
One is the live master and and the others are hot standbys in different
datacenters. The intent is that these are kept in sync with the master
using svnsync from a post-commit hook. One of the slaves is a
