Upgrade 0.10 to 0.11 - where did cgi-bin go?

12 views
Skip to first unread message

kfsone

unread,
Jul 2, 2008, 5:52:19 PM7/2/08
to Trac Users
Operating System: Fedora Core 6
Install method: Manual install or easy_install
Previous version: 0.10
New version: 0.11
Content delivery method: FastCGI via Apache

The TracUpgrade page suggests that you will want to remove the cgi-bin
etc, but the Apache configuration page recommends that you remove the
0.10 /usr/share/trac/cgi-bin (and friends).

So I made a folder /usr/share/trac/from-0.10 and moved the folders
listed into this subdirectory.

I ran 'python setup.py install' as root ... Everything went thru, I
upgraded my two environments and their wikis in /usr/local/trac/...

I ran an updatedb and did locate fcgi

[kfsone@fres1 ~]$ locate fcgi
/usr/lib/python2.3/site-packages/trac-0.10/web/fcgi_frontend.py
/usr/lib/python2.3/site-packages/trac-0.10/web/fcgi_frontend.pyc
/usr/lib/python2.3/site-packages/trac-0.10/web/_fcgi.py
/usr/lib/python2.3/site-packages/trac-0.10/web/_fcgi.pyc
/usr/lib/python2.3/site-packages/Trac-0.11-py2.3.egg/trac/admin/
templates/deploy_trac.fcgi
/usr/lib/python2.3/site-packages/Trac-0.11-py2.3.egg/trac/web/
fcgi_frontend.py
/usr/lib/python2.3/site-packages/Trac-0.11-py2.3.egg/trac/web/
fcgi_frontend.pyc
/usr/lib/python2.3/site-packages/Trac-0.11-py2.3.egg/trac/web/_fcgi.py
/usr/lib/python2.3/site-packages/Trac-0.11-py2.3.egg/trac/web/
_fcgi.pyc
/usr/share/trac/backup-from-0.10/cgi-bin/trac.fcgi
/home/kfsone/Trac-0.11/trac/admin/templates/deploy_trac.fcgi
/home/kfsone/Trac-0.11/trac/web/fcgi_frontend.py
/home/kfsone/Trac-0.11/trac/web/_fcgi.py
/home/kfsone/Trac-0.11/cgi-bin/trac.fcgi
/home/kfsone/Trac-0.11/build/lib/trac/admin/templates/deploy_trac.fcgi
/home/kfsone/Trac-0.11/build/lib/trac/web/fcgi_frontend.py
/home/kfsone/Trac-0.11/build/lib/trac/web/_fcgi.py

the latter being the files in the install location. I tried running
easy_install as well, but it made no difference.

So now I am confused. The documentation at http://trac.edgewall.org/wiki/TracFastCgi
still says to use:

ScriptAlias / /srv/tracsite/cgi-bin/trac.fcgi/

But there's no cgi-bin ... Is there a step in the upgrade process I am
missing? I've tried putting the old cgi-bin, templates, wiki-docs etc
back, which makes the site sorta-work until I try to view a ticket...
Well, no surprise there.

Am I missing some obvious step? I've gone over TracInstall,
TracUpgrade and TracFastCgi a bunch of times, I've spent 2 hours
searching and reading thru what I hoped would be related posts, blog
entries, wiki pages, etc...

Tearing hair out here and I have a bunch of angry producers
threatening to manually insert tickets into me :)

Noah Kantrowitz

unread,
Jul 2, 2008, 9:53:06 PM7/2/08
to trac-...@googlegroups.com, trac...@googlegroups.com
Use `trac-admin /path/to/env deploy` to generate the *gi files. I am
thinking I may rework this slightly for 0.12 (and maybe 0.11.1 if
people feel this question is getting too common) so that it also
generates the *gi files at initenv in a cgi-bin/ subfolder of the env.
I think this would serve to make this feature much more discoverable.

--Noah

Oliver Smith

unread,
Jul 3, 2008, 1:35:23 AM7/3/08
to trac-...@googlegroups.com
Noah Kantrowitz said the following on 7/2/2008 8:53 PM:
Mostly I think the issue is that the documentation covering this section
is still 0.10 based giving you explicit instructions that make things
incremently worse :)

- Oliver

Colin Guthrie

unread,
Jul 3, 2008, 5:27:49 AM7/3/08
to trac-...@googlegroups.com, trac...@googlegroups.com

Do you have to use this method? Or can you just copy the files from the
cgi-bin source folder?

I ask this from a distro packaging perspective where we want to provide
a trac-{fcgi,cgi} package. The only thing the user needs to do is to
update a variable in the config file to point at their trac env path...

Is this generally frowned upon now? (or will it simply not work?)

Cheers

Col

Reply all
Reply to author
Forward
0 new messages