| 1 |
Ühel kenal päeval, K, 19.07.2017 kell 15:57, kirjutas Joshua Kinard: |
| 2 |
> On 07/19/2017 15:43, Andrew Savchenko wrote: |
| 3 |
> > On Wed, 19 Jul 2017 21:24:49 +0200 Paweł Hajdan, Jr. wrote: |
| 4 |
> > > Hey folks, |
| 5 |
> > > |
| 6 |
> > > This is mysterious, and likely some issue with my setup, although |
| 7 |
> > > it |
| 8 |
> > > used to work. |
| 9 |
> > > |
| 10 |
> > > Trying tocommit with repoman commit (app-portage/repoman version |
| 11 |
> > > 2.3.1) |
| 12 |
> > > results in the following: |
| 13 |
> > > |
| 14 |
> > > * 4 files being committed... |
| 15 |
> > > error: gpg failed to sign the data |
| 16 |
> > > fatal: failed to write commit object |
| 17 |
> > > !!! Exiting on git (shell) error code: 128 |
| 18 |
> > > |
| 19 |
> |
| 20 |
> [snip] |
| 21 |
> > |
| 22 |
> |
| 23 |
> [snip] |
| 24 |
> |
| 25 |
> > Make sure that GPG_TTY is set in your shell. |
| 26 |
> |
| 27 |
> ^^^--- This is likely the issue. |
| 28 |
> |
| 29 |
> Add: |
| 30 |
> export GPG_TTY=`tty` |
| 31 |
> |
| 32 |
> To your ~/.bash_profile (or wherever you put your PORTAGE_GPG_KEY |
| 33 |
> value), and |
| 34 |
> that should solve the issue. I got bit by this once, and spent a |
| 35 |
> while |
| 36 |
> convincing Google that I'm not a robot to get that answer. |
| 37 |
|
| 38 |
Sounds like a workaround, and yes, I know it's been suggested before, |
| 39 |
including to me. |
| 40 |
Some pinentry issues imho if GPG_TTY makes it work, at least it was |
| 41 |
when I hit that half a year ago with this suggested as a solution. It's |
| 42 |
not a solution, it's a workaround, as users need to do something. |
| 43 |
|
| 44 |
FWIW, I don't have GPG_TTY set at all and things work fine, but I'm on |
| 45 |
pinentry-gnome3 |
| 46 |
I think pinentry-curses and pinentry-tty might have had such trouble |
| 47 |
that need GPG_TTY stuff. |
| 48 |
|
| 49 |
|
| 50 |
Mart |
Archives