I seem to be incapable of creating an encrypted git-annex repository with the instructions provided at [[tips/fully_encrypted_git_repositories_with_gcrypt/]]. The setup step fails with *gcrypt: Repository not found: (path-to-repo)*.
### What steps will reproduce the problem?
I *think* I naively followed the tips page, but I might be wrong. Here's the minimal reproducer I could find, but originally the problem occured with an SSH remote which I thought was the culprit.
fatal: helper gcrypt does not support --signed=if-asked
git-annex: unable to determine gcrypt-id of remote
"""]]
Note that this failure leaves the repository with an half-configured remote. Trying to rerun the setup gives this error:
git-annex: There is already a remote named "encrypted"
Removing the remote seems to be sufficient to restore a working state and try again:
git remote rm encrypted
I also note that the `encryption step` part takes a looong time when we try to reproduce the issue multiple time... I will report this in a separate issue.
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
Of course! As you very likely know, I use git-annex daily and I'm a really happy user. :) This is, however, the first time I give gcrypt a shot.
Update: turns out this is a bug in git-remote-gcrypt and this probably doesn't need to be tracked in git-annex. the workaround is to comment out the `push.sign=ifAsked` entry in the git config, or to make git-remote-gcrypt ignore unknown options. so [[done]]. --[[anarcat]]