summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar andrew <andrew@web>2017-12-05 13:49:42 +0000
committerGravatar admin <admin@branchable.com>2017-12-05 13:49:42 +0000
commit8aaa367f27c3ef30db8db2815331ad229b922735 (patch)
tree5b93facaf080bd07b760fca7164de7de0c2fa4cb
parent6dfa06522ace4e37f1358fa9a4106fbe3e35db2e (diff)
Added a comment: gcrypt, git-annex and rsync requires absolute path
-rw-r--r--doc/bugs/gcrypt_remote__58___every_sync_uploads_huge_manifest/comment_7_2ad1079ba07013fbb8adabc673042a8f._comment8
1 files changed, 8 insertions, 0 deletions
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 000000000..b02478766
--- /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.
+"""]]