Open mslw opened 2 years ago
The reason is likely this: remote-datalad-annex
is actually git-remote-datalad-annex
called as a subcommand by git. Adn git cannot find it. git-remote-datalad-annex
is installed by datalad-next
into the environment where itself is installed. This environment's script/bin path does not seem to be known to the PATH
setting of the environment that git is running in.
From the diagnostic info you provided it is clear that multiple python versions are in the PATH and also Git. It is unclear to me where datalad-next was installed in relation to that.
Maybe we should add the installation location to the wtf
output on extensions.
This is a user report. Gooey 0.1 (
0.1.0+9.g2f5814c
) on Windows.Running push to a webdav sibling (filetree mode) ends with the following error. Files were sent to the remote - we can't know for sure as the remote folder was changed since, but I suspect that git annex export (of file content) worked, and publishing the packaged git repo failed.
Full traceback
(user name edited out) ``` Running: Dataset('C:\\projectB04').push(to='sciebo') failed! Traceback (most recent call last): File "C:\Users\Diagnostic infos
(user name edited out) ``` # WTF ## configurationI am not sure what could cause the unavailability of
datalad-annex
, since datalad-next is, clearly, installed. The error comes from git itself, and I can replicate it when running the git command in a virtualenv without datalad-next.If we get a successful report from Gooey 0.2, I think we can safely close this one. But meanwhile - does anybody see something concerning?