Re: Commits are no longer gpg-signed in 2.9.0 when "commit.gpgsign" is enabled

From: Santiago Torres <santiago@nyu.edu>
Date: Jul 11, 2016, 16:51 UTC
Message-ID: <20160711165108.iv2wq2m2vfh5mate@LykOS.localdomain>
In-Reply-To: <5783C90D.1010909@web.de>

On Mon, Jul 11, 2016 at 06:27:57PM +0200, Nils Fenner wrote:

Show 5 quoted lines

> Hi Santiago,
> 
> repeated your test here and actually found something interesting. When
> committing via 'git gui', commits are not being gpg-signed, while firing
> a 'git commit' shows the passphrase dialog and signs the commit correctly.

I have the feeling that this is an issue with your gpg configuration not playing well with the gui. Do you know which pinentry program is being used (e.g., type /usr/bin/pinentry).

> What you mean by wme? Is it the gpg-agent's config or something?
>

Sorry, I meant a Minimum Working Example, although that'll be hard to reproduce in this case. Your configuration seems to be proper.

> Hope that points in the right direction.

I think that we can take further troubleshooting off-list. This doesn't seem to be behavior with git (although we can come back with a bug report if something is naturally-broken/could be improved)

Cheers! -Santiago.