On Thu, 20 Jul 2017 00:44:12 +0300 Mart Raudsepp wrote: > Ühel kenal päeval, K, 19.07.2017 kell 15:57, kirjutas Joshua Kinard: > > On 07/19/2017 15:43, Andrew Savchenko wrote: > > > 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 > > > > > > > > [snip] > > > > > > > [snip] > > > > > Make sure that GPG_TTY is set in your shell. > > > > ^^^--- This is likely the issue. > > > > Add: > > export GPG_TTY=`tty` > > > > To your ~/.bash_profile (or wherever you put your PORTAGE_GPG_KEY > > value), and > > that should solve the issue. I got bit by this once, and spent a > > while > > convincing Google that I'm not a robot to get that answer. > > Sounds like a workaround, and yes, I know it's been suggested before, > including to me. > Some pinentry issues imho if GPG_TTY makes it work, at least it was > when I hit that half a year ago with this suggested as a solution. It's > not a solution, it's a workaround, as users need to do something. > > FWIW, I don't have GPG_TTY set at all and things work fine, but I'm on > pinentry-gnome3 > I think pinentry-curses and pinentry-tty might have had such trouble > that need GPG_TTY stuff.
man gpg-agent says:
You should always add the following lines to your .bashrc or
whatever initialization file is used for all shell invocations:
GPG_TTY=$(tty)
export GPG_TTY
Thus there is no need to speculate if this is a workaround or if
one needs to convince Google they is not a robot. Just read the
official manual :)
Best regards,
Andrew Savchenko
pgp4XOI2PklUx.pgp
Description: PGP signature
