[ sorry for the delay -- I just returned from vacation ] On Fri, 8 Aug 2008, Johannes Schindelin wrote: > Hi, > > my auto gc kicked in, and shows this: > > fatal: corrupt packed object for 2c1e128aa51e3a64bd61556c0cd488628b423ccf > error: failed to run repack > > Fortunately, I have the uncorrupted object somewhere else. So I copy the > single object as a loose one, and all is fine. Right? > > Wrong. Well, to be sure things are then right or wrong, just do a git show 2c1e128aa51e3a64bd61556c0cd488628b423ccf If you can't see the object before, and are able to see it once it has been copied over, then things are "right". > Repack still picks up the corrupt object instead of the good one. What's > the best way out? How do you repack? The only way to get rid of a corrupted object in that case is to 'git repack -a -f'. Nicolas -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
