From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.42.229.71 with SMTP id jh7cs7239icb; Thu, 27 Jan 2011 04:29:22 -0800 (PST) Received: by 10.142.232.3 with SMTP id e3mr1603047wfh.40.1296131362207; Thu, 27 Jan 2011 04:29:22 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id e29si19442299vcs.117.2011.01.27.04.29.21; Thu, 27 Jan 2011 04:29:22 -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 85B601678323; Thu, 27 Jan 2011 07:29:21 -0500 (EST) Received: from mail-qy0-f178.google.com (mail-qy0-f178.google.com [209.85.216.178]) by rubyforge.org (Postfix) with ESMTP id 0141818581B2 for ; Thu, 27 Jan 2011 07:02:51 -0500 (EST) Received: by qyk33 with SMTP id 33so2111301qyk.2 for ; Thu, 27 Jan 2011 04:02:51 -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=G5aG5fBNktMxPbGr8/mHvBZO6Ergb4o7x/Ra1O+zeAg=; b=k2HeYDKlJGNp2/yd3xVqKZ0vm0FkZsNI8NqOk4K2OHon895+p+y/xtEX+LLl4GCDSZ /ZvO4mLtOmeC5HiAyA9FrTSlCHK5sObVt8mYYZbsiqrtMV896AJ7+38oE12X/2QS0xBt mPRGq8Z6ivCMvC50fzGUhXyEPXbV/OMzruVZk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=XRSSfc0+UgWTLWWPjwq5QeJCgKyf6psvDsbIawdKhiDWFunPx6LFAfkT59L6In4m1H 9cGj8J8mVvI+vv2EmTgew8u/8RzUNoX4NSxu4chvnFHdLd2n9qEr5sYgkk9A6vt2IDOZ zMUu4bmRFhtNdKVK2LXNeF1qEE3HqX0zPZYvA= MIME-Version: 1.0 Received: by 10.229.225.18 with SMTP id iq18mr1519474qcb.26.1296129771523; Thu, 27 Jan 2011 04:02:51 -0800 (PST) Received: by 10.229.218.79 with HTTP; Thu, 27 Jan 2011 04:02:51 -0800 (PST) Date: Thu, 27 Jan 2011 12:02:51 +0000 Message-ID: From: Hamish D To: Sup developer discussion Subject: Re: [sup-devel] sup dies when gpgme not present 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 >> I have some more ideas for improvements, but I'm happy that this >> reproduces the behaviour of using the gpg binary, and I find sup usage >> much smoother with this change. Thank you. > When the gpgme gem is not installed, this patch makes sup die on start > with: > > --- NameError from thread: main > uninitialized constant Redwood::CryptoManager::GPGME > /home/alvherre/Code/sup-mail/lib/sup/crypto.rb:49:in `initialize' > ... The code around that line is: # test if the gpgme gem is available @gpgme_present = begin begin GPGME.check_version({:protocol => GPGME::PROTOCOL_OpenPGP}) <-- line 49 true rescue GPGME::Error false end rescue NameError false end So we should rescue the NameError. Could you check whether the code for your sup looks like that? Could you also temporarily remove the gpgme gem, update to the latest from master and see if you still get the same problem? Thanks in advance, and sorry for not getting back sooner. Hamish _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel