Re: After update to 1.6.3.1. I get this error: error: bad index file sha1 signature

From: Thorben Schröder <stillepost@gmail.com>
Date: May 29, 2009, 13:09 UTC
Message-ID: <64fe838e0905290609i7e8e1e87o2bb4100f9bd5cfcf@mail.gmail.com>
In-Reply-To: <4A1FABCC.7000808@viscovery.net>

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>:

Show 30 quoted lines

> 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
>
>