Please describe the problem.
An encrypted remote is added to a working git annex repository (mind ":~/" in the remote add command). However, after that any git annex command fails.
What steps will reproduce the problem?
> git remote add encrypted gcrypt::ssh://git@gitlab.com:~/gitlabname/reponame.git
> git push encrypted master
gcrypt: Repository not found: ssh://git@gitlab.com:~/gitlabname/reponame.git
gcrypt: Setting up new repository
gcrypt: Remote ID is :id:abcdefghijklmnopqrst
Counting objects: 53, done.
Compressing objects: 100% (52/52), done.
Total 53 (delta 12), reused 0 (delta 0)
gcrypt: Encrypting to: --throw-keyids --default-recipient-self
gcrypt: Requesting manifest signature
...
To gcrypt::ssh://git@gitlab.com:~/gitlabname/reponame.git
* [new branch] master -> master
>
> git annex sync
git-annex: bad url ssh://git@gitlab.com:~/gitlabname/reponame.git
What version of git-annex are you using? On what operating system?
5.20150419-g900e1b6 on Mac OS X
Please provide any additional information below.
# If you can, paste a complete transcript of the problem occurring here.
# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
# End of transcript or log.
Fixed in 2aa4fab62a69bb3fb5073d571d8ec110a61a144e done --Joey
According to the git-fetch man page, the syntax to use for this kind of url is:
Your url is missing the leading slash before the
~
, and has a : with no port specified.It is in fact, not a legal url.
Now, git might accept it despite not documenting it as an accepted form, but why wander into undefined territory when there are legal ways to write this url that work fine?
Does GitLab promote using these malformed urls?
Thank you. I was wondering about the URL as flagged above. When I specify the URL as I did, the git commands work but when I change it to ssh://git@gitlab.com:/~/gitlabname/reponame.git, git command fails with
So perhaps I need to investigate how to get gcrypt to work with remote git(lab) repositories. Thanks.