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

Re: Problem: fatal oops during git fetch

From
Dmitry Potapov <dpotapov@gmail.com>
Date
Jan 14, 2010, 05:28 UTC
Message-ID
<20100114052839.GG10586@dpotapov.dyndns.org>
In-Reply-To
<op.u6hrkho1a8ed4e@dellschleppa>
On Wed, Jan 13, 2010 at 11:03:43PM +0100, Tilo Schwarz wrote:
Show 12 quoted lines
> 
> Yesterday I tried to fetch bug fixes from one remote machine to the main  
> development machine being on branch 'test' using
> 
> git fetch remote/test
> 
> I got something like
> 
> fatal: oops 'SHA1'
> Fetch failed
> 
> Any ideas what happened here?

My guess is that the remote repository is corrupted, and the specified SHA1 object was not found or it was corrupted. Try to run:

  git fsck --full
in the remote repository.
Dmitry
Previous: Tilo Schwarz
Message 2 of 2 in “Problem: fatal oops during git fetch”
  1. Tilo SchwarzJan 13, 2010
  2. Dmitry PotapovJan 14, 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.