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] sed: Update to version 4.10
Date: Mon, 27 Apr 2026 20:47:01 +0200	[thread overview]
Message-ID: <20260427184701.2249214-3-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20260427184701.2249214-1-adolf.belka@ipfire.org>

- Update from version 4.9 to 4.10
- Update of rootfile
- Changelog
4.10
Bug fixes
  sed 's/a/b/g' (and other global substitutions) now works on input
   lines longer than 2GB. Previously, matches beyond the 2^31 byte offset
   would evoke a "panic" (exit 4).
   [bug present since the beginning]
  'sed --follow-symlinks -i' no longer has a TOCTOU race that could let
   an attacker swap a symlink between resolution and open, causing sed to
   read attacker-chosen content and write it to the original target.
   [bug introduced in sed 4.1e]
  sed no longer falsely matches when back-references are combined with
   optional groups (.?) and the $ anchor.  For example, this no longer
   falsely matches the empty string at beginning of line:
     $ echo ab | sed -E 's/^(.?)(.?).?\2\1$/X/'
     Xab
   [bug present since "the beginning"]
  In --posix mode, sed no longer mishandles backslash escapes (\n,
   \t, \a, etc.) after a named character class like [[:alpha:]].
   For example, 's/^A\n[[:alpha:]]\n*/XXX/' would fail to match the
   trailing newline, treating \n as a literal backslash and an 'n'
   rather than a newline.  This happened when an earlier backslash
   escape in the same regex had already been converted, shifting the
   in-place normalization buffer.
   [bug introduced in sed 4.9]
  sed --debug no longer crashes when a label (":") command is compiled
   before the --debug option is processed, e.g., sed -f<(...) --debug.
   [bug introduced in sed 4.7 with --debug]
  sed no longer rejects the documented GNU extension 'a**' (equivalent
   to 'a*') in Basic Regular Expression (BRE) mode.  Previously, this
   worked only with -E (ERE mode), even though grep has always accepted
   it in BRE mode.
   [bug present since "the beginning"]
  sed no longer rejects "\c[" in regular expressions
   [bug present since the beginning]
  'sed --follow-symlinks -i' no longer mishandles an operand that is a
   short symbolic link to a long symbolic link to a file.
   [bug introduced in sed 4.9]
  Fix some some longstanding but unlikely integer overflows.
  Internally, 'sed' now more often prefers signed integer arithmetic,
   which can be checked automatically via 'gcc -fsanitize=undefined'.
Changes in behavior
  In the default C locale, diagnostics now quote 'like this' (with
   apostrophes) instead of `like this' (with a grave accent and an
   apostrophe).  This tracks the GNU coding standards.
   'sed --posix' now warns about uses of backslashes in the 's' command
   that are handled by GNU sed but are not portable to other
   implementations.
Build-related
  builds no longer fail on platforms without the <getopt.h> header or
   getopt_long function.
   [bug introduced in sed 4.9]

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

diff --git a/lfs/sed b/lfs/sed
index 89ca4f250..f11096053 100644
--- a/lfs/sed
+++ b/lfs/sed
@@ -1,7 +1,7 @@
 ###############################################################################
 #                                                                             #
 # IPFire.org - A linux based firewall                                         #
-# Copyright (C) 2007-2018  IPFire Team  <info@ipfire.org>                     #
+# Copyright (C) 2007-2026  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        = 4.9
+VER        = 4.10
 
 THISAPP    = sed-$(VER)
 DL_FILE    = $(THISAPP).tar.xz
@@ -53,7 +53,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_BLAKE2 = 6c7c7dc782b87c3bd0b5e826ba46c2f1dc7bd8c1159945fcf14b394711742964628774cf9f27d844b672721d7849e6c31992d82fafb9ed4118b7feb60406d1e1
+$(DL_FILE)_BLAKE2 = 6decea38a3e6eb3b672af2380ec3f32759b60350dba528d28a57b74806db33208baed69a8497d423bc7626105930e3e9c9ea68f68b8bcd4a3270f2d8922a2487
 
 install : $(TARGET)
 
-- 
2.54.0



      parent reply	other threads:[~2026-04-27 18:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-27 18:46 [PATCH] core202: Ship sed Adolf Belka
2026-04-27 18:47 ` [PATCH] man-pages: Update to version 6.18 Adolf Belka
2026-04-27 18:47 ` Adolf Belka [this message]

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=20260427184701.2249214-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