From 195f870265f75cf54dda0b27f203ae11b0ab1336 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 15 Aug 2022 14:05:05 -0400 Subject: [PATCH] comment --- ...1_ba5b0ed901c99a23ff72d68b83c0d2fa._comment | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 doc/bugs/failure_getting__47__copying_on_git-lfs_remote___40__gcrypt__41__/comment_1_ba5b0ed901c99a23ff72d68b83c0d2fa._comment diff --git a/doc/bugs/failure_getting__47__copying_on_git-lfs_remote___40__gcrypt__41__/comment_1_ba5b0ed901c99a23ff72d68b83c0d2fa._comment b/doc/bugs/failure_getting__47__copying_on_git-lfs_remote___40__gcrypt__41__/comment_1_ba5b0ed901c99a23ff72d68b83c0d2fa._comment new file mode 100644 index 0000000000..62bbca6f71 --- /dev/null +++ b/doc/bugs/failure_getting__47__copying_on_git-lfs_remote___40__gcrypt__41__/comment_1_ba5b0ed901c99a23ff72d68b83c0d2fa._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2022-08-15T17:42:49Z" + content=""" +I think that the problem is that keyid= can only be specified once, +so the last keyid= you specified was used, which was yours, and it ignored +the other one. + +Try `git-annex enableremote origin keyid+=FCE2EDE78BD9B2CB` + +I found some documentation that says that keyid= can be repeated multiple +times, and I think that documentation is wrong, and probably led you +astray. It's also possible that it used to work and was broken in some +option parsing changes, unsure. I'm working to correct the documentation now. + +(Or, encryption=shared seems likely to avoid whatever the problem is.) +"""]] -- 2.30.2