[Logcheck-devel] Re: Bug#311216: logcheck: mails "egrep: Invalid content of \{\}"

[Jamie L. Penman-Smithson]

On Mon, 2005-05-30 at 21:49 +0100, Jamie L. Penman-Smithson wrote:
<snip>
> On Mon, 2005-05-30 at 14:28 -0400, John A. Martin wrote:
> > >>>>> "Jamie" == Jamie L Penman-Smithson
> > >>>>> "Re: Bug#311216: logcheck: mails "egrep: Invalid content of \{\}""
> > >>>>>  Mon, 30 May 2005 17:58:30 +0100
> >     >> 
> >     >> egrep: Invalid content of \{\}
> >     >> `----
> 
> > Hmm... I have several boxen each doing the same with yesterday's
> > upgrade.  It looks like the problem occurs on boxen with mixed
> > stable/unstable but not on Sid boxen.
> <snip>
> > It looks like maybe grep-2.4.2-3 gives the problem while
> > grep-2.5.1.ds1-4 does not.  That is not tested, just something that
> > differs between the boxen showing the problem and one that doesn't.  I
> > didn't notice before because the Sid box doesn't normally do logcheck.
> 
> I've tested this and your hypothesis is correct. In woody grep requires
> that { and } characters are escaped, grep 2.5.1 doesn't care whether
> they're escaped or not.

What d'you all think about adding a versioned dependency for grep, since
it appears that grep >= 2.5.1-1 doesn't exhibit this issue.

Of course the alternative solution is to ensure that { and } are always
escaped when used literally.

Thoughts?

-j
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.alioth.debian.org/pipermail/logcheck-devel/attachments/20050601/718614c2/attachment.pgp