On 3/28/07, C. Michael Pilato <cmpilato@xxxxxxxxxx> wrote:
Kylo Ginsberg wrote:
> I'm trying to install viewvc to access a subversion repository, and
> when accessed via apache I get:
>
> Premature end of script headers: viewvc.cgi
>
> However, a couple things work:
> 1) bin/standalone.py works fine against the subversion repository
> 2) viewvc.cgi works fine against a cvs repository
Have you tried just running viewvc.cgi from the command prompt? You should
get sane output from it that begins with a Content-type header.
$ /usr/local/viewvc-1.1-dev/bin/cgi/viewvc.cgi
Content-Type: text/html; charset=UTF-8
Thanks, I resolved my problem.
For the record, I got my best clues by running "strace -etrace=file viewvc.cgi".
And the problem I was having was that I have two installations of
subversion (and specific to this problem, of the subversion python
bindings) on the machine in question. I was specifying the
appropriate path for the subversion binaries themselves in
viewvc.conf, *but* the python bindings were getting pulled from the
wrong place.
Kind of interesting why: subversion recommends specifying the path to
the bindings like so:
echo /usr/local/lib/svn-python > /usr/lib/python2.x/site-packages/subversion.pth
Unfortunately, when python parses .pth files (at least python 2.4) it
tacks the new directories at the *end* of sys.path, rather than
inserting them in the position they were found. So in my case
/usr/lib/python2.x/site-packages was at the head of sys.path, the
freshly installed subversion bindings were now to be found at the end
of sys.path, and somewhere in the middle was the older, unwanted
subversion bindings. So I got the latter.
In my case, the recommendation to install python bindings using a .pth
file caused a bit of a detour.
Cheers,
Kylo
|
| 
