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

Debugging strange "corrupt pack" errors on SuSE 9

From
Martin Langhoff <martin.langhoff@gmail.com>
Date
Jun 20, 2007, 02:36 UTC
Message-ID
<46a038f90706191936m121a94e4x1e59dff4fe217988@mail.gmail.com>

A colleage at work is using git to manage code updates to a heavily firewalled machine at a client site. In a nutshell, we "push" the interesting code to a repo on usb-stick, and we pull from it on the client's machine.

We do some coding and testing on that machine, so ocassionally we bring some patches back.

Now the working repo on the client machine has started to die with "corrupt pack" errors. I am trying to get my hands on the literal error messages, and exact software versions installed. Right now all I know is that it is SuSE 9 x86, git 1.4.x, cogito .17.x . The error appears on git-diff, git-fsck-objects --full

We did bring a copy of the working copy with the "corrupt pack" to our office, and here git (v1.5.1 and 1.5.2) thinks it's perfectly well.

So I am a bit puzzled - while we try to get 1.5.x on the client machine and see what happens, is there anything that could be causing this? Any additional tests that we should run?

cheers,
martin
Next: Nicolas Pitre
Message 1 of 10 in “Debugging strange "corrupt pack" errors on SuSE 9”
  1. Martin LanghoffJun 20, 2007
  2. Nicolas PitreJun 20, 2007
  3. Martin LanghoffJun 20, 2007
  4. Martin LanghoffJun 20, 2007
  5. Nicolas PitreJun 20, 2007
  6. Nicolas PitreJun 20, 2007
  7. Martin LanghoffJun 20, 2007
  8. Nicolas PitreJun 20, 2007
  9. Nicolas PitreJun 20, 2007
  10. Jakub NarebskiJun 20, 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.