From 759346cc65661188ce65680e798844c7e041a1a5 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 5 Jan 2022 15:42:46 -0400 Subject: [PATCH] remove incorrect speculation --- .../comment_4_1360ee3e3b711990f59e0320e7892cd2._comment | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/doc/forum/Failing_to_get_files_from_rclone_special_remote/comment_4_1360ee3e3b711990f59e0320e7892cd2._comment b/doc/forum/Failing_to_get_files_from_rclone_special_remote/comment_4_1360ee3e3b711990f59e0320e7892cd2._comment index a0a5da33ef..7edf7a61f0 100644 --- a/doc/forum/Failing_to_get_files_from_rclone_special_remote/comment_4_1360ee3e3b711990f59e0320e7892cd2._comment +++ b/doc/forum/Failing_to_get_files_from_rclone_special_remote/comment_4_1360ee3e3b711990f59e0320e7892cd2._comment @@ -3,10 +3,7 @@ subject="""comment 4""" date="2022-01-05T19:24:50Z" content=""" -Thanks for verifying. If decryption is failing, I'd guess you somehow -picked the wrong one to enable. The encryption information is included in -the remote's configuration, which could otherwise be close enough that it's -able to get files from the remote, but then fail to decrypt them. +Thanks for verifying. Also FWIW, I'm pushing some changes that improve `git-annex enableremote` in this situation, so it does not choose a random remote to enable.