From 0d35a61802aad5a70dfdf877dd72e1435b12aa98 Mon Sep 17 00:00:00 2001 From: pot Date: Mon, 25 Jul 2016 18:23:13 +0000 Subject: Added a comment: Same issue --- .../comment_5_f45d09939527be362c586ae1d470afe4._comment | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 doc/bugs/Packfile_does_not_match_digest__58___gcrypt_with_assistant/comment_5_f45d09939527be362c586ae1d470afe4._comment (limited to 'doc') diff --git a/doc/bugs/Packfile_does_not_match_digest__58___gcrypt_with_assistant/comment_5_f45d09939527be362c586ae1d470afe4._comment b/doc/bugs/Packfile_does_not_match_digest__58___gcrypt_with_assistant/comment_5_f45d09939527be362c586ae1d470afe4._comment new file mode 100644 index 000000000..4fbbfe1ca --- /dev/null +++ b/doc/bugs/Packfile_does_not_match_digest__58___gcrypt_with_assistant/comment_5_f45d09939527be362c586ae1d470afe4._comment @@ -0,0 +1,7 @@ +[[!comment format=mdwn + username="pot" + subject="Same issue" + date="2016-07-25T18:23:13Z" + content=""" +Anyone got any ideas on how to fix this, or move forward without starting again and trashing the gcrypt repos? Bit of a serious bug this, if it can't be repaired. I was using git-annex for backups, but finding your backups are corrupt would be a bit of a nightmare! +"""]] -- cgit v1.2.3