• Pages
    • Categories
    Looking glass
    Navigate/Search
    «
    »

    trac installation woes

    Trac is by far the best developer-centric project management tool i’ve used so far. I’ve always had the pleasure to use it, but thankfully not to administrate it. After 4 configurations, compilations, and installations (all done manually of course) of all its dependencies (yes 4 installation CYCLES! and that does not count the number of times trying to fiddle around and coaxing it to work), namely:

    1. Python 2.3.5
    2. SQLite 3.3.6
    3. PySqlite 2.3.2
    4. Clearsilver 0.10.3
    5. Subversion 1.3.2
    6. Swig 1.3.29
    7. and finally, trac itself, 0.96

    it now gives me a segmentation fault??! At the admin configuration step??????! GRRRRRRRRRRRRRRRRRRRR I’ve been going at it on and off for 2 weeks now, am I missing something?! Geez! I’m very close this time though… very… I can smell the ticket messages clogging my email.

    For a more complete picture, click here.

    On another note, because of trac and whoever’s responsible for the installation documentation, I have been delayed with
    posting my notes on barcampEarth. Those are to come soon.

    Published at Thursday, August 31st, 2006 @ 11:39 pm Category rant, software
    Comments feed RSS 2.0 Trackback Trackback

    6 Responses to “trac installation woes”

    1. aadil Says:
      September 1st, 2006 at 6:57 am

      Compiling from scratch? Weren’t there packages available for the system? I rarely compile on Linux these days, only on NetBSD do I ./configure, make and make install. :)

    2. Hans Says:
      September 1st, 2006 at 3:52 pm

      hey Oliver yeah I know how’s work is important : as can be shown by that nice listing of code above ahhhhhhhhhh but you’re the lucky winner of some tagging game : I’ve tagged you for the 6Tagger Game, wanna come and play with your ABOUT ME and leave some codes of you behind? ;) ;) hey I think for those that don’t respect the contract there’s some hohhhhh dangerous things(Angele knows about it) that might break into your code

    3. oli Says:
      September 2nd, 2006 at 5:44 pm

      Yeah, unfortunately aadil, even if I’d love to have trac as a package, there is none that i can use. trac is in fact available as a debian package, but the web host i’m using does not have the apt, dpkg or rpm utilities available. Even if they did, I don’t have root access… so everything needs to be installed in my home directory, and from scratch as well!

    4. aadil Says:
      September 3rd, 2006 at 8:15 am

      What kind of web host is that? No package utilities? Oo

      According to DAG repositories, Trac is available as an RPM file (see http://dag.wieers.com/packages/trac/).

    5. tsmith Says:
      September 11th, 2006 at 2:22 am

      Hi Olivier,

      The “Indexing repository” message is printed right before the very last step in the environment setup process – creating wiki index pages for your (already existant) subversion repository.

      The fact that this is failing means one of two things:

      1) Your subversion directory is not a valid subversion repository (that is, it either doesn’t exist yet or is simply emtpy), or
      2) Your SWIG bindings aren’t playing well with your subversion installation.

      See http://trac.edgewall.org/wiki/TracSubversion for more info. Instructions on that page say “Do not install swig 1.3.28 or 1.3.29. Version 1.3.27 seems to works fine.” You may want to regress to 1.3.27 (or 1.3.28, since later on in the page it says “Trac and Subversion 1.3.2 – This version adds support for SWIG 1.3.28″).

      Cheers,
      Tim

    6. oli Says:
      September 12th, 2006 at 10:03 am

      Hey Tim!

      to fix the problem, I ended up installing subversion 1.2.3 and swig 1.2.5
      Everything worked fine afterwards. Geez, although the documentation is there, its spread out all over the net.

      Thanks for the heads up!

    Leave a Reply