From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.42.240.136 with SMTP id la8cs129028icb; Wed, 9 Feb 2011 17:24:49 -0800 (PST) Received: by 10.229.236.193 with SMTP id kl1mr5474632qcb.114.1297301088778; Wed, 09 Feb 2011 17:24:48 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id e5si1848777qck.84.2011.02.09.17.24.48; Wed, 09 Feb 2011 17:24:48 -0800 (PST) Received-SPF: pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-devel-bounces@rubyforge.org; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 13C161D780EE; Wed, 9 Feb 2011 20:24:48 -0500 (EST) Received: from mail-qw0-f50.google.com (mail-qw0-f50.google.com [209.85.216.50]) by rubyforge.org (Postfix) with ESMTP id 670811858356 for ; Wed, 9 Feb 2011 19:57:55 -0500 (EST) Received: by qwd6 with SMTP id 6so667636qwd.23 for ; Wed, 09 Feb 2011 16:57:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=S16NcRUc+ru5/o+celH2RdNL4PZMEh0H0T9hSZTZU+I=; b=Idm/1zSocjp4CLWkg3dw6Tm0YdFnFZZ+7jOYeD5u00NXy9hYzXP3PPwKIy8x0Ljgit sRJYvFU+5E+VbS0EFpAqWB/MuIDi6mgReq0dnrIBGSf73KMQpcmAw09a2+k0c8xcTa1n MSpjJ2/r9R7r/6Cz4rRlWQHrJzuDEOlxJQUF4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=YfTHU4ZowAOY45LXBkWHIt15RZNISyfD/JL44dKafLKBfs1J+jPJ4JDHJTj+HiY8Wr DTx+ZLCjbbn4NxnzTuAXksCDte2s4DnoyyqpjUU0RN3CItUhwCVdC866kMqIjmylNaH/ ggMOk/2gz6YkYFaLSqIqaTN19BGBJpneUH2yA= MIME-Version: 1.0 Received: by 10.229.184.208 with SMTP id cl16mr15417975qcb.216.1297299475567; Wed, 09 Feb 2011 16:57:55 -0800 (PST) Received: by 10.229.218.79 with HTTP; Wed, 9 Feb 2011 16:57:55 -0800 (PST) Date: Thu, 10 Feb 2011 00:57:55 +0000 Message-ID: From: Hamish D To: Sup developer discussion Subject: [sup-devel] Improved GPG start up checks X-BeenThere: sup-devel@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Sup developer discussion List-Id: Sup developer discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org Better gpg error checking. The crypto initialize code now checks for a number of common reasons for GPG not working, all related to the gpg-agent side of things. It will then give a reasonably friendly error message, helping diagnose why GPG is not working for you. In particular it will check whether the environment variable is set, whether the environment variable points to a file, and whether that file is a socket. On branch gpgme and next. Though this change also merged the improved rescue of NameError from the master branch to the gpgme branch, and the improved rescue was already on the next branch, so a quick manual merge was required to merge into next, and will presumably also be required to merge the gpgme stuff into master. I should probably start a new branch for further gpg improvements to save trouble down the road. Let me know if you want me to pick out commits for cherry-pick to get past this. Hamish Downer _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel