From c139a73b876040377bb96f887e085be971f8ffb7 Mon Sep 17 00:00:00 2001 From: "talmukoydu@ab15521191b4d02584d003f3f211d90f575d5ebb" Date: Sun, 19 Mar 2023 19:08:14 +0000 Subject: [PATCH 1/4] Added a comment: `git annex sync` not syncing automatically with gcrypt remotes --- ..._ea7ae356fecea4b0cc846146312cc48d._comment | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 doc/sync/comment_29_ea7ae356fecea4b0cc846146312cc48d._comment diff --git a/doc/sync/comment_29_ea7ae356fecea4b0cc846146312cc48d._comment b/doc/sync/comment_29_ea7ae356fecea4b0cc846146312cc48d._comment new file mode 100644 index 0000000000..0419882289 --- /dev/null +++ b/doc/sync/comment_29_ea7ae356fecea4b0cc846146312cc48d._comment @@ -0,0 +1,20 @@ +[[!comment format=mdwn + username="talmukoydu@ab15521191b4d02584d003f3f211d90f575d5ebb" + nickname="talmukoydu" + avatar="http://cdn.libravatar.org/avatar/965ffeb49ec136674054e50928ddb2ed" + subject="`git annex sync` not syncing automatically with gcrypt remotes" + date="2023-03-19T19:08:13Z" + content=""" +@joey Is this a bug or am I missing something? + +Notes: +* I am using the latest `git-remote-gcrypt`, version 1.5 + +* `ssh user@user.rsync.net \"git init --bare repo\"` +* `git remote add test gcrypt::rsync://xxxx@xxxx.rsync.net:repo` +* `git annex sync -> DOES NOT SYNC to test remote` + +* `ssh user@user.rsync.net \"git init --bare repo\"` +* `git remote add test gcrypt::xxxx@xxxx.rsync.net/full/path/to/repo` +* `git annex sync -> DOES SYNC to test remote` +"""]] From c006cfca565c5f6cd7037dcce2e1bd44bf48aa00 Mon Sep 17 00:00:00 2001 From: "talmukoydu@ab15521191b4d02584d003f3f211d90f575d5ebb" Date: Sun, 19 Mar 2023 19:08:48 +0000 Subject: [PATCH 2/4] removed --- ..._ea7ae356fecea4b0cc846146312cc48d._comment | 20 ------------------- 1 file changed, 20 deletions(-) delete mode 100644 doc/sync/comment_29_ea7ae356fecea4b0cc846146312cc48d._comment diff --git a/doc/sync/comment_29_ea7ae356fecea4b0cc846146312cc48d._comment b/doc/sync/comment_29_ea7ae356fecea4b0cc846146312cc48d._comment deleted file mode 100644 index 0419882289..0000000000 --- a/doc/sync/comment_29_ea7ae356fecea4b0cc846146312cc48d._comment +++ /dev/null @@ -1,20 +0,0 @@ -[[!comment format=mdwn - username="talmukoydu@ab15521191b4d02584d003f3f211d90f575d5ebb" - nickname="talmukoydu" - avatar="http://cdn.libravatar.org/avatar/965ffeb49ec136674054e50928ddb2ed" - subject="`git annex sync` not syncing automatically with gcrypt remotes" - date="2023-03-19T19:08:13Z" - content=""" -@joey Is this a bug or am I missing something? - -Notes: -* I am using the latest `git-remote-gcrypt`, version 1.5 - -* `ssh user@user.rsync.net \"git init --bare repo\"` -* `git remote add test gcrypt::rsync://xxxx@xxxx.rsync.net:repo` -* `git annex sync -> DOES NOT SYNC to test remote` - -* `ssh user@user.rsync.net \"git init --bare repo\"` -* `git remote add test gcrypt::xxxx@xxxx.rsync.net/full/path/to/repo` -* `git annex sync -> DOES SYNC to test remote` -"""]] From 18b9731131fca2d2c51cd25a91b71e576641d26d Mon Sep 17 00:00:00 2001 From: "talmukoydu@ab15521191b4d02584d003f3f211d90f575d5ebb" Date: Sun, 19 Mar 2023 19:20:45 +0000 Subject: [PATCH 3/4] Added a comment: `git annex sync` not automatically syncing gcrypt remotes using relative paths --- ..._161c5d3f693de45070e037d27ee7e8aa._comment | 27 +++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 doc/sync/comment_29_161c5d3f693de45070e037d27ee7e8aa._comment diff --git a/doc/sync/comment_29_161c5d3f693de45070e037d27ee7e8aa._comment b/doc/sync/comment_29_161c5d3f693de45070e037d27ee7e8aa._comment new file mode 100644 index 0000000000..c234527fac --- /dev/null +++ b/doc/sync/comment_29_161c5d3f693de45070e037d27ee7e8aa._comment @@ -0,0 +1,27 @@ +[[!comment format=mdwn + username="talmukoydu@ab15521191b4d02584d003f3f211d90f575d5ebb" + nickname="talmukoydu" + avatar="http://cdn.libravatar.org/avatar/965ffeb49ec136674054e50928ddb2ed" + subject="`git annex sync` not automatically syncing gcrypt remotes using relative paths" + date="2023-03-19T19:20:44Z" + content=""" +@joey Is this a bug or am I missing something? + +Notes: + +* I am using the latest git-remote-gcrypt, version 1.5 + +Flow 1 + +* `git remote add test gcrypt::rsync://user@user.rsync.net:relative/path/to/repo` +* `git annex sync` -> DOES NOT SYNC to test remote +* Nothing has been synced so I CANNOT successfully clone from the test remote with `git clone gcrypt::rsync://user@user.rsync.net:relative/path/to/repo` +* `git push test git-annex master` +* I can successfully clone from the test remote with `git clone gcrypt::rsync://user@user.rsync.net:relative/path/to/repo` + +Flow 2 + +* `git remote add test gcrypt::rsync://user@user.rsync.net/full/path/to/repo` +* `git annex sync` -> DOES SYNC to test remote +* I can successfully clone from the test remote with `git clone gcrypt::rsync://user@user.rsync.net:relative/path/to/repo` +"""]] From b09405eeab5da9c8fa77b6c73f61856c2c007af4 Mon Sep 17 00:00:00 2001 From: "talmukoydu@ab15521191b4d02584d003f3f211d90f575d5ebb" Date: Sun, 19 Mar 2023 19:27:46 +0000 Subject: [PATCH 4/4] Added a comment: RE: `git annex sync` not automatically syncing gcrypt remotes using relative paths --- .../comment_30_f75f5957dbd0f6fd7b2d7291f06e7489._comment | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 doc/sync/comment_30_f75f5957dbd0f6fd7b2d7291f06e7489._comment diff --git a/doc/sync/comment_30_f75f5957dbd0f6fd7b2d7291f06e7489._comment b/doc/sync/comment_30_f75f5957dbd0f6fd7b2d7291f06e7489._comment new file mode 100644 index 0000000000..41a455d79d --- /dev/null +++ b/doc/sync/comment_30_f75f5957dbd0f6fd7b2d7291f06e7489._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="talmukoydu@ab15521191b4d02584d003f3f211d90f575d5ebb" + nickname="talmukoydu" + avatar="http://cdn.libravatar.org/avatar/965ffeb49ec136674054e50928ddb2ed" + subject="RE: `git annex sync` not automatically syncing gcrypt remotes using relative paths" + date="2023-03-19T19:27:46Z" + content=""" +@joey definitely seems like a bug. I am able to easily verify by changing the remote url back and forth in the .git/config and then running git annex sync. If the relative url is used git annex sync does not sync to that remote. +"""]]