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

Re: Problem with the dump HTTP transport

From
Junio C Hamano <junkio@cox.net>
Date
Dec 21, 2005, 17:59 UTC
Message-ID
<7vu0d2baaq.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<1135166574.26233.64.camel@localhost>
Marcel Holtmann <marcel@holtmann.org> writes:
Show 7 quoted lines
> Cannot obtain needed object c2f3bf071ee90b01f2d629921bb04c4f798f02fa
> while processing commit 0000000000000000000000000000000000000000.
> cg-fetch: objects fetch failed
>
> Both, git and cogito, are the latest versions from yesterday. So it
> seems every time you repack, you need to do something extra to keep the
> dump HTTP transport happy.

The last sentence is correct and I do that (the magic word is git-update-server-info, and that is done as part of git-repack automatically), but it does not seem to apply here. It most likely is a mirroring delay. That c2f3... object is the commit at the tip of the master branch, and the repository is fully packed right now (except v1.0.0 tag object which is loose).

Previous: Luben TuikovNext: Marcel Holtmann
Message 3 of 5 in “Problem with the dump HTTP transport”
  1. Marcel HoltmannDec 21, 2005
  2. Luben TuikovDec 21, 2005
  3. Junio C HamanoDec 21, 2005
  4. Marcel HoltmannDec 21, 2005
  5. Junio C HamanoDec 21, 2005

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.