Thanks for the update. As most of my GnuPG use is via script I normally do not see problems it is when I am trying to resolve problem that I run into issues where the new interface requires X or curses to interact with GnuPG.
Of course better error messages about not being able to connect to X would have been very useful when I first noted the problem. -Jim On Wed, 21 Jul 2010 16:33, [email protected] said: > Fedora 13 removed 'gnupg' (i.e. gnupg 1.4.x) and caused the 'gnupg2' (i.e. gnupg 2.x) package to replace it. This breaks all sorts of scripts and things that were written to use 1.4.x. FWIW, the new 2.0.16 may help to mitigate this problem if the --use-standard-socket option is used. The agent will then be started if needed. You can't use this feature if your home directory is NFS mounted or you are not using X. Shalom-Salam, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. Proud partner. Susan G. Komen for the Cure. Please consider our environment before printing this e-mail or attachments. ---------------------------------- CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you. ---------------------------------- _______________________________________________ Gnupg-users mailing list [email protected] http://lists.gnupg.org/mailman/listinfo/gnupg-users
