On Oct 6, 1:11 pm, Simon Lipp <[email protected]> wrote: > > I'm not sure why later cloning the new repository fails, but I would > > suggest using more sensible approach to putting the repository to > > another machine in the first place: [...] > > $ git push --mirror foo > Doesn’t change anything : on my local machine, after creating the > remote repository with your method : > > $ git clone ssh://u...@host/~/test.git > remote: Generating pack... > remote: Done counting 10171 objects. > remote: error: unable to find 719d3089ebb11eba608b13070c4e35be5e3969d6 > remote: fatal: unable to get type of object > 719d3089ebb11eba608b13070c4e35be5e3969d6 error: git-upload-pack: > git-pack-objects died with error. fatal: git-upload-pack: aborting due > to possible repository corruption on the remote side. remote: aborting > due to possible repository corruption on the remote side. fatal: > protocol error: bad pack header > > Note that git push --mirror indicated “Counting objects: *10170*, > done” (not 10171). Very interesting. What happens if you clone on the same host? $ cd /tmp/foo $ git clone /path/to/test or $ git clone file:///path/to/test ?
If it fails, try looking at `git fsck`. -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/git-users?hl=en.
