Tiny fix/workaround/... for gpg2

Having just put SL6 on my laptop, and along the way acquired gpg version 2,
I found I had to apply the following patch to exmh.  Without it, there's a
complaint that exmh can't unambiguously find my keyID in my key file
(pgpExec.tcl line 930).  The patch tweaks the regex pattern slightly.  It
seems to do the right thing for me...

--- /usr/lib/exmh/pgpGpg.tcl	2011-12-21 14:15:32.000000000 +0000
+++ lib/pgpGpg.tcl	2011-12-21 14:21:12.000000000 +0000
@@ -379,7 +379,7 @@
 set pgp(gpg,pat_splitKeys) \n
 # Patterns that match out interesting keys
 set pgp(gpg,pat_keySec) \
-                {^(pub|sec):[^:]*:[^:]*:([^:]*):[0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F]([^:]+):[^:]*:[^:]*:[^:]*:[^:]*:([^:]+).*$}
+                {^(pub|sec):[^:]*:[^:]*:([^:]*):[0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F]([^:]+):[^:]*:[^:]*:[^:]*:[^:]*:([^:]*).*$}
 set pgp(gpg,pat_keySec_sub) \
                 {^(ssb):[^:]*:[^:]*:([^:]+):[0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F]([^:]+):[^:]*:[^:]*:[^:]*:[^:]*:[^:]*.*$}
 set pgp(gpg,pat_keyPub) $pgp(gpg,pat_keySec)

--
George D M Ross MSc PhD CEng MBCS CITP, University of Edinburgh,
School of Informatics, 10 Crichton Street, Edinburgh, Scotland, EH8 9AB
Mail: [email protected]   Voice: 0131 650 5147   Fax: 0131 650 6899
PGP: 1024D/AD758CC5  B91E D430 1E0D 5883 EF6A  426C B676 5C2B AD75 8CC5

The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.

_______________________________________________
Exmh-users mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/exmh-users

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Exmh version 2.7.2 2005/01/04

iEYEARECAAYFAk7x7i8ACgkQtnZcK611jMVCQACfdsXf7+AEvaAXyEw++haTa+2e
16AAn0vh3zvZsxOKc+gVbensezBWZJDV
=UdZC
-----END PGP SIGNATURE-----