From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id DBA42139694 for ; Wed, 19 Jul 2017 21:44:22 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8E7B71FC044; Wed, 19 Jul 2017 21:44:17 +0000 (UTC) Received: from smtp.gentoo.org (dev.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 412871FC003 for ; Wed, 19 Jul 2017 21:44:17 +0000 (UTC) Received: from [192.168.2.13] (85.253.91.80.cable.starman.ee [85.253.91.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: leio) by smtp.gentoo.org (Postfix) with ESMTPSA id CBE53341857 for ; Wed, 19 Jul 2017 21:44:15 +0000 (UTC) Message-ID: <1500500652.32362.9.camel@gentoo.org> Subject: Re: [gentoo-dev] can't gpg sign with repoman, but can with git From: Mart Raudsepp To: gentoo-dev@lists.gentoo.org Date: Thu, 20 Jul 2017 00:44:12 +0300 In-Reply-To: <1067a22c-5df0-8536-ff99-c55ef3b4bfc3@gentoo.org> References: <20170719224357.65daa079368e57f637380fe3@gentoo.org> <1067a22c-5df0-8536-ff99-c55ef3b4bfc3@gentoo.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.22.6 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-Archives-Salt: 0eb24c93-7039-46f0-b17e-d40b8573dbaf X-Archives-Hash: 6c3541e277f4247922c895e93c8953d9 Ü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. Mart