From: Hamish D <dmishd@gmail.com>
To: Sup developer discussion <sup-devel@rubyforge.org>
Subject: [sup-devel] Improved GPG start up checks
Date: Thu, 10 Feb 2011 00:57:55 +0000 [thread overview]
Message-ID: <AANLkTins1JXJbrOca0EL7AyYBCt3rXm6TumbMNOdSk8p@mail.gmail.com> (raw)
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
reply other threads:[~2011-02-10 1:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=AANLkTins1JXJbrOca0EL7AyYBCt3rXm6TumbMNOdSk8p@mail.gmail.com \
--to=dmishd@gmail.com \
--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