From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] sed: Update to version 4.9
Date: Mon, 21 Nov 2022 08:28:03 +0000 [thread overview]
Message-ID: <97cf49dc-84f4-0c63-86ee-40a1a80be4bc@ipfire.org> (raw)
In-Reply-To: <20221119214851.3386858-1-adolf.belka@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2324 bytes --]
Reviewed-by: Peter Müller <peter.mueller(a)ipfire.org>
> - Update from version 4.8 to 4.9
> - Update of rootfile not required
> - Changelog
> * Noteworthy changes in release 4.9 (2022-11-06) [stable]
> ** Bug fixes
> 'sed --follow-symlinks -i' no longer loops forever when its operand
> is a symbolic link cycle.
> [bug introduced in sed 4.2]
> a program with an execution line longer than 2GB can no longer trigger
> an out-of-bounds memory write.
> using the R command to read an input line of length longer than 2GB
> can no longer trigger an out-of-bounds memory read.
> 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 sed 4.8]
> I/O errors involving temp files no longer confuse sed into using a
> FILE * pointer after fclosing it, which has undefined behavior in C.
> ** New Features
> The 'r' command now accepts address 0, allowing inserting a file before
> the first line.
> ** Changes in behavior
> Sed now prints the less-surprising variant in a corner case of
> POSIX-unspecified behavior. Before, this would print "n".
> Now, it prints "X":
> printf n | sed 'sn\nnXn'; echo
>
> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
> ---
> lfs/sed | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/lfs/sed b/lfs/sed
> index 157be07cd..89ca4f250 100644
> --- a/lfs/sed
> +++ b/lfs/sed
> @@ -24,7 +24,7 @@
>
> include Config
>
> -VER = 4.8
> +VER = 4.9
>
> THISAPP = sed-$(VER)
> DL_FILE = $(THISAPP).tar.xz
> @@ -53,7 +53,7 @@ objects = $(DL_FILE)
>
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>
> -$(DL_FILE)_BLAKE2 = 62f6b6500cc9a20a35cafc2b09b12bb7da67fa0afb0b1b26153babc0023424b3126f44d29eba14c25fc4490996c90738b191c9440c66da6c120bbb9bc6f6df65
> +$(DL_FILE)_BLAKE2 = 6c7c7dc782b87c3bd0b5e826ba46c2f1dc7bd8c1159945fcf14b394711742964628774cf9f27d844b672721d7849e6c31992d82fafb9ed4118b7feb60406d1e1
>
> install : $(TARGET)
>
next prev parent reply other threads:[~2022-11-21 8:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 21:48 Adolf Belka
2022-11-21 8:28 ` Peter Müller [this message]
2022-11-21 9:11 ` Michael Tremer
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=97cf49dc-84f4-0c63-86ee-40a1a80be4bc@ipfire.org \
--to=peter.mueller@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