currently trying to datalad ls someone else's repository would start crashing with all the errors to be unable to lock that repository, while git annex info is ran.
In recent http://git-annex.branchable.com/bugs/impossible_to_perform___34__read-only__34___git_annex_info_without_write_permissions/#comment-04827552f7895ca8557e416e48e173c1 @joeyh implemented a config option to avoid "git-annex merge" being ran in the background, which would provide remedy here. The only question either we should make it a default mode of operation for annex info in case of ls, optional, or automagic (enable if permissions issues reported in the initial attempted git annex info run)
What is the problem?
currently trying to
datalad ls
someone else's repository would start crashing with all the errors to be unable to lock that repository, whilegit annex info
is ran. In recent http://git-annex.branchable.com/bugs/impossible_to_perform___34__read-only__34___git_annex_info_without_write_permissions/#comment-04827552f7895ca8557e416e48e173c1 @joeyh implemented a config option to avoid "git-annex merge" being ran in the background, which would provide remedy here. The only question either we should make it a default mode of operation forannex info
in case ofls
, optional, or automagic (enable if permissions issues reported in the initial attemptedgit annex info
run)