From 0e18bf029e6721b1c9665b0fbea6d281b9d65f7c Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 23 Mar 2023 14:21:36 -0400 Subject: [PATCH] comment --- ..._b4523baf0cdfc2ad70cded93b1629eca._comment | 30 +++++++++++++++++++ 1 file changed, 30 insertions(+) create mode 100644 doc/bugs/gcrypt_remotes_using_relative_paths/comment_1_b4523baf0cdfc2ad70cded93b1629eca._comment diff --git a/doc/bugs/gcrypt_remotes_using_relative_paths/comment_1_b4523baf0cdfc2ad70cded93b1629eca._comment b/doc/bugs/gcrypt_remotes_using_relative_paths/comment_1_b4523baf0cdfc2ad70cded93b1629eca._comment new file mode 100644 index 0000000000..7f589384a2 --- /dev/null +++ b/doc/bugs/gcrypt_remotes_using_relative_paths/comment_1_b4523baf0cdfc2ad70cded93b1629eca._comment @@ -0,0 +1,30 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2023-03-23T17:53:22Z" + content=""" +The lack of a transcript made this bug hard to understand. After about +half an hour of staring at it, I realized that you mean that `git-annex sync` +does not even attempt to sync with the remote when it has the relative url: + + joey@darkstar:~/tmp/bb>git remote add test gcrypt::rsync://user@user.rsync.net:relative/path/to/repo + joey@darkstar:~/tmp/bb>git-annex sync + commit + On branch master + nothing to commit, working tree clean + ok + +It does sync with it when asked to sync with explicitly that remote: + + joey@darkstar:~/tmp/bb>git-annex sync test + commit + On branch master + nothing to commit, working tree clean + ok + pull test + gcrypt: Repository not found: rsync://user@user.rsync.net:relative/path/to/repo + ok + +With the absolute url, it does sync with it when no remote +is explicitly specified. +"""]]