From patchwork Wed Feb 3 15:01:48 2021 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Adolf Belka X-Patchwork-Id: 3857 Return-Path: Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) client-signature RSA-PSS (4096 bits)) (Client CN "mail01.haj.ipfire.org", Issuer "R3" (verified OK)) by web04.haj.ipfire.org (Postfix) with ESMTPS id 4DW4dq5dPqz3wdN for ; Wed, 3 Feb 2021 15:01:51 +0000 (UTC) Received: from mail02.haj.ipfire.org (mail02.haj.ipfire.org [172.28.1.201]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) client-signature ECDSA (P-384)) (Client CN "mail02.haj.ipfire.org", Issuer "R3" (verified OK)) by mail01.ipfire.org (Postfix) with ESMTPS id 4DW4dq2Fn9z1Wp; Wed, 3 Feb 2021 15:01:51 +0000 (UTC) Received: from mail02.haj.ipfire.org (localhost [127.0.0.1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4DW4dq2Mdrz2yNY; Wed, 3 Feb 2021 15:01:51 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) client-signature RSA-PSS (4096 bits)) (Client CN "mail01.haj.ipfire.org", Issuer "R3" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4DW4dp2RLlz2xcn for ; Wed, 3 Feb 2021 15:01:50 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) server-digest SHA384) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4DW4dn1TxYzlG; Wed, 3 Feb 2021 15:01:49 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1612364509; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=kDb9f+2epQ109ejemKTDOggOLjhAdYv/cAMV8lXyyuQ=; b=wmtlup8vzk7WMTkbgFzJgbJXC3uWWQ/8KNuluqrqZXDVDtNUm8fwMetSODzPEwlrdJwkPP 2mvCuAcIAhDkJBDA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1612364509; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=kDb9f+2epQ109ejemKTDOggOLjhAdYv/cAMV8lXyyuQ=; b=O3uPAqtFbWHdnpm9b4XFkuVCgZybAcoX49HZddeao22vKnOKRRtvnwEfzKkG9tAAdE/C0F iReUFLTzuwHTM/cSqpH1qRDBAesprr0yotNMM/k4J1Xovpp990KSNQFNQKvKt+I7tiB3jJ WdtZWYWMkAbImOsxqU9kqajGnS+RvZb2frVXfSLMAOm74EGZHItiqMst4q5kjCcbfDsFoa vYyvEWqvzlFe64x2kasF7DqXc27F9SdylZ5hJZsPSoIi4WiwSc0emTlii7m+6KPYWhdRZv S0nq8cCvtBYERAQPNJdARLGX3yRF4QAK+iDC97CZN+TSoirivgZahXxbeFzdow== From: Adolf Belka To: development@lists.ipfire.org Subject: [PATCH] sed: Update to 4.8 Date: Wed, 3 Feb 2021 16:01:48 +0100 Message-Id: <20210203150148.3184888-1-adolf.belka@ipfire.org> MIME-Version: 1.0 X-BeenThere: development@lists.ipfire.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IPFire development talk List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: development-bounces@lists.ipfire.org Sender: "Development" - Update sed from 4.4 to 4.8 - Updated rootfile - Changelog * Noteworthy changes in release 4.8 (2020-01-14) [stable] ** Bug fixes - "sed -i" now creates temporary files with correct umask (limited to u=rwx). Previously sed would incorrectly set umask on temporary files, resulting in problems under certain fuse-like file systems. [bug introduced in sed 4.2.1] ** Release distribute gzip-compressed tarballs once again ** Improvements a year's worth of gnulib development, including improved DFA performance * Noteworthy changes in release 4.7 (2018-12-20) [stable] ** Bug fixes - Some uses of \b in the C locale and with the DFA matcher would fail, e.g., the following would mistakenly print "123-x" instead of "123": echo 123-x|LC_ALL=C sed 's/.\bx//' - Using a multibyte locale or certain regexp constructs (some ranges, backreferences) would avoid the bug. [bug introduced in sed 4.6] * Noteworthy changes in release 4.6 (2018-12-19) [stable] ** Improvements - sed now prints a clear error message when r/R/w/W (and s///w) commands are missing a filename. Previously, w/W commands would fail with confusing error message, while r/R would be a silent no-op. - sed now uses fully-buffered output (instead of line-buffered) when writing to files. This should noticeably improve performance of "sed -i" and other write commands. Buffering can be disabled (as before) with "sed -u". - sed in non-cygwin windows environments (e.g. mingw) now properly handles '\n' newlines in -b/--binary mode. ** Bug fixes - sed no longer accesses invalid memory (heap overflow) when given invalid backreferences in 's' command [bug#32082, present at least since sed-4.0.6]. - sed no longer adds extraneous NUL when given s/$//n command. [related to bug#32271, present since sed-4.0.7] - sed no longer accesses invalid memory (heap overflow) with s/$//n regexes. [bug#32271, present since sed-4.3]. ** New Features New option, --debug: print the input sed script in canonical form and annotate program execution. * Noteworthy changes in release 4.5 (2018-03-31) [stable] ** Bug fixes - sed now fails when matching very long input lines (>2GB). Before, sed would silently ignore the regex without indicating an error. [Bug present at least since sed-3.02] - sed no longer rejects comments and closing braces after y/// commands. [Bug existed at least since sed-3.02] - sed -E --posix no longer ignores special meaning of '+','?','|' . [Bug introduced in the original implementation of --posix option in v4.1a-5-gba68fb4] - sed -i now creates selinux context based on the context of the symlink instead of the symlink target. [Bug present since at least sed-4.2] - sed -i --follow-symlinks remains unchanged. - sed now treats the sequence '\x5c' (ASCII 92, backslash) as literal backslash character, not as an escape prefix character. [Bug present since sed-3.02.80] Old behavior: $ echo z | sed -E 's/(z)/\x5c1/' # identical to 's/(z)/\1/' z New behavior: $ echo z | sed -E 's/(z)/\x5c1/' \1 Signed-off-by: Adolf Belka --- config/rootfiles/common/sed | 2 +- lfs/sed | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/config/rootfiles/common/sed b/config/rootfiles/common/sed index 8db08fa39..f355a89ca 100644 --- a/config/rootfiles/common/sed +++ b/config/rootfiles/common/sed @@ -1,3 +1,3 @@ bin/sed #usr/share/info/sed.info -#usr/share/man/man1/sed.1 +#usr/share/man/man1/sed.1 \ No newline at end of file diff --git a/lfs/sed b/lfs/sed index 9123183e3..9c5b33e4a 100644 --- a/lfs/sed +++ b/lfs/sed @@ -24,7 +24,7 @@ include Config -VER = 4.4 +VER = 4.8 THISAPP = sed-$(VER) DL_FILE = $(THISAPP).tar.xz @@ -53,7 +53,7 @@ objects = $(DL_FILE) $(DL_FILE) = $(DL_FROM)/$(DL_FILE) -$(DL_FILE)_MD5 = e0c583d4c380059abd818cd540fe6938 +$(DL_FILE)_MD5 = 6d906edfdb3202304059233f51f9a71d install : $(TARGET)