mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

comment, reopen

Browse source
This commit is contained in:
Joey Hess 2016-05-23 14:36:59 -04:00
parent f348634df0
commit 9e81a39a01
Failed to extract signature
2 changed files with 19 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

4
doc/bugs/annex.gnupg-options_not_used_by_assistant.mdwn
View file

@ -78,4 +78,6 @@ gpg: cannot open `/dev/tty': Device not configured
### 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) ### 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)
> added annex.gnupg-decrypt-options; [[done]] --[[Joey]] > added annex.gnupg-decrypt-options; done --[[Joey]]
>> Reopening, see comment. --[[Joey]]

16
doc/bugs/annex.gnupg-options_not_used_by_assistant/comment_3_4bb4bed22dc8dcc0308a557d3dae76e4._comment Normal file
View file

@ -0,0 +1,16 @@
[[!comment format=mdwn
username="joey"
subject="""comment 3"""
date="2016-05-23T18:21:16Z"
content="""
The gpg calls in that log are being done by git-annex, not by
git-remote-gcrypt.
I think this is decryptCipher, which can run gpg --decrypt and didn't
get annex.gnupg-decrypt-options wired up to it. Although normally the
creds would be cached when the special remote is set up or the first time
it's used and should not need to be decrypted again.
Threading gnupg-decrypt-options through to decryptCipher looks likely to
involve nearly a full day's work.
"""]]