Re: svnsync problems

2015-02-21 Thread Tony Sweeney
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

Re: svnsync problems

2015-02-20 Thread Nico Kadel-Garcia
> 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

Re: svnsync problems

2015-02-20 Thread Branko Čibej
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

Re: svnsync problems

2015-02-20 Thread Nico Kadel-Garcia
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

Re: svnsync problems

2015-02-20 Thread Philip Martin
"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

Re: svnsync problems

2015-02-20 Thread Andreas Stieger
> 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

Re: svnsync problems

2015-02-20 Thread Philip Martin
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