forum/gcrypt os x app vs brewgit-annexhttp://git-annex.branchable.com/forum/gcrypt_os_x_app_vs_brew/git-annexikiwiki2014-08-19T21:54:16ZProblem solvedhttp://git-annex.branchable.com/forum/gcrypt_os_x_app_vs_brew/comment_1_cce5e2c16720cc8e32a4a479f50ce6b3/Ganwell2014-08-14T23:53:05Z2014-08-14T23:53:05Z
It turns out gpgtools will save to wrong passphrase to the keychain without complaining. Thats why standard gpg worked and gpgtools didn't: There was a typo in the passphrase in the keychain.
comment 2http://git-annex.branchable.com/forum/gcrypt_os_x_app_vs_brew/comment_2_8df8ba1ccea0f68110593ed90a9cad6d/joeyh.name2014-08-15T16:04:08Z2014-08-15T16:04:08Z
Note that you can avoid the trying of multiple keys by doing <code>git config gcrypt.publish-participants true</code> -- this is done by default by the assistant when setting up new gcrypt remotes. It needs my branch of git-remote-gcrypt, which is included in the osx app, I don't know which one is being used in brew.
brew doesn't include git-remote-gcrypthttp://git-annex.branchable.com/forum/gcrypt_os_x_app_vs_brew/comment_3_be4de1663a37f49a4e42d6b21c0178fe/Ganwell2014-08-19T21:54:16Z2014-08-19T21:54:16Z
<p>Brew doesn't include git-remote-gcrypt, so I installed your fork of it manually. That works well and if you use a symlink to include it in the PATH you can easily update (pull) the repo. If one can install git-remote-gcrypt using brew, I don't know how.</p>
<p>Best, Jean-Louis</p>