sed: Update to version 4.9

  - 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@ipfire.org>
---
 lfs/sed | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
  

Reviewed-by: Peter Müller <peter.mueller@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@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)
>
  

Reviewed-by: Michael Tremer <michael.tremer@ipfire.org>

> On 19 Nov 2022, at 21:48, Adolf Belka <adolf.belka@ipfire.org> wrote:
> 
> - 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@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)
> 
> -- 
> 2.38.1
>