You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by W-Mark Kubacki <wm...@hurrikane.de> on 2005/12/10 11:30:22 UTC
Python bindings and SVN 1.3.0-rc4
Hello!
After having upgraded to SVN 1.3.0-rc4 I receive these errors with Trac
(which is written in Python) and tend to believe the error is on SVN (or
it's bindings') side:
argument number 0: a 'apr_pool_t *' is expected,
'instance(<libsvn.core.GenericSWIGWrapper instance at 0xb4735a0c>)' is
received
(Reading http://svn.haxx.se/dev/archive-2005-10/0112.shtml reminds one
about the experienced issue, but that was before 1.3.0-rc4.)
I truly don't know the origin of this all. In case I've forgotten to
re-compile something, drop me a line. ;-)
Thanks in advance.
Gruß,
W-Mark Kubacki
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Python bindings and SVN 1.3.0
Posted by W-Mark Kubacki <wm...@hurrikane.de>.
Guten morgen,
well, the bug still exists in SVN 1.3.0.
I have recompiled *everything*. (Yes, everything. No problem under Gentoo.)
Gruß,
W-Mark Kubacki
Traceback (most recent call last):
File
"/usr/lib/python2.4/site-packages/trac/web/modpython_frontend.py", line
206, in handler
dispatch_request(mpr.path_info, mpr, env)
[...]
File "/usr/lib/python2.4/site-packages/svn/fs.py", line 19, in ?
from libsvn.fs import *
File "/usr/lib/python2.4/site-packages/libsvn/fs.py", line 29, in ?
import core
File "/usr/lib/python2.4/site-packages/libsvn/core.py", line 3049, in ?
svn_pool_create()
File "/usr/lib/python2.4/site-packages/libsvn/core.py", line 1098, in
svn_pool_create
return apply(_core.svn_pool_create, args)
TypeError: argument number 0: a 'apr_pool_t *' is expected,
'instance(<libsvn.core.GenericSWIGWrapper instance at 0xa8ac518c>)' is
received
David James wrote:
> ---------- Forwarded message ----------
> From: W-Mark Kubacki <wm...@hurrikane.de>
> Date: Dec 11, 2005 11:22 AM
> Subject: Re: Python bindings and SVN 1.3.0-rc4
>
> David James wrote:
>> On 12/11/05, W-Mark Kubacki <wm...@hurrikane.de> wrote:
>>> The error occurs with any version of Trac 0.9 series
>>> [snip config information]
>>> [...]
>> This looks like it's a bug related to interaction between Subversion's
>> python bindings and mod_python. I have not tested Subversion 1.3.0rc4
>> with mod_python yet, but I am hoping to do so soon. [...]
>> Cheers,
>>
>> David
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Python bindings and SVN 1.3.0
Posted by W-Mark Kubacki <wm...@hurrikane.de>.
Guten morgen,
well, the bug still exists in SVN 1.3.0.
I have recompiled *everything*. (Yes, everything. No problem under Gentoo.)
Gruß,
W-Mark Kubacki
Traceback (most recent call last):
File
"/usr/lib/python2.4/site-packages/trac/web/modpython_frontend.py", line
206, in handler
dispatch_request(mpr.path_info, mpr, env)
[...]
File "/usr/lib/python2.4/site-packages/svn/fs.py", line 19, in ?
from libsvn.fs import *
File "/usr/lib/python2.4/site-packages/libsvn/fs.py", line 29, in ?
import core
File "/usr/lib/python2.4/site-packages/libsvn/core.py", line 3049, in ?
svn_pool_create()
File "/usr/lib/python2.4/site-packages/libsvn/core.py", line 1098, in
svn_pool_create
return apply(_core.svn_pool_create, args)
TypeError: argument number 0: a 'apr_pool_t *' is expected,
'instance(<libsvn.core.GenericSWIGWrapper instance at 0xa8ac518c>)' is
received
David James wrote:
> ---------- Forwarded message ----------
> From: W-Mark Kubacki <wm...@hurrikane.de>
> Date: Dec 11, 2005 11:22 AM
> Subject: Re: Python bindings and SVN 1.3.0-rc4
>
> David James wrote:
>> On 12/11/05, W-Mark Kubacki <wm...@hurrikane.de> wrote:
>>> The error occurs with any version of Trac 0.9 series
>>> [snip config information]
>>> [...]
>> This looks like it's a bug related to interaction between Subversion's
>> python bindings and mod_python. I have not tested Subversion 1.3.0rc4
>> with mod_python yet, but I am hoping to do so soon. [...]
>> Cheers,
>>
>> David
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Fwd: Python bindings and SVN 1.3.0-rc4
Posted by David James <ja...@gmail.com>.
---------- Forwarded message ----------
From: W-Mark Kubacki <wm...@hurrikane.de>
Date: Dec 11, 2005 11:22 AM
Subject: Re: Python bindings and SVN 1.3.0-rc4
David James wrote:
> On 12/11/05, W-Mark Kubacki <wm...@hurrikane.de> wrote:
>> The error occurs with any version of Trac 0.9 series
>> [snip config information]
>> [...]
> This looks like it's a bug related to interaction between Subversion's
> python bindings and mod_python. I have not tested Subversion 1.3.0rc4
> with mod_python yet, but I am hoping to do so soon. A few questions:
> 1) Are you using mod_python?
Yes
> 2) If you restart Apache, does it help?
No
> 3) If you switch Trac to CGI mode, does it still report the errors?
Sorry, cannot test that.
> 4) Do the test suites for the Python bindings and Trac pass when you
> ran them via the command-line?
>
> Running the test suite for the Python bindings:
> From the Subversion directory, type make check-swig-py
Results in:
cd /tmp/subversion-1.3.0-rc4/subversion/bindings/swig/python; \
/usr/bin/python
/tmp/subversion-1.3.0-rc4/subversion/bindings/swig/python/tests/run_all.py
Traceback (most recent call last):
File
"/tmp/subversion-1.3.0-rc4/subversion/bindings/swig/python/tests/run_all.py",
line 18, in ?
import pool
File
"/tmp/subversion-1.3.0-rc4/subversion/bindings/swig/python/tests/pool.py",
line 3, in ?
import svn.client
File
"/tmp/subversion-1.3.0-rc4/subversion/bindings/swig/python/svn/client.py",
line 19, in ?
from libsvn.client import *
File
"/tmp/subversion-1.3.0-rc4/subversion/bindings/swig/python/libsvn/client.py",
line 5, in ?
import _client
ImportError:
/tmp/subversion-1.3.0-rc4/subversion/libsvn_ra_dav/.libs/libsvn_ra_dav-1.so.0:
undefined symbol: ne_get_content_type
make: *** [check-swig-py] Fehler 1
> Running the test suite for Trac:
> From the Trac directory, type cp trac/test.py . && python test.py
Initially I got *a lot of* errors and tracebacks. Here's one:
File "/tmp/trac-0.9.2/trac/versioncontrol/tests/svn_fs.py", line 49,
in setUp
r = repos.svn_repos_create(REPOS_PATH, '', '', None, None, pool)
File "/usr/lib/python2.4/site-packages/libsvn/repos.py", line 55, in
svn_repos_create
return apply(_repos.svn_repos_create, args)
libsvn._core.SubversionException: ('Repository creation failed', 200011)
Exception exceptions.AssertionError: <exceptions.AssertionError instance
at 0xb76a5dcc> in <bound method Pool.__del__ of
<trac.versioncontrol.svn_fs.Pool object at 0xb77418cc>> ignored
Please notice that the address 0xb77418-- varies.
>
> Cheers,
>
> David
>
> --
> David James -- http://www.cs.toronto.edu/~james
--
David James -- http://www.cs.toronto.edu/~james
Fwd: Python bindings and SVN 1.3.0-rc4
Posted by David James <ja...@gmail.com>.
---------- Forwarded message ----------
From: W-Mark Kubacki <wm...@hurrikane.de>
Date: Dec 11, 2005 11:22 AM
Subject: Re: Python bindings and SVN 1.3.0-rc4
David James wrote:
> On 12/11/05, W-Mark Kubacki <wm...@hurrikane.de> wrote:
>> The error occurs with any version of Trac 0.9 series
>> [snip config information]
>> [...]
> This looks like it's a bug related to interaction between Subversion's
> python bindings and mod_python. I have not tested Subversion 1.3.0rc4
> with mod_python yet, but I am hoping to do so soon. A few questions:
> 1) Are you using mod_python?
Yes
> 2) If you restart Apache, does it help?
No
> 3) If you switch Trac to CGI mode, does it still report the errors?
Sorry, cannot test that.
> 4) Do the test suites for the Python bindings and Trac pass when you
> ran them via the command-line?
>
> Running the test suite for the Python bindings:
> From the Subversion directory, type make check-swig-py
Results in:
cd /tmp/subversion-1.3.0-rc4/subversion/bindings/swig/python; \
/usr/bin/python
/tmp/subversion-1.3.0-rc4/subversion/bindings/swig/python/tests/run_all.py
Traceback (most recent call last):
File
"/tmp/subversion-1.3.0-rc4/subversion/bindings/swig/python/tests/run_all.py",
line 18, in ?
import pool
File
"/tmp/subversion-1.3.0-rc4/subversion/bindings/swig/python/tests/pool.py",
line 3, in ?
import svn.client
File
"/tmp/subversion-1.3.0-rc4/subversion/bindings/swig/python/svn/client.py",
line 19, in ?
from libsvn.client import *
File
"/tmp/subversion-1.3.0-rc4/subversion/bindings/swig/python/libsvn/client.py",
line 5, in ?
import _client
ImportError:
/tmp/subversion-1.3.0-rc4/subversion/libsvn_ra_dav/.libs/libsvn_ra_dav-1.so.0:
undefined symbol: ne_get_content_type
make: *** [check-swig-py] Fehler 1
> Running the test suite for Trac:
> From the Trac directory, type cp trac/test.py . && python test.py
Initially I got *a lot of* errors and tracebacks. Here's one:
File "/tmp/trac-0.9.2/trac/versioncontrol/tests/svn_fs.py", line 49,
in setUp
r = repos.svn_repos_create(REPOS_PATH, '', '', None, None, pool)
File "/usr/lib/python2.4/site-packages/libsvn/repos.py", line 55, in
svn_repos_create
return apply(_repos.svn_repos_create, args)
libsvn._core.SubversionException: ('Repository creation failed', 200011)
Exception exceptions.AssertionError: <exceptions.AssertionError instance
at 0xb76a5dcc> in <bound method Pool.__del__ of
<trac.versioncontrol.svn_fs.Pool object at 0xb77418cc>> ignored
Please notice that the address 0xb77418-- varies.
>
> Cheers,
>
> David
>
> --
> David James -- http://www.cs.toronto.edu/~james
--
David James -- http://www.cs.toronto.edu/~james
Re: Python bindings and SVN 1.3.0-rc4
Posted by David James <ja...@gmail.com>.
On 12/11/05, W-Mark Kubacki <wm...@hurrikane.de> wrote:
> The error occurs with any version of Trac 0.9 series
> [snip config information]
> Steps to reproduce:
> 1. install these versions
> 2. make some commits to your SVN repository
> 3. go to Trac's page and try to open "timeline", "changeset viewer" or
> "code browser" (that is, any component interacting with Trac)
>
> You will either receive a blank page or a traceback.
> I've attached three tracebacks to this email, which (essentially) only
> differ in the last line containing that address.
>
> And there is something that makes me very puzzled:
> If you reloaded that page after having received that error (and
> traceback) everything is shown properly. - And yes, I've cleaned my
> browser's cache.
> Perhaps Trac has some sort of failback-code, I don't know. (Downgrading
> to SVN 1.2.3 makes the errors disappear.)
This looks like it's a bug related to interaction between Subversion's
python bindings and mod_python. I have not tested Subversion 1.3.0rc4
with mod_python yet, but I am hoping to do so soon. A few questions:
1) Are you using mod_python?
2) If you restart Apache, does it help?
3) If you switch Trac to CGI mode, does it still report the errors?
4) Do the test suites for the Python bindings and Trac pass when you
ran them via the command-line?
Running the test suite for the Python bindings:
Re: Python bindings and SVN 1.3.0-rc4
Posted by David James <ja...@gmail.com>.
On 12/11/05, W-Mark Kubacki <wm...@hurrikane.de> wrote:
> The error occurs with any version of Trac 0.9 series
> [snip config information]
> Steps to reproduce:
> 1. install these versions
> 2. make some commits to your SVN repository
> 3. go to Trac's page and try to open "timeline", "changeset viewer" or
> "code browser" (that is, any component interacting with Trac)
>
> You will either receive a blank page or a traceback.
> I've attached three tracebacks to this email, which (essentially) only
> differ in the last line containing that address.
>
> And there is something that makes me very puzzled:
> If you reloaded that page after having received that error (and
> traceback) everything is shown properly. - And yes, I've cleaned my
> browser's cache.
> Perhaps Trac has some sort of failback-code, I don't know. (Downgrading
> to SVN 1.2.3 makes the errors disappear.)
This looks like it's a bug related to interaction between Subversion's
python bindings and mod_python. I have not tested Subversion 1.3.0rc4
with mod_python yet, but I am hoping to do so soon. A few questions:
1) Are you using mod_python?
2) If you restart Apache, does it help?
3) If you switch Trac to CGI mode, does it still report the errors?
4) Do the test suites for the Python bindings and Trac pass when you
ran them via the command-line?
Running the test suite for the Python bindings:
Re: Python bindings and SVN 1.3.0-rc4
Posted by W-Mark Kubacki <wm...@hurrikane.de>.
Hello!
The error occurs with any version of Trac 0.9 series (and probably with
any version below 0.9). (Linux distro is Gentoo.)
. SWIG: 1.3.21
. APR: 0.9.7
. NEON: 0.24.7
. Python: 2.4.2
. GCC: 3.3.6 (and 3.4.4-r1 - no difference)
Steps to reproduce:
1. install these versions
2. make some commits to your SVN repository
3. go to Trac's page and try to open "timeline", "changeset viewer" or
"code browser" (that is, any component interacting with Trac)
You will either receive a blank page or a traceback.
I've attached three tracebacks to this email, which (essentially) only
differ in the last line containing that address.
And there is something that makes me very puzzled:
If you reloaded that page after having received that error (and
traceback) everything is shown properly. - And yes, I've cleaned my
browser's cache.
Perhaps Trac has some sort of failback-code, I don't know. (Downgrading
to SVN 1.2.3 makes the errors disappear.)
Gruß,
W-Mark Kubacki
P.S: Good luck and, enjoy being at school. Your free time will
dramatically decrease when studying.
David James wrote:
> On 12/10/05, W-Mark Kubacki <wm...@hurrikane.de> wrote:
>> After having upgraded to SVN 1.3.0-rc4 I receive these errors with Trac
>> (which is written in Python) and tend to believe the error is on SVN (or
>> it's bindings') side:
>>
>> argument number 0: a 'apr_pool_t *' is expected,
>> 'instance(<libsvn.core.GenericSWIGWrapper instance at 0xb4735a0c>)' is
>> received
>
> Hi Mark,
>
> This looks like an important bug in the new 1.3.0 Python bindings in
> Subversion. Could you describe which version of Trac you're using, and
> how to reproduce the bug? (Do you know which function or line of code
> in Trac is triggering this?)
>
> Thanks,
>
> David
>
> P.S. I'm in the middle of exams in school right now, so I might not
> have a chance to follow up on this right away.
>
> --
> David James -- http://www.cs.toronto.edu/~james
Re: Python bindings and SVN 1.3.0-rc4
Posted by W-Mark Kubacki <wm...@hurrikane.de>.
Hello!
The error occurs with any version of Trac 0.9 series (and probably with
any version below 0.9). (Linux distro is Gentoo.)
. SWIG: 1.3.21
. APR: 0.9.7
. NEON: 0.24.7
. Python: 2.4.2
. GCC: 3.3.6 (and 3.4.4-r1 - no difference)
Steps to reproduce:
1. install these versions
2. make some commits to your SVN repository
3. go to Trac's page and try to open "timeline", "changeset viewer" or
"code browser" (that is, any component interacting with Trac)
You will either receive a blank page or a traceback.
I've attached three tracebacks to this email, which (essentially) only
differ in the last line containing that address.
And there is something that makes me very puzzled:
If you reloaded that page after having received that error (and
traceback) everything is shown properly. - And yes, I've cleaned my
browser's cache.
Perhaps Trac has some sort of failback-code, I don't know. (Downgrading
to SVN 1.2.3 makes the errors disappear.)
Gruß,
W-Mark Kubacki
P.S: Good luck and, enjoy being at school. Your free time will
dramatically decrease when studying.
David James wrote:
> On 12/10/05, W-Mark Kubacki <wm...@hurrikane.de> wrote:
>> After having upgraded to SVN 1.3.0-rc4 I receive these errors with Trac
>> (which is written in Python) and tend to believe the error is on SVN (or
>> it's bindings') side:
>>
>> argument number 0: a 'apr_pool_t *' is expected,
>> 'instance(<libsvn.core.GenericSWIGWrapper instance at 0xb4735a0c>)' is
>> received
>
> Hi Mark,
>
> This looks like an important bug in the new 1.3.0 Python bindings in
> Subversion. Could you describe which version of Trac you're using, and
> how to reproduce the bug? (Do you know which function or line of code
> in Trac is triggering this?)
>
> Thanks,
>
> David
>
> P.S. I'm in the middle of exams in school right now, so I might not
> have a chance to follow up on this right away.
>
> --
> David James -- http://www.cs.toronto.edu/~james
Re: Python bindings and SVN 1.3.0-rc4
Posted by David James <ja...@gmail.com>.
On 12/10/05, W-Mark Kubacki <wm...@hurrikane.de> wrote:
> After having upgraded to SVN 1.3.0-rc4 I receive these errors with Trac
> (which is written in Python) and tend to believe the error is on SVN (or
> it's bindings') side:
>
> argument number 0: a 'apr_pool_t *' is expected,
> 'instance(<libsvn.core.GenericSWIGWrapper instance at 0xb4735a0c>)' is
> received
Hi Mark,
This looks like an important bug in the new 1.3.0 Python bindings in
Subversion. Could you describe which version of Trac you're using, and
how to reproduce the bug? (Do you know which function or line of code
in Trac is triggering this?)
Thanks,
David
P.S. I'm in the middle of exams in school right now, so I might not
have a chance to follow up on this right away.
--
David James -- http://www.cs.toronto.edu/~james
Re: Python bindings and SVN 1.3.0-rc4
Posted by David James <ja...@gmail.com>.
On 12/10/05, W-Mark Kubacki <wm...@hurrikane.de> wrote:
> After having upgraded to SVN 1.3.0-rc4 I receive these errors with Trac
> (which is written in Python) and tend to believe the error is on SVN (or
> it's bindings') side:
>
> argument number 0: a 'apr_pool_t *' is expected,
> 'instance(<libsvn.core.GenericSWIGWrapper instance at 0xb4735a0c>)' is
> received
Hi Mark,
This looks like an important bug in the new 1.3.0 Python bindings in
Subversion. Could you describe which version of Trac you're using, and
how to reproduce the bug? (Do you know which function or line of code
in Trac is triggering this?)
Thanks,
David
P.S. I'm in the middle of exams in school right now, so I might not
have a chance to follow up on this right away.
--
David James -- http://www.cs.toronto.edu/~james