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

Re: push fails with return code 22

From
Jeff King <peff@peff.net>
Date
Apr 28, 2017, 15:20 UTC
Message-ID
<20170428152025.7lgkirbhpsccupt3@sigill.intra.peff.net>
In-Reply-To
<CAH6sfJX338f=WyEbCBXX_bzq=homhMs=cjPtzmH9cSvtBKPnaw@mail.gmail.com>
On Fri, Apr 28, 2017 at 11:09:55AM -0400, Andrew Watson wrote:
Show 6 quoted lines
> Thanks for pointing me to git help http-backend. I confirmed the
> modules are loaded and the CGI environment variables. I've added
> "AcceptPathInfo On" to my httpd.conf just to be safe.
> 
> I'm not sure what /info/refs is supposed to look like, but it is
> empty. Could that be the issue?

No, that shouldn't matter. The on-disk file is used only for dumb-http requests. In a working smart-http system, the info/refs request should go to the CGI, which will generate the ref advertisement dynamically.

> Do you see anything in my apache configuration that looks wrong?
It looks reasonable to me, but I'm far from an expert on Apache config.

When you clone, is it using smart-http there? Try using GIT_CURL_VERBOSE to see what the response is to the initial /info/refs fetch when you clone.

-Peff
Previous: Andrew WatsonNext: Andrew Watson
Message 4 of 7 in “push fails with return code 22”
  1. Andrew WatsonApr 27, 2017
  2. Jeff KingApr 27, 2017
  3. Andrew WatsonApr 28, 2017
  4. Jeff KingApr 28, 2017
  5. Andrew WatsonApr 28, 2017
  6. Jeff KingApr 28, 2017
  7. Andrew WatsonApr 28, 2017

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.