Git development
 help / color / mirror / Atom feed
From: Hugo Roy <hugo@fsfe.org>
To: git@vger.kernel.org
Subject: [bug report] Signing your work: GnuPG signing failed (gpg version 2.1)
Date: Wed, 5 Aug 2015 22:35:45 +0200	[thread overview]
Message-ID: <20150805203545.GD4325@xps> (raw)

[-- Attachment #1: Type: text/plain, Size: 1397 bytes --]


Hello,

I've tried to sign a commit following
https://git-scm.com/book/tr/v2/Git-Tools-Signing-Your-Work however,
this is what happened:

    % git commit -a -S -m "signed commit testing"
    gpg: échec de la signature : Opération annulée
    gpg: signing failed: Opération annulée
    error: gpg n'a pas pu signer les données
    fatal: échec de l'écriture de l'objet commit

sorry for the locale, "annulée" means cancelled and the last two
lines mean:

    error: gpg could not sign data
    fatal: failure to write the commit object

However, when I tried later, nothing specific happened and the commit
was done just as if I did not add the -S option:

    % git commit -a -S -m "signed commit test"
    [master 739cdd3] signed commit test
    1 file changed, 5 deletions(-)

Commit:
https://github.com/hugoroy/.emacs.d/commit/b8e5b72def0c5fcc760c84d6ecd2b95b9727ae62



I notice in the git-scm.com manual that they use GnuPG version 1. I
use GnuPG 2.1.6 with libgcrypt 1.6.3.

Let me know if you need more information or any pointer to help me
debug this more in depth.

thanks,
Hugo


-- 
Hugo Roy – Free Software Foundation Europe https://fsfe.org/about/roy
 
Please use cryptography for email: see https://emailselfdefense.fsf.org/en/
Merci d’utiliser la cryptographie pour l’email : voir https://emailselfdefense.fsf.org/fr/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

             reply	other threads:[~2015-08-05 20:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-05 20:35 Hugo Roy [this message]
2015-08-05 22:55 ` [bug report] Signing your work: GnuPG signing failed (gpg version 2.1) brian m. carlson

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150805203545.GD4325@xps \
    --to=hugo@fsfe.org \
    --cc=git@vger.kernel.org \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox