> > Assuming it works and that "git annex test" doesn't show any problems, > > is there anything else I can do to help with git-annex? > > The idea to link the test code into the main binary is quite > unorthodox. I can imagine some arguments for it, but I'll have to > overcome a lot of prior beliefs to accept this as a best practice.
This is the only place I've seen it. Maybe the author did it this way so that users can reassure themselves that their storage backends are working (using the more specialized "git annex testremote" command). > $ touch /home/greg/.config/git-annex/program > $ git-annex test > ... > get (ssh remote): FAIL (1.20s) > ./Test/Framework.hs:57: > get of file failed (transcript follows) > get foo (from origin...) /bin/sh: git-annex-shell: not foundrsync: > connection unexpectedly closed (0 bytes received so far) [Receiver]rsync > error: error in rsync protocol data stream (code 12) at io.c(228) > [Receiver=3.2.3]rsync exited 12 rsync failed -- run git annex again to > resume file transfer transfer failed Unable to access these remotes: origin > Try making some of these remotes available: > a45e9dcd-c958-4026-96e4-a0d9a6fc322b -- test repo [origin]failedgit-annex: > get: 1 failed > ... > 6 out of 975 tests failed (1002.59s) > (Failures above could be due to a bug in git-annex, or an incompatibility > with utilities, such as git, installed on this system.) > > The failing tests are due to unconfigured rsync stuff. I don't think that's an rsync problem. Unfortunately the git-annex-shell binary is missing, and that's pretty critical (needed to access the repository from other machines; sort of like git push/pull). Incidentally, the man pages also seem to be missing. (I think git-annex tries to connect a local rsync process to a remote git-annex-shell process, which would explain why we also see an rsync error message.) I guess this could be solved with custom logic in devel/git-annex/Makefile. I can try to write some custom install commands, maybe tomorrow or Friday. (If you point me to the appropriate variable for overriding/augmenting the install script, that would help; I'm still pretty new to ports.) Alternatively, I think the cabal (v2-)install commands installs what's needed (at least, it gets git-annex-shell, which is the really important thing). Is there some way to take advantage of that in your cabal infrastrsucture? -- James
