From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0 Subject: Re: Install gpg2 as gpg Date: Tue, 14 Jun 2016 12:49:42 +0000 Message-ID: <20160614124942.GD3999@khazad-dum> References: <20160613195538.GA1358@jasmine> <20160613202423.GA5290@khazad-dum> <20160613210708.GA12792@jasmine> <20160614075246.GA1570@solar> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="llIrKcgUOe3dCx0c" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44402) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bCnn2-0007jk-91 for guix-devel@gnu.org; Tue, 14 Jun 2016 08:49:57 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bCnmy-00035f-Ad for guix-devel@gnu.org; Tue, 14 Jun 2016 08:49:56 -0400 Received: from 93-95-228-168.1984.is ([93.95.228.168]:45806 helo=beleriand.n0.is) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bCnmx-00034h-Sa for guix-devel@gnu.org; Tue, 14 Jun 2016 08:49:52 -0400 Received: by beleriand.n0.is (OpenSMTPD) with ESMTPSA id d2527f07 TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO for ; Tue, 14 Jun 2016 12:49:46 +0000 (UTC) Content-Disposition: inline In-Reply-To: <20160614075246.GA1570@solar> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: guix-devel@gnu.org --llIrKcgUOe3dCx0c Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2016-06-14(09:52:46AM+0200), Andreas Enge wrote: > Hello, > > On Mon, Jun 13, 2016 at 05:07:08PM -0400, Leo Famulari wrote: > > On Mon, Jun 13, 2016 at 08:24:23PM +0000, ng0 wrote: > > > What if we patched gpg-1 to not colide with gpg-2? > > > > > > For example, move gpg and gpgv and man pages of them > > > for gpg-1 to something which has -1 in its name. > > > On the other hand this would have to be consistent and be followed > > > straigth to not colide again. I'm not sure if this > > > approach will work out in the long run. > > > > Unless this is a configuration option supported by upstream GnuPG, I > > don't want to do that. For the same reason, my patch does not affect > > gnupg-2.0. The -as-gnupg2 option got me for a moment, I forgot that this is gnupg-1. > > I agree with this argument - one of our principles is to mess as little > as possible with upstream packages. In this case, since there is a special > configuration option for gnupg-2, we may use it, but then we would have > to pay the price that both gnupg-1 (or gnupg-2.0) and gnupg-2.1 could not > be installed together any more. Maybe it would then be consistent to drop > gnupg-2.0 from the distribution. gnupg-2.0 and gnupg-2.1 are currently individual packages which can be installed side by side in guix? > Finally I managed to make gnupg-2.1 work together with mutt, but it was > not completely straightforward... So we should document the change if we > make it. Yes, there have been some changes, but they are documented upstream. When this is desired for Guix, I can see if I can recall what I did in 2015 where it went from working to broken to almost working and now completely functional with GnuPG2.1.x I'd be curious if it just works when I can move to GuixSD again with libgcrypt-1.7 merged. > By the way, should we maybe make pinentry a propagated input of gnupg-2.1? > If I understand correctly, gnupg-2.1 will not work without it (and mixing > pinentry from Debian with gnupg-2.1 from Guix was one of the reasons for > gnupg not working at first). > > Andreas > > -- =E2=99=A5=E2=92=B6 ng0 For non-prism friendly talk find me on psyced.org / loupsycedyglgamf.onion --llIrKcgUOe3dCx0c Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- iF4EARYKAAYFAldf/WYACgkQhhoAchyzrCADBQD9HdCOLjaF2LKVYgbqAvqulkFx tpdmdpJJiZZN/NhMOksBAKS1+OYmnymA8beil+2bVYwoJYl9+s222Ppo51xBBx4D =pzHu -----END PGP SIGNATURE----- --llIrKcgUOe3dCx0c--