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

Debugging corrupt object generation

From
Julian Phillips <julian@quantumfyre.co.uk>
Date
Nov 1, 2007, 22:57 UTC
Message-ID
<Pine.LNX.4.64.0711012256080.17812@beast.quantumfyre.co.uk>

I have been trying to import a repository using fast-import, and as part of this I have extended fast-import to support copying a path from any arbitrary commit. This works fine on my small test repository.

However, when I run against my (vastly more complicated) real work repository things don't go so well. I get a few thousand commits in, and then it breaks. It appears that I have somehow managed to create a corrupt object or something.

After a certain commit, and attempt to use that commit generates a "fatal: unable to apply delta". This appears to be coming from unpack_delta_entry in sha1_file.c.

Can anyone give me any hints as to how I find out what is causing the problem? I'm not even sure what it is that isn't working ... and all attempts to replicate the problem with my test repository have failed.

-- 
Julian

  ---
...the prevailing Catholic odor - incense, wax, centuries of mild bleating
from the lips of the flock.
-- Thomas Pynchon, _Gravity's Rainbow_
Next: Nicolas Pitre
Message 1 of 4 in “Debugging corrupt object generation”
  1. Julian PhillipsNov 1, 2007
  2. Nicolas PitreNov 1, 2007
  3. Julian PhillipsNov 2, 2007
  4. Shawn O. PearceNov 2, 2007

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.