mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

comment

Browse source
This commit is contained in:
Joey Hess 2023-11-28 12:23:35 -04:00
parent a237f98a70
commit 241a344128
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 15 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
doc/forum/git-remote-gcrypt_and_rsyncd/comment_1_34dd343ed75918f5969f6a23dfae3317._comment Normal file
View file

@ -0,0 +1,15 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2023-11-28T16:06:22Z"
content="""
That is a pretty weird error message! It looks like git-annex may have run
git but tried to pass it a working directory that does not exist. It would
be interesting to know what git command, passing --debug would tell you.
But: The gcrypt special remote is documented as needing gitrepo=rsync:// to
operate over ssh. And git-remote-gcrypt interprets a rsync:// url as rsync
over ssh (see its man page). Yes, "host::" in rsync indicates direct contact
to a rsync daemon, not using ssh, but that will not work with git-remote-gcrypt
to the best of my knowledge.
"""]]