public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Cc: Adolf Belka <adolf.belka@ipfire.org>
Subject: [PATCH] grep: Update to version 3.12
Date: Sun,  4 May 2025 15:17:06 +0200	[thread overview]
Message-ID: <20250504131711.3311134-3-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20250504131711.3311134-1-adolf.belka@ipfire.org>

- Update from version 3.11 to 3.12
- Update of rootfile not required
- Changelog
    3.12
	** Bug fixes
	  Searching a directory with at least 100,000 entries no longer fails
	   with "Operation not supported" and exit status 2. Now, this prints 1
	   and no diagnostic, as expected:
	     $ mkdir t && cd t && seq 100000|xargs touch && grep -r x .; echo $?
	     1
	   [bug introduced in grep 3.11]
	  -mN where 1 < N no longer mistakenly lseeks to end of input merely
	   because standard output is /dev/null.
	** Changes in behavior
	  The --unix-byte-offsets (-u) option is gone. In grep-3.7 (2021-08-14)
	   it became a warning-only no-op. Before then, it was a Windows-only no-op.
	  On Windows platforms and on AIX in 32-bit mode, grep in some cases
	   now supports Unicode characters outside the Basic Multilingual Plane.

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

diff --git a/lfs/grep b/lfs/grep
index dde47ffa2..e29285a23 100644
--- a/lfs/grep
+++ b/lfs/grep
@@ -1,7 +1,7 @@
 ###############################################################################
 #                                                                             #
 # IPFire.org - A linux based firewall                                         #
-# Copyright (C) 2007-2023  IPFire Team  <info@ipfire.org>                     #
+# Copyright (C) 2007-2025  IPFire Team  <info@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.11
+VER        = 3.12
 
 THISAPP    = grep-$(VER)
 DL_FILE    = $(THISAPP).tar.xz
@@ -50,7 +50,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_BLAKE2 = e21785bca20b5a090d32bb5dc525fb298af30165106ed4c289b1518ea3d2acdcacfd6309b12f13be29a4b958f19588546119c695deb2b7500d49dcff86357bdc
+$(DL_FILE)_BLAKE2 = 93d06bce04793f4b4c94d92febc6092f669e50e1bfc1bef3c911a2ca322560bdab8619e88a05a4d6ea4908b2d01da1926a99a22eecc513bd48b8957984bdfa12
 
 install : $(TARGET)
 
-- 
2.49.0



  parent reply	other threads:[~2025-05-04 13:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-04 13:17 [PATCH] diffutils: " Adolf Belka
2025-05-04 13:17 ` [PATCH] gawk: Update to version 5.3.2 Adolf Belka
2025-05-04 13:17 ` Adolf Belka [this message]
2025-05-04 13:17 ` [PATCH] harfbuzz: Update to version 11.2.0 Adolf Belka
2025-05-04 13:17 ` [PATCH] hwdata: Update to version 0.394 Adolf Belka
2025-05-04 13:17 ` [PATCH] patch: Update to version 2.8 Adolf Belka
2025-05-04 13:17 ` [PATCH] tshark: Update to version 4.4.6 Adolf Belka
2025-05-04 13:17 ` [PATCH] xfsprogs: Update to version 6.14.0 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=20250504131711.3311134-3-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