Merge branch 'master' of ssh://git-annex.branchable.com

doc/bugs/testremote_with_external_remote_hangs_after_asyncexternal_merge.mdwn

@@ -0,0 +1,58 @@
+The DataLad tests run one of our custom special remotes through `git
+annex testremote`.  As mentioned in a recent [DataLad issue][1], this
+test has started to fail.  When I run the test locally, it hangs.
+This starts with the recent merge of the asyncexternal branch
+(95d9a3cf8).
+
+Here's a reproducer that takes DataLad out of the equation.  It uses
+the example external remote.
+
+[[!format sh """
+#!/bin/sh
+
+set -eu
+
+ga_srcdir="$(realpath "${1?requires git-annex source directory as argument}")"
+cd "$(mktemp -d "${TMPDIR:-/tmp}"/gx-testremote-XXXXXXX)"
+top="$PWD"
+
+mkdir bin
+git -C "$ga_srcdir" cat-file -p \
+    1740c4ef650dd2bf3b1d91322d55aace7667b822:doc/special_remotes/external/example.sh \
+    >bin/git-annex-remote-foo
+chmod +x bin/git-annex-remote-foo
+export PATH="$top/bin:$PATH"
+
+export MYPASSWORD="x"
+export MYLOGIN="x"
+mkdir d
+
+git init a
+(
+    cd a
+    git annex init main
+    git annex initremote d \
+        type=external externaltype=foo directory="$top/d" encryption=none
+    git annex testremote --fast d
+)
+"""]]
+
+With the latest commit on master checked out (67cad93f8), the above
+script stalls on my end at
+
+```
+testremote d (generating test keys...)
+  Cannot run git-annex-remote-!dne! -- It is not installed in PATH (/home/kyle/src/c/git-bin:/home/kyle/src/c/git-bin/bin-wrappers:/tmp/gx-testremote-aiS5Ztm/bin:/home/kyle/src/haskell/git-annex/.stack-work/install/x86_64-linux-tinfo6/5bf51f244130923958226fa250ede392c8c3d23ac815c7b4b9d65910222773d4/8.6.5/bin:/home/kyle/.stack/snapshots/x86_64-linux-tinfo6/5bf51f244130923958226fa250ede392c8c3d23ac815c7b4b9d65910222773d4/8.6.5/bin:/home/kyle/.stack/compiler-tools/x86_64-linux-tinfo6/ghc-8.6.5/bin:/home/kyle/.stack/programs/x86_64-linux/ghc-tinfo6-8.6.5/bin:/home/kyle/src/python/venvs/datalad//bin:/home/kyle/src/c/git-bin/bin-wrappers:/home/kyle/.guix-profile/bin:/home/kyle/.config/guix/current/bin:/home/kyle/.cabal/bin:/usr/lib/ccache/bin:/home/kyle/.local/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games)
+Remote Tests
+  unavailable remote
+    removeKey:
+```
+
+With the first commit before the merge checked out (0900bb2ca), the
+`testremote` call completes successfully.
+
+[1]: https://github.com/datalad/datalad/issues/4825
+
+
+[[!meta author=kyle]]
+[[!tag projects/datalad]]

doc/forum/NTFS_drive_mounted_on_Linux.mdwn

@@ -0,0 +1,6 @@
+Maybe someone here can help me with this. I'm trying out git-annex as a way to handle my photo collection. My case is as follows.
+I have a laptop running Manjaro. I have my photo collection on a USB drive formatted NTFS so I can also use it on Windows systems. I'd like to use git-annex to selectively check out files from that drive to my laptop. The files are (immutable) .NEF raw files and .xmp text files that I could track with regular git.
+
+The problem is that NTFS mounted on Linux does not seem to honour the write bit, so git-annex detects a crippled file system and defaults to unlocked mode. Effectively this halves the storage capacity of my external drive (with every file in both the annex and the working directory), which is of course less than ideal.
+
+Is there a way to handle this? Did I configure my mounting options incorrectly, or is git-annex not the right tool for this job and should I just use rsync?

doc/forum/Problem_with_Anaconda_and_git-annex_on_Windows.mdwn

@@ -0,0 +1 @@
+I have a problem with using git-annex with Anaconda (I'm using Windows 10). I have installed Git (using "conda install -c conda-forge git" under Anaconda prompt) and then git-annex (in the Anaconda3/Library directory, as suggested e.g., here: http://handbook.datalad.org/en/inm7/intro/installation.html#windows-10). However, Anaconda doesn't seem to recognize git-annex at all (for example, running "git annex test" gives the error that "annex" is not a valid git command). At the same time I can run git and git-annex using Windows command line). I'd appreciate any help (is it somehow a problem with installation paths or something deeper?).