git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
* After update to 1.6.3.1. I get this error: error: bad index file sha1  signature
@ 2009-05-29  7:25 Thorben Schröder
  2009-05-29  9:33 ` Johannes Sixt
  0 siblings, 1 reply; 3+ messages in thread
From: Thorben Schröder @ 2009-05-29  7:25 UTC (permalink / raw
  To: git

Hi,

I've recently updated from 1.6.1.2 to 1.6.3.1 on OS X. And after that
transition I get this:

  error: bad index file sha1 signature
  fatal: index file corrupt

on any git command I invoke in any of my repositories. I even tried to
go back to 1.6.1.2 but the error still occurs.

Is there any thing I can do to fix this? Would be great, otherwise all
my local repositories are busted :/

Thank you a lot for your help in advance!

Thorben

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: After update to 1.6.3.1. I get this error: error: bad index file sha1    signature
  2009-05-29  7:25 After update to 1.6.3.1. I get this error: error: bad index file sha1 signature Thorben Schröder
@ 2009-05-29  9:33 ` Johannes Sixt
  2009-05-29 13:09   ` Thorben Schröder
  0 siblings, 1 reply; 3+ messages in thread
From: Johannes Sixt @ 2009-05-29  9:33 UTC (permalink / raw
  To: Thorben Schröder; +Cc: git

Thorben Schröder schrieb:
> I've recently updated from 1.6.1.2 to 1.6.3.1 on OS X. And after that
> transition I get this:
> 
>   error: bad index file sha1 signature
>   fatal: index file corrupt
> 
> on any git command I invoke in any of my repositories. I even tried to
> go back to 1.6.1.2 but the error still occurs.
> 
> Is there any thing I can do to fix this? Would be great, otherwise all
> my local repositories are busted :/

In one of your less important repositories you can try:

   $ mv .git/index .git/index.prev
   $ git reset

This reconstructs the index file from the HEAD commit. You loose only what
you might have staged for the next commit, but otherwise this will neither
change you repostitory nor your working directory.

You can keep .git/index.prev around for a while; perhaps someone from this
list wants it for more diagnoses.

As to why this happened, I don't know, but it's certainly interesting.

-- Hannes

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: After update to 1.6.3.1. I get this error: error: bad index file  sha1 signature
  2009-05-29  9:33 ` Johannes Sixt
@ 2009-05-29 13:09   ` Thorben Schröder
  0 siblings, 0 replies; 3+ messages in thread
From: Thorben Schröder @ 2009-05-29 13:09 UTC (permalink / raw
  To: Johannes Sixt; +Cc: git

This does the trick for me but only with the result to get an other
error on any pull or clone:

E.g. when I do git pull:
remote: Counting objects: 575, done.
remote: Compressing objects: 100% (260/260), done.
remote: Total 384 (delta 157), reused 0 (delta 0)
Receiving objects: 100% (384/384), 41.48 KiB, done.
fatal: pack is corrupted (SHA1 mismatch)
fatal: index-pack failed

:/ I had this problem before and could solve it with recompiling
OpenSSL and then recompiling git pointing to that new compiled OpenSSL
lib. I've tried this again but it didn't help.

Any idea? Would be so great!

Thorben

2009/5/29 Johannes Sixt <j.sixt@viscovery.net>:
> Thorben Schröder schrieb:
>> I've recently updated from 1.6.1.2 to 1.6.3.1 on OS X. And after that
>> transition I get this:
>>
>>   error: bad index file sha1 signature
>>   fatal: index file corrupt
>>
>> on any git command I invoke in any of my repositories. I even tried to
>> go back to 1.6.1.2 but the error still occurs.
>>
>> Is there any thing I can do to fix this? Would be great, otherwise all
>> my local repositories are busted :/
>
> In one of your less important repositories you can try:
>
>   $ mv .git/index .git/index.prev
>   $ git reset
>
> This reconstructs the index file from the HEAD commit. You loose only what
> you might have staged for the next commit, but otherwise this will neither
> change you repostitory nor your working directory.
>
> You can keep .git/index.prev around for a while; perhaps someone from this
> list wants it for more diagnoses.
>
> As to why this happened, I don't know, but it's certainly interesting.
>
> -- Hannes
>
>

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2009-05-29 13:09 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-05-29  7:25 After update to 1.6.3.1. I get this error: error: bad index file sha1 signature Thorben Schröder
2009-05-29  9:33 ` Johannes Sixt
2009-05-29 13:09   ` Thorben Schröder

Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).