From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: pgg doesn't seem to like me
Date: Tue, 08 Oct 2002 16:18:26 +0200 [thread overview]
Message-ID: <ilubs65aua5.fsf@latte.josefsson.org> (raw)
In-Reply-To: <878z1959wu.fsf@athene.jamux.com> (jam@jamux.com's message of "Tue, 08 Oct 2002 09:37:21 -0400")
jam@jamux.com (John A. Martin) writes:
>>>>>> "Simon" == Simon Josefsson
>>>>>> "Re: pgg doesn't seem to like me"
>>>>>> Sun, 06 Oct 2002 02:03:35 +0200
>
> Simon> Uhm, are there any other outstanding PGG problems? [...]
> Simon> Or PGP/MIME and S/MIME problems in general?
>
> When compiling cvs gnus (about 12:30 GMT 8 Aug) atop XEmacs-21.4.8
> (xemacs21-nomule_21.4.8-2_i386.deb), Emacs complained about the
> following:
>
> mm-url.el:
> ** the function encode-coding-string is not known to be defined.
>
> mm-util.el:
> ** the function detect-coding-region is not known to be defined.
>
> pgg-parse.el:
> ** reference to free variable pgg-parse-crc24
> ** The following functions are not known to be defined:
> define-ccl-program, ccl-execute-on-string, pgg-parse-crc24-string
>
> pgg.el:
> ** The following functions are not known to be defined:
> decode-coding-region, encode-coding-region
Gnus is written to not generate warnings under Emacs only, according
to the manual. Those warnings are harmless, but if someone knows how
to avoid them, patches are welcome...
> What is a convenient unambiguous way to identify the particular cvs
> version used? How come folks don't often seem to bother?
CVS revision of the files used is probably the only way. If you
updated all files, CVS revision of lisp/ChangeLog is probably enough.
I guess (hope) people update to latest CVS before reporting problems.
next prev parent reply other threads:[~2002-10-08 14:18 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 17:27 John A. Martin
2002-10-01 18:56 ` John A. Martin
2002-10-01 19:16 ` Josh Huber
2002-10-01 20:11 ` John A. Martin
2002-10-01 20:58 ` Josh Huber
2002-10-01 21:21 ` John A. Martin
2002-10-01 21:38 ` Josh Huber
2002-10-01 21:50 ` Jesper Harder
2002-10-01 23:32 ` John A. Martin
2002-10-02 18:36 ` John A. Martin
2002-10-02 19:20 ` John A. Martin
2002-10-03 0:22 ` Clemens Fischer
2002-10-03 23:00 ` Simon Josefsson
2002-10-03 23:04 ` Simon Josefsson
2002-10-05 4:45 ` John A. Martin
2002-10-05 11:24 ` Simon Josefsson
2002-10-05 15:12 ` John A. Martin
2002-10-05 21:22 ` Raymond Scholz
2002-10-06 0:03 ` Simon Josefsson
2002-10-06 10:14 ` Raymond Scholz
2002-10-09 21:59 ` Simon Josefsson
2002-10-10 0:15 ` Simon Josefsson
2002-10-10 17:36 ` Raymond Scholz
2002-10-06 19:46 ` John A. Martin
2002-10-10 0:13 ` Simon Josefsson
2002-10-10 4:55 ` John A. Martin
2002-10-10 14:18 ` Josh Huber
2002-10-10 15:18 ` Simon Josefsson
2002-10-10 14:55 ` John A. Martin
2002-10-10 15:54 ` Simon Josefsson
2002-10-07 16:23 ` Andreas Fuchs
2002-10-07 23:58 ` Clemens Fischer
2002-10-10 0:34 ` Simon Josefsson
2002-10-10 0:32 ` Simon Josefsson
2002-10-10 10:42 ` Andreas Fuchs
2002-10-10 15:00 ` Simon Josefsson
2002-10-10 18:28 ` Andreas Fuchs
2002-10-10 23:24 ` Simon Josefsson
2002-10-08 2:11 ` John A. Martin
2002-10-10 0:42 ` Simon Josefsson
2002-10-08 13:37 ` John A. Martin
2002-10-08 14:18 ` Simon Josefsson [this message]
[not found] ` <gd.y1yr8f6yp8y.fsf@fly.verified.de>
[not found] ` <iluofa94z60.fsf@latte.josefsson.org>
2002-10-05 11:58 ` Raymond Scholz
2002-10-05 14:17 ` John A. Martin
2002-10-05 21:21 ` Raymond Scholz
2002-10-01 22:54 ` Simon Josefsson
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=ilubs65aua5.fsf@latte.josefsson.org \
--to=jas@extundo.com \
--cc=ding@gnus.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).