From: Jonathan Brielmaier <jonathan.brielmaier@web.de>
To: Leo Famulari <leo@famulari.name>
Cc: 41941@debbugs.gnu.org
Subject: bug#41941: Signing git commits with PGP fails
Date: Fri, 19 Jun 2020 16:43:10 +0200 [thread overview]
Message-ID: <2036f2a5-4ec9-0e44-3e71-e6860f5979fa@web.de> (raw)
In-Reply-To: <20200619015247.GA1458@jasmine.lan>
On 19.06.20 03:52, Leo Famulari wrote:
> On Fri, Jun 19, 2020 at 12:35:09AM +0200, Jonathan Brielmaier wrote:
>> I have a strange error/problem with signing git commits with PGP.
>
> The setup can be complicated...
>
>> Following situation
>>
>> `git` is installed via system configuration
>> `git:send-email` via `guix install` into the user profile
>>
>> ~/.gitconfig has
>> ```
>> [commit]
>> gpgsign = true
>> ```
>
> I also have:
>
> ------
> [gpg]
> program = gpg
> [user]
> signingkey = B0515948F1E7D3C1B98038A02646FA30BACA7F08
> ------
Oke, the signingkey parameter is also present in my config.
>> but trying to sign a git commit fails:
>> ```
>> git commit -m "test"
>> error: gpg failed to sign the data
>> fatal: failed to write commit object
>> ```
>
> Do you also have a GPG pinentry program installed? Are you able to sign
> an arbitrary file with GPG, outside of Git? For example:
>
> $ gpg --output test.sig --sign file
I have pinentry installed from the config.scm, but it's still
```
gpg --output test.sig --sign TODO.md
gpg: signing failed: No pinentry
gpg: signing failed: No pinentry
```
Do I need an additional service?
next prev parent reply other threads:[~2020-06-19 14:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 22:35 bug#41941: Signing git commits with PGP fails Jonathan Brielmaier
2020-06-19 1:52 ` Leo Famulari
2020-06-19 14:43 ` Jonathan Brielmaier [this message]
2020-06-19 16:17 ` Leo Famulari
2020-06-19 16:42 ` Jonathan Brielmaier
2020-06-19 18:13 ` Leo Famulari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2036f2a5-4ec9-0e44-3e71-e6860f5979fa@web.de \
--to=jonathan.brielmaier@web.de \
--cc=41941@debbugs.gnu.org \
--cc=leo@famulari.name \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).