New Ticket     Wiki     Browse Source     Timeline     Roadmap     Ticket Reports     Search

Ticket #15938 (closed defect: invalid)

Opened 4 years ago

Last modified 3 years ago

trac-0.11 installation error

Reported by: incanus@… Owned by: dluke@…
Priority: Normal Milestone:
Component: ports Version: 1.6.0
Keywords: trac cgi Cc: incanus@…
Port:

Description

After upgrade from trac-0.10.4 to 0.11, it seems like some of the files are missing. Removing and reinstalling has the same effect. At the very least, trac.cgi is missing, which is what brought it to my attention since I was using CGI mode. Build log attached.

Attachments

trac-0.11 build log.txt Download (291.3 KB) - added by incanus@… 4 years ago.

Change History

Changed 4 years ago by incanus@…

Changed 4 years ago by incanus@…

  • cc incanus@… added

Cc Me!

Changed 4 years ago by raimue@…

  • owner changed from macports-tickets@… to dluke@…

Assigning to maintainer.

Changed 4 years ago by dluke@…

  • owner changed from dluke@… to dluke@…
  • status changed from new to assigned

I don't believe that trac.[f]cgi is included in 0.11.

Looks like there's a template for one in /opt/local/lib/python2.5/site-packages/trac/admin/templates/

I'll take a look at this more soon, though and make sure.

Changed 4 years ago by dluke@…

  • status changed from assigned to closed
  • resolution set to invalid

Oh, I found the answer.

It's /opt/local/lib/python2.5/site-packages/trac/web/cgi_frontend.py

(where /opt/local is whatever you have PREFIX set to).

Changed 4 years ago by incanus@…

  • status changed from closed to reopened
  • resolution invalid deleted

I still think that there are some major changes that are not allowing proper CGI operation, at least as packaged with MacPorts. If you look at the discussion  here, there are bigger changes afoot that may require some specific MacPorts setup. At the very least, after upgrading to 0.11 in MacPorts and spending at least an hour on things, my Trac environment is still not working in CGI mode. Some sort of migration or upgrade needs to happen, though just what I can't figure out, but MacPorts did not do it for me, which seems a little inconvenient.

Not meant to criticize, just draw attention to this. Since writing  this guide, I have been contacted by several others with similar confusion.

Changed 4 years ago by dluke@…

  • status changed from reopened to closed
  • resolution set to invalid

I don't see how this requires MacPorts setup.

The thread you linked to includes the command you run to get the cgi/fcgi/wscgi scripts that are set up for a particular trac environment.

Since MacPorts has no idea where your trac environment is set up (and how you're running it), I don't see how it can handle this for you. People run trac with tracd, cgi, fast_cgi, wscgi, and mod_python.

Of course, if you can think of something specific that could be made better (and especially if you can send a patch), I'm happy to improve the port.

As far as I can tell, what really needs updating is the documentation on Edgewall's site.

Changed 4 years ago by incanus@…

Fair enough -- I'll keep at it and try to contribute if I can figure this out. Thanks for your help.

Changed 3 years ago by anonymous

  • milestone Port Bugs deleted

Milestone Port Bugs deleted

Note: See TracTickets for help on using tickets.