fatal: The same object 'hash' appears twice in the pack #246

Closed
ErikVerheul opened this Issue May 23, 2012 · 1 comment

Projects

None yet

3 participants

@ErikVerheul

When pushing to Github I get:

$ hg -v --debug --traceback push git+ssh://git@github.com/ErikVerheul/kunagi.git
pushing to git+ssh://git@github.com/ErikVerheul/kunagi.git
importing Hg objects into Git
creating and sending data
calling ssh: "C:\Program Files (x86)\Git\bin\ssh.exe" git@github.com "git-receive-pack '/ErikVerheul/kunagi.git'"
["git-receive-pack '/ErikVerheul/kunagi.git'"]
fatal: The same object 10dc4aa9b0d5c10c3bc3e9cb4d20c55b513727ed appears twice in the pack
Traceback (most recent call last):
File "mercurial\dispatch.pyo", line 58, in _runcatch
File "mercurial\dispatch.pyo", line 601, in _dispatch
File "mercurial\dispatch.pyo", line 406, in runcommand
File "mercurial\dispatch.pyo", line 655, in _runcommand
File "mercurial\dispatch.pyo", line 609, in checkargs
File "mercurial\dispatch.pyo", line 598, in
File "mercurial\util.pyo", line 433, in check
File "mercurial\extensions.pyo", line 133, in wrap
File "mercurial\util.pyo", line 433, in check
File "hgext\mq.pyo", line 3050, in mqcommand
File "mercurial\util.pyo", line 433, in check
File "mercurial\commands.pyo", line 3028, in push
File "C:\hggit_0.2.6\schacon-hg-git-dfeba31\hggit\hgrepo.py", line 22, in push
File "C:\hggit_0.2.6\schacon-hg-git-dfeba31\hggit\git_handler.py", line 152, in push
File "C:\hggit_0.2.6\schacon-hg-git-dfeba31\hggit\git_handler.py", line 554, in upload_pack
File "dulwich\client.pyo", line 187, in send_pack
File "dulwich\client.pyo", line 110, in _parse_status_report
SendPackError: unpack index-pack abnormal exit
** unknown exception encountered, please report by visiting
** http://mercurial.selenic.com/wiki/BugTracker
** Python 2.6.6 (r266:84297, Aug 24 2010, 18:13:38) [MSC v.1500 64 bit (AMD64)]
** Mercurial Distributed SCM (version 1.8.4)
** Extensions loaded: fixfrozenexts, mq, hggit
Traceback (most recent call last):
File "hg", line 36, in
File "mercurial\dispatch.pyo", line 16, in run
File "mercurial\dispatch.pyo", line 36, in dispatch
File "mercurial\dispatch.pyo", line 58, in _runcatch
File "mercurial\dispatch.pyo", line 601, in _dispatch
File "mercurial\dispatch.pyo", line 406, in runcommand
File "mercurial\dispatch.pyo", line 655, in _runcommand
File "mercurial\dispatch.pyo", line 609, in checkargs
File "mercurial\dispatch.pyo", line 598, in
File "mercurial\util.pyo", line 433, in check
File "mercurial\extensions.pyo", line 133, in wrap
File "mercurial\util.pyo", line 433, in check
File "hgext\mq.pyo", line 3050, in mqcommand
File "mercurial\util.pyo", line 433, in check
File "mercurial\commands.pyo", line 3028, in push
File "C:\hggit_0.2.6\schacon-hg-git-dfeba31\hggit\hgrepo.py", line 22, in push
git.push(remote.path, revs, force)
File "C:\hggit_0.2.6\schacon-hg-git-dfeba31\hggit\git_handler.py", line 152, in push
changed_refs = self.upload_pack(remote, revs, force)
File "C:\hggit_0.2.6\schacon-hg-git-dfeba31\hggit\git_handler.py", line 554, in upload_pack
changed_refs = client.send_pack(path, changed, genpack)
File "dulwich\client.pyo", line 187, in send_pack
File "dulwich\client.pyo", line 110, in _parse_status_report
dulwich.errors.SendPackError: unpack index-pack abnormal exit

the same error is also reported at https://groups.google.com/forum/?fromgroups#!topic/hg-git/_SV5xJ1AFnQ

Is there a bug fix (in the making)?

thanks,
Erik

@CarlosTorrecillas

I had the same error but that happened to me when I wanted to push a big project (4 months worth of work) from HG to Git. I have tried with new projects, small projects and works. I wonder if that has something to do with the size of the package we are trying to push, like a timeout or something, because it's really weird it works for all the projects I create brand new. I also thought that might be because of the branches but I did another test with a brand new repo, created several branches and pushed correctly...so I don't know what's going on.

@durin42 durin42 closed this Dec 14, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment