response

diff --git a/doc/special_remotes/rclone/comment_6_da9d155ac18208f08c3c085eda0ec7be._comment b/doc/special_remotes/rclone/comment_6_da9d155ac18208f08c3c085eda0ec7be._comment
new file mode 100644 (file)
index 0000000..b1273d0
--- /dev/null
+++ b/doc/special_remotes/rclone/comment_6_da9d155ac18208f08c3c085eda0ec7be._comment
@@ -0,0 +1,17 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""Re: corruption using git-annex-remote-rclone"""
+ date="2024-10-21T14:35:17Z"
+ content="""
+This is plausible. git-annex requires that special remotes only show a file
+as present after a successful upload. If the data store doesn't work that
+way, the file needs to be uploaded to a temporary name and renamed
+atomically instead. If that's not possible, the data store is not safe for
+use by git-annex.
+
+Given all the different types data stores supported by rclone, this may be
+difficult, but it's the right thing for the external special remote to do.
+I think you should file a bug.
+
+(Does `rclone gitannex` also have this problem?)
+"""]]