Re: repo corruption - Egit's fault?

Eugene Sajine [off-list ref] wrote:

When I???m looking at the bare repo in CGit ??it shows me ??Bad object:
and object SHA-1 instead of ??the tree.

As the only difference between this project and about 30 others was
that there was an additional branch pushed via Egit I suspect that
this is what screwed up things, but I ???m not sure??? I???m in progress of
testing it I don???t know if I will be able to reproduce.

Its a somewhat known problem, but thus far has only shown up in
contexts where I'm unable to get enough data to debug the problem.

  https://bugs.eclipse.org/bugs/show_bug.cgi?id=286653

Please, advise if this can be fixed and which options I have if it
will happen again (how to properly and quickly restore bare repo)

Delete the branch and repush it.  The bug is that EGit didn't push
all of the objects needed by the branch.  If you put the missing
objects from the source client into the server repository, it'll
be fine.

To prevent this in the future, you can force a server to check during
push by enabling receive.fsckObjects in the server repository's
configuration file.  A broken EGit client will have the push
rejected immediately.

-- 
Shawn.