sorccu/cufon — Issue #220: git pull command error, knows the HEAD but can't find it
Author: adantart
Created: 2011-11-24 10:05:40+00:00
State: open

I don't know if it's a Github stuff ... maybe not ...

Scenario:
Github repo with just created with one file of one line (the minimum to do the test)

Players:
1) Windows 7 + Eclipse + egit.core_1.1.0.201109151100-r (we have tried also with the last nightly build)
2) Linux + Git 1.7.7.3 (we have tried with 1.6 also)

Steps:
1) Any of players create the repository with one file and one line in it. Github shows correctly the stuff.
The last commit hash is now (for example): 1

2) Linux player changes the line, commits and pushes
The last commit hash is now: 2

3) Windows player pulls ... changes the line, commits and pushes
The last commit hash is now: 3

4) Linux can't pull anymore, it appears: error:
unable to find "hash 3"
fatal: object "hash 3" not found

BUG: Since the moment Windows player pushes the first time, the Linux players can't pull anymore.

Things to have in mind:
- github shows the 3 commits correctly, the last one the number 3
- in the linux: git fsck shows nothing at all ...
- if the linux delete the repo and clone it again, it pulls correctly up to "hash 3"
- if the linux do a reset to HEAD, it responds: HEAD is now at "hash 2"

In some way, linux git knows the HEAD is "hash 3", but it can't find it.