GNU bug report logs - #17655
new snapshot available: grep-2.19.13-ecf36

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 17655 in the body.
You can then email your comments to 17655 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Jim Meyering <jim <at> meyering.net>
To: bug-grep <at> gnu.org
Cc: TP coordinator <coordinator <at> translationproject.org>,
 platform-testers <at> gnu.org
Subject: new snapshot available: grep-2.19.13-ecf36
Date: Sat, 31 May 2014 08:10:10 -0700

Thanks again to Marc Aldorasi for noticing/reporting the bug in
--max-count=N (-m N).  This snapshot differs from the preceding one
only by the commit for that fix and the many updated translation files.
Thanks to all the translators, too!

grep snapshot:
  http://meyering.net/grep/grep-ss.tar.xz      1.2 MB
  http://meyering.net/grep/grep-ss.tar.xz.sig
  http://meyering.net/grep/grep-2.19.13-ecf36.tar.xz

Changes in grep since 2.19.12-96bd:

Jim Meyering (1):
      grep: fix --max-count=N (-m N) to stop reading after Nth match

Message #8 received at 17655 <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Jim Meyering <jim <at> meyering.net>, 17655 <at> debbugs.gnu.org
Cc: platform-testers <at> gnu.org
Subject: Re: bug#17655: new snapshot available: grep-2.19.13-ecf36
Date: Sat, 31 May 2014 14:26:26 -0700

Thanks.  I tried this snapshot on a few platforms (not as many as last 
time) with the same results, so it's looking good.

The failures on AIX 7.1 (same as last time) annoyed me enough that I 
installed what I hope is a fix for them as gnulib commit 
93ce02b4fa01a3c1c194d91f8fd09e1efe04537c.  I don't think these AIX bugs 
need to slow down the grep release.  The only affected flag that grep 
uses is O_NOFOLLOW, and I think the bug merely causes undefined behavior 
that happens to behave as if O_NOFOLLOW is not defined, which is all 
that the fix does anyway.  (Luckily for grep users on AIX, the 
O_NOFOLLOW is used only to avoid a rare race condition.)

I can't help but be curious why the AIX engineers decided to define 
O_NOFOLLOW to a value outside the 'int' range.  Perhaps they had one 
beer too many?

Message #11 received at 17655 <at> debbugs.gnu.org (full text, mbox):

From: Jim Meyering <jim <at> meyering.net>
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: platform-testers <at> gnu.org, 17655 <at> debbugs.gnu.org
Subject: Re: bug#17655: new snapshot available: grep-2.19.13-ecf36
Date: Sat, 31 May 2014 15:40:27 -0700

On Sat, May 31, 2014 at 2:26 PM, Paul Eggert <eggert <at> cs.ucla.edu> wrote:
> Thanks.  I tried this snapshot on a few platforms (not as many as last time)
> with the same results, so it's looking good.

Glad to hear it. Thanks again.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.