git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Thorben Schröder" <stillepost@gmail.com>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: git@vger.kernel.org
Subject: Re: After update to 1.6.3.1. I get this error: error: bad index file  sha1 signature
Date: Fri, 29 May 2009 15:09:01 +0200	[thread overview]
Message-ID: <64fe838e0905290609i7e8e1e87o2bb4100f9bd5cfcf@mail.gmail.com> (raw)
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>:
> 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
>
>

      reply	other threads:[~2009-05-29 13:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=64fe838e0905290609i7e8e1e87o2bb4100f9bd5cfcf@mail.gmail.com \
    --to=stillepost@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=j.sixt@viscovery.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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 NNTP newsgroup(s).