Re: svnserve crashes in libdispatch on OS X Mavericks (10.9) server

2013-11-02 Thread Ryan Schmidt
On Nov 3, 2013, at 01:45, Ben Reser wrote: > On 11/2/13 11:03 PM, Ryan Schmidt wrote: >> He already reported the problem to us at MacPorts. We told him to report it >> here because we don’t think it’s a MacPorts-specific problem. >> >> https://trac.macports.org/ticket/41112 > > Thanks for the r

Re: svnserve crashes in libdispatch on OS X Mavericks (10.9) server

2013-11-02 Thread Ben Reser
On 11/2/13 11:03 PM, Ryan Schmidt wrote: > He already reported the problem to us at MacPorts. We told him to report it > here because we don’t think it’s a MacPorts-specific problem. > > https://trac.macports.org/ticket/41112 Thanks for the reference. If it's not reproducible in general for peo

Re: svnserve crashes in libdispatch on OS X Mavericks (10.9) server

2013-11-02 Thread Ryan Schmidt
On Nov 3, 2013, at 00:25, Ben Reser wrote: > On 11/1/13 12:52 PM, Tony Piselli wrote: >> Upgraded to 10.9 server and reinstalled macports (2.2.1) and subversion, >> version 1.8.4. Can't use subversion locally or with svnserve from another >> client. Here's the svnserve crash report: > > I thin

Re: svnserve crashes in libdispatch on OS X Mavericks (10.9) server

2013-11-02 Thread Ben Reser
On 11/1/13 12:52 PM, Tony Piselli wrote: > Upgraded to 10.9 server and reinstalled macports (2.2.1) and subversion, > version 1.8.4. Can't use subversion locally or with svnserve from another > client. Here's the svnserve crash report: I think you should report this to macports. I built 1.8.4 o

Re: Corrupted Repository

2013-11-02 Thread Thorsten Schöning
Guten Tag Vincent QB, am Samstag, 2. November 2013 um 23:15 schrieben Sie: > The problems appear starting with the version of subversion in > Ubuntu 13.10 (version 1.7.9 along with 1.8.4). If I go back to > Ubuntu 13.04 (version 1.7.5), the problems disappear. I was able to > create a new dump. Ho

Re: IPv6 URL support in SVN? v1.8.4 works with IPv4, not with IPv6

2013-11-02 Thread Ben Reser
On 11/2/13 10:48 AM, d...@sent.com wrote: > reading @ > > @ > > http://www.wandisco.com/svnforum/threads/54273-svn-error-when-checkout-from-ipv6-url > > IPv6 support is (?) in svn v>1.8 That post is actually not particularly helpful. It looks like there was a regression at some poi

Re: Corrupted Repository

2013-11-02 Thread Vincent QB
Hello again, The problems appear starting with the version of subversion in Ubuntu 13.10 (version 1.7.9 along with 1.8.4). If I go back to Ubuntu 13.04 (version 1.7.5), the problems disappear. I was able to create a new dump. However, it crashes in the same way when loading in Ubuntu 13.10. Could

Re: IPv6 URL support in SVN? v1.8.4 works with IPv4, not with IPv6

2013-11-02 Thread darx
> suggest you take that question to the APR developers; it's > d...@apr.apache.org. done, @ http://www.mail-archive.com/dev%40apr.apache.org/msg25430.html thx!

Re: IPv6 URL support in SVN? v1.8.4 works with IPv4, not with IPv6

2013-11-02 Thread darx
On Sat, Nov 2, 2013, at 01:09 PM, Branko Čibej wrote: > Also, which version of APR you're using (and how it was compiled) is > fairly important. You can determine the former by running the command > > svn --version --verbose > > with the 1.8.x client, or > > apr-1-config --version > > a

Re: IPv6 URL support in SVN? v1.8.4 works with IPv4, not with IPv6

2013-11-02 Thread Branko Čibej
On 02.11.2013 21:06, d...@sent.com wrote: > On Sat, Nov 2, 2013, at 10:55 AM, Mark Phippard wrote: >> I believe support for IPv6 in the SVN client is based solely on how the >> APR library was compiled. It has to have IPv6 support compiled in as it >> does the TCP connections etc. > It appears to b

Re: IPv6 URL support in SVN? v1.8.4 works with IPv4, not with IPv6

2013-11-02 Thread Branko Čibej
On 02.11.2013 20:00, Dave Huang wrote: > On Nov 2, 2013, at 12:48, d...@sent.com wrote: > >> With my resolvers set to IPv6 >> >> cat /etc/resolv.conf >> nameserver 2600:3c01::2 >> nameserver 2600:3c01::3 >> options rotate >> in short, 'everything' IPv6 w

Re: IPv6 URL support in SVN? v1.8.4 works with IPv4, not with IPv6

2013-11-02 Thread darx
On Sat, Nov 2, 2013, at 10:55 AM, Mark Phippard wrote: > I believe support for IPv6 in the SVN client is based solely on how the > APR library was compiled. It has to have IPv6 support compiled in as it > does the TCP connections etc. It appears to be a problem with SVN's ability to name-resolve,

Re: How to determine subversion repository format

2013-11-02 Thread Branko Čibej
On 02.11.2013 18:11, Bradley Giesbrecht wrote: > On Nov 1, 2013, at 10:46 AM, Bob Archer wrote: > >>> I am getting this svn client message: >>> The working copy at >>> is too old (format 29) to work with client version '1.8.4 (r1534716)' >>> (expects >>> format 31). You need to upgrade the workin

Re: IPv6 URL support in SVN? v1.8.4 works with IPv4, not with IPv6

2013-11-02 Thread Dave Huang
On Nov 2, 2013, at 12:48, d...@sent.com wrote: > With my resolvers set to IPv6 > > cat /etc/resolv.conf > nameserver 2600:3c01::2 > nameserver 2600:3c01::3 > options rotate > in short, 'everything' IPv6 works here ... except for subversion, FWIW

Re: IPv6 URL support in SVN? v1.8.4 works with IPv4, not with IPv6

2013-11-02 Thread Mark Phippard
I believe support for IPv6 in the SVN client is based solely on how the APR library was compiled. It has to have IPv6 support compiled in as it does the TCP connections etc. > On Nov 2, 2013, at 1:48 PM, d...@sent.com wrote: > > With my resolvers set to IPv6 > >cat /etc/resolv.conf >

IPv6 URL support in SVN? v1.8.4 works with IPv4, not with IPv6

2013-11-02 Thread darx
With my resolvers set to IPv6 cat /etc/resolv.conf nameserver 2600:3c01::2 nameserver 2600:3c01::3 options rotate lookups work dig Awww.nlnetlabs.nl +short 213.154.224.1 dig Agit.varnish-cache.o

Re: How to determine subversion repository format

2013-11-02 Thread Bradley Giesbrecht
On Nov 1, 2013, at 10:46 AM, Bob Archer wrote: >> I am getting this svn client message: >> The working copy at >> is too old (format 29) to work with client version '1.8.4 (r1534716)' >> (expects >> format 31). You need to upgrade the working copy first. >> >> I am interested in knowing where "