From 7f04d03688b5f71b120d1450456cb6e488c35e3c Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 8 Oct 2018 12:04:57 -0400 Subject: [PATCH] response --- ...1_5ec1d63e8f2896876fc88d53b6170b74._comment | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 doc/bugs/git-annex.linux.6.20180914_-__62___assistant_requires_s3_bucket/comment_1_5ec1d63e8f2896876fc88d53b6170b74._comment diff --git a/doc/bugs/git-annex.linux.6.20180914_-__62___assistant_requires_s3_bucket/comment_1_5ec1d63e8f2896876fc88d53b6170b74._comment b/doc/bugs/git-annex.linux.6.20180914_-__62___assistant_requires_s3_bucket/comment_1_5ec1d63e8f2896876fc88d53b6170b74._comment new file mode 100644 index 0000000000..1a147ffa59 --- /dev/null +++ b/doc/bugs/git-annex.linux.6.20180914_-__62___assistant_requires_s3_bucket/comment_1_5ec1d63e8f2896876fc88d53b6170b74._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2018-10-08T16:01:21Z" + content=""" +It seems to me this must depend on the repository that you have the +assistant configured to run in. If that repository has a S3 remote set up +in the git config, but is somehow missing the bucket name configuration, +that would explain this error message. + +Or, the S3 remote in question might have been configured with +autoenable=true, so git-annex tries to enabled it on a new clone? + +So please show your repository's .git/config file, and also +the output of this command run in the repository: + +`git show git-annex:remote.log | grep autoenable | cut -d" " -f1` +"""]]