mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

response

Browse source
This commit is contained in:
Joey Hess 2018-10-08 12:04:57 -04:00
parent 9ada622067
commit 7f04d03688
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 18 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

18
doc/bugs/git-annex.linux.6.20180914_-__62___assistant_requires_s3_bucket/comment_1_5ec1d63e8f2896876fc88d53b6170b74._comment Normal file
View file

@ -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`
"""]]