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

Re: Remote corruption issue, linked to thin pack code?

From
Thomas Rast <trast@student.ethz.ch>
Date
Aug 26, 2010, 07:13 UTC
Message-ID
<201008260914.00741.trast@student.ethz.ch>
In-Reply-To
<alpine.LFD.2.00.1008252107070.622@xanadu.home>
Nicolas Pitre wrote:
> > The respective repos show no errors with git-fsck.
> 
> What about 'git fsck --full'?  Given git v1.5.4 on the remote, you 
> should try --full with 'git fsck' as this wasn't the default back then.

Well, I instructed him to try --full, as you can see in the conversation:

  http://colabti.org/irclogger/irclogger_log/git?date=2010-08-25#l2196
Nothing interesting.
> >   http://eloxoph.com/localrepo.zip
> >   http://eloxoph.com/remoterepo.zip
> 
> 2010-08-25 21:24:52 ERROR 404: Not Found.
Hrm.  Apparently a mis-edit on my part, it should be
  http://eloxoph.com/remoteserverrepo.zip
> How do you know it is there while git (on the remote) is telling you it 
> is not?
> 
> What about 'git cat-file -t e28ae6b61c384732c506' ?

It's fine in my unpacked copy. Jonas, what were the results on the server?

> Maybe after I can reproduce this issue locally.

As a side note, I couldn't reproduce locally with the above repos but then I didn't have the time to downgrade to 1.5.4.

Jonas also has to answer the rest of the questions for obvious reasons. (I'm away from the net for a few days anyway...)

-- 
Thomas Rast
trast@{inf,student}.ethz.ch
Previous: Nicolas PitreNext: Jonas Thiem
Message 3 of 4 in “Remote corruption issue, linked to thin pack code?”
  1. Thomas RastAug 25, 2010
  2. Nicolas PitreAug 26, 2010
  3. Thomas RastAug 26, 2010
  4. Jonas ThiemAug 26, 2010

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.