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

Re: Problems with git over http

From
Uwe Kleine-König <ukleinek@strlen.de>
Date
Sep 20, 2008, 18:42 UTC
Message-ID
<20080920184257.GD18932@strlen.de>
In-Reply-To
<264855a00809201013h6003abbfr9bbdd20c92e9201d@mail.gmail.com>
Hello Sean,
On Sat, Sep 20, 2008 at 01:13:53PM -0400, Sean Davis wrote:
Show 15 quoted lines
> I am new to git and trying to set up a remote repository over http.  I
> have configured apache2 and the bare, empty repository.  Using curl, I
> can get the file HEAD without a password (seems .netrc is correct?).
> However, when I try to push to the repository, I get the following:
> 
> sdavis@lestrade:/tmp/testing> git push
> http://sdavis@watson.nci.nih.gov/git/sean_git.git/ master
> fatal: exec http-push failed.
> error: failed to push some refs to
> 'http://sdavis@watson.nci.nih.gov/git/sean_git.git/'
> 
> What can I do to try to debug this, as the error message isn't helping
> me to sort out what is wrong.  The client and server are both running
> git-1.5.x (although the minor versions are a bit different).  Any
> suggestions?

Try cloning first. And check the error log of apache. I don't know how pushing over http works, but maybe you installed git into /usr/local and /usr/local/bin is not in the PATH for the apache user?

Best regards Uwe

Previous: Sean DavisNext: Sean Davis
Message 2 of 7 in “Problems with git over http”
  1. Sean DavisSep 20, 2008
  2. Uwe Kleine-KönigSep 20, 2008
  3. Sean DavisSep 20, 2008
  4. Jakub NarebskiSep 20, 2008
  5. Sean DavisSep 20, 2008
  6. Matthieu MoySep 21, 2008
  7. Sean DavisSep 21, 2008

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.