public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] grep: Update to version 3.11
Date: Thu, 18 May 2023 20:43:22 +0200	[thread overview]
Message-ID: <20230518184328.172754-5-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20230518184328.172754-1-adolf.belka@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2213 bytes --]

- Update from version 3.10 to 3.11
- Update of rootfile not required
- Changelog
* Noteworthy changes in release 3.11 (2023-05-13) [stable]
	** Bug fixes
	  With -P, patterns like [\d] now work again.  Fixing this has caused
	  grep to revert to the behavior of grep 3.8, in that patterns like \w
	  and \b go back to using ASCII rather than Unicode interpretations.
	  However, future versions of GNU grep and/or PCRE2 are likely to fix
	  this and change the behavior of \w and \b back to Unicode again,
	  without breaking [\d] as 3.10 did.
	  [bug introduced in grep 3.10]

	  grep no longer fails on files dated after the year 2038,
	  when running on 32-bit x86 and ARM hosts using glibc 2.34+.
	  [bug introduced in grep 3.9]

	  grep -P no longer fails to match patterns using negated classes
	  like \D or \W when linked with PCRE2 10.34 or newer.
	  [bug introduced in grep 3.8]
	** Changes in behavior
	  grep --version now prints a line describing the version of PCRE2 it uses.
	  For example, it prints this when built with the very latest from git:
	    grep -P uses PCRE2 10.43-DEV 2023-04-14
	  or this with what's currently available in Fedora 37:
	    grep -P uses PCRE2 10.40 2022-04-14

	  previous versions of grep wouldn't respect the user provided settings for
	  PCRE_CFLAGS and PCRE_LIBS when building if a libpcre2-8 pkg-config module
	  was found.

Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
---
 lfs/grep | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/lfs/grep b/lfs/grep
index 1a0b45350..dde47ffa2 100644
--- a/lfs/grep
+++ b/lfs/grep
@@ -24,7 +24,7 @@
 
 include Config
 
-VER        = 3.10
+VER        = 3.11
 
 THISAPP    = grep-$(VER)
 DL_FILE    = $(THISAPP).tar.xz
@@ -50,7 +50,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_BLAKE2 = 5ff169a4ed39e8af1e6729fd2e1bafd39036a4f56cf831f990d58bf9e76bc7d8b055254ae7f60509be4e8bf2f3737edb15431a8ecfc7fc058578d2abea3d73b9
+$(DL_FILE)_BLAKE2 = e21785bca20b5a090d32bb5dc525fb298af30165106ed4c289b1518ea3d2acdcacfd6309b12f13be29a4b958f19588546119c695deb2b7500d49dcff86357bdc
 
 install : $(TARGET)
 
-- 
2.40.1


  parent reply	other threads:[~2023-05-18 18:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-18 18:43 [PATCH] diffutils: Update to version 3.9 Adolf Belka
2023-05-18 18:43 ` [PATCH] ed: Update to version 1.19 Adolf Belka
2023-05-18 18:43 ` [PATCH] gawk: Update to vesrion 5.2.2 Adolf Belka
2023-05-18 18:43 ` [PATCH] go: Update to version 1.20.4 Adolf Belka
2023-05-18 18:43 ` Adolf Belka [this message]
2023-05-18 18:43 ` [PATCH] less: Update to version 633 Adolf Belka
2023-05-18 18:43 ` [PATCH] man: Update to version 2.11.2 Adolf Belka
2023-05-18 18:43 ` [PATCH] procps: Update to version v4.0.3 Adolf Belka
2023-05-18 18:43 ` [PATCH] sqlite: Update to version 3420000 Adolf Belka
2023-05-18 18:43 ` [PATCH] texinfo: Update to version 7.0.3 Adolf Belka
2023-05-18 18:43 ` [PATCH] whois: Update to version 5.5.17 Adolf Belka

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=20230518184328.172754-5-adolf.belka@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.org \
    /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