From e712d30eef909aa760d69831cba4982fd767c4c8 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 11 Nov 2024 16:41:50 -0400 Subject: [PATCH] comment --- ..._585dbd71cf35b8185c34d2847105e1de._comment | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 doc/bugs/importtree_with_versioning__61__yes__58___check_first/comment_1_585dbd71cf35b8185c34d2847105e1de._comment diff --git a/doc/bugs/importtree_with_versioning__61__yes__58___check_first/comment_1_585dbd71cf35b8185c34d2847105e1de._comment b/doc/bugs/importtree_with_versioning__61__yes__58___check_first/comment_1_585dbd71cf35b8185c34d2847105e1de._comment new file mode 100644 index 0000000000..b5717babf7 --- /dev/null +++ b/doc/bugs/importtree_with_versioning__61__yes__58___check_first/comment_1_585dbd71cf35b8185c34d2847105e1de._comment @@ -0,0 +1,20 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2024-11-11T20:11:37Z" + content=""" +Unfortunately does not implement +the versioning check, so it will need to be added there. And it tends to take +some time for new versions of the build dependency to reach everywhere. + + + +I do think that is the only safe way to go though. I considered making +git-annex assume that a bucket where versioning cannot be set is read-only. +If git-annex is really never going to write to a bucket, it's safe to +assume versioning is enabled. But, unfortunately, ACLs can sometimes +prevent changing configs like versioning, but still allow other write +operations. Also, a S3 remote might be initialized without permission to +write to an existing bucket, but later S3 creds be used that do allow +writing. +"""]]