From fe2f39abbb0f8eb89e47f74fe50948084b313bbe Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 2 Jun 2022 11:59:26 -0400 Subject: [PATCH] close as already fixed --- ...undant_quote_in_the_filepath_with_rsync_remote.mdwn | 2 ++ ...comment_1_53d3e78c0fb4d4c398dd47498e6348aa._comment | 10 ++++++++++ 2 files changed, 12 insertions(+) create mode 100644 doc/bugs/Redundant_quote_in_the_filepath_with_rsync_remote/comment_1_53d3e78c0fb4d4c398dd47498e6348aa._comment diff --git a/doc/bugs/Redundant_quote_in_the_filepath_with_rsync_remote.mdwn b/doc/bugs/Redundant_quote_in_the_filepath_with_rsync_remote.mdwn index b011eb46b3..71bbb75271 100644 --- a/doc/bugs/Redundant_quote_in_the_filepath_with_rsync_remote.mdwn +++ b/doc/bugs/Redundant_quote_in_the_filepath_with_rsync_remote.mdwn @@ -45,3 +45,5 @@ Makes this particular error go away, only to fail with ../../../.git/annex/tmp/GPGHMACSHA1--addf78b2c59182e951d16ce90e03900cfe15dc7d: openBinaryFile: does not exist (No such file or directory) This is likely because the file has been downloaded into tmp directory with the trailing quote. To summarize, it seems that file and its parent folder in the rsync remote directory tree are being wrapped by single quotes, resulting into a file lookup failure. + +> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/Redundant_quote_in_the_filepath_with_rsync_remote/comment_1_53d3e78c0fb4d4c398dd47498e6348aa._comment b/doc/bugs/Redundant_quote_in_the_filepath_with_rsync_remote/comment_1_53d3e78c0fb4d4c398dd47498e6348aa._comment new file mode 100644 index 0000000000..8d06f3faae --- /dev/null +++ b/doc/bugs/Redundant_quote_in_the_filepath_with_rsync_remote/comment_1_53d3e78c0fb4d4c398dd47498e6348aa._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2022-06-02T15:58:10Z" + content=""" +This is a breakage caused by rsync 3.2.4 which broke backwards +compatability. + +It is fixed in git-annex 10.20220504. +"""]]