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-03-23 14:21:36 -04:00
parent 3f75e9294c
commit 0e18bf029e
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 30 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

30
doc/bugs/gcrypt_remotes_using_relative_paths/comment_1_b4523baf0cdfc2ad70cded93b1629eca._comment Normal file
View file

@ -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.
"""]]