Re: 1.8.x backport issue #4476 - svnsync with r0 mergeinfo - resolve the veto

2015-02-13 Thread Philip Martin
Philip Martin writes: > Julian Foad writes: > >> Hi Philip. I've updated the 1.8.x nomination of issue #4476 - svnsync >> with r0 mergeinfo - to resolve the concern that's the subject of your >> veto. Please could you review and remove your veto if >> possible. Thanks. > > The new test, svnsync_

RE: svn commit: r1659553 - /subversion/trunk/subversion/libsvn_wc/update_editor.c

2015-02-13 Thread Bert Huijben
> -Original Message- > From: i...@apache.org [mailto:i...@apache.org] > Sent: vrijdag 13 februari 2015 14:27 > To: comm...@subversion.apache.org > Subject: svn commit: r1659553 - > /subversion/trunk/subversion/libsvn_wc/update_editor.c > > Author: ivan > Date: Fri Feb 13 13:26:53 2015 > Ne

Re: 1.8.x backport issue #4476 - svnsync with r0 mergeinfo - resolve the veto

2015-02-13 Thread Philip Martin
Julian Foad writes: > Hi Philip. I've updated the 1.8.x nomination of issue #4476 - svnsync > with r0 mergeinfo - to resolve the concern that's the subject of your > veto. Please could you review and remove your veto if > possible. Thanks. The new test, svnsync_tests.py 30, is a FAIL. -- Phili

Document svn:auto-props on 'svn help propset'

2015-02-13 Thread Bert Huijben
Would something like [[ Index: subversion/svn/svn.c === --- subversion/svn/svn.c(revision 1659683) +++ subversion/svn/svn.c(working copy) @@ -1424,6 +1424,12 @@ " directory:\n" "svn:ignore - A l

pin-externals fails to handle spaces properly

2015-02-13 Thread Stefan Kueng
Hi, While trying out the new 'pin externals' feature, I found a problem: if the external definition has spaces in them for the local path, something like this: ^/branches/test1 'ext with spaces' then that will get changed to ^/branches/test1@1234 ext with spaces which basically breaks the e

Re: 1.7.x backport r1643074 - load with invalid mergeinfo - resolve the veto

2015-02-13 Thread Ben Reser
On 2/13/15 10:07 AM, Julian Foad wrote: > Ben, you currently have a veto recorded against 1.7.x backport r1643074 - > load with invalid mergeinfo: > > > * r1643074 >Don't let invalid mergeinfo stop 'svnadmin load' from working. > Part of issue #4476 "Mergeinfo containing r0 makes svns

1.8.x backport issue #4476 - svnsync with r0 mergeinfo - resolve the veto

2015-02-13 Thread Julian Foad
Hi Philip. I've updated the 1.8.x nomination of issue #4476 - svnsync with r0 mergeinfo - to resolve the concern that's the subject of your veto. Please could you review and remove your veto if possible. Thanks. - Julian

1.7.x backport r1643074 - load with invalid mergeinfo - resolve the veto

2015-02-13 Thread Julian Foad
Ben, you currently have a veto recorded against 1.7.x backport r1643074 - load with invalid mergeinfo:   * r1643074    Don't let invalid mergeinfo stop 'svnadmin load' from working. Part of issue #4476 "Mergeinfo containing r0 makes svnsync and svnadmin dump fail".    Justification:   

Re: svn commit: r1659013 - /subversion/trunk/subversion/libsvn_subr/dso.c

2015-02-13 Thread Ivan Zhakov
On 13 February 2015 at 18:54, Philip Martin wrote: > Philip Martin writes: > >> Ivan Zhakov writes: >> >>> This API is present from Subversion 1.2, so I suggest add call to >>> svn_dso_initialize2() in svn_ra_initialize()/svn_fs_inialize(): do you >>> have any objections against this approach? >

Re: svn commit: r1659013 - /subversion/trunk/subversion/libsvn_subr/dso.c

2015-02-13 Thread Philip Martin
Philip Martin writes: > Ivan Zhakov writes: > >> This API is present from Subversion 1.2, so I suggest add call to >> svn_dso_initialize2() in svn_ra_initialize()/svn_fs_inialize(): do you >> have any objections against this approach? > > Yes, that sounds like a good idea. No objections. And,

Re: svn commit: r1659013 - /subversion/trunk/subversion/libsvn_subr/dso.c

2015-02-13 Thread Philip Martin
Ivan Zhakov writes: > This API is present from Subversion 1.2, so I suggest add call to > svn_dso_initialize2() in svn_ra_initialize()/svn_fs_inialize(): do you > have any objections against this approach? Yes, that sounds like a good idea. -- Philip Martin | Subversion Committer WANdisco // *

Re: svn commit: r1659013 - /subversion/trunk/subversion/libsvn_subr/dso.c

2015-02-13 Thread Ivan Zhakov
On 12 February 2015 at 21:28, Philip Martin wrote: > Ivan Zhakov writes: > >> As far I understand out testsuite still may fail in some rare >> circumstances with --parallel option, until we add >> svn_dso_initialize2(). It's bad when tests are failing sometimes. > > I just seen a failure and it r

Re: Minimum Python requirement for autogen.sh?

2015-02-13 Thread Branko Čibej
On 13.02.2015 11:25, Daniel Shahaf wrote: > The attached patch makes autogen.sh support Python 3. However, it > increases the minimal Python requirement from 2.5 to 2.6 for people who > run autogen.sh or build on Windows. The minimum Python required for > 'make check' on Unix is unaffected and re

Re: svn commit: r1659426 - /subversion/trunk/subversion/libsvn_subr/sqlite.c

2015-02-13 Thread Branko Čibej
On 12.02.2015 23:42, i...@apache.org wrote: > Author: ivan > Date: Thu Feb 12 22:42:35 2015 > New Revision: 1659426 > > URL: http://svn.apache.org/r1659426 > Log: > Use journal_mode = TRUNCATE for sqlite [1] instead of default DELETE value. > It makes svn checkout about 10% faster on Windows at ex

Re: Aw: Status of ctypes-python bindings

2015-02-13 Thread Branko Čibej
On 13.02.2015 13:30, Julian Foad wrote: > Andreas Stieger wrote: >> Branko Čibej wrote: >>> I've been looking at the ctypes-based Python bindings. They're barely >>> maintained; the only changes in the last two years seem to have been >>> minor tweaks to make the tests run. I'm also not aware of an

Re: Aw: Status of ctypes-python bindings

2015-02-13 Thread Julian Foad
Andreas Stieger wrote: > Branko Čibej wrote: >> I've been looking at the ctypes-based Python bindings. They're barely >> maintained; the only changes in the last two years seem to have been >> minor tweaks to make the tests run. I'm also not aware of anyone using >> them, or any packager bundling t

RE: Minimum Python requirement for autogen.sh?

2015-02-13 Thread Bert Huijben
> -Original Message- > From: Daniel Shahaf [mailto:d...@daniel.shahaf.name] > Sent: vrijdag 13 februari 2015 11:25 > To: dev@subversion.apache.org > Subject: Minimum Python requirement for autogen.sh? > > The attached patch makes autogen.sh support Python 3. However, it > increases the

Minimum Python requirement for autogen.sh?

2015-02-13 Thread Daniel Shahaf
The attached patch makes autogen.sh support Python 3. However, it increases the minimal Python requirement from 2.5 to 2.6 for people who run autogen.sh or build on Windows. The minimum Python required for 'make check' on Unix is unaffected and remains 2.5. Python 2.6 was released in 2008, aka,

Aw: Re: svn commit: r1659397 - in /subversion/trunk: TODO build/ac-macros/swig.m4

2015-02-13 Thread Andreas Stieger
Hi, > Gesendet: Donnerstag, 12. Februar 2015 um 21:59 Uhr > Von: "Branko Čibej" > An: dev@subversion.apache.org > Betreff: Re: svn commit: r1659397 - in /subversion/trunk: TODO > build/ac-macros/swig.m4 > > On 12.02.2015 21:55, br...@apache.org wrote: > > Author: brane > > Date: Thu Feb 12 20:55

Aw: Status of ctypes-python bindings

2015-02-13 Thread Andreas Stieger
Hi, Branko Čibej wrote: > I've been looking at the ctypes-based Python bindings. They're barely > maintained; the only changes in the last two years seem to have been > minor tweaks to make the tests run. I'm also not aware of anyone using > them, or any packager bundling them. > > This was an in