the apache server error log seems to filled with trac/python errors... very odd looking stuff..
one of the predominant, repeating ones is about not being able to extract files to the egg cache... whats strange is where it says the egg cache is pointing to is not where the egg cache is set to with python env var in trac.conf at apache start time... I know the trac.conf is getting parsed at startup because if I insert an error, apache chokes... thats where the location is specified to for the web trac so its almost as if that file is getting parsed but not actually updating anything or being used... On May 10, 11:23 am, Mr Papa <[email protected]> wrote: > appreciate all the help guys... > > making some great progress... managed to get pythong using the right > bindings and get it talking to svn... i can even resync trac with > svn... woot... > > I havent tried checklist step 3 because, well, um, not sure how to get > the python pid... using ps or pstree, I dont really see a python > process... > > so anyways, trac "seems" to be working, except I cant access it from > the web where it should be... I just get a 404 page... must be > something in my .conf files but they are copies of the old server > where the web access was working... permissions? apache owns > everything... will compare settings again with old server (finally > got them to reactivate it)... > > other ideas? > > On May 10, 10:26 am, Christian Boos <[email protected]> wrote: > > > Emmanuel Blot wrote: > > >> just to clarify, when you say python bindings, are you referring to > > >> swig? > > > > Not really: SWIG is a *generator*: it helps building the wrapper code > > > that stands between the Python interpreter (SWIG may generate wrapper > > > for many other language) and the underlying C native library (.so). > > > Python bindings are made of Python (.py) code and C wrappers (c file > > > compiled into a .so lib), which are both generated with the SWIG tool. > > > >> there is a swig executable in /usr/local/bin (same place as svn > > >> executables) that returns version 1.3.25 which is what I built... or > > >> are there shard object libraries in use for the bindings? > > > > SWIG is only required to *build* the bindings, not to run them. > > > The SWIG version only matters when you build the bindings. > > > Not even, as the generated bindings are shipped in the Subversion source > > tarball. > > You only need SWIG when building Subversion from a source checkout, or > > when you want to modify the .i files. > > So most of the time (including in this situation) SWIG doesn't even come > > into the picture. > > IIRC, the advice from the TracSubversion page comes from a time when the > > generated bindings /weren't/ shipped (the 1.2.x / 1.3.x period, again IIRC). > > > I'd suggest to the original poster to follow the steps > > inhttp://trac.edgewall.org/wiki/TracSubversion#Checklistinparticular step 3. > > > -- Christian --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
