GNU bug report logs - #15724
FYI, grep-2.15 is released:

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 15724 in the body.
You can then email your comments to 15724 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
Subject: FYI, grep-2.15 is released:
Date: Sat, 26 Oct 2013 12:11:40 -0700

Here's the announcement:

  https://savannah.gnu.org/forum/forum.php?forum_id=7763

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

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Jim Meyering <jim <at> meyering.net>, 15724 <at> debbugs.gnu.org
Subject: Re: bug#15724: FYI, grep-2.15 is released:
Date: Sat, 26 Oct 2013 12:20:36 -0700

Jim Meyering wrote:
> Here's the announcement:
> 
>   https://savannah.gnu.org/forum/forum.php?forum_id=7763
> 
> 
> 

In that release 'grep --version' outputs this:

grep (GNU grep) 2.14.56-1e3d

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

From: Jim Meyering <jim <at> meyering.net>
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: 15724 <at> debbugs.gnu.org
Subject: Re: bug#15724: FYI, grep-2.15 is released:
Date: Sat, 26 Oct 2013 18:25:09 -0700

On Sat, Oct 26, 2013 at 12:20 PM, Paul Eggert <eggert <at> cs.ucla.edu> wrote:
> Jim Meyering wrote:
>> Here's the announcement:
>>
>>   https://savannah.gnu.org/forum/forum.php?forum_id=7763
>>
>>
>>
>
> In that release 'grep --version' outputs this:
>
> grep (GNU grep) 2.14.56-1e3d

Well, that's an unpleasant surprise -- and cause for at least one more
pre-release check.
I don't know yet what went wrong, but will post as soon as I do.
Thanks for the heads up.

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

From: Jim Meyering <jim <at> meyering.net>
To: bug-gnulib <at> gnu.org, 15724 <15724 <at> debbugs.gnu.org>
Subject: [PATCH] maint.mk: fix "release" target to build _version
Date: Sat, 26 Oct 2013 19:30:46 -0700

[Message part 1 (text/plain, inline)]

This fixes a problem Paul noticed with grep-2.15:

[k.txt (text/plain, attachment)]

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

From: Jim Meyering <jim <at> meyering.net>
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: 15724 <at> debbugs.gnu.org
Subject: Re: bug#15724: FYI, grep-2.15 is released:
Date: Sat, 26 Oct 2013 20:15:26 -0700

[Message part 1 (text/plain, inline)]

 On Sat, Oct 26, 2013 at 6:25 PM, Jim Meyering <jim <at> meyering.net> wrote:
> On Sat, Oct 26, 2013 at 12:20 PM, Paul Eggert <eggert <at> cs.ucla.edu> wrote:
>> Jim Meyering wrote:
>>> Here's the announcement:
>>>
>>>   https://savannah.gnu.org/forum/forum.php?forum_id=7763
>>>
>>>
>>>
>>
>> In that release 'grep --version' outputs this:
>>
>> grep (GNU grep) 2.14.56-1e3d
>
> Well, that's an unpleasant surprise -- and cause for at least one more
> pre-release check.
> I don't know yet what went wrong, but will post as soon as I do.
> Thanks for the heads up.

As explained in
http://git.sv.gnu.org/cgit/gnulib.git/commit/?id=4c2f17d2a6, this was
due to a mismatch between README-release instructions and semantics of
the "release" target in maint.mk.  I've adjusted the latter so this
won't happen again.  Here's the change that pulls in the gnulib fix:

[k.txt (text/plain, attachment)]

Message #22 received at 15724-done <at> debbugs.gnu.org (full text, mbox):

From: Pádraig Brady <P <at> draigBrady.com>
To: Jim Meyering <jim <at> meyering.net>
Cc: 15724-done <at> debbugs.gnu.org
Subject: Re: [PATCH] maint.mk: fix "release" target to build _version
Date: Mon, 28 Oct 2013 00:53:39 +0000

On 10/27/2013 02:30 AM, Jim Meyering wrote:
> This fixes a problem Paul noticed with grep-2.15:
> 
> From 4c2f17d2a671eb6fc6ae318647040598f67705cc Mon Sep 17 00:00:00 2001
> From: Jim Meyering <meyering <at> fb.com>
> Date: Sat, 26 Oct 2013 19:26:13 -0700
> Subject: [PATCH] maint.mk: fix "release" target to build _version
> 
> This fixes a bug in README-release whereby following the outlined
> steps, one would publish a tarball whose programs would report
> --version output not consistent with the package version number.
> This bug caused grep-2.15 to produce a grep program whose
> --version option made it print 2.14.56-1e3d rather than 2.15.
> * top/maint.mk (release): Making this target build "_version"
> ensures that the new version number is reflected in configure.

Cool, we'll get that on the next gnulib sync,
which we'll be doing soon,
so marking this done.

thanks,
Pádraig.

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

From: Jim Meyering <jim <at> meyering.net>
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: 15724 <15724 <at> debbugs.gnu.org>
Subject: Re: bug#15724: FYI, grep-2.15 is released:
Date: Sun, 27 Oct 2013 19:27:52 -0700

For the record, you can correct the contents of an unpacked
grep-2.15 directory by running the following command:

cd grep-2.15 && grep -rl '2\.14.56-1e3d' .|xargs perl -pi -e
's/2\.14.56-1e3d/2.15/g'

This changes what grep --version prints (making it 2.15, not 2.14.xxx...)
and corrects the few references in documentation.

I'll wait a few days and then make a 2.16 release.

Previous Next

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