From bf3c032a3123aab5bd635aa6a4c62ee40e1985f9 Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Fri, 24 May 2019 03:05:32 +0000 Subject: [PATCH] strange interaction of checkpresentkey and annex-readonly=true --- .../checkpresentkey_fails_on_read-only_remote.mdwn | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/bugs/checkpresentkey_fails_on_read-only_remote.mdwn diff --git a/doc/bugs/checkpresentkey_fails_on_read-only_remote.mdwn b/doc/bugs/checkpresentkey_fails_on_read-only_remote.mdwn new file mode 100644 index 0000000000..7230b5c5eb --- /dev/null +++ b/doc/bugs/checkpresentkey_fails_on_read-only_remote.mdwn @@ -0,0 +1,10 @@ +In an external special remote, if I set annex-readonly=true, I get + +[[!format sh """ + git annex --verbose --debug checkpresentkey MD5E-s18932--663e2e38c829d7b3fff12fce3a6fdb6d.fasta 380286ac-2e8f-4285-94da-406eca323411 +... +(checking dnanexus...) Configuration does not allow accessing dx://file-BXF0vYQ0QyBF509G9J12g927/contaminants.clip_db.fasta +"""]] + +Removing the annex-readonly setting lets checkpresentkey work. But isn't checkpresentkey a read-only operation? +