From 1807fb2a8ad19d96e25aa77d4be9161f5f01a8e8 Mon Sep 17 00:00:00 2001 From: andrew Date: Tue, 5 Dec 2017 13:49:42 +0000 Subject: [PATCH] Added a comment: gcrypt, git-annex and rsync requires absolute path --- .../comment_7_2ad1079ba07013fbb8adabc673042a8f._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/bugs/gcrypt_remote__58___every_sync_uploads_huge_manifest/comment_7_2ad1079ba07013fbb8adabc673042a8f._comment diff --git a/doc/bugs/gcrypt_remote__58___every_sync_uploads_huge_manifest/comment_7_2ad1079ba07013fbb8adabc673042a8f._comment b/doc/bugs/gcrypt_remote__58___every_sync_uploads_huge_manifest/comment_7_2ad1079ba07013fbb8adabc673042a8f._comment new file mode 100644 index 0000000000..b024787665 --- /dev/null +++ b/doc/bugs/gcrypt_remote__58___every_sync_uploads_huge_manifest/comment_7_2ad1079ba07013fbb8adabc673042a8f._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="andrew" + avatar="http://cdn.libravatar.org/avatar/acc0ece1eedf07dd9631e7d7d343c435" + subject="gcrypt, git-annex and rsync requires absolute path" + date="2017-12-05T13:49:42Z" + content=""" +I struggled to get git-annex sync working for some time with gcrypt and the rsync transport protocol. It turns out I was using a relative path to my repo instead of an absolute path. In my .git/config with a url like this: `gcrypt::rsync://username@servername:relative-path-to-git-repo` where relative path is relative to my user's home directory, git push would work fine, but git-annex sync would complain it couldn't find the repository. Changing my url to an absolute path like `gcrypt::rsync://username@servername:absolute-path-to-git-repo` now allows both git-annex sync and git push to work. Andrew. +"""]]