From 027bd5bfeb15638584426a04eb719efc1b3edec2 Mon Sep 17 00:00:00 2001 From: yarikoptic Date: Thu, 7 Nov 2024 21:39:42 +0000 Subject: [PATCH] --- .../importtree_with_versioning__61__yes__58___check_first.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/bugs/importtree_with_versioning__61__yes__58___check_first.mdwn b/doc/bugs/importtree_with_versioning__61__yes__58___check_first.mdwn index baf88934f1..01c34bb718 100644 --- a/doc/bugs/importtree_with_versioning__61__yes__58___check_first.mdwn +++ b/doc/bugs/importtree_with_versioning__61__yes__58___check_first.mdwn @@ -1,6 +1,6 @@ ### Please describe the problem. -I wanted to use this remote to "crawl" S3 bucket in `importtree=yes` mode. Bucket (dandiarchive) supports versioning, so it would be great to enable versioning here as well so URLs would use versionId. But unfortunately adding `versioning=yes` makes `git-annex` to try to establish versioning on the bucket (even if it is already enabled). +I wanted to use S3 special remote to "crawl" S3 bucket in `importtree=yes` mode. Bucket (dandiarchive) supports versioning, so it would be great to enable versioning here as well so URLs would use versionId. But unfortunately adding `versioning=yes` makes `git-annex` to try to establish versioning on the bucket (even if it is already enabled). command to try with (should work for anyone since public bucket):