From: Eli Barzilay <eli@barzilay.org>
To: git@vger.kernel.org
Subject: gitweb problem?
Date: Mon, 01 Mar 2010 01:54:29 -0500 [thread overview]
Message-ID: <m34ol0wmze.fsf@winooski.ccs.neu.edu> (raw)
Whenever I view the toplevel gitweb page (running as a cgi script
under apache), but not when in a specific repo, I get this in my error
log:
gitweb.cgi: Use of uninitialized value $git_dir in concatenation (.) or string at /home/git/gitweb/gitweb.cgi line 2065.
fatal: error processing config file(s)
gitweb.cgi: Use of uninitialized value $git_dir in concatenation (.) or string at /home/git/gitweb/gitweb.cgi line 2221.
gitweb.cgi: Use of uninitialized value $git_dir in concatenation (.) or string at /home/git/gitweb/gitweb.cgi line 2218.
(taken verbatim from the apache error log, removed uninteresting line
prefixes.)
I'm using the pathinfo option, so perhaps there is a problem with that
setup?
Looking at the source, the last two line numbers are in
`git_get_project_config' -- so my guess is that the code is trying to
get the options from the repository config file even when showing the
toplevel page. Based on this, and also guessing that $git_dir is
unset when viewing the toplevel page, I added
return unless (defined $git_dir);
to the top (of the `git_get_project_config' function), and I get no
warnings and everything works as it should.
(Disclaimer: I can barely read perl, and I'm a git newbie, so all of
this can be due to some other stupid mistake.)
--
((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay:
http://barzilay.org/ Maze is Life!
next reply other threads:[~2010-03-01 6:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-01 6:54 Eli Barzilay [this message]
2010-03-01 10:24 ` gitweb problem? Jakub Narebski
2010-03-01 11:51 ` Eli Barzilay
2010-03-01 13:40 ` Jakub Narebski
2010-03-01 21:51 ` [PATCH] gitweb: Fix project-specific feature override behavior Jakub Narebski
2010-03-02 4:40 ` gitweb problem? Eli Barzilay
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m34ol0wmze.fsf@winooski.ccs.neu.edu \
--to=eli@barzilay.org \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).