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

comment

Browse source
This commit is contained in:
Joey Hess 2024-11-11 16:41:50 -04:00
parent 1e18df9c3a
commit e712d30eef
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 20 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
doc/bugs/importtree_with_versioning__61__yes__58___check_first/comment_1_585dbd71cf35b8185c34d2847105e1de._comment Normal file
View file

@ -0,0 +1,20 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2024-11-11T20:11:37Z"
content="""
Unfortunately <https://hackage.haskell.org/package/aws> 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.
<https://github.com/aristidb/aws/issues/290>
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.
"""]]