From 372ace599a41aec4c30ddf9d7814f18a0d6751c9 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 14 Jun 2021 13:13:46 -0400 Subject: [PATCH] comment --- ...ent_1_c36b1968c69e9794c723ff29d1738759._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/bugs/__34__failed_to_send_content_to_remote__34__/comment_1_c36b1968c69e9794c723ff29d1738759._comment diff --git a/doc/bugs/__34__failed_to_send_content_to_remote__34__/comment_1_c36b1968c69e9794c723ff29d1738759._comment b/doc/bugs/__34__failed_to_send_content_to_remote__34__/comment_1_c36b1968c69e9794c723ff29d1738759._comment new file mode 100644 index 0000000000..6782785529 --- /dev/null +++ b/doc/bugs/__34__failed_to_send_content_to_remote__34__/comment_1_c36b1968c69e9794c723ff29d1738759._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2021-06-14T17:06:19Z" + content=""" +From the --deubg you provided, the important part is that rsync is +succeeding to copy the file, but then git-annex for some reason thinks it +failed, or has some other problem. Eg, if the annexed object was corrupt, +it could copy it with rsync and then fail to verify the copy. + +Your git-annex version is a year out of date, so you should upgrade. The +code that is failing has definitely been changed a lot in the meantime, +though not that I can remember to fix a bug like this. +"""]]