summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar darkfeline <darkfeline@web>2015-10-18 20:15:56 +0000
committerGravatar admin <admin@branchable.com>2015-10-18 20:15:56 +0000
commit03b3b8e5c23a1b3c1c21014a4024fdf5197108f1 (patch)
tree826c8cba58d3984f2e71f8da54d380d3c9e29fd2
parent55a75684e96fbc569ef33e4cdd99709b6abb2b56 (diff)
Added a comment
-rw-r--r--doc/forum/Help_fixing_S3_mistake/comment_3_a00bca3b6b0d7b6c20ca1ca749c93469._comment16
1 files changed, 16 insertions, 0 deletions
diff --git a/doc/forum/Help_fixing_S3_mistake/comment_3_a00bca3b6b0d7b6c20ca1ca749c93469._comment b/doc/forum/Help_fixing_S3_mistake/comment_3_a00bca3b6b0d7b6c20ca1ca749c93469._comment
new file mode 100644
index 000000000..acf1d0bb5
--- /dev/null
+++ b/doc/forum/Help_fixing_S3_mistake/comment_3_a00bca3b6b0d7b6c20ca1ca749c93469._comment
@@ -0,0 +1,16 @@
+[[!comment format=mdwn
+ username="darkfeline"
+ subject="comment 3"
+ date="2015-10-18T20:15:56Z"
+ content="""
+Thanks for the help. I'm currently stuck partway through fixing this.
+
+1. I changed the UUID of the remote \"amazon\" in .git/config to the UUID of B.
+2. I changed contents of the annex-uuid file in the S3 bucket from the UUID of A to the UUID of B (making sure to not include a newline).
+
+After this, I think I can follow your steps to fix the problem. However, Git annex is now reporting the error whenever I try to run a command:
+
+ trusted repositories: git-annex: S3 bucket not configured
+
+My understanding of this message is that Git annex is not seeing the UUID it is expecting in the S3 bucket, and that it will be fixed when some cache expires. Is this correct?
+"""]]