From: Xavier Maillard <zedek@gnu-rox.org>
Subject: [BUG]: Can't send news after upgrading Gnus
Date: Wed, 14 Jan 2004 00:53:29 +0100 [thread overview]
Message-ID: <plop87hdyzmmme.fsf@gnu-rox.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1363 bytes --]
Hello,
I tried to post onto a newsgroup tonight and it failed. Here is the
relevant backtrace:
,----
| Debugger entered--Lisp error: (wrong-number-of-arguments #[(object &optional beg end) "\b;ƒ \0Ã\b!‡Š\bqˆÄ †\x13\0e
| †\x18\0d\")‡" [object beg end sha1-string sha1-region] 3 ("/opt/share/emacs/21.3.50/site-lisp/flim/sha1-el.elc" . 6990)] 4)
| sha1("49263bfd11d73bc69527c0e4cebc45de632a254e" nil nil binary)
| canlock-sha1("49263bfd11d73bc69527c0e4cebc45de632a254e")
| canlock-make-cancel-key("<plop87ptdnmmwt.fsf@gnu-rox.org>" "49263bfd11d73bc69527c0e4cebc45de632a254e")
| canlock-insert-header()
| message-insert-canlock()
| message-send-news(nil)
| message-send-via-news(nil)
| message-send(nil)
| message-send-and-exit(nil)
| call-interactively(message-send-and-exit)
`----
I saw that something related to sha1 in the Changelog:
,----[ Changelog ]
| 2004-01-13 Katsumi Yamaoka <yamaoka@jpl.org>
|
| * message.el (message-canlock-generate): Require sha1-el.
`----
My problem is that I have 2 different sha1 package here:
* one in flim/
* and one installed by Gnus Makefile in /opt/share/emacs/site-lisp
Is this normal ?
I am running Emacs CVS and 'No Gnus' v.02
zeDek
--
GnusFR (http://www.gnusfr.org)
EmacsFR (http://www.emacsfr.org)
.emacs: Because customisation is fun!
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next reply other threads:[~2004-01-13 23:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-13 23:53 Xavier Maillard [this message]
2004-01-14 0:00 ` Simon Josefsson
2004-01-14 0:14 ` Katsumi Yamaoka
2004-01-14 6:42 ` Xavier Maillard
2004-01-14 6:45 ` Xavier Maillard
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=plop87hdyzmmme.fsf@gnu-rox.org \
--to=zedek@gnu-rox.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;
as well as URLs for NNTP newsgroup(s).