From: Norman Walsh <ndw@nwalsh.com>
Subject: Signing issues with gnus from CVS
Date: Wed, 17 May 2006 19:07:42 -0400 [thread overview]
Message-ID: <878xp01c8x.fsf@nwalsh.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1116 bytes --]
I've been having sporadic key signing issues so I upgraded from CVS
this morning and tried the latest. It's still happening:
Debugger entered--Lisp error: (error "Sign error")
signal(error ("Sign error"))
error("Sign error")
mml2015-pgg-sign((part (sign . "pgpmime") (tag-location . 477) (contents . "...")))
mml2015-sign((part (sign . "pgpmime") (tag-location . 477) (contents . "...")))
mml-pgpmime-sign-buffer((part (sign . "pgpmime") (tag-location . 477) (contents . "...")))
mml-generate-mime-1((part (sign . "pgpmime") (tag-location . 477) (contents . "...")))
mml-generate-mime()
message-encode-message-body()
gnus-inews-do-gcc()
gnus-agent-possibly-do-gcc()
run-hooks(message-sent-hook)
message-send(nil)
message-send-and-exit(nil)
* call-interactively(message-send-and-exit)
User error, I presume. Clues solicited.
Be seeing you,
norm
--
Norman Walsh <ndw@nwalsh.com> | Everything should be made as simple as
http://nwalsh.com/ | possible, but no simpler.
[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]
next reply other threads:[~2006-05-17 23:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-17 23:07 Norman Walsh [this message]
[not found] ` <smuzmhfr0zb.fsf@linuxpal.mit.edu>
2006-05-18 12:30 ` Norman Walsh
2006-05-18 12:42 ` Bastien
[not found] ` <87ejyrfqsm.fsf-iS72tiDCHhS1g9c2/K602IXGvZO2VSpW@public.gmane.org>
2006-05-18 13:21 ` Jochen Küpper
2006-05-19 22:56 ` PGG broken? (was: Signing issues with gnus from CVS) Marcus Frings
2006-05-23 21:25 ` PGG broken? Marcus Frings
2006-05-24 16:10 ` Norman Walsh
2006-06-02 3:44 ` Andreas Seltenreich
2006-06-04 4:38 ` Andreas Seltenreich
2006-06-18 15:09 ` Marcus Frings
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=878xp01c8x.fsf@nwalsh.com \
--to=ndw@nwalsh.com \
/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;
as well as URLs for NNTP newsgroup(s).