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 559CC139694 for ; Thu, 20 Jul 2017 05:50:12 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 46847E0F57; Thu, 20 Jul 2017 05:50:02 +0000 (UTC) Received: from smtp.gentoo.org (mail.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 CD742E0EB6 for ; Thu, 20 Jul 2017 05:50:01 +0000 (UTC) Received: from localhost (unknown [91.246.101.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: bircoph) by smtp.gentoo.org (Postfix) with ESMTPSA id A1EC234183C for ; Thu, 20 Jul 2017 05:49:59 +0000 (UTC) Date: Thu, 20 Jul 2017 08:49:41 +0300 From: Andrew Savchenko To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] can't gpg sign with repoman, but can with git Message-Id: <20170720084941.52a0a9f4da604dd2de65fe74@gentoo.org> In-Reply-To: <1500500652.32362.9.camel@gentoo.org> References: <20170719224357.65daa079368e57f637380fe3@gentoo.org> <1067a22c-5df0-8536-ff99-c55ef3b4bfc3@gentoo.org> <1500500652.32362.9.camel@gentoo.org> X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.30; i686-pc-linux-gnu) 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-Type: multipart/signed; protocol="application/pgp-signature"; micalg="PGP-SHA512"; boundary="Signature=_Thu__20_Jul_2017_08_49_42_+0300_DqbPMJw1ToHw/rxo" X-Archives-Salt: 2e4f1630-5662-4c0a-aa33-e17436b9c9f0 X-Archives-Hash: a8519da9a21a58827f05db9ccbf81fb9 --Signature=_Thu__20_Jul_2017_08_49_42_+0300_DqbPMJw1ToHw/rxo Content-Type: text/plain; charset=UTF-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, 20 Jul 2017 00:44:12 +0300 Mart Raudsepp wrote: > =C3=9Chel kenal p=C3=A4eval, K, 19.07.2017 kell 15:57, kirjutas Joshua Ki= nard: > > On 07/19/2017 15:43, Andrew Savchenko wrote: > > > On Wed, 19 Jul 2017 21:24:49 +0200 Pawe=C5=82 Hajdan, Jr. wrote: > > > > Hey folks, > > > >=20 > > > > This is mysterious, and likely some issue with my setup, although > > > > it > > > > used to work. > > > >=20 > > > > Trying tocommit with repoman commit (app-portage/repoman version > > > > 2.3.1) > > > > results in the following: > > > >=20 > > > > * 4 files being committed... > > > > error: gpg failed to sign the data > > > > fatal: failed to write commit object > > > > !!! Exiting on git (shell) error code: 128 > > > >=20 > >=20 > > [snip] > > >=20 > >=20 > > [snip] > >=20 > > > Make sure that GPG_TTY is set in your shell. > >=20 > > ^^^--- This is likely the issue. > >=20 > > Add: > > =C2=A0=C2=A0=C2=A0=C2=A0export GPG_TTY=3D`tty` > >=20 > > To your ~/.bash_profile (or wherever you put your PORTAGE_GPG_KEY > > value), and > > that should solve the issue.=C2=A0=C2=A0I got bit by this once, and spe= nt a > > while > > convincing Google that I'm not a robot to get that answer. >=20 > 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. >=20 > 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=3D$(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 --Signature=_Thu__20_Jul_2017_08_49_42_+0300_DqbPMJw1ToHw/rxo Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE63ZIHsdeM+1XgNer9lNaM7oe5I0FAllwRHYACgkQ9lNaM7oe 5I1nnw//SEESOSdKTdB8oaNZO/ajw18I5tnn7Wuz5dHLW2cj2CAAYgzGzkfK2ZAq ofWFjz7z/Q+cYdsytBIorqO0ZIMeouUymS6aOVHqFjzJWAiSX8JDzz9MiHMtlV/r 7CSCST8pwvEAXHih1kR9pKgtVa9voGs+C1WikW6c6VCwNmlHr89jMQtn2gk3zOC6 J+vEhHATsMiktFFHHKcqIsQ+1fW0wOWh7BHOz0D6eXvlhY/leCpIxuidJmNALCng KJupLAa9NWCmYC2PyGp/7U3z2FRJCbw6s3BTqkVuG9N20CR4MTgBw44Ki/wxQXwH CFl5M1e7MCjOEzWpK47w0o5TlG4fh56W58YT2HXNtxisjpg7T7Z7GadAukYeIuoI 2aTEOhJ3/RFBVuuP4Nz9vwMiZRahYI6FjzCKZcoxGepGOdxhlzOOAdZK5dLMi6LU nsNkX7pRzynpj+1cFcjce2/4NUl0b+Jn953rrUwpPScT2hpN/7KbpiFPD7Nwsy6S gJiWLdMBYLrdj/LzeQg0swHdVYDIFD4KxwRGvp4Sfvpd7qdDqH+2GsiczFoS7rNQ o0+mHToX1KscY3K/NgHnIVRrIMaQMHw6r+aDhMl/CAnjiIEZYHb8GCE5Yvx9Ieyh 5OWUD5+y01CFmJNnBcbNhDQ+UsFGY/rmKxF8sX/lyRJ6zVgEwC8= =nY7k -----END PGP SIGNATURE----- --Signature=_Thu__20_Jul_2017_08_49_42_+0300_DqbPMJw1ToHw/rxo--