| 1 |
On Wed, 19 Jul 2017 21:24:49 +0200 Paweł Hajdan, Jr. wrote: |
| 2 |
> Hey folks, |
| 3 |
> |
| 4 |
> This is mysterious, and likely some issue with my setup, although it |
| 5 |
> used to work. |
| 6 |
> |
| 7 |
> Trying tocommit with repoman commit (app-portage/repoman version 2.3.1) |
| 8 |
> results in the following: |
| 9 |
> |
| 10 |
> * 4 files being committed... |
| 11 |
> error: gpg failed to sign the data |
| 12 |
> fatal: failed to write commit object |
| 13 |
> !!! Exiting on git (shell) error code: 128 |
| 14 |
> |
| 15 |
> However, committing directly with git commit works (and asks for gpg |
| 16 |
> passphrase). |
| 17 |
> |
| 18 |
> In .git/config I have the following: |
| 19 |
> |
| 20 |
> [user] |
| 21 |
> signingkey = 0x4F1A2555EA71991D |
| 22 |
> [commit] |
| 23 |
> gpgsign = 1 |
| 24 |
> [push] |
| 25 |
> gpgsign = 1 |
| 26 |
> |
| 27 |
> In /etc/make.conf I have: |
| 28 |
> |
| 29 |
> PORTAGE_GPG_KEY="0x4F1A2555EA71991D" |
| 30 |
> |
| 31 |
> In ~/.gnupg/gpg-agent.conf I have the following: |
| 32 |
> |
| 33 |
> pinentry-program /usr/bin/pinentry |
| 34 |
> |
| 35 |
> eselect pinentry show prints pinentry-gnome3 |
| 36 |
> |
| 37 |
> I'm using app-crypt/gnupg-2.1.20-r1, last updated May 24. |
| 38 |
> |
| 39 |
> Interestingly, I recently (July 17) re-emerged |
| 40 |
> app-crypt/pinentry-0.9.7-r1, probably changing some USE flags. It may |
| 41 |
> have been broken before that anyway, I don't remember now. |
| 42 |
> |
| 43 |
> Most of all, I'm interested how to get more debug info from repoman than |
| 44 |
> it currently shows me. |
| 45 |
> |
| 46 |
> Any other insights would be welcome. Please let me know if you need any |
| 47 |
> other info. |
| 48 |
|
| 49 |
Try to see with strace what is going on. When some weird stuff |
| 50 |
happens this is what I usually do. |
| 51 |
|
| 52 |
Also try to switch pinentry to other implementations (ncurses, qt). |
| 53 |
Make sure that GPG_TTY is set in your shell. |
| 54 |
|
| 55 |
Best regards, |
| 56 |
Andrew Savchenko |
Archives