git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Potential bug in gitweb 1.7.2

From
Anders Kaseorg <andersk@mit.edu>
Date
Jul 26, 2010, 09:27 UTC
Message-ID
<alpine.DEB.2.00.1007260508290.14251@dr-wily.mit.edu>
In-Reply-To
<20100726050849.GA16858@burratino>
On Mon, 26 Jul 2010, Jonathan Nieder wrote:
Show 5 quoted lines
> Indeed, the rules for installation have changed with v1.7.2, so the 
> packaging may need to be adjusted[1] to match (see gitweb/INSTALL).  
> Please report this to the Ubuntu git team.
> 
> [1] e.g. http://repo.or.cz/w/debian-git/jrn.git/commit/ff41c31c5

Thanks for the report. But, the 1.7.2-0ppa1 package in the git-core PPA was constructed by merging your jrn/for-gerrit branch (1.7.2~rc3-0.1, commit f84e1eb) with upstream v1.7.2, and updating debian/versions.upstream and debian/changelog.upstream. It already includes that commit.

Indeed, when I install the gitweb 1.7.2-0ppa1 package, put some repositories into /var/cache/git, and go to http://localhost/gitweb/ , it works correctly for me.

The error that Julio originally posted:
> > [Sat Jul 24 23:11:41 2010] [error] [client 192.168.1.100] Can't call 
> > method "http" on an undefined value at /usr/share/gitweb/index.cgi 
> > line 3401., referer: http://192.168.1.142/gitweb/

looks very strange, and does not seem like it would result from just a packaging problem.

Anders
Previous: Jonathan NiederNext: Julio Lajara
Message 3 of 15 in “Potential bug in gitweb 1.7.2”
  1. Julio LajaraJul 26, 2010
  2. Jonathan NiederJul 26, 2010
  3. Anders KaseorgJul 26, 2010
  4. Julio LajaraJul 26, 2010
  5. Jakub NarebskiJul 26, 2010
  6. Ævar Arnfjörð BjarmasonJul 26, 2010
  7. Julio LajaraJul 26, 2010
  8. Jakub NarebskiJul 26, 2010
  9. gitweb: allow configurations that change with each requestJonathan Nieder, Jul 31, 2010
  10. Jakub NarebskiAug 2, 2010
  11. Jonathan NiederAug 2, 2010
  12. Jakub NarebskiAug 2, 2010
  13. Jonathan NiederJul 26, 2010
  14. Anders KaseorgJul 26, 2010
  15. Jonathan NiederJul 27, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.