You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Kris <kr...@theendless.org> on 2008/04/14 17:50:55 UTC
svnsync failure - possible bug with report
Hi guys,
I'm experiencing a problem syncing a svn repository. I've done the
requisite searching on google and through the users archive and have
not found anything that might help me out so here's my problem. I've
obfuscated the paths for obvious reasons.
> svnsync synchronize https://XXXX.XXXX/repository --username sync
...
svnsync: Error running context: APR does not understand this error code
free(): invalid pointer 0x806a4f8!
That's the error I get at some point well in to the initial sync
process. The error log from the apache server is:
Could not CHECKOUT resource /XXXX/!svn/ver/1236/XXX/XXX/XXX/XXX/XXX/
aux_/main.c. [409, #0]
Unable to fetch the node revision id of the version resource within
the revision. [409, #160013]
Information for both servers:
svn version 1.4.6
apache version 2.2.8
neon version 0.26.1
openssl 0.9.8g
If there is anything else that you might need, please feel free to
ask. Any help is appreciated.
Thanks,
Kris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svnsync failure - possible bug with report
Posted by Kris <kr...@theendless.org>.
Erik,
Ok, In light of your advice I've wiped out the /usr/local/lib
directory so there were no svn libraries. Then I did:
make distclean
./configure '--with-ssl' '--with-apr=/services/apache-svn' '--with-apr-
util=/services/apache-svn' '--with-apxs=/services/apache-svn/bin/apxs'
'--with-swig'
make && make swig-py
make install && make install-swig-py
svn co https://XXX.XXXX.XXX/repository/project - > Works perfect with
SSL
However, trac fails with the standard Warning: Can't synchronize with
the repository (Unsupported version control system "svn". Check that
the Python support libraries for "svn" are correctly installed.).
I then did:
Python 2.5.2 (r252:60911, Apr 8 2008, 12:45:11)
[GCC 4.0.2 20050901 (prerelease) (SUSE Linux)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from svn import core
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/local/lib/svn-python/svn/core.py", line 19, in <module>
from libsvn.core import *
File "/usr/local/lib/svn-python/libsvn/core.py", line 7, in <module>
import _core
ImportError: /usr/local/lib/libsvn_ra_neon-1.so.0: undefined symbol:
SSL_pending
>>>
Trac is still not happy - I'm totally lost.
Any ideas?
Kris
On 23-Apr-08, at 3:59 PM, Erik Huelsmann wrote:
> On Thu, Apr 17, 2008 at 11:18 PM, Kris <kr...@theendless.org> wrote:
>> One last thing:
>>
>> ldd -r /usr/local/lib/libsvn_ra_dav-1.so.0
>> linux-gate.so.1 => (0xffffe000)
>> libsvn_delta-1.so.0 => /usr/local/lib/libsvn_delta-1.so.0
>> (0x40034000)
>> libsvn_subr-1.so.0 => /usr/local/lib/libsvn_subr-1.so.0
>> (0x4003d000)
>> libaprutil-1.so.0 => /services/apache-svn/lib/
>> libaprutil-1.so.0
>> (0x40067000)
>> libexpat.so.0 => /usr/lib/libexpat.so.0 (0x4007d000)
>> libapr-1.so.0 => /services/apache-svn/lib/libapr-1.so.0
>> (0x4009d000)
>> librt.so.1 => /lib/tls/librt.so.1 (0x400c0000)
>> libcrypt.so.1 => /lib/libcrypt.so.1 (0x400c9000)
>> libpthread.so.0 => /lib/tls/libpthread.so.0 (0x400fc000)
>> libdl.so.2 => /lib/libdl.so.2 (0x4010e000)
>> libz.so.1 => /lib/libz.so.1 (0x40112000)
>> libc.so.6 => /lib/tls/libc.so.6 (0x40125000)
>> libsqlite3.so.0 => /usr/local/lib/libsqlite3.so.0 (0x40246000)
>> /lib/ld-linux.so.2 (0x80000000)
>>
>> No unresolved dependancies there.
>
> Right, but I don't think libsvn_ra_dav is directly built against
> OpenSSL (from which the error seems to come). It should be linked
> against libneon, which is linked either to OpenSSL or GnuTLS.
>
> However, if you built a recent trunk version, you shouldn't have a
> libsvn_ra_dav anymore: it's been renamed to libsvn_ra_neon. Having an
> old lib lying around could explain any number of weird problems.
>
> Could you have a close look at it again, please?
>
> Bye,
>
> Erik.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svnsync failure - possible bug with report
Posted by Erik Huelsmann <eh...@gmail.com>.
On Thu, Apr 17, 2008 at 11:18 PM, Kris <kr...@theendless.org> wrote:
> One last thing:
>
> ldd -r /usr/local/lib/libsvn_ra_dav-1.so.0
> linux-gate.so.1 => (0xffffe000)
> libsvn_delta-1.so.0 => /usr/local/lib/libsvn_delta-1.so.0
> (0x40034000)
> libsvn_subr-1.so.0 => /usr/local/lib/libsvn_subr-1.so.0 (0x4003d000)
> libaprutil-1.so.0 => /services/apache-svn/lib/libaprutil-1.so.0
> (0x40067000)
> libexpat.so.0 => /usr/lib/libexpat.so.0 (0x4007d000)
> libapr-1.so.0 => /services/apache-svn/lib/libapr-1.so.0 (0x4009d000)
> librt.so.1 => /lib/tls/librt.so.1 (0x400c0000)
> libcrypt.so.1 => /lib/libcrypt.so.1 (0x400c9000)
> libpthread.so.0 => /lib/tls/libpthread.so.0 (0x400fc000)
> libdl.so.2 => /lib/libdl.so.2 (0x4010e000)
> libz.so.1 => /lib/libz.so.1 (0x40112000)
> libc.so.6 => /lib/tls/libc.so.6 (0x40125000)
> libsqlite3.so.0 => /usr/local/lib/libsqlite3.so.0 (0x40246000)
> /lib/ld-linux.so.2 (0x80000000)
>
> No unresolved dependancies there.
Right, but I don't think libsvn_ra_dav is directly built against
OpenSSL (from which the error seems to come). It should be linked
against libneon, which is linked either to OpenSSL or GnuTLS.
However, if you built a recent trunk version, you shouldn't have a
libsvn_ra_dav anymore: it's been renamed to libsvn_ra_neon. Having an
old lib lying around could explain any number of weird problems.
Could you have a close look at it again, please?
Bye,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svnsync failure - possible bug with report
Posted by Kris <kr...@theendless.org>.
One last thing:
ldd -r /usr/local/lib/libsvn_ra_dav-1.so.0
linux-gate.so.1 => (0xffffe000)
libsvn_delta-1.so.0 => /usr/local/lib/libsvn_delta-1.so.0
(0x40034000)
libsvn_subr-1.so.0 => /usr/local/lib/libsvn_subr-1.so.0
(0x4003d000)
libaprutil-1.so.0 => /services/apache-svn/lib/libaprutil-1.so.
0 (0x40067000)
libexpat.so.0 => /usr/lib/libexpat.so.0 (0x4007d000)
libapr-1.so.0 => /services/apache-svn/lib/libapr-1.so.0
(0x4009d000)
librt.so.1 => /lib/tls/librt.so.1 (0x400c0000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x400c9000)
libpthread.so.0 => /lib/tls/libpthread.so.0 (0x400fc000)
libdl.so.2 => /lib/libdl.so.2 (0x4010e000)
libz.so.1 => /lib/libz.so.1 (0x40112000)
libc.so.6 => /lib/tls/libc.so.6 (0x40125000)
libsqlite3.so.0 => /usr/local/lib/libsqlite3.so.0 (0x40246000)
/lib/ld-linux.so.2 (0x80000000)
No unresolved dependancies there.
Kris
On 17-Apr-08, at 5:14 PM, Kris wrote:
> Sorry guys - One major correction! I accidently had the wrong error
> in my copy-buffer, they looked so similar that I missed it, however,
> the key difference is in what library this symbol mismatch is
> occuring.
>
> Python 2.5.2 (r252:60911, Apr 8 2008, 12:45:11)
> [GCC 4.0.2 20050901 (prerelease) (SUSE Linux)] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> >>> from svn import core
> Traceback (most recent call last):
> File "<stdin>", line 1, in <module>
> File "/usr/local/lib/svn-python/svn/core.py", line 19, in <module>
> from libsvn.core import *
> File "/usr/local/lib/svn-python/libsvn/core.py", line 5, in <module>
> import _core
> ImportError: /usr/local/lib/libsvn_ra_dav-1.so.0: undefined symbol:
> SSL_pending
>
> The ImportError happens in /usr/local/lib/libsvn_ra_dav-1.so.0
>
> NOT
>
> /usr/local/lib/libsvn_ra_neon-1.so.0
>
> Kris
>
> On 17-Apr-08, at 9:52 AM, Kris wrote:
>
>> Erik,
>>
>> I had to install svn 1.6.0-dev, svnsync the repository to get past
>> the point I was having problems with and then downgrade back to svn
>> 1.4.6 so that trac would continue to work. It's not actually Trac,
>> it's the python bindings (swig-py) that are giving me the problem.
>> It's related to neon and the SSL library, I would assume. I'm
>> getting that all too common error:
>>
>> > python
>> Python 2.5.2 (r252:60911, Apr 8 2008, 12:45:11)
>> [GCC 4.0.2 20050901 (prerelease) (SUSE Linux)] on linux2
>> Type "help", "copyright", "credits" or "license" for more
>> information.
>> >>> from svn import core
>> Traceback (most recent call last):
>> File "<stdin>", line 1, in <module>
>> File "/usr/local/lib/svn-python/svn/core.py", line 19, in <module>
>> from libsvn.core import *
>> File "/usr/local/lib/svn-python/libsvn/core.py", line 7, in <module>
>> import _core
>> ImportError: /usr/local/lib/libsvn_ra_neon-1.so.0: undefined
>> symbol: SSL_pending
>> >>> quit
>>
>> I do a 'make distclean' before I configure and install anything, so
>> we start from scratch every time.
>>
>> On my system I only have 1 version of openssl and it's 0.9.8g. I
>> build neon in its own directory and install it to it's default
>> prefix with the following config options:
>> '--with-ssl=openssl'. Configure finds openssl and compiles cleanly.
>>
>> Then I build the svn trunk with the following configure options: '--
>> with-ssl' '--with-apr=/services/apache-svn' '--with-apr-util=/
>> services/apache-svn' '--with-apxs=/services/apache-svn/bin/apxs' '--
>> with-swig' '--with-neon=/usr/local'. Followed by the standard
>> 'make && make swig-py && make install && make install-swig-py'. It
>> all compiles cleanly and installs.
>>
>> At this point the svn client works with SSL, but the python
>> bindings crap out. If you need any more info, ask away.
>>
>> Kris
>>
>> On 17-Apr-08, at 7:37 AM, Erik Huelsmann wrote:
>>
>>> On 4/16/08, Kris <kr...@theendless.org> wrote:
>>>> Karl,
>>>>
>>>> Thanks so much, that did it. It's too bad that I have to run
>>>> development
>>>> code though. =\
>>>>
>>>> However, running svn 1.6.0-dev did break my trac system =(
>>>
>>> That's a bug: new "code" is supposed to be fully backward compatible
>>> with earlier releases. What was the problem you were experiencing?
>>> (Or
>>> was it a local configuration issue?)
>>>
>>> Bye,
>>>
>>> Erik.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>>> For additional commands, e-mail: users-help@subversion.tigris.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>> For additional commands, e-mail: users-help@subversion.tigris.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svnsync failure - possible bug with report
Posted by Kris <kr...@theendless.org>.
Sorry guys - One major correction! I accidently had the wrong error
in my copy-buffer, they looked so similar that I missed it, however,
the key difference is in what library this symbol mismatch is occuring.
Python 2.5.2 (r252:60911, Apr 8 2008, 12:45:11)
[GCC 4.0.2 20050901 (prerelease) (SUSE Linux)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from svn import core
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/local/lib/svn-python/svn/core.py", line 19, in <module>
from libsvn.core import *
File "/usr/local/lib/svn-python/libsvn/core.py", line 5, in <module>
import _core
ImportError: /usr/local/lib/libsvn_ra_dav-1.so.0: undefined symbol:
SSL_pending
The ImportError happens in /usr/local/lib/libsvn_ra_dav-1.so.0
NOT
/usr/local/lib/libsvn_ra_neon-1.so.0
Kris
On 17-Apr-08, at 9:52 AM, Kris wrote:
> Erik,
>
> I had to install svn 1.6.0-dev, svnsync the repository to get past
> the point I was having problems with and then downgrade back to svn
> 1.4.6 so that trac would continue to work. It's not actually Trac,
> it's the python bindings (swig-py) that are giving me the problem.
> It's related to neon and the SSL library, I would assume. I'm
> getting that all too common error:
>
> > python
> Python 2.5.2 (r252:60911, Apr 8 2008, 12:45:11)
> [GCC 4.0.2 20050901 (prerelease) (SUSE Linux)] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> >>> from svn import core
> Traceback (most recent call last):
> File "<stdin>", line 1, in <module>
> File "/usr/local/lib/svn-python/svn/core.py", line 19, in <module>
> from libsvn.core import *
> File "/usr/local/lib/svn-python/libsvn/core.py", line 7, in <module>
> import _core
> ImportError: /usr/local/lib/libsvn_ra_neon-1.so.0: undefined symbol:
> SSL_pending
> >>> quit
>
> I do a 'make distclean' before I configure and install anything, so
> we start from scratch every time.
>
> On my system I only have 1 version of openssl and it's 0.9.8g. I
> build neon in its own directory and install it to it's default
> prefix with the following config options:
> '--with-ssl=openssl'. Configure finds openssl and compiles cleanly.
>
> Then I build the svn trunk with the following configure options: '--
> with-ssl' '--with-apr=/services/apache-svn' '--with-apr-util=/
> services/apache-svn' '--with-apxs=/services/apache-svn/bin/apxs' '--
> with-swig' '--with-neon=/usr/local'. Followed by the standard 'make
> && make swig-py && make install && make install-swig-py'. It all
> compiles cleanly and installs.
>
> At this point the svn client works with SSL, but the python bindings
> crap out. If you need any more info, ask away.
>
> Kris
>
> On 17-Apr-08, at 7:37 AM, Erik Huelsmann wrote:
>
>> On 4/16/08, Kris <kr...@theendless.org> wrote:
>>> Karl,
>>>
>>> Thanks so much, that did it. It's too bad that I have to run
>>> development
>>> code though. =\
>>>
>>> However, running svn 1.6.0-dev did break my trac system =(
>>
>> That's a bug: new "code" is supposed to be fully backward compatible
>> with earlier releases. What was the problem you were experiencing?
>> (Or
>> was it a local configuration issue?)
>>
>> Bye,
>>
>> Erik.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>> For additional commands, e-mail: users-help@subversion.tigris.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svnsync failure - possible bug with report
Posted by Kris <kr...@theendless.org>.
Erik,
I had to install svn 1.6.0-dev, svnsync the repository to get past the
point I was having problems with and then downgrade back to svn 1.4.6
so that trac would continue to work. It's not actually Trac, it's the
python bindings (swig-py) that are giving me the problem. It's
related to neon and the SSL library, I would assume. I'm getting that
all too common error:
> python
Python 2.5.2 (r252:60911, Apr 8 2008, 12:45:11)
[GCC 4.0.2 20050901 (prerelease) (SUSE Linux)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from svn import core
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/local/lib/svn-python/svn/core.py", line 19, in <module>
from libsvn.core import *
File "/usr/local/lib/svn-python/libsvn/core.py", line 7, in <module>
import _core
ImportError: /usr/local/lib/libsvn_ra_neon-1.so.0: undefined symbol:
SSL_pending
>>> quit
I do a 'make distclean' before I configure and install anything, so we
start from scratch every time.
On my system I only have 1 version of openssl and it's 0.9.8g. I
build neon in its own directory and install it to it's default prefix
with the following config options:
'--with-ssl=openssl'. Configure finds openssl and compiles cleanly.
Then I build the svn trunk with the following configure options: '--
with-ssl' '--with-apr=/services/apache-svn' '--with-apr-util=/services/
apache-svn' '--with-apxs=/services/apache-svn/bin/apxs' '--with-swig'
'--with-neon=/usr/local'. Followed by the standard 'make && make swig-
py && make install && make install-swig-py'. It all compiles cleanly
and installs.
At this point the svn client works with SSL, but the python bindings
crap out. If you need any more info, ask away.
Kris
On 17-Apr-08, at 7:37 AM, Erik Huelsmann wrote:
> On 4/16/08, Kris <kr...@theendless.org> wrote:
>> Karl,
>>
>> Thanks so much, that did it. It's too bad that I have to run
>> development
>> code though. =\
>>
>> However, running svn 1.6.0-dev did break my trac system =(
>
> That's a bug: new "code" is supposed to be fully backward compatible
> with earlier releases. What was the problem you were experiencing? (Or
> was it a local configuration issue?)
>
> Bye,
>
> Erik.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svnsync failure - possible bug with report
Posted by Erik Huelsmann <eh...@gmail.com>.
On 4/16/08, Kris <kr...@theendless.org> wrote:
> Karl,
>
> Thanks so much, that did it. It's too bad that I have to run development
> code though. =\
>
> However, running svn 1.6.0-dev did break my trac system =(
That's a bug: new "code" is supposed to be fully backward compatible
with earlier releases. What was the problem you were experiencing? (Or
was it a local configuration issue?)
Bye,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svnsync failure - possible bug with report
Posted by Kris <kr...@theendless.org>.
Karl,
Thanks so much, that did it. It's too bad that I have to run
development code though. =\
However, running svn 1.6.0-dev did break my trac system =(
thanks again,
Kris
On 16-Apr-08, at 2:35 PM, Karl Fogel wrote:
> Kris <kr...@theendless.org> writes:
>> If there are no recommendations I assume I should be OK posting this
>> to the dev@ list or filing a bug report? I am assuming that this is
>> actually a bug in the svn system. Is this a reasonable assumption?
>
> It does sound like a bug, but before you report it, can you try
> reproducing with the latest trunk svn code? It might be fixed
> already...
>
> Thanks,
> -Karl
>
>> On 14-Apr-08, at 1:50 PM, Kris wrote:
>>
>>> Hi guys,
>>>
>>> I'm experiencing a problem syncing a svn repository. I've done the
>>> requisite searching on google and through the users archive and have
>>> not found anything that might help me out so here's my problem.
>>> I've obfuscated the paths for obvious reasons.
>>>
>>>> svnsync synchronize https://XXXX.XXXX/repository --username sync
>>> ...
>>> svnsync: Error running context: APR does not understand this error
>>> code
>>> free(): invalid pointer 0x806a4f8!
>>>
>>> That's the error I get at some point well in to the initial sync
>>> process. The error log from the apache server is:
>>>
>>> Could not CHECKOUT resource /XXXX/!svn/ver/1236/XXX/XXX/XXX/XXX/XXX/
>>> aux_/main.c. [409, #0]
>>> Unable to fetch the node revision id of the version resource within
>>> the revision. [409, #160013]
>>>
>>> Information for both servers:
>>> svn version 1.4.6
>>> apache version 2.2.8
>>> neon version 0.26.1
>>> openssl 0.9.8g
>>>
>>>
>>> If there is anything else that you might need, please feel free to
>>> ask. Any help is appreciated.
>>>
>>> Thanks,
>>> Kris
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>>> For additional commands, e-mail: users-help@subversion.tigris.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>> For additional commands, e-mail: users-help@subversion.tigris.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svnsync failure - possible bug with report
Posted by Karl Fogel <kf...@red-bean.com>.
Kris <kr...@theendless.org> writes:
> If there are no recommendations I assume I should be OK posting this
> to the dev@ list or filing a bug report? I am assuming that this is
> actually a bug in the svn system. Is this a reasonable assumption?
It does sound like a bug, but before you report it, can you try
reproducing with the latest trunk svn code? It might be fixed
already...
Thanks,
-Karl
> On 14-Apr-08, at 1:50 PM, Kris wrote:
>
>> Hi guys,
>>
>> I'm experiencing a problem syncing a svn repository. I've done the
>> requisite searching on google and through the users archive and have
>> not found anything that might help me out so here's my problem.
>> I've obfuscated the paths for obvious reasons.
>>
>> > svnsync synchronize https://XXXX.XXXX/repository --username sync
>> ...
>> svnsync: Error running context: APR does not understand this error
>> code
>> free(): invalid pointer 0x806a4f8!
>>
>> That's the error I get at some point well in to the initial sync
>> process. The error log from the apache server is:
>>
>> Could not CHECKOUT resource /XXXX/!svn/ver/1236/XXX/XXX/XXX/XXX/XXX/
>> aux_/main.c. [409, #0]
>> Unable to fetch the node revision id of the version resource within
>> the revision. [409, #160013]
>>
>> Information for both servers:
>> svn version 1.4.6
>> apache version 2.2.8
>> neon version 0.26.1
>> openssl 0.9.8g
>>
>>
>> If there is anything else that you might need, please feel free to
>> ask. Any help is appreciated.
>>
>> Thanks,
>> Kris
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>> For additional commands, e-mail: users-help@subversion.tigris.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svnsync failure - possible bug with report
Posted by Kris <kr...@theendless.org>.
Hello,
If there are no recommendations I assume I should be OK posting this
to the dev@ list or filing a bug report? I am assuming that this is
actually a bug in the svn system. Is this a reasonable assumption?
Thanks.
Kris
On 14-Apr-08, at 1:50 PM, Kris wrote:
> Hi guys,
>
> I'm experiencing a problem syncing a svn repository. I've done the
> requisite searching on google and through the users archive and have
> not found anything that might help me out so here's my problem.
> I've obfuscated the paths for obvious reasons.
>
> > svnsync synchronize https://XXXX.XXXX/repository --username sync
> ...
> svnsync: Error running context: APR does not understand this error
> code
> free(): invalid pointer 0x806a4f8!
>
> That's the error I get at some point well in to the initial sync
> process. The error log from the apache server is:
>
> Could not CHECKOUT resource /XXXX/!svn/ver/1236/XXX/XXX/XXX/XXX/XXX/
> aux_/main.c. [409, #0]
> Unable to fetch the node revision id of the version resource within
> the revision. [409, #160013]
>
> Information for both servers:
> svn version 1.4.6
> apache version 2.2.8
> neon version 0.26.1
> openssl 0.9.8g
>
>
> If there is anything else that you might need, please feel free to
> ask. Any help is appreciated.
>
> Thanks,
> Kris
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org