From e3db70e237b508663b1852053d20188c79932b97 Mon Sep 17 00:00:00 2001 From: filippo Date: Mon, 31 Aug 2015 10:33:52 +0000 Subject: [PATCH 1/3] --- ...9__t_find_gpg_if_it__39__s_named_gpg2.mdwn | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 doc/bugs/git-annex_can__39__t_find_gpg_if_it__39__s_named_gpg2.mdwn diff --git a/doc/bugs/git-annex_can__39__t_find_gpg_if_it__39__s_named_gpg2.mdwn b/doc/bugs/git-annex_can__39__t_find_gpg_if_it__39__s_named_gpg2.mdwn new file mode 100644 index 0000000000..d75d2f217a --- /dev/null +++ b/doc/bugs/git-annex_can__39__t_find_gpg_if_it__39__s_named_gpg2.mdwn @@ -0,0 +1,19 @@ +### Please describe the problem. + +git-annex requires a `gpg -> gpg2` alias, which is dangerous for other software to misuse. + +### What steps will reproduce the problem? + +Run any gpg-requiring operation on a machine that has only gpg2 installed and no gpg alias. + + gpg: createProcess: runInteractiveProcess: exec: does not exist (No such file or directory) + +### What version of git-annex are you using? On what operating system? + +git-annex version: 5.20150710 + +OS X, gpg2 installed with brew + +### Have you had any luck using git-annex before? + +git-annex took some time to get in the mentality and configure, but now it's a beautiful perfectly oiled file management system. Thanks! From c040203ba77c87e7c851097e41a1d668d99160b4 Mon Sep 17 00:00:00 2001 From: ypid Date: Mon, 31 Aug 2015 19:06:02 +0000 Subject: [PATCH 2/3] Fixed spelling. --- doc/design/metadata.mdwn | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/design/metadata.mdwn b/doc/design/metadata.mdwn index 9da0a36261..35e45f8119 100644 --- a/doc/design/metadata.mdwn +++ b/doc/design/metadata.mdwn @@ -79,7 +79,7 @@ subdirs. # other uses for metadata -Uses are not limited to view branches. +Users are not limited to view branches. `git annex checkoutmeta year=2014 talk` in a subdir of master could create the same tree of files filter would. The user can then commit that if desired. @@ -177,7 +177,7 @@ So, possible approaches: * Metadata should be copied to the new key when adding a modified version of a file. **done** -* Filesystems that are not case sensative (including case preserving OSX) +* Filesystems that are not case sensitive (including case preserving OSX) will cause problems if view branches try to use different cases for 2 directories representing a metadata field. From b8456fa8234e0e05a28819ff7735c37896655f59 Mon Sep 17 00:00:00 2001 From: "https://openid.stackexchange.com/user/e65e6d0e-58ba-41de-84cc-1f2ba54cf574" Date: Mon, 31 Aug 2015 20:16:26 +0000 Subject: [PATCH 3/3] --- ..._encrypted_remove_won__39__t_prompt_with_pinentry-gtk2.mdwn | 3 +++ 1 file changed, 3 insertions(+) create mode 100644 doc/forum/syncing_to_an_encrypted_remove_won__39__t_prompt_with_pinentry-gtk2.mdwn diff --git a/doc/forum/syncing_to_an_encrypted_remove_won__39__t_prompt_with_pinentry-gtk2.mdwn b/doc/forum/syncing_to_an_encrypted_remove_won__39__t_prompt_with_pinentry-gtk2.mdwn new file mode 100644 index 0000000000..8e6f2805a2 --- /dev/null +++ b/doc/forum/syncing_to_an_encrypted_remove_won__39__t_prompt_with_pinentry-gtk2.mdwn @@ -0,0 +1,3 @@ +I'm trying to sync my unencrypted local repo to an encrypted remote located on an external drive. I'm using Debian 8.1. When I run `git-annex sync encrypted-remote` I get prompted in my shell for the password. I'm not sure why, as other places pinentry-gtk2 pops up. This is annoying because my gpg key isn't getting cached, so I have to enter my long password several times. + +How can I make git-annex/git-remote-gcrypt use pinentry-gtk2?