From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [PATCH] Converted crypto to use the gpgme gem
Date: Wed, 19 Jan 2011 13:12:18 -0300 [thread overview]
Message-ID: <1295453319-sup-2362@alvh.no-ip.org> (raw)
In-Reply-To: <AANLkTinvv59bWu0UfjW2K-xDRUP42tDwmgMh5yZdmaN_@mail.gmail.com>
Excerpts from Hamish D's message of dom nov 28 19:51:43 -0300 2010:
> OK, here is a set of 4 patches that implement the change over to the
> gpgme library. There's quite a bit of work in there so I thought I'd
> leave it as a few patches, but I have done some tidying.
>
> 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.
When the gpgme gem is not installed, this patch makes sup die on start
with:
[mié ene 19 13:05:39 -0300 2011] No 'gpgme' gem detected. Install it for email encryption, decryption and signatures.
[mié ene 19 13:05:39 -0300 2011] dynamically loading setlocale() from libc.so.6
[mié ene 19 13:05:39 -0300 2011] setting locale...
[mié ene 19 13:05:39 -0300 2011] locking /home/alvherre/.sup/lock...
[mié ene 19 13:05:39 -0300 2011] stopped cursing
[mié ene 19 13:05:39 -0300 2011] ERROR: oh crap, an exception
[mié ene 19 13:05:39 -0300 2011] unlocking /home/alvherre/.sup/lock...
----------------------------------------------------------------
I'm very sorry. It seems that an error occurred in Sup. Please
accept my sincere apologies. Please submit the contents of
/home/alvherre/.sup/exception-log.txt and a brief report of the
circumstances to http://masanjin.net/sup-bugs/ so that I might
address this problem. Thank you!
Sincerely,
William
----------------------------------------------------------------
--- NameError from thread: main
uninitialized constant Redwood::CryptoManager::GPGME
/home/alvherre/Code/sup-mail/lib/sup/crypto.rb:49:in `initialize'
...
Ruby is from Debian package ruby1.8,
ruby 1.8.7 (2010-08-16 patchlevel 302) [x86_64-linux]
I'm gonna install the gem now, but this should probably be fixed
nonetheless.
--
Álvaro Herrera -- Se vende casa en Ñuñoa: www.portalinmobiliario.com/993147
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
prev parent reply other threads:[~2011-01-19 16:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-06 20:08 Hamish D
2010-11-08 11:21 ` Hamish D
2010-11-08 22:32 ` Hamish D
2010-11-11 9:09 ` Gaudenz Steinlin
2010-11-11 17:25 ` Hamish D
2010-11-16 11:42 ` Gaudenz Steinlin
2010-11-16 14:20 ` Hamish D
2010-11-16 18:36 ` Gaudenz Steinlin
2010-11-16 23:05 ` Hamish D
2010-11-28 22:51 ` Hamish D
2010-11-29 9:41 ` Gaudenz Steinlin
2010-11-30 6:22 ` Tero Tilus
2010-12-01 8:37 ` Gaudenz Steinlin
2010-12-06 23:31 ` Hamish D
2010-12-23 18:43 ` Rich Lane
2011-01-19 3:11 ` Rich Lane
2011-01-30 23:57 ` Hamish D
2011-01-30 23:59 ` Hamish D
2011-01-19 16:12 ` Alvaro Herrera [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1295453319-sup-2362@alvh.no-ip.org \
--to=alvherre@alvh.no-ip.org \
--cc=sup-devel@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox