From: Christian Kurz <shorty@jupiter.rhein-neckar.de>
Subject: Bug in Gnus 0.40
Date: 07 Nov 1998 08:44:52 +0100 [thread overview]
Message-ID: <87n264ymiz.fsf@jupiter.rhein-neckar.de> (raw)
Hi,
when I try to display the following Article in Gnus 0.40, I get the
following error message: Invalid Regexp: "Invalid Preceding Regular
Expression". Could anybody check, if this is really a bug? I'm not so
good with lisp, I only understand I a little bit and I can use it for
configuration, but not more.
Christian
Here the Article, with a cutted header:
X-From-Line: debian-devel-request@lists.debian.org Sat Nov 07 08:28:25 1998
From: Zed Pobre <zed@moebius.interdestination.com>
To: Debian Developer <debian-devel@lists.debian.org>
Subject: Re: PGP vs. GnuPG again... sorry
Mime-Version: 1.0
Content-Type: multipart/signed; protocol="application/pgp-signature";
micalg=pgp-md5; boundary=VS++wcV0S1rZb1Fb
X-Mailer: Mutt 0.94.12i
In-Reply-To: <873e7wqvl2.fsf@nocrew.org>; from James Troup on Fri, Nov 06, 1998 at 10:56:25PM +0000
X-No-Archive: Yes
Lines: 68
--VS++wcV0S1rZb1Fb
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
On Fri, Nov 06, 1998 at 10:56:25PM +0000, James Troup wrote:
>=20
> Why don't you just go and look? (~maor/dinstall/)
Thanks for the location. =20
=20
Had you considered abandoning the exit code check and instead
grepping through the output for "BAD signature"? Sorry for the lack
of a patch; my perl skills won't be up to the task for at least
another 6-12 months. However, the general outline (same as used by
pinepgp, btw.), runs:
run gpg, storing output somewhere (the "open(GPG, "gpg --verify
[...])" bit, but dumping output to either a variable or a temp
file; not sure how this is done in perl)
if(grep "No valid RFC1991" output)=20
(flag=3Dfail)
elif(grep "BAD signature" output)
(flag=3Dfail)
elif(grep "(Key not in keyring)" output) (not sure what
(flag=3Dfail) corresponds to this=20
error)
if(flag =3D=3D fail)
$.rm.=3D"Rejected...";
return 0;=20
It's a very crude example, of course, but I think it shows the
general idea. Is there a technical reason why this would be
infeasable for dinstall/etc?
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Zed Pobre <zed@va.debian.org> | PGP key on servers, fingerprint on finger
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--VS++wcV0S1rZb1Fb
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: 5.0
MessageID: 4PvyaxCr9ytAUHWjTMUgSPxhbcvhBhQo
iQEVAwUBNkOwo9wPDK/EqFJbAQHbPAf8CROS2qPqqaU7n/qZGSlMR31B9Wc8mJk4
qpMGfj17XAEwTtPOzgQQ+61j5ayBlsDljUKet71p6NX+mTh+GSQ9nPJ5Fd9jaZxT
QNQxz8H2+V8QzqYhX052kP7exE3SIVDUkExwXxjT76GoyDyXAvZVdCX5sXy/Dxlv
VQDQZ2DHwBXh4cT90NAMgD69xDK+e88A9Sm8Lmy05wn0IiTNlYSU5YnUzaIcw07K
d/1EUfMO51io4sltyiDP4f41Xdj1I/fQkCSaf+irZSDpMf5yXL6PhSWi3iC4FmIM
A8t6cU3zanPG/wVl4lI5z74N8uk/3vSLhGtSHMkXi1qWAL0i38qJGQ==
=Eutf
-----END PGP SIGNATURE-----
--VS++wcV0S1rZb1Fb--
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
--
M$: Our software of tomorrow will make sure that on your
hardware of tomorrow everything will work at the usual speed. ;-)
next reply other threads:[~1998-11-07 7:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-07 7:44 Christian Kurz [this message]
1998-11-07 16:51 ` Lars Magne Ingebrigtsen
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=87n264ymiz.fsf@jupiter.rhein-neckar.de \
--to=shorty@jupiter.rhein-neckar.de \
/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).