As a side note: any advice on web testing tools? I'm trying to confirm whether the Trac/Subversion/mod_python workaround is working or not with svn 1.4, swig 1.3.27, and trac 0.9.6.
Since the problem is intermittent and not easily reproducible, I thought I might use some web testing framework. Any suggestions? /Lars Lars Stavholm wrote: > Noah Kantrowitz wrote: >> On a related not, can anyone say if #2611 is still seen with Subversion >> 1.4 or not? > > I've upgraded subversion to 1.4 and I'm using swig 1.3.27 > on a SuSE Linux 10.1 box, no joy, problem persists. > > The intermittent error still occurs: > > ... > TypeError: argument number 2: a 'apr_pool_t *' is expected, > 'instance(<libsvn.core.GenericSWIGWrapper instance at 0xb2b85aac>)' > is received > > I have no idea what to do about this, it's driving me crazy. > > Anyone? Any ideas? > > /Lars > >> --Noah >> >> Manuzhai wrote: >>> On 9/15/06, Rainer Sokoll <[EMAIL PROTECTED]> wrote: >>>> if I upgrade subversion to 1.4 and dump/load the repositories to benefit >>>> from subversion's new file format - will that affect trac (0.9.6) in any >>>> way? >>> Trac seems to work just fine for me with Subversion 1.4. But, I am >>> running 0.10b1. However, the dump/load cycle doesn't matter; all that >>> is hidden from Trac behind Subversion's API. >>> >>> Regards, >>> >>> Manuzhai >>> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users -~----------~----~----~----~------~----~------~--~---
