response

doc/forum/Migrate_from_one_connection_mechanism_for_special_remote_to_another/comment_1_6e8e3350ae26b6c59daa56b7e86cc46a._comment

@@ -0,0 +1,14 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2018-05-30T15:21:57Z"
+ content="""
+Yes, there is an intermediate encryption key.
+
+What may work is to use `git annex enableremote` on the original remote
+with `externaltype=rclone`, which will make it use the other program.
+
+Whether this will work depends on implementation details of both special
+remotes. If they use the same names/urls/whatever to access the data stored
+in them, it should work.
+"""]]

stack.yaml

@@ -16,9 +16,16 @@ flags:
 packages:
 - '.'
 extra-deps:
-- aws-0.17.1
+- IfElse-0.85
+- aws-0.20
 - bloomfilter-2.0.1.0
+- esqueleto-2.5.3
+- sandi-0.4.2
 - torrent-10000.1.1
+- persistent-2.7.3.1
+- conduit-1.3.0.2
+- resourcet-1.2.1
+allow-newer: true
 explicit-setup-deps:
   git-annex: true
-resolver: lts-9.9
+resolver: lts-11.11