Your message dated Wed, 3 Jan 2007 16:08:23 +0100 (CET)
with message-id <[EMAIL PROTECTED]>
and subject line Bug#386716: procmail: manual page misleads into believing
regexps are egrep compatible
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: procmail
Version: 3.22-11
Severity: wishlist
procmailrc(5) states:
> These regular expressions are completely compatible to the normal
> egrep(1) extended regular expressions. See also Extended regular
> expressions.
However, egrep(1) lists many different forms that are not supported by
procmail (such as "{N}").
Although a long text afterwards procmailrc(5) cautions the user,
> (beware that some egrep implementations include other non-standard
> extensions) ,
I propose that "completely compatible" is substituted with "similar" in
the first paragraph (or at least that "the normal egrep(1) extended
regular expressions" is substituted with "a subset of the regular
expressions supported by egrep(1)").
This did bite me; seeing just the first paragraph, I was misled to
conclude "if it works in egrep, it will work in procmail", which is,
obviously, wrong.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
--- End Message ---
--- Begin Message ---
Hi.
You will notice that I have sent the author a reminder about the old bug,
so I'm closing this one to avoid having a duplicate. [ If you want to
subscribe to the old bug, the BTS now allows it ].
Thanks.
--- End Message ---
