diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2016-05-23 13:00:49 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2016-05-23 13:00:49 -0400 |
| commit | 85395cf9a41ae30c122189fb4c4d59d2630cf68b (patch) | |
| tree | 074dcf34c2d0c6deedb47740b1e3357a304e6f2d | |
| parent | 81d9661e081a7ca11f4bf5547ffe180071fd81ef (diff) | |
comment
| -rw-r--r-- | doc/bugs/__34__invalid_object__34___errors_cropping_up/comment_1_d146a64ef8d76c2a7e45bf85d8943456._comment | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/doc/bugs/__34__invalid_object__34___errors_cropping_up/comment_1_d146a64ef8d76c2a7e45bf85d8943456._comment b/doc/bugs/__34__invalid_object__34___errors_cropping_up/comment_1_d146a64ef8d76c2a7e45bf85d8943456._comment new file mode 100644 index 000000000..6c7b8e268 --- /dev/null +++ b/doc/bugs/__34__invalid_object__34___errors_cropping_up/comment_1_d146a64ef8d76c2a7e45bf85d8943456._comment @@ -0,0 +1,17 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2016-05-23T16:52:23Z" + content=""" +Try running `git fsck` and see if it complains about a corrupt object file. +You may then need to delete the object file and fix up the repository to +not refer to it. `git annex repair` can probably handle that. + +> Some object in the broken repo seems to be causing this issue somehow. + +Maybe, but you also say that the object it complains about has varied. +Perhaps you have multiple corrupt objects in the git repo.. + +You mention "litelog". What is that and how is it relevant? Is Android +involved somehow? +"""]] |