From 6db7079cb0af5c1bfe2fd755c9ac0b47f1ecfc24 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 1 Sep 2021 10:47:33 -0400 Subject: [PATCH] close --- ...t_content_via_ssh_without_write_perms.mdwn | 2 ++ ..._ba7e53135285dbf198f5aa12d7edc1cd._comment | 22 +++++++++++++++++++ 2 files changed, 24 insertions(+) create mode 100644 doc/bugs/unable_to_get_content_via_ssh_without_write_perms/comment_7_ba7e53135285dbf198f5aa12d7edc1cd._comment diff --git a/doc/bugs/unable_to_get_content_via_ssh_without_write_perms.mdwn b/doc/bugs/unable_to_get_content_via_ssh_without_write_perms.mdwn index 917879012b..fe09223da3 100644 --- a/doc/bugs/unable_to_get_content_via_ssh_without_write_perms.mdwn +++ b/doc/bugs/unable_to_get_content_via_ssh_without_write_perms.mdwn @@ -72,3 +72,5 @@ create a git-annex repo owned by another user, provide permissions for others to [[!meta author=yoh]] [[!tag projects/datalad]] + +> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/unable_to_get_content_via_ssh_without_write_perms/comment_7_ba7e53135285dbf198f5aa12d7edc1cd._comment b/doc/bugs/unable_to_get_content_via_ssh_without_write_perms/comment_7_ba7e53135285dbf198f5aa12d7edc1cd._comment new file mode 100644 index 0000000000..d59723763f --- /dev/null +++ b/doc/bugs/unable_to_get_content_via_ssh_without_write_perms/comment_7_ba7e53135285dbf198f5aa12d7edc1cd._comment @@ -0,0 +1,22 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 7""" + date="2021-09-01T14:32:11Z" + content=""" +I'm going to close this, since I was able to replicate and fix one of the +errors, and was not able to replicate the other one. If the other one +still happens, follow up with the output of the current version of +git-annex, as I've requested 3 times now. + +There is a test case now that tests the same thing, too. It has passed +on all the builders. (Except windows. I've learned git-annex cannot support +readonly repos on Windows, because it has to be able to create lock files +there.) + +(There are still situations where git-annex needs to write to a repo in order to +use it. The main one is if the it needs to upgrade the repo. I think +failing in that specific situation is ok, and it fails with an informative +error message IIRC. It's also possible there's some other situation of some +kind where the readonly repo is in a state where git-annex wants to write +to it, but if there is, I can fix it when the situation comes to light.) +"""]]