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.8
Date: Thu, 05 Jan 2023 19:21:05 +0100	[thread overview]
Message-ID: <20230105182110.3725538-1-adolf.belka@ipfire.org> (raw)

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

- Update from version 3.7 to 3.8
- Update of rootfile not required
- Changelog
    * Noteworthy changes in release 3.8 (2022-09-02) [stable]
	** Changes in behavior
		  The -P option is now based on PCRE2 instead of the older PCRE,
		  thanks to code contributed by Carlo Arenas.
		  The egrep and fgrep commands, which have been deprecated since
		  release 2.5.3 (2007), now warn that they are obsolescent and should
		  be replaced by grep -E and grep -F.
		  The confusing GREP_COLOR environment variable is now obsolescent.
		  Instead of GREP_COLOR='xxx', use GREP_COLORS='mt=xxx'.  grep now
		  warns if GREP_COLOR is used and is not overridden by GREP_COLORS.
		  Also, grep now treats GREP_COLOR like GREP_COLORS by silently
		  ignoring it if it attempts to inject ANSI terminal escapes.
		  Regular expressions with stray backslashes now cause warnings, as
		  their unspecified behavior can lead to unexpected results.
		  For example, '\a' and 'a' are not always equivalent
		  <https://bugs.gnu.org/39678>.  Similarly, regular expressions or
		  subexpressions that start with a repetition operator now also cause
		  warnings due to their unspecified behavior; for example, *a(+b|{1}c)
		  now has three reasons to warn.  The warnings are intended as a
		  transition aid; they are likely to be errors in future releases.
		  Regular expressions like [:space:] are now errors even if
		  POSIXLY_CORRECT is set, since POSIX now allows the GNU behavior.
	** Bug fixes
		  In locales using UTF-8 encoding, the regular expression '.' no
		  longer sometimes fails to match Unicode characters U+D400 through
		  U+D7FF (some Hangul Syllables, and Hangul Jamo Extended-B) and
		  Unicode characters U+108000 through U+10FFFF (half of Supplemental
		  Private Use Area plane B).
		  [bug introduced in grep 3.4]
		  The -s option no longer suppresses "binary file matches" messages.
		  [Bug#51860 introduced in grep 3.5]
	** Documentation improvements
		  The manual now covers unspecified behavior in patterns like \x, (+),
		  and range expressions outside the POSIX locale.

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

diff --git a/lfs/grep b/lfs/grep
index c72df7154..deb180348 100644
--- a/lfs/grep
+++ b/lfs/grep
@@ -1,7 +1,7 @@
 ###############################################################################
 #                                                                             #
 # IPFire.org - A linux based firewall                                         #
-# Copyright (C) 2007-2018  IPFire Team  <info(a)ipfire.org>                     #
+# Copyright (C) 2007-2023  IPFire Team  <info(a)ipfire.org>                     #
 #                                                                             #
 # This program is free software: you can redistribute it and/or modify        #
 # it under the terms of the GNU General Public License as published by        #
@@ -24,7 +24,7 @@
 
 include Config
 
-VER        = 3.7
+VER        = 3.8
 
 THISAPP    = grep-$(VER)
 DL_FILE    = $(THISAPP).tar.xz
@@ -50,7 +50,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_BLAKE2 = acf03b1fe8065dac48d686de070bab9ecddae65c97f3b0e2be484e8abdd06d1fbdbb396f3d73dadadf9618aad2f02cf6416094bad64d5f2f15eab6b6b3adfeda
+$(DL_FILE)_BLAKE2 = 24cf6f7aa35c85f59f508969ee9731c5be1e5c613e64e636f464bbdde917bb99ba739e4b82abf08da127ad0400d62e27d139f85142035745121d381982ec6c36
 
 install : $(TARGET)
 
-- 
2.39.0


             reply	other threads:[~2023-01-05 18:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-05 18:21 Adolf Belka [this message]
2023-01-05 18:21 ` [PATCH] haproxy: Update to version 2.7.1 Adolf Belka
2023-01-05 18:21 ` [PATCH] hdparm: Update to version 9.65 Adolf Belka
2023-01-05 18:21 ` [PATCH] iana-etc: Update to version 20221226 Adolf Belka
2023-01-05 18:21 ` [PATCH] igmpproxy: Update to version 0.4 Adolf Belka
2023-01-05 18:45   ` Michael Tremer
2023-01-05 18:21 ` [PATCH] sdl2: Update to version 2.26.2 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=20230105182110.3725538-1-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