{"thread":{"id":"19568","subject":"After update to 1.6.3.1. I get this error: error: bad index file sha1 signature","startedAt":"2009-05-29T07:25:27Z","lastAt":"2009-05-29T13:09:01Z","messageCount":3,"participants":["Thorben Schröder","Johannes Sixt"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"114986","messageId":"64fe838e0905290025h6bf2172agea4beb1ccff6dd6e@mail.gmail.com","threadId":"19568","inReplyTo":null,"subject":"After update to 1.6.3.1. I get this error: error: bad index file sha1 signature","fromName":"Thorben Schröder","fromEmail":"stillepost@gmail.com","sentAt":"2009-05-29T07:25:27Z","receivedAt":"2009-05-29T07:25:27Z","isPatch":false,"sender":{"key":"stillepost@gmail.com","avatar":null},"body":"Hi,\n\nI've recently updated from 1.6.1.2 to 1.6.3.1 on OS X. And after that\ntransition I get this:\n\n  error: bad index file sha1 signature\n  fatal: index file corrupt\n\non any git command I invoke in any of my repositories. I even tried to\ngo back to 1.6.1.2 but the error still occurs.\n\nIs there any thing I can do to fix this? Would be great, otherwise all\nmy local repositories are busted :/\n\nThank you a lot for your help in advance!\n\nThorben\n"},{"id":"114998","messageId":"4A1FABCC.7000808@viscovery.net","threadId":"19568","inReplyTo":"64fe838e0905290025h6bf2172agea4beb1ccff6dd6e@mail.gmail.com","subject":"Re: After update to 1.6.3.1. I get this error: error: bad index file sha1 signature","fromName":"Johannes Sixt","fromEmail":"j.sixt@viscovery.net","sentAt":"2009-05-29T09:33:00Z","receivedAt":"2009-05-29T09:33:00Z","isPatch":false,"sender":{"key":"j6t@kdbg.org","avatar":"https://avatars.githubusercontent.com/u/14810926?v=4"},"body":"Thorben Schröder schrieb:\n> I've recently updated from 1.6.1.2 to 1.6.3.1 on OS X. And after that\n> transition I get this:\n> \n>   error: bad index file sha1 signature\n>   fatal: index file corrupt\n> \n> on any git command I invoke in any of my repositories. I even tried to\n> go back to 1.6.1.2 but the error still occurs.\n> \n> Is there any thing I can do to fix this? Would be great, otherwise all\n> my local repositories are busted :/\n\nIn one of your less important repositories you can try:\n\n   $ mv .git/index .git/index.prev\n   $ git reset\n\nThis reconstructs the index file from the HEAD commit. You loose only what\nyou might have staged for the next commit, but otherwise this will neither\nchange you repostitory nor your working directory.\n\nYou can keep .git/index.prev around for a while; perhaps someone from this\nlist wants it for more diagnoses.\n\nAs to why this happened, I don't know, but it's certainly interesting.\n\n-- Hannes\n"},{"id":"115009","messageId":"64fe838e0905290609i7e8e1e87o2bb4100f9bd5cfcf@mail.gmail.com","threadId":"19568","inReplyTo":"4A1FABCC.7000808@viscovery.net","subject":"Re: After update to 1.6.3.1. I get this error: error: bad index file sha1 signature","fromName":"Thorben Schröder","fromEmail":"stillepost@gmail.com","sentAt":"2009-05-29T13:09:01Z","receivedAt":"2009-05-29T13:09:01Z","isPatch":false,"sender":{"key":"stillepost@gmail.com","avatar":null},"body":"This does the trick for me but only with the result to get an other\nerror on any pull or clone:\n\nE.g. when I do git pull:\nremote: Counting objects: 575, done.\nremote: Compressing objects: 100% (260/260), done.\nremote: Total 384 (delta 157), reused 0 (delta 0)\nReceiving objects: 100% (384/384), 41.48 KiB, done.\nfatal: pack is corrupted (SHA1 mismatch)\nfatal: index-pack failed\n\n:/ I had this problem before and could solve it with recompiling\nOpenSSL and then recompiling git pointing to that new compiled OpenSSL\nlib. I've tried this again but it didn't help.\n\nAny idea? Would be so great!\n\nThorben\n\n2009/5/29 Johannes Sixt <j.sixt@viscovery.net>:\n> Thorben Schröder schrieb:\n>> I've recently updated from 1.6.1.2 to 1.6.3.1 on OS X. And after that\n>> transition I get this:\n>>\n>>   error: bad index file sha1 signature\n>>   fatal: index file corrupt\n>>\n>> on any git command I invoke in any of my repositories. I even tried to\n>> go back to 1.6.1.2 but the error still occurs.\n>>\n>> Is there any thing I can do to fix this? Would be great, otherwise all\n>> my local repositories are busted :/\n>\n> In one of your less important repositories you can try:\n>\n>   $ mv .git/index .git/index.prev\n>   $ git reset\n>\n> This reconstructs the index file from the HEAD commit. You loose only what\n> you might have staged for the next commit, but otherwise this will neither\n> change you repostitory nor your working directory.\n>\n> You can keep .git/index.prev around for a while; perhaps someone from this\n> list wants it for more diagnoses.\n>\n> As to why this happened, I don't know, but it's certainly interesting.\n>\n> -- Hannes\n>\n>\n"}]}