On Wed, 19 Jul 2017 21:24:49 +0200 Paweł Hajdan, Jr. wrote: > Hey folks, > > This is mysterious, and likely some issue with my setup, although it > used to work. > > Trying tocommit with repoman commit (app-portage/repoman version 2.3.1) > results in the following: > > * 4 files being committed... > error: gpg failed to sign the data > fatal: failed to write commit object > !!! Exiting on git (shell) error code: 128 > > However, committing directly with git commit works (and asks for gpg > passphrase). > > In .git/config I have the following: > > [user] > signingkey = 0x4F1A2555EA71991D > [commit] > gpgsign = 1 > [push] > gpgsign = 1 > > In /etc/make.conf I have: > > PORTAGE_GPG_KEY="0x4F1A2555EA71991D" > > In ~/.gnupg/gpg-agent.conf I have the following: > > pinentry-program /usr/bin/pinentry > > eselect pinentry show prints pinentry-gnome3 > > I'm using app-crypt/gnupg-2.1.20-r1, last updated May 24. > > Interestingly, I recently (July 17) re-emerged > app-crypt/pinentry-0.9.7-r1, probably changing some USE flags. It may > have been broken before that anyway, I don't remember now. > > Most of all, I'm interested how to get more debug info from repoman than > it currently shows me. > > Any other insights would be welcome. Please let me know if you need any > other info.
Try to see with strace what is going on. When some weird stuff happens this is what I usually do. Also try to switch pinentry to other implementations (ncurses, qt). Make sure that GPG_TTY is set in your shell. Best regards, Andrew Savchenko
pgpPbBjgKVJD1.pgp
Description: PGP signature
