Geek Answers Handbook

Github push error: decompression failed: anomalous exit with index

I am having problems pushing a new git changeset into the github repository. First, I cloned my local changes with a depth of 1 to delete the story as:

git clone --depth 1 file:///Users/kunal<path to project>

Then I ran git init remote add and click like inside the cloned directory:

 > git init > git remote add origin https://github.com/kp27/pymovie2.git > git push -u origin master

I see the file upload, but then I get:

 Counting objects: 7110, done. Delta compression using up to 8 threads. Compressing objects: 100% (3785/3785), done. Writing objects: 100% (7110/7110), 7.60 MiB | 247 KiB/s, done. Total 7110 (delta 2283), reused 7110 (delta 2283) error: unpack failed: index-pack abnormal exit

Any ideas what could be causing this? My first guess is that a depth of 1 causes it, but I'm not sure why.

+6
source share
6 answers

You need to contact github for this, it is something on the receiving side.

You can also clone the github repository and instead of cloning your local files, just copy them and add them.

+3
source

I deleted the contents of / .git / and tried again - it worked. Be careful when doing this.

History: There was a similar problem related to some error in renaming folders, which persisted even after deletion and (re) cloning

(on mac os x): First I copied the files to a safe directory on the computer, then went to / .git / and deleted all the contents (cmd-shift-g..git "in Finder) and finally deleted / .git / in the terminal

then he was able to lock and push

+2
source

For me, this happened when I tried to click new files that were not added to the index. try adding files to the index using Team-> Add to Index in eclipse via the EGit plugin.

+1
source

In the case of repacking, it did not help to pull using rebase, it can help:

 git pull --rebase
0
source

I had the same case, not gitgub, but for a different git repo. If you can, check if the user is registered with git and has permission to write to these directories, and if not, then in chmod and continue to know what you already know ...

0
source

You no longer have to clone it, just run this command in git repo git repack remote/origin/master For more information check out this http://www.andyjarrett.co.uk/2009/10/08/unpacker-error- when-pushing-git /

-1
source

More articles:


All Articles