nixpkgs/pkgs/tools/security/gnupg/gpgkey2ssh-20.patch

diff --git a/tools/gpgkey2ssh.c b/tools/gpgkey2ssh.c
index 903fb5b..d5611dc 100644
--- a/tools/gpgkey2ssh.c
+++ b/tools/gpgkey2ssh.c
@@ -268,7 +268,7 @@ main (int argc, char **argv)
   keyid = argv[1];
 
   ret = asprintf (&command,
-		  "gpg --list-keys --with-colons --with-key-data '%s'",
+		  "@out@/bin/gpg --list-keys --with-colons --with-key-data '%s'",
 		  keyid);
   assert (ret > 0);
Make gpgkey2ssh use absolute path to gpg2, fixes #11912 2015-12-27 20:56:52 +01:00			`diff --git a/tools/gpgkey2ssh.c b/tools/gpgkey2ssh.c`
			`index 903fb5b..d5611dc 100644`
			`--- a/tools/gpgkey2ssh.c`
			`+++ b/tools/gpgkey2ssh.c`
gnupg20: 2.0.29 -> 2.0.30 See https://lists.gnupg.org/pipermail/gnupg-announce/2016q1/000385.html 2016-03-31 17:16:46 +02:00			`@@ -268,7 +268,7 @@ main (int argc, char **argv)`
Make gpgkey2ssh use absolute path to gpg2, fixes #11912 2015-12-27 20:56:52 +01:00			`keyid = argv[1];`

			`ret = asprintf (&command,`
			`- "gpg --list-keys --with-colons --with-key-data '%s'",`
gnupg: 2.1.22 -> 2.1.23 This release in a RC for gnupg-2.2. The main difference as far as nixpkgs is concerned is that the binary `gpg2` is now called `gpg` and `gpgv2` is called `gpgv`. This update fixed all explicit use of `gpg2` and `gpgv2` across nixpkgs, but there might be some packaged software that internally use `gpg2` not handeled by this commit. See http://lists.gnu.org/archive/html/info-gnu/2017-08/msg00001.html for full release information 2017-08-10 11:43:48 +02:00			`+ "@out@/bin/gpg --list-keys --with-colons --with-key-data '%s'",`
Make gpgkey2ssh use absolute path to gpg2, fixes #11912 2015-12-27 20:56:52 +01:00			`keyid);`
			`assert (ret > 0);`