+ case "${usergroup_phase}" in + local run_cmd + run_cmd=run_su + shift + run_su /opt/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent WRKLOG=/tmp/bulklog/bash-5.2.37/work.log + su pbulk -c '"$@"' make /opt/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent WRKLOG=/tmp/bulklog/bash-5.2.37/work.log => Checksum BLAKE2s OK for bash-5.2.tar.gz => Checksum SHA512 OK for bash-5.2.tar.gz => Checksum BLAKE2s OK for bash52-001 => Checksum SHA512 OK for bash52-001 => Checksum BLAKE2s OK for bash52-002 => Checksum SHA512 OK for bash52-002 => Checksum BLAKE2s OK for bash52-003 => Checksum SHA512 OK for bash52-003 => Checksum BLAKE2s OK for bash52-004 => Checksum SHA512 OK for bash52-004 => Checksum BLAKE2s OK for bash52-005 => Checksum SHA512 OK for bash52-005 => Checksum BLAKE2s OK for bash52-006 => Checksum SHA512 OK for bash52-006 => Checksum BLAKE2s OK for bash52-007 => Checksum SHA512 OK for bash52-007 => Checksum BLAKE2s OK for bash52-008 => Checksum SHA512 OK for bash52-008 => Checksum BLAKE2s OK for bash52-009 => Checksum SHA512 OK for bash52-009 => Checksum BLAKE2s OK for bash52-010 => Checksum SHA512 OK for bash52-010 => Checksum BLAKE2s OK for bash52-011 => Checksum SHA512 OK for bash52-011 => Checksum BLAKE2s OK for bash52-012 => Checksum SHA512 OK for bash52-012 => Checksum BLAKE2s OK for bash52-013 => Checksum SHA512 OK for bash52-013 => Checksum BLAKE2s OK for bash52-014 => Checksum SHA512 OK for bash52-014 => Checksum BLAKE2s OK for bash52-015 => Checksum SHA512 OK for bash52-015 => Checksum BLAKE2s OK for bash52-016 => Checksum SHA512 OK for bash52-016 => Checksum BLAKE2s OK for bash52-017 => Checksum SHA512 OK for bash52-017 => Checksum BLAKE2s OK for bash52-018 => Checksum SHA512 OK for bash52-018 => Checksum BLAKE2s OK for bash52-019 => Checksum SHA512 OK for bash52-019 => Checksum BLAKE2s OK for bash52-020 => Checksum SHA512 OK for bash52-020 => Checksum BLAKE2s OK for bash52-021 => Checksum SHA512 OK for bash52-021 => Checksum BLAKE2s OK for bash52-022 => Checksum SHA512 OK for bash52-022 => Checksum BLAKE2s OK for bash52-023 => Checksum SHA512 OK for bash52-023 => Checksum BLAKE2s OK for bash52-024 => Checksum SHA512 OK for bash52-024 => Checksum BLAKE2s OK for bash52-025 => Checksum SHA512 OK for bash52-025 => Checksum BLAKE2s OK for bash52-026 => Checksum SHA512 OK for bash52-026 => Checksum BLAKE2s OK for bash52-027 => Checksum SHA512 OK for bash52-027 => Checksum BLAKE2s OK for bash52-028 => Checksum SHA512 OK for bash52-028 => Checksum BLAKE2s OK for bash52-029 => Checksum SHA512 OK for bash52-029 => Checksum BLAKE2s OK for bash52-030 => Checksum SHA512 OK for bash52-030 => Checksum BLAKE2s OK for bash52-031 => Checksum SHA512 OK for bash52-031 => Checksum BLAKE2s OK for bash52-032 => Checksum SHA512 OK for bash52-032 => Checksum BLAKE2s OK for bash52-033 => Checksum SHA512 OK for bash52-033 => Checksum BLAKE2s OK for bash52-034 => Checksum SHA512 OK for bash52-034 => Checksum BLAKE2s OK for bash52-035 => Checksum SHA512 OK for bash52-035 => Checksum BLAKE2s OK for bash52-036 => Checksum SHA512 OK for bash52-036 => Checksum BLAKE2s OK for bash52-037 => Checksum SHA512 OK for bash52-037 ===> Installing dependencies for bash-5.2.37 ========================================================================== The supported build options for bash are: nls The currently selected options are: nls You can select which build options to use by setting PKG_DEFAULT_OPTIONS or the following variable. Its current value is shown: PKG_OPTIONS.bash (not defined) ========================================================================== ========================================================================== The following variables will affect the build process of this package, bash-5.2.37. Their current value is shown below: * CURSES_DEFAULT = ncurses Based on these variables, the following variables have been set: * CURSES_TYPE = ncurses * TERMCAP_TYPE = curses You may want to abort the process now with CTRL-C and change the value of variables in the first group before continuing. Be sure to run `/opt/pkg/bin/bmake clean' after the changes. ========================================================================== => Tool dependency bison>=1.0: found bison-3.8.2nb1 => Tool dependency gtexinfo>=4.1: found gtexinfo-7.2 => Tool dependency gettext-tools>=0.15: found gettext-tools-0.22.5nb1 => Tool dependency cwrappers>=20150314: found cwrappers-20220403 => Tool dependency checkperms>=1.1: found checkperms-1.12 => Full dependency pkg_install-info-[0-9]*: found pkg_install-info-4.5nb3 => Full dependency gettext-lib>=0.22: found gettext-lib-0.22.5 => Full dependency ncurses>=6.5: found ncurses-6.5nb1 => Full dependency libiconv>=1.9.1: found libiconv-1.17 ===> Overriding tools for bash-5.2.37 ===> Extracting for bash-5.2.37 ===> Patching for bash-5.2.37 => Applying distribution patches for bash-5.2.37 => Applying distribution patch bash52-001 Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- | BASH PATCH REPORT | ================= | |Bash-Release: 5.2 |Patch-ID: bash52-001 | |Bug-Reported-by: Emanuele Torre |Bug-Reference-ID: |Bug-Reference-URL: https://lists.gnu.org/archive/html/bug-bash/2022-09/msg00060.html | |Bug-Description: | |Expanding unset arrays in an arithmetic context can cause a segmentation fault. | |Patch (apply with `patch -p0'): | |*** ../bash-5.2/subst.c 2022-08-31 17:36:46.000000000 -0400 |--- subst.c 2022-09-30 09:12:05.000000000 -0400 -------------------------- Patching file subst.c using Plan A... Hunk #1 succeeded at 10858. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** ../bash-5.2/patchlevel.h 2020-06-22 14:51:03.000000000 -0400 |--- patchlevel.h 2020-10-01 11:01:28.000000000 -0400 -------------------------- Patching file patchlevel.h using Plan A... Hunk #1 succeeded at 26. done => Applying distribution patch bash52-002 Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- | BASH PATCH REPORT | ================= | |Bash-Release: 5.2 |Patch-ID: bash52-002 | |Bug-Reported-by: Kan-Ru Chen |Bug-Reference-ID: |Bug-Reference-URL: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021109 | |Bug-Description: | |Starting bash with an invalid locale specification for LC_ALL/LANG/LC_CTYPE |can cause the shell to crash. | |Patch (apply with `patch -p0'): | |*** ../bash-5.2-patched/lib/readline/nls.c 2022-08-15 09:38:51.000000000 -0400 |--- lib/readline/nls.c 2022-10-05 09:23:22.000000000 -0400 -------------------------- Patching file lib/readline/nls.c using Plan A... Hunk #1 succeeded at 142. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- | |*** ../bash-5.2/patchlevel.h 2020-06-22 14:51:03.000000000 -0400 |--- patchlevel.h 2020-10-01 11:01:28.000000000 -0400 -------------------------- Patching file patchlevel.h using Plan A... Hunk #1 succeeded at 26. done => Applying distribution patch bash52-003 Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- | BASH PATCH REPORT | ================= | |Bash-Release: 5.2 |Patch-ID: bash52-003 | |Bug-Reported-by: D630 |Bug-Reference-ID: |Bug-Reference-URL: https://lists.gnu.org/archive/html/bug-bash/2022-10/msg00092.html | |Bug-Description: | |Command substitutions need to preserve newlines instead of replacing them |with semicolons, especially in the presence of multiple here-documents. | |Patch (apply with `patch -p0'): | |*** ../bash-5.2-patched/print_cmd.c 2022-07-26 09:16:39.000000000 -0400 |--- print_cmd.c 2022-10-17 10:41:06.000000000 -0400 -------------------------- Patching file print_cmd.c using Plan A... Hunk #1 succeeded at 298. Hunk #2 succeeded at 317. Hunk #3 succeeded at 1371. Hunk #4 succeeded at 1452. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** ../bash-5.2/patchlevel.h 2020-06-22 14:51:03.000000000 -0400 |--- patchlevel.h 2020-10-01 11:01:28.000000000 -0400 -------------------------- Patching file patchlevel.h using Plan A... Hunk #1 succeeded at 26. done => Applying distribution patch bash52-004 Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- | BASH PATCH REPORT | ================= | |Bash-Release: 5.2 |Patch-ID: bash52-004 | |Bug-Reported-by: Antoine |Bug-Reference-ID: <8bd59753-05ff-9b09-2337-2c7f52ded650@glitchimini.net> |Bug-Reference-URL: https://lists.gnu.org/archive/html/bug-bash/2022-10/msg00022.html | |Bug-Description: | |Bash needs to keep better track of nested brace expansions to avoid problems |with quoting and POSIX semantics. | |Patch (apply with `patch -p0'): | |*** ../bash-5.2-patched/subst.c 2022-10-05 10:22:02.000000000 -0400 |--- subst.c 2022-10-06 15:19:08.000000000 -0400 -------------------------- Patching file subst.c using Plan A... Hunk #1 succeeded at 1804. Hunk #2 succeeded at 1837. Hunk #3 succeeded at 1863. Hunk #4 succeeded at 1877. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** ../bash-5.2/patchlevel.h 2020-06-22 14:51:03.000000000 -0400 |--- patchlevel.h 2020-10-01 11:01:28.000000000 -0400 -------------------------- Patching file patchlevel.h using Plan A... Hunk #1 succeeded at 26. done => Applying distribution patch bash52-005 Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- | BASH PATCH REPORT | ================= | |Bash-Release: 5.2 |Patch-ID: bash52-005 | |Bug-Reported-by: Justin Wood (Callek) |Bug-Reference-ID: |Bug-Reference-URL: https://lists.gnu.org/archive/html/bug-bash/2022-10/msg00088.html | |Bug-Description: | |Null pattern substitution replacement strings can cause a crash. | |Patch (apply with `patch -p0'): | |*** ../bash-5.2-patched/subst.c 2022-10-05 10:22:02.000000000 -0400 |--- subst.c 2022-10-13 16:57:26.000000000 -0400 -------------------------- Patching file subst.c using Plan A... Hunk #1 succeeded at 8966. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** ../bash-5.2/patchlevel.h 2020-06-22 14:51:03.000000000 -0400 |--- patchlevel.h 2020-10-01 11:01:28.000000000 -0400 -------------------------- Patching file patchlevel.h using Plan A... Hunk #1 succeeded at 26. done => Applying distribution patch bash52-006 Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- | BASH PATCH REPORT | ================= | |Bash-Release: 5.2 |Patch-ID: bash52-006 | |Bug-Reported-by: feng xiangjun |Bug-Reference-ID: |Bug-Reference-URL: https://lists.gnu.org/archive/html/bug-bash/2022-10/msg00089.html | |Bug-Description: | |In interactive shells, interrupting the shell while entering a command |substitution can inhibit alias expansion. | |Patch (apply with `patch -p0'): | |*** ../bash-5.2-patched/parse.y 2022-10-08 13:10:06.000000000 -0400 |--- parse.y 2022-10-14 10:03:19.000000000 -0400 -------------------------- Patching file parse.y using Plan A... Hunk #1 succeeded at 3307. Hunk #2 succeeded at 4391. Hunk #3 succeeded at 6405. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** ../bash-20221007/parser.h 2022-08-30 11:39:56.000000000 -0400 |--- parser.h 2022-10-14 09:56:18.000000000 -0400 -------------------------- Patching file parser.h using Plan A... Hunk #1 succeeded at 51. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** ../bash-20221007/builtins/shopt.def 2022-10-07 10:25:55.000000000 -0400 |--- builtins/shopt.def 2022-10-14 09:30:11.000000000 -0400 -------------------------- Patching file builtins/shopt.def using Plan A... Hunk #1 succeeded at 150. Hunk #2 succeeded at 202. Hunk #3 succeeded at 354. Hunk #4 succeeded at 635. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** ../bash-20221007/builtins/common.h 2022-10-07 10:10:17.000000000 -0400 |--- builtins/common.h 2022-10-14 09:29:25.000000000 -0400 -------------------------- Patching file builtins/common.h using Plan A... Hunk #1 succeeded at 258. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** ../bash-20221007/execute_cmd.c 2022-10-10 10:48:54.000000000 -0400 |--- execute_cmd.c 2022-10-14 09:32:24.000000000 -0400 -------------------------- Patching file execute_cmd.c using Plan A... Hunk #1 succeeded at 1537. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** ../bash-20221007/general.c 2021-11-04 14:12:38.000000000 -0400 |--- general.c 2022-10-14 09:34:24.000000000 -0400 -------------------------- Patching file general.c using Plan A... Hunk #1 succeeded at 92. Hunk #2 succeeded at 107. Hunk #3 succeeded at 118. Hunk #4 succeeded at 125. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- | |*** ../bash-5.2-patched/shell.c 2022-03-04 15:13:00.000000000 -0500 |--- shell.c 2022-10-14 09:36:19.000000000 -0400 -------------------------- Patching file shell.c using Plan A... Hunk #1 succeeded at 1845. Hunk #2 succeeded at 1866. Hunk #3 succeeded at 1883. Hunk #4 succeeded at 2026. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** ../bash-5.2-patched/y.tab.c 2022-09-23 10:18:27.000000000 -0400 |--- y.tab.c 2022-10-14 14:57:26.000000000 -0400 -------------------------- Patching file y.tab.c using Plan A... Hunk #1 succeeded at 5618. Hunk #2 succeeded at 6702. Hunk #3 succeeded at 8716. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** ../bash-5.2/patchlevel.h 2020-06-22 14:51:03.000000000 -0400 |--- patchlevel.h 2020-10-01 11:01:28.000000000 -0400 -------------------------- Patching file patchlevel.h using Plan A... Hunk #1 succeeded at 26. done => Applying distribution patch bash52-007 Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- | BASH PATCH REPORT | ================= | |Bash-Release: 5.2 |Patch-ID: bash52-007 | |Bug-Reported-by: Bruce Jerrick |Bug-Reference-ID: |Bug-Reference-URL: https://bugzilla.redhat.com/show_bug.cgi?id=2134307 | |Bug-Description: | |This patch fixes several problems with alias expansion inside command |substitutions when in POSIX mode. | |Patch (apply with `patch -p0'): | |*** /fs1/chet/scratch/bash-5.2.6/parse.y 2022-11-02 10:36:54.000000000 -0400 |--- parse.y 2022-10-24 10:53:26.000000000 -0400 -------------------------- Patching file parse.y using Plan A... Hunk #1 succeeded at 3614. Hunk #2 succeeded at 3914. Hunk #3 succeeded at 3947. Hunk #4 succeeded at 4086. Hunk #5 succeeded at 4512. Hunk #6 succeeded at 5030. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** ../bash-5.2.6/y.tab.c 2022-11-02 10:36:54.000000000 -0400 |--- y.tab.c 2022-11-02 10:55:58.000000000 -0400 -------------------------- Patching file y.tab.c using Plan A... Hunk #1 succeeded at 5924. Hunk #2 succeeded at 6223. Hunk #3 succeeded at 6256. Hunk #4 succeeded at 6395. Hunk #5 succeeded at 6816. Hunk #6 succeeded at 7331. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** /fs1/chet/scratch/bash-5.2.6/builtins/evalstring.c 2022-07-18 14:46:56.000000000 -0400 |--- builtins/evalstring.c 2022-10-18 10:57:51.000000000 -0400 -------------------------- Patching file builtins/evalstring.c using Plan A... Hunk #1 succeeded at 432. Hunk #2 succeeded at 510. Hunk #3 succeeded at 540. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** /fs1/chet/scratch/bash-5.2.6/command.h 2021-04-30 15:43:15.000000000 -0400 |--- command.h 2022-10-18 11:44:31.000000000 -0400 -------------------------- Patching file command.h using Plan A... Hunk #1 succeeded at 115. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** /fs1/chet/scratch/bash-5.2.6/subst.c 2022-11-02 10:28:10.000000000 -0400 |--- subst.c 2022-10-20 12:41:07.000000000 -0400 -------------------------- Patching file subst.c using Plan A... Hunk #1 succeeded at 7133. Hunk #2 succeeded at 11306. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** ../bash-5.2/patchlevel.h 2020-06-22 14:51:03.000000000 -0400 |--- patchlevel.h 2020-10-01 11:01:28.000000000 -0400 -------------------------- Patching file patchlevel.h using Plan A... Hunk #1 succeeded at 26. done => Applying distribution patch bash52-008 Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- | BASH PATCH REPORT | ================= | |Bash-Release: 5.2 |Patch-ID: bash52-008 | |Bug-Reported-by: Glenn Jackman |Bug-Reference-ID: |Bug-Reference-URL: https://lists.gnu.org/archive/html/bug-bash/2022-10/msg00095.html | |Bug-Description: | |Array subscript expansion can inappropriately quote brackets if the expression |contains < or >. | |Patch (apply with `patch -p0'): | |*** ../bash-20221015/subst.c 2022-10-18 10:47:33.000000000 -0500 |--- subst.c 2022-10-20 11:41:07.000000000 -0500 -------------------------- Patching file subst.c using Plan A... Hunk #1 succeeded at 3820. Hunk #2 succeeded at 4033. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** ../bash-5.2/patchlevel.h 2020-06-22 14:51:03.000000000 -0400 |--- patchlevel.h 2020-10-01 11:01:28.000000000 -0400 -------------------------- Patching file patchlevel.h using Plan A... Hunk #1 succeeded at 26. done => Applying distribution patch bash52-009 Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- | BASH PATCH REPORT | ================= | |Bash-Release: 5.2 |Patch-ID: bash52-009 | |Bug-Reported-by: Corey Hickey |Bug-Reference-ID: <134330ef-0ead-d73e-68eb-d58fc51efdba@fatooh.org> |Bug-Reference-URL: https://lists.gnu.org/archive/html/help-bash/2022-10/msg00025.html | |Bug-Description: | |Bash arithmetic expansion should allow `@' and `*' to be used as associative |array keys in expressions. | |Patch (apply with `patch -p0'): | |*** ../bash-5.2-patched/expr.c 2022-07-11 10:03:34.000000000 -0400 |--- expr.c 2022-10-31 10:51:08.000000000 -0400 -------------------------- Patching file expr.c using Plan A... Hunk #1 succeeded at 1169. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** ../bash-5.2/patchlevel.h 2020-06-22 14:51:03.000000000 -0400 |--- patchlevel.h 2020-10-01 11:01:28.000000000 -0400 -------------------------- Patching file patchlevel.h using Plan A... Hunk #1 succeeded at 26. done => Applying distribution patch bash52-010 Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- | BASH PATCH REPORT | ================= | |Bash-Release: 5.2 |Patch-ID: bash52-010 | |Bug-Reported-by: larsh@apache.org |Bug-Reference-ID: |Bug-Reference-URL: https://savannah.gnu.org/support/?110744 | |Bug-Description: | |Bash-5.2 checks the first 128 characters of an executable file that execve() |refuses to execute to see whether it's a binary file before trying to |execute it as a shell script. This defeats some previously-supported use |cases like "self-executing" jar files or "self-uncompressing" scripts. | |Patch (apply with `patch -p0'): | |*** ../bash-5.2-patched/general.c 2022-11-07 10:31:42.000000000 -0500 |--- general.c 2022-11-18 14:48:45.000000000 -0500 -------------------------- Patching file general.c using Plan A... Hunk #1 succeeded at 684. Hunk #2 succeeded at 691. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** ../bash-5.2/patchlevel.h 2020-06-22 14:51:03.000000000 -0400 |--- patchlevel.h 2020-10-01 11:01:28.000000000 -0400 -------------------------- Patching file patchlevel.h using Plan A... Hunk #1 succeeded at 26. done => Applying distribution patch bash52-011 Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- | BASH PATCH REPORT | ================= | |Bash-Release: 5.2 |Patch-ID: bash52-011 | |Bug-Reported-by: Fabien Orjollet |Bug-Reference-ID: |Bug-Reference-URL: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023776 | |Bug-Description: | |Patch (apply with `patch -p0'): | |Using timeouts and readline editing with the `read' builtin (read -e -t) can |leave the readline timeout enabled, potentially resulting in an erroneous |timeout on the next call. | |*** ../bash-5.2-patched/builtins/read.def 2022-06-02 14:23:19.000000000 -0400 |--- builtins/read.def 2022-11-10 10:27:45.000000000 -0500 -------------------------- Patching file builtins/read.def using Plan A... Hunk #1 succeeded at 168. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** ../bash-5.2/patchlevel.h 2020-06-22 14:51:03.000000000 -0400 |--- patchlevel.h 2020-10-01 11:01:28.000000000 -0400 -------------------------- Patching file patchlevel.h using Plan A... Hunk #1 succeeded at 26. done => Applying distribution patch bash52-012 Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- | BASH PATCH REPORT | ================= | |Bash-Release: 5.2 |Patch-ID: bash52-012 | |Bug-Reported-by: Kerin Millar |Bug-Reference-ID: <20221002095107.89561bc811e549b55644df11@plushkava.net> |Bug-Reference-URL: https://lists.gnu.org/archive/html/bug-bash/2022-10/msg00001.html | |Bug-Description: | |When running in bash compatibility mode, nested command substitutions can |leave the `extglob' option enabled. | |Patch (apply with `patch -p0'): | |*** /fs1/chet/scratch/bash-5.2.12/builtins/shopt.def 2022-11-07 10:31:42.000000000 -0500 |--- builtins/shopt.def 2022-10-14 09:30:11.000000000 -0400 -------------------------- Patching file builtins/shopt.def using Plan A... Hunk #1 succeeded at 150. Hunk #2 succeeded at 212. Hunk #3 succeeded at 383. Hunk #4 succeeded at 649. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** /fs1/chet/scratch/bash-5.2.12/builtins/common.h 2022-11-07 10:31:42.000000000 -0500 |--- builtins/common.h 2022-10-14 09:29:25.000000000 -0400 -------------------------- Patching file builtins/common.h using Plan A... Hunk #1 succeeded at 258. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** /fs1/chet/scratch/bash-5.2.12/execute_cmd.c 2022-11-07 10:31:42.000000000 -0500 |--- execute_cmd.c 2022-11-02 16:32:12.000000000 -0400 -------------------------- Patching file execute_cmd.c using Plan A... Hunk #1 succeeded at 4015. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** /fs1/chet/scratch/bash-5.2.9/parse.y 2022-11-07 10:31:47.000000000 -0500 |--- parse.y 2022-11-14 11:27:22.000000000 -0500 -------------------------- Patching file parse.y using Plan A... Hunk #1 succeeded at 126. Hunk #2 succeeded at 3321. Hunk #3 succeeded at 4143. Hunk #4 succeeded at 4256. Hunk #5 succeeded at 4299. Hunk #6 succeeded at 4317. Hunk #7 succeeded at 4755. Hunk #8 succeeded at 4811. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** y.tab.c.save 2022-11-07 10:31:47.000000000 -0500 |--- y.tab.c 2022-11-18 15:58:03.000000000 -0500 -------------------------- Patching file y.tab.c using Plan A... Hunk #1 succeeded at 176. Hunk #2 succeeded at 5616. Hunk #3 succeeded at 6436. Hunk #4 succeeded at 6547. Hunk #5 succeeded at 6590. Hunk #6 succeeded at 6608. Hunk #7 succeeded at 7046. Hunk #8 succeeded at 7102. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** ../bash-5.2/patchlevel.h 2020-06-22 14:51:03.000000000 -0400 |--- patchlevel.h 2020-10-01 11:01:28.000000000 -0400 -------------------------- Patching file patchlevel.h using Plan A... Hunk #1 succeeded at 26. done => Applying distribution patch bash52-013 Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- | BASH PATCH REPORT | ================= | |Bash-Release: 5.2 |Patch-ID: bash52-013 | |Bug-Reported-by: Ralf Oehler |Bug-Reference-ID: <20221120140252.2fc6489b@bilbo> |Bug-Reference-URL: https://lists.gnu.org/archive/html/bug-bash/2022-11/msg00082.html | |Bug-Description: | |Bash can leak memory when referencing a non-existent associative array |element. | |Patch (apply with `patch -p0'): | |*** ../bash-5.2-patched/subst.c 2022-11-05 17:27:48.000000000 -0400 |--- subst.c 2022-11-21 14:42:59.000000000 -0500 -------------------------- Patching file subst.c using Plan A... Hunk #1 succeeded at 7508. Hunk #2 succeeded at 7516. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** ../bash-5.2/patchlevel.h 2020-06-22 14:51:03.000000000 -0400 |--- patchlevel.h 2020-10-01 11:01:28.000000000 -0400 -------------------------- Patching file patchlevel.h using Plan A... Hunk #1 succeeded at 26. done => Applying distribution patch bash52-014 Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- | BASH PATCH REPORT | ================= | |Bash-Release: 5.2 |Patch-ID: bash52-014 | |Bug-Reported-by: Andreas Schwab |Bug-Reference-ID: |Bug-Reference-URL: https://lists.gnu.org/archive/html/bug-bash/2022-10/msg00076.html | |Bug-Description: | |Bash defers processing additional terminating signals when running the |EXIT trap while exiting due to a terminating signal. This patch allows the |new terminating signal to kill the shell immediately. | |Patch (apply with `patch -p0'): | |*** ../bash-5.2-patched/execute_cmd.c 2022-11-23 17:09:18.000000000 -0500 |--- execute_cmd.c 2022-11-28 10:36:08.000000000 -0500 -------------------------- Patching file execute_cmd.c using Plan A... Hunk #1 succeeded at 3649. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** ../bash-5.2-patched/sig.c 2021-11-04 14:15:31.000000000 -0400 |--- sig.c 2022-12-06 09:45:11.000000000 -0500 -------------------------- Patching file sig.c using Plan A... Hunk #1 succeeded at 95. Hunk #2 succeeded at 495. Hunk #3 succeeded at 543. Hunk #4 succeeded at 585. Hunk #5 succeeded at 590. Hunk #6 succeeded at 631. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** ../bash-5.2/patchlevel.h 2020-06-22 14:51:03.000000000 -0400 |--- patchlevel.h 2020-10-01 11:01:28.000000000 -0400 -------------------------- Patching file patchlevel.h using Plan A... Hunk #1 succeeded at 26. done => Applying distribution patch bash52-015 Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- | BASH PATCH REPORT | ================= | |Bash-Release: 5.2 |Patch-ID: bash52-015 | |Bug-Reported-by: Frode Nordahl |Bug-Reference-ID: <20221119070714.351759-1-frode.nordahl@canonical.com> |Bug-Reference-URL: https://lists.gnu.org/archive/html/bug-bash/2022-11/msg00078.html | |Bug-Description: | |There are several cases where bash is too aggressive when optimizing out forks |in subshells. For example, `eval' and traps should never be optimized. | |Patch (apply with `patch -p0'): | |*** ../bash-5.2-patched/builtins/common.h 2022-11-23 17:09:18.000000000 -0500 |--- builtins/common.h 2022-11-19 18:03:59.000000000 -0500 -------------------------- Patching file builtins/common.h using Plan A... Hunk #1 succeeded at 52. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** ../bash-5.2-patched/builtins/evalstring.c 2022-11-05 17:27:44.000000000 -0400 |--- builtins/evalstring.c 2022-11-19 18:23:21.000000000 -0500 -------------------------- Patching file builtins/evalstring.c using Plan A... Hunk #1 succeeded at 133. Hunk #2 succeeded at 291. Hunk #3 succeeded at 504. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** ../bash-5.2-patched/builtins/eval.def 2016-01-25 13:28:37.000000000 -0500 |--- builtins/eval.def 2022-11-19 18:04:25.000000000 -0500 -------------------------- Patching file builtins/eval.def using Plan A... Hunk #1 succeeded at 54. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** ../bash-5.2-patched/trap.c 2022-08-10 08:59:45.000000000 -0400 |--- trap.c 2022-12-12 10:57:51.000000000 -0500 -------------------------- Patching file trap.c using Plan A... Hunk #1 succeeded at 305. Hunk #2 succeeded at 421. Hunk #3 succeeded at 446. Hunk #4 succeeded at 1008. Hunk #5 succeeded at 1115. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** ../bash-5.2-patched/parse.y 2022-11-23 17:09:18.000000000 -0500 |--- parse.y 2022-11-19 18:15:34.000000000 -0500 -------------------------- Patching file parse.y using Plan A... Hunk #1 succeeded at 2844. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** ../bash-5.2-patched/jobs.c 2022-07-18 10:19:56.000000000 -0400 |--- jobs.c 2022-11-19 18:10:24.000000000 -0500 -------------------------- Patching file jobs.c using Plan A... Hunk #1 succeeded at 4243. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** ../bash-5.2-patched/y.tab.c 2022-11-23 17:09:18.000000000 -0500 |--- y.tab.c 2022-11-23 17:21:17.000000000 -0500 -------------------------- Patching file y.tab.c using Plan A... Hunk #1 succeeded at 5154. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** ../bash-5.2-patched/execute_cmd.c 2022-11-05 17:27:41.000000000 -0400 |--- execute_cmd.c 2022-11-22 17:09:38.000000000 -0500 -------------------------- Patching file execute_cmd.c using Plan A... Hunk #1 succeeded at 1665. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** ../bash-5.2/patchlevel.h 2020-06-22 14:51:03.000000000 -0400 |--- patchlevel.h 2020-10-01 11:01:28.000000000 -0400 -------------------------- Patching file patchlevel.h using Plan A... Hunk #1 succeeded at 26. done => Applying distribution patch bash52-016 Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- | BASH PATCH REPORT | ================= | |Bash-Release: 5.2 |Patch-ID: bash52-016 | |Bug-Reported-by: F G |Bug-Reference-ID: |Bug-Reference-URL: | |Bug-Description: | |If an expression in an arithmetic for loop expands to NULL, the shell |would crash. | |Patch (apply with `patch -p0'): | |*** ../bash-5.2-patched/execute_cmd.c Thu Feb 23 14:15:05 2023 |--- execute_cmd.c Mon Feb 27 17:53:08 2023 -------------------------- Patching file execute_cmd.c using Plan A... Hunk #1 succeeded at 3051. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** ../bash-5.2/patchlevel.h 2020-06-22 14:51:03.000000000 -0400 |--- patchlevel.h 2020-10-01 11:01:28.000000000 -0400 -------------------------- Patching file patchlevel.h using Plan A... Hunk #1 succeeded at 26. done => Applying distribution patch bash52-017 Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- | BASH PATCH REPORT | ================= | |Bash-Release: 5.2 |Patch-ID: bash52-017 | |Bug-Reported-by: Dan Church |Bug-Reference-ID: <1a8fd1d6-a3ac-9a67-78eb-b9a7435304c8@gmx.com> |Bug-Reference-URL: https://lists.gnu.org/archive/html/bug-bash/2022-12/msg00076.html | |Bug-Description: | |In certain cases, using the `.' builtin in a subshell would optimize away |the rest of the commands in the subshell. | |Patch (apply with `patch -p0'): | |*** ../bash-5.2-patched/builtins/evalfile.c 2019-07-20 16:16:08.000000000 -0400 |--- builtins/evalfile.c 2022-12-22 12:13:08.000000000 -0500 -------------------------- Patching file builtins/evalfile.c using Plan A... Hunk #1 succeeded at 267. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** ../bash-5.2/patchlevel.h 2020-06-22 14:51:03.000000000 -0400 |--- patchlevel.h 2020-10-01 11:01:28.000000000 -0400 -------------------------- Patching file patchlevel.h using Plan A... Hunk #1 succeeded at 26. done => Applying distribution patch bash52-018 Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- | BASH PATCH REPORT | ================= | |Bash-Release: 5.2 |Patch-ID: bash52-018 | |Bug-Reported-by: Todd Stein | Eduardo A . Bustamante López |Bug-Reference-ID: | |Bug-Reference-URL: https://savannah.gnu.org/support/?110745 | https://lists.gnu.org/archive/html/bug-bash/2023-02/msg00141.html | |Bug-Description: | |There are two problems with returning tokens to yyparse() when the shell |encounters a syntax error or when it reads EOF. | |When reading a WORD token, the parser has to return the correct value to |yyparse. Previous versions returned a value < 0, which the bash parser |translated into YYERRCODE for bison, and in newer versions of bison, the |appropriate reset actions didn't happen. We should return YYUNDEF, which |bison uses for `invalid token'. Since we can return a token < 0 for both |invalid tokens and EOF, the bash tokenizer needs to differentiate between |those two cases. | |Patch (apply with `patch -p0'): | |*** ../bash-5.2-patched/parse.y 2022-12-13 12:09:02.000000000 -0500 |--- parse.y 2023-11-08 14:29:13.000000000 -0500 -------------------------- Patching file parse.y using Plan A... Hunk #1 succeeded at 453. Hunk #2 succeeded at 2913. Hunk #3 succeeded at 3711. Hunk #4 succeeded at 4172. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- | |*** /Users/chet/src/bash/bash-5.2-patched/y.tab.c 2022-12-13 12:09:02.000000000 -0500 |--- y.tab.c 2023-11-08 14:38:01.000000000 -0500 -------------------------- Patching file y.tab.c using Plan A... Hunk #1 succeeded at 993. Hunk #2 succeeded at 1002. Hunk #3 succeeded at 1058. Hunk #4 succeeded at 1120. Hunk #5 succeeded at 1134. Hunk #6 succeeded at 1176. Hunk #7 succeeded at 1216. Hunk #8 succeeded at 1225. Hunk #9 succeeded at 1236. Hunk #10 succeeded at 1401. Hunk #11 succeeded at 1436. Hunk #12 succeeded at 1459. Hunk #13 succeeded at 2019. Hunk #14 succeeded at 2047. Hunk #15 succeeded at 2069. Hunk #16 succeeded at 2079. Hunk #17 succeeded at 2089. Hunk #18 succeeded at 2099. Hunk #19 succeeded at 2109. Hunk #20 succeeded at 2119. Hunk #21 succeeded at 2129. Hunk #22 succeeded at 2139. Hunk #23 succeeded at 2149. Hunk #24 succeeded at 2159. Hunk #25 succeeded at 2169. Hunk #26 succeeded at 2179. Hunk #27 succeeded at 2189. Hunk #28 succeeded at 2199. Hunk #29 succeeded at 2209. Hunk #30 succeeded at 2220. Hunk #31 succeeded at 2231. Hunk #32 succeeded at 2242. Hunk #33 succeeded at 2253. Hunk #34 succeeded at 2264. Hunk #35 succeeded at 2275. Hunk #36 succeeded at 2285. Hunk #37 succeeded at 2295. Hunk #38 succeeded at 2305. Hunk #39 succeeded at 2315. Hunk #40 succeeded at 2325. Hunk #41 succeeded at 2335. Hunk #42 succeeded at 2345. Hunk #43 succeeded at 2355. Hunk #44 succeeded at 2365. Hunk #45 succeeded at 2375. Hunk #46 succeeded at 2385. Hunk #47 succeeded at 2395. Hunk #48 succeeded at 2405. Hunk #49 succeeded at 2415. Hunk #50 succeeded at 2425. Hunk #51 succeeded at 2435. Hunk #52 succeeded at 2445. Hunk #53 succeeded at 2455. Hunk #54 succeeded at 2465. Hunk #55 succeeded at 2475. Hunk #56 succeeded at 2485. Hunk #57 succeeded at 2495. Hunk #58 succeeded at 2505. Hunk #59 succeeded at 2544. Hunk #60 succeeded at 2588. Hunk #61 succeeded at 2748. Hunk #62 succeeded at 2758. Hunk #63 succeeded at 2768. Hunk #64 succeeded at 2778. Hunk #65 succeeded at 2940. Hunk #66 succeeded at 2995. Hunk #67 succeeded at 3025. Hunk #68 succeeded at 3176. Hunk #69 succeeded at 3195. Hunk #70 succeeded at 3218. Hunk #71 succeeded at 3235. Hunk #72 succeeded at 3278. Hunk #73 succeeded at 3300. Hunk #74 succeeded at 3319. Hunk #75 succeeded at 3342. Hunk #76 succeeded at 3370. Hunk #77 succeeded at 3380. Hunk #78 succeeded at 3404. Hunk #79 succeeded at 3429. Hunk #80 succeeded at 3462. Hunk #81 succeeded at 3689. Hunk #82 succeeded at 5228. Hunk #83 succeeded at 6026. Hunk #84 succeeded at 6487. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- | |*** ../bash-5.2/patchlevel.h 2020-06-22 14:51:03.000000000 -0400 |--- patchlevel.h 2020-10-01 11:01:28.000000000 -0400 -------------------------- Patching file patchlevel.h using Plan A... Hunk #1 succeeded at 26. done => Applying distribution patch bash52-019 Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- | BASH PATCH REPORT | ================= | |Bash-Release: 5.2 |Patch-ID: bash52-019 | |Bug-Reported-by: Steffen Nurpmeso |Bug-Reference-ID: <20230116233547.2jFxL%steffen@sdaoden.eu> |Bug-Reference-URL: https://lists.gnu.org/archive/html/bug-bash/2023-01/msg00057.html | |Bug-Description: | |There are some cases where the shell reaped a background (asynchronous) job |and would incorrectly try to set the terminal's process group back to the |shell's. In these cases it never set the terminal process group to that |jobs's process group initially, so resetting it is incorrect. | |Patch (apply with `patch -p0'): | |*** ../bash-5.2-patched/jobs.c 2022-12-13 12:09:02.000000000 -0500 |--- jobs.c 2023-10-26 12:12:10.000000000 -0400 -------------------------- Patching file jobs.c using Plan A... Hunk #1 succeeded at 3036. Hunk #2 succeeded at 3599. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- | |*** ../bash-5.2/patchlevel.h 2020-06-22 14:51:03.000000000 -0400 |--- patchlevel.h 2020-10-01 11:01:28.000000000 -0400 -------------------------- Patching file patchlevel.h using Plan A... Hunk #1 succeeded at 26. done => Applying distribution patch bash52-020 Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- | BASH PATCH REPORT | ================= | |Bash-Release: 5.2 |Patch-ID: bash52-020 | |Bug-Reported-by: Dima Korobskiy |Bug-Reference-ID: <16664c2d-40ec-df33-b932-83db06e39a82@gmail.com> |Bug-Reference-URL: https://lists.gnu.org/archive/html/bug-bash/2023-08/msg00125.html | |Bug-Description: | |The parser did not allow `time' to appear as the first reserved word in a |command substitution. | |Patch (apply with `patch -p0'): | |*** ../bash-5.2-patched/parse.y Tue Dec 13 12:53:21 2022 |--- parse.y Fri Sep 1 10:36:28 2023 -------------------------- Patching file parse.y using Plan A... Hunk #1 succeeded at 3151. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** ../bash-5.2-patched/y.tab.c Tue Dec 13 12:53:21 2022 |--- y.tab.c Fri Sep 1 10:36:44 2023 -------------------------- Patching file y.tab.c using Plan A... Hunk #1 succeeded at 5466. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- | |*** ../bash-5.2/patchlevel.h 2020-06-22 14:51:03.000000000 -0400 |--- patchlevel.h 2020-10-01 11:01:28.000000000 -0400 -------------------------- Patching file patchlevel.h using Plan A... Hunk #1 succeeded at 26. done => Applying distribution patch bash52-021 Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- | BASH PATCH REPORT | ================= | |Bash-Release: 5.2 |Patch-ID: bash52-021 | |Bug-Reported-by: Norbert Lange |Bug-Reference-ID: |Bug-Reference-URL: https://lists.gnu.org/archive/html/bug-bash/2022-12/msg00046.html | |Bug-Description: | |There is an off-by-one error that causes command substitutions to fail when |they appear in a word expansion inside a here-document. | |Patch (apply with `patch -p0'): | |*** ../bash-5.2-patched/subst.c 2022-12-13 12:08:58.000000000 -0500 |--- subst.c 2022-12-14 09:09:53.000000000 -0500 -------------------------- Patching file subst.c using Plan A... Hunk #1 succeeded at 1699. Hunk #2 succeeded at 1719. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- | |*** ../bash-5.2/patchlevel.h 2020-06-22 14:51:03.000000000 -0400 |--- patchlevel.h 2020-10-01 11:01:28.000000000 -0400 -------------------------- Patching file patchlevel.h using Plan A... Hunk #1 succeeded at 26. done => Applying distribution patch bash52-022 Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- | BASH PATCH REPORT | ================= | |Bash-Release: 5.2 |Patch-ID: bash52-022 | |Bug-Reported-by: srobertson@peratonlabs.com |Bug-Reference-ID: |Bug-Reference-URL: https://lists.gnu.org/archive/html/bug-bash/2022-09/msg00049.html | |Bug-Description: | |It's possible for readline to try to zero out a line that's not null- |terminated, leading to a memory fault. | |Patch (apply with `patch -p0'): | |*** ../bash-5.2-patched/lib/readline/display.c 2022-04-05 10:47:31.000000000 -0400 |--- lib/readline/display.c 2022-12-13 13:11:22.000000000 -0500 -------------------------- Patching file lib/readline/display.c using Plan A... Hunk #1 succeeded at 2735. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- | |*** ../bash-5.2/patchlevel.h 2020-06-22 14:51:03.000000000 -0400 |--- patchlevel.h 2020-10-01 11:01:28.000000000 -0400 -------------------------- Patching file patchlevel.h using Plan A... Hunk #1 succeeded at 26. done => Applying distribution patch bash52-023 Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- | BASH PATCH REPORT | ================= | |Bash-Release: 5.2 |Patch-ID: bash52-023 | |Bug-Reported-by: Emanuele Torre |Bug-Reference-ID: <20230206140824.1710288-1-torreemanuele6@gmail.com> |Bug-Reference-URL: https://lists.gnu.org/archive/html/bug-bash/2023-02/msg00045.html | |Bug-Description: | |Running `local -' multiple times in a shell function would overwrite the |original saved set of options. | |Patch (apply with `patch -p0'): | |*** ../bash-5.2-patched/builtins/declare.def 2023-01-04 20:40:28.000000000 -0500 |--- builtins/declare.def 2023-02-08 15:36:49.000000000 -0500 -------------------------- Patching file builtins/declare.def using Plan A... Hunk #1 succeeded at 421. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- | |*** ../bash-5.2/patchlevel.h 2020-06-22 14:51:03.000000000 -0400 |--- patchlevel.h 2020-10-01 11:01:28.000000000 -0400 -------------------------- Patching file patchlevel.h using Plan A... Hunk #1 succeeded at 26. done => Applying distribution patch bash52-024 Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- | BASH PATCH REPORT | ================= | |Bash-Release: 5.2 |Patch-ID: bash52-024 | |Bug-Reported-by: Marco |Bug-Reference-ID: |Bug-Reference-URL: https://lists.gnu.org/archive/html/bug-bash/2023-02/msg00044.html | |Bug-Description: | |Fix bug where associative array compound assignment would not expand tildes |in values. | |Patch (apply with `patch -p0'): | |*** ../bash-20230105/arrayfunc.c Thu Jan 5 14:23:28 2023 |--- arrayfunc.c Wed Feb 8 16:27:48 2023 -------------------------- Patching file arrayfunc.c using Plan A... Hunk #1 succeeded at 651. Hunk #2 succeeded at 843. Hunk #3 succeeded at 1031. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** ../bash-20230201/subst.c Mon Jan 30 16:19:46 2023 |--- subst.c Mon Feb 6 16:25:22 2023 -------------------------- Patching file subst.c using Plan A... Hunk #1 succeeded at 10803. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- | |*** ../bash-5.2/patchlevel.h 2020-06-22 14:51:03.000000000 -0400 |--- patchlevel.h 2020-10-01 11:01:28.000000000 -0400 -------------------------- Patching file patchlevel.h using Plan A... Hunk #1 succeeded at 26. done => Applying distribution patch bash52-025 Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- | BASH PATCH REPORT | ================= | |Bash-Release: 5.2 |Patch-ID: bash52-025 | |Bug-Reported-by: Andrew Neff |Bug-Reference-ID: |Bug-Reference-URL: https://lists.gnu.org/archive/html/bug-bash/2022-10/msg00100.html | |Bug-Description: | |Make sure a subshell checks for and handles any terminating signals before |exiting (which might have arrived after the command completed) so the parent |and any EXIT trap will see the correct value for $?. | |Patch (apply with `patch -p0'): | |*** ../bash-5.2.9/execute_cmd.c 2022-11-02 10:36:54.000000000 -0400 |--- execute_cmd.c 2022-10-27 16:52:55.000000000 -0400 -------------------------- Patching file execute_cmd.c using Plan A... Hunk #1 succeeded at 1726. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- | |*** ../bash-5.2/patchlevel.h 2020-06-22 14:51:03.000000000 -0400 |--- patchlevel.h 2020-10-01 11:01:28.000000000 -0400 -------------------------- Patching file patchlevel.h using Plan A... Hunk #1 succeeded at 26. done => Applying distribution patch bash52-026 Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- | BASH PATCH REPORT | ================= | |Bash-Release: 5.2 |Patch-ID: bash52-026 | |Bug-Reported-by: Stefan Klinger |Bug-Reference-ID: |Bug-Reference-URL: https://lists.gnu.org/archive/html/bug-readline/2023-08/msg00018.html | |Bug-Description: | |The custom color prefix that readline uses to color possible completions |must have a leading `.'. | |Patch (apply with `patch -p0'): | |*** ../bash-5.2-patched/lib/readline/colors.c 2021-12-08 11:38:25.000000000 -0500 |--- lib/readline/colors.c 2023-08-28 16:40:04.000000000 -0400 -------------------------- Patching file lib/readline/colors.c using Plan A... Hunk #1 succeeded at 74. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- | |*** ../bash-5.2/patchlevel.h 2020-06-22 14:51:03.000000000 -0400 |--- patchlevel.h 2020-10-01 11:01:28.000000000 -0400 -------------------------- Patching file patchlevel.h using Plan A... Hunk #1 succeeded at 26. done => Applying distribution patch bash52-027 Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- | BASH PATCH REPORT | ================= | |Bash-Release: 5.2 |Patch-ID: bash52-027 | |Bug-Reported-by: Emanuel Haupt |Bug-Reference-ID: <20221001123841.27e1bfb3bf3ed58ab32ea2b5@FreeBSD.org> |Bug-Reference-URL: https://lists.gnu.org/archive/html/bug-bash/2022-10/msg00000.html | |Bug-Description: | |The configure test for the presence of strtoimax(3) is inverted. | |Patch (apply with `patch -p0'): | | |*** ../bash-5.2-patched/m4/strtoimax.m4 Mon Apr 11 16:31:52 2022 |--- m4/strtoimax.m4 Tue Apr 9 11:12:36 2024 -------------------------- Patching file m4/strtoimax.m4 using Plan A... Hunk #1 succeeded at 30. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** ..//bash-5.2-patched/configure Fri Sep 23 10:13:22 2022 |--- configure Tue Apr 9 11:13:21 2024 -------------------------- Patching file configure using Plan A... Hunk #1 succeeded at 20444. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- | |*** ../bash-5.2/patchlevel.h 2020-06-22 14:51:03.000000000 -0400 |--- patchlevel.h 2020-10-01 11:01:28.000000000 -0400 -------------------------- Patching file patchlevel.h using Plan A... Hunk #1 succeeded at 26. done => Applying distribution patch bash52-028 Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- | BASH PATCH REPORT | ================= | |Bash-Release: 5.2 |Patch-ID: bash52-028 | |Bug-Reported-by: Mark March |Bug-Reference-ID: <834896722.6304071.1718744118467@mail.yahoo.com> |Bug-Reference-URL: https://lists.gnu.org/archive/html/bug-bash/2024-06/msg00122.html | |Bug-Description: | |A DEBUG trap in an asynchronous process can steal the controlling terminal |away from the calling shell, causing it to exit. | |Patch (apply with `patch -p0'): | |*** ../bash-20240609/trap.c Fri May 3 12:12:38 2024 |--- trap.c Wed Jun 26 10:41:40 2024 -------------------------- Patching file trap.c using Plan A... Hunk #1 succeeded at 1217. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** ../bash-5.2/patchlevel.h 2020-06-22 14:51:03.000000000 -0400 |--- patchlevel.h 2020-10-01 11:01:28.000000000 -0400 -------------------------- Patching file patchlevel.h using Plan A... Hunk #1 succeeded at 26. done => Applying distribution patch bash52-029 Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- | BASH PATCH REPORT | ================= | |Bash-Release: 5.2 |Patch-ID: bash52-029 | |Bug-Reported-by: Grisha Levit |Bug-Reference-ID: |Bug-Reference-URL: https://lists.gnu.org/archive/html/bug-bash/2023-04/msg00072.html | |Bug-Description: | |There are problems with recovery after parser errors when parsing compound |assignments. For instance, the `local' builtin reports an error but never |cleans up the function context. | |Patch (apply with `patch -p0'): | |*** ../bash-20230427/parse.y Fri Apr 14 11:50:29 2023 |--- parse.y Mon May 1 16:25:14 2023 -------------------------- Patching file parse.y using Plan A... Hunk #1 succeeded at 6471. Hunk #2 succeeded at 6543. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- | |*** ../bash-20230427/y.tab.c Tue Jul 30 15:19:31 2024 |--- y.tab.c Tue Jul 30 15:20:21 2024 -------------------------- Patching file y.tab.c using Plan A... Hunk #1 succeeded at 8786. Hunk #2 succeeded at 8858. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- | |*** ../bash-5.2/patchlevel.h 2020-06-22 14:51:03.000000000 -0400 |--- patchlevel.h 2020-10-01 11:01:28.000000000 -0400 -------------------------- Patching file patchlevel.h using Plan A... Hunk #1 succeeded at 26. done => Applying distribution patch bash52-030 Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- | BASH PATCH REPORT | ================= | |Bash-Release: 5.2 |Patch-ID: bash52-030 | |Bug-Reported-by: Steven Pelley |Bug-Reference-ID: |Bug-Reference-URL: https://lists.gnu.org/archive/html/bug-bash/2024-01/msg00104.html | |Bug-Description: | |`wait -n' can fail to return some jobs if they exit due to signals the shell |does not report to the user. | |Patch (apply with `patch -p0'): | |*** ../bash-5.2-patched/jobs.c Thu Nov 9 14:59:14 2023 |--- jobs.c Tue Jul 30 15:27:44 2024 -------------------------- Patching file jobs.c using Plan A... Hunk #1 succeeded at 4288. Hunk #2 succeeded at 4331. Hunk #3 succeeded at 4351. Hunk #4 succeeded at 4365. Hunk #5 succeeded at 4380. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- | |*** ../bash-5.2/patchlevel.h 2020-06-22 14:51:03.000000000 -0400 |--- patchlevel.h 2020-10-01 11:01:28.000000000 -0400 -------------------------- Patching file patchlevel.h using Plan A... Hunk #1 succeeded at 26. done => Applying distribution patch bash52-031 Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- | BASH PATCH REPORT | ================= | |Bash-Release: 5.2 |Patch-ID: bash52-031 | |Bug-Reported-by: Grisha Levit |Bug-Reference-ID: |Bug-Reference-URL: https://lists.gnu.org/archive/html/bug-bash/2023-06/msg00045.html | |Bug-Description: | |There is a memory leak in the code that implements the optimized $( Applying distribution patch bash52-032 Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- | BASH PATCH REPORT | ================= | |Bash-Release: 5.2 |Patch-ID: bash52-032 | |Bug-Reported-by: Albert Akchurin |Bug-Reference-ID: Mon, 11 Dec 2023 20:41:58 +0600 |Bug-Reference-URL: https://lists.gnu.org/archive/html/bug-bash/2023-12/msg00047.html | |Bug-Description: | |Patch (apply with `patch -p0'): | |When printing functions containing coprocesses, the displayed coproc command |has the word COPROC inserted unconditionally, resulting in function bodies |that cannot be re-read as input. | |*** ../bash-5.2-patched/print_cmd.c Mon Aug 21 16:09:44 2023 |--- print_cmd.c Mon Dec 11 15:34:30 2023 -------------------------- Patching file print_cmd.c using Plan A... Hunk #1 succeeded at 357. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- | |*** ../bash-5.2/patchlevel.h 2020-06-22 14:51:03.000000000 -0400 |--- patchlevel.h 2020-10-01 11:01:28.000000000 -0400 -------------------------- Patching file patchlevel.h using Plan A... Hunk #1 succeeded at 26. done => Applying distribution patch bash52-033 Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- | BASH PATCH REPORT | ================= | |Bash-Release: 5.2 |Patch-ID: bash52-033 | |Bug-Reported-by: Florian Weimer |Bug-Reference-ID: <87leasmvoo.fsf@oldenburg.str.redhat.com> |Bug-Reference-URL: https://lists.gnu.org/archive/html/bug-bash/2023-11/msg00104.html | |Bug-Description: | |A typo in the autoconf test for strtold causes false negatives for strtold |being available and working when compiled with gcc-14. | |Patch (apply with `patch -p0'): | |*** ../bash-5.2-patched/configure.ac Fri Aug 11 14:52:31 2023 |--- configure.ac Tue Nov 21 12:00:25 2023 -------------------------- Patching file configure.ac using Plan A... Hunk #1 succeeded at 887 (offset -13 lines). Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- | |*** ../bash-5.2-patched/configure Fri Aug 18 16:27:53 2023 |--- configure Tue Nov 21 12:00:30 2023 -------------------------- Patching file configure using Plan A... Hunk #1 succeeded at 15686 (offset -246 lines). Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- | |*** ../bash-5.2-patched/builtins/printf.def Fri Jun 24 10:09:50 2022 |--- builtins/printf.def Tue Aug 13 10:36:55 2024 -------------------------- Patching file builtins/printf.def using Plan A... Hunk #1 succeeded at 710. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- | |*** ../bash-5.2/patchlevel.h 2020-06-22 14:51:03.000000000 -0400 |--- patchlevel.h 2020-10-01 11:01:28.000000000 -0400 -------------------------- Patching file patchlevel.h using Plan A... Hunk #1 succeeded at 26. done => Applying distribution patch bash52-034 Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- | BASH PATCH REPORT | ================= | |Bash-Release: 5.2 |Patch-ID: bash52-034 | |Bug-Reported-by: Wiley Young |Bug-Reference-ID: |Bug-Reference-URL: https://lists.gnu.org/archive/html/bug-bash/2023-05/msg00146.html | |Bug-Description: | |If we parse a compound assignment during an alias expansion, it's possible |to have the current input string popped out from underneath the parse. In |this case, we should not restore the input we were using when we began to |parse the compound assignment. | |Patch (apply with `patch -p0'): | |*** ../bash-5.2-patched/parse.y Fri May 26 16:57:03 2023 |--- parse.y Thu Jun 1 16:30:19 2023 -------------------------- Patching file parse.y using Plan A... Hunk #1 succeeded at 6494 (offset -364 lines). Hunk #2 succeeded at 6520 (offset -364 lines). Hunk #3 succeeded at 6549 (offset -364 lines). Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** ../bash-5.2-patched/y.tab.c Mon Sep 23 10:02:46 2024 |--- y.tab.c Mon Sep 23 10:02:49 2024 -------------------------- Patching file y.tab.c using Plan A... Hunk #1 succeeded at 8804. Hunk #2 succeeded at 8830. Hunk #3 succeeded at 8859. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- | |*** ../bash-5.2/patchlevel.h 2020-06-22 14:51:03.000000000 -0400 |--- patchlevel.h 2020-10-01 11:01:28.000000000 -0400 -------------------------- Patching file patchlevel.h using Plan A... Hunk #1 succeeded at 26. done => Applying distribution patch bash52-035 Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- | BASH PATCH REPORT | ================= | |Bash-Release: 5.2 |Patch-ID: bash52-035 | |Bug-Reported-by: Henry Bent |Bug-Reference-ID: |Bug-Reference-URL: https://lists.gnu.org/archive/html/bug-bash/2022-11/msg00044.html | |Bug-Description: | |There are systems that supply one of select or pselect, but not both. | |Patch (apply with `patch -p0'): | |https://lists.gnu.org/archive/html/bug-bash/2022-11/msg00058.html | |*** ../bash/bash-5.2-patched/lib/readline/input.c 2022-04-08 15:43:24.000000000 -0400 |--- lib/readline/input.c 2022-11-16 09:10:41.000000000 -0500 -------------------------- Patching file lib/readline/input.c using Plan A... Hunk #1 succeeded at 152. Hunk #2 succeeded at 251. Hunk #3 succeeded at 808. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** ../bash-5.2-patched/lib/sh/input_avail.c 2021-05-24 11:16:33.000000000 -0400 |--- lib/sh/input_avail.c 2022-11-16 09:12:48.000000000 -0500 -------------------------- Patching file lib/sh/input_avail.c using Plan A... Hunk #1 succeeded at 34. Hunk #2 succeeded at 106. Hunk #3 succeeded at 115. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- | |*** ../bash-5.2/patchlevel.h 2020-06-22 14:51:03.000000000 -0400 |--- patchlevel.h 2020-10-01 11:01:28.000000000 -0400 -------------------------- Patching file patchlevel.h using Plan A... Hunk #1 succeeded at 26. done => Applying distribution patch bash52-036 Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- | BASH PATCH REPORT | ================= | |Bash-Release: 5.2 |Patch-ID: bash52-036 | |Bug-Reported-by: Grisha Levit |Bug-Reference-ID: |Bug-Reference-URL: https://lists.gnu.org/archive/html/bug-bash/2023-04/msg00082.html | |Bug-Description: | |When readline is accumulating bytes until it reads a complete multibyte |character, reading a byte that makes the multibyte character invalid can |result in discarding the bytes in the partial character. | |Patch (apply with `patch -p0'): | |*** ../bash-5.2-patched/lib/readline/text.c Mon May 1 09:37:52 2023 |--- lib/readline/text.c Mon May 29 12:22:29 2023 -------------------------- Patching file lib/readline/text.c using Plan A... Hunk #1 succeeded at 86. Hunk #2 succeeded at 706. Hunk #3 succeeded at 724. Hunk #4 succeeded at 753. Hunk #5 succeeded at 790. Hunk #6 succeeded at 854. Hunk #7 succeeded at 891. Hunk #8 succeeded at 906. Hunk #9 succeeded at 936. Hunk #10 succeeded at 1018. Hunk #11 succeeded at 1094. Hunk #12 succeeded at 1114. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** ../bash-5.2/patchlevel.h 2020-06-22 14:51:03.000000000 -0400 |--- patchlevel.h 2020-10-01 11:01:28.000000000 -0400 -------------------------- Patching file patchlevel.h using Plan A... Hunk #1 succeeded at 26. done => Applying distribution patch bash52-037 Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- | BASH PATCH REPORT | ================= | |Bash-Release: 5.2 |Patch-ID: bash52-037 | |Bug-Reported-by: Martin Castillo |Bug-Reference-ID: <2d42153b-cf65-caba-dff1-cd3bc6268c7e@uni-bremen.de> |Bug-Reference-URL: https://lists.gnu.org/archive/html/bug-readline/2023-01/msg00000.html | |Bug-Description: | |Fix the case where text to be completed from the line buffer (quoted) is |compared to the common prefix of the possible matches (unquoted) and the |quoting makes the former appear to be longer than the latter. Readline |assumes the match doesn't add any characters to the word and doesn't display |multiple matches. | |Patch (apply with `patch -p0'): | |*** ../bash-5.2-patched/lib/readline/complete.c Tue Apr 5 10:47:06 2022 |--- lib/readline/complete.c Sat Jan 7 14:19:45 2023 -------------------------- Patching file lib/readline/complete.c using Plan A... Hunk #1 succeeded at 2038. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- | |*** ../bash-5.2/patchlevel.h 2020-06-22 14:51:03.000000000 -0400 |--- patchlevel.h 2020-10-01 11:01:28.000000000 -0400 -------------------------- Patching file patchlevel.h using Plan A... Hunk #1 succeeded at 26. done => Applying pkgsrc patches for bash-5.2.37 => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/shells/bash/patches/patch-Makefile.in => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/shells/bash/patches/patch-Makefile.in Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-Makefile.in,v 1.2 2025/03/30 21:16:22 wiz Exp $ | |This patch fixes the build on OpenBSD, where LIBINTL and |LIBICONV are incorrectly set. | |--- Makefile.in.orig 2014-01-25 21:27:30.000000000 +0000 |+++ Makefile.in -------------------------- Patching file Makefile.in using Plan A... Hunk #1 succeeded at 372 (offset 19 lines). Hunk #2 succeeded at 380 (offset 19 lines). done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/shells/bash/patches/patch-builtins_printf.def => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/shells/bash/patches/patch-builtins_printf.def Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-builtins_printf.def,v 1.1 2022/11/25 23:29:47 adam Exp $ | |Fixes PRIdMAX and PRIuMAX on AIX < 5.1. | |--- builtins/printf.def.orig 2014-01-03 15:35:33.000000000 +0000 |+++ builtins/printf.def -------------------------- Patching file builtins/printf.def using Plan A... Hunk #1 succeeded at 97 (offset 2 lines). Hunk #2 succeeded at 109 (offset 2 lines). Hunk #3 succeeded at 663 (offset 57 lines). Hunk #4 succeeded at 639 (offset 2 lines). done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/shells/bash/patches/patch-builtins_psize.c => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/shells/bash/patches/patch-builtins_psize.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-builtins_psize.c,v 1.1 2022/11/25 23:29:47 adam Exp $ | |Use the definition of errno from . | |--- builtins/psize.c.orig 2008-08-14 19:56:53.000000000 +0000 |+++ builtins/psize.c -------------------------- Patching file builtins/psize.c using Plan A... Hunk #1 succeeded at 41. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/shells/bash/patches/patch-builtins_ulimit.def => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/shells/bash/patches/patch-builtins_ulimit.def Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-builtins_ulimit.def,v 1.3 2016/06/11 12:54:24 rillig Exp $ | |Add support for the "number of threads" ulimit that appeared |in NetBSD 6.99.x. | |--- builtins/ulimit.def.orig 2013-11-01 01:46:06.000000000 +0000 |+++ builtins/ulimit.def -------------------------- Patching file builtins/ulimit.def using Plan A... Hunk #1 succeeded at 152 (offset 9 lines). done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/shells/bash/patches/patch-configure => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/shells/bash/patches/patch-configure Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-configure,v 1.2 2015/03/07 22:40:48 rodent Exp $ | |Use -Wl,-R instead of just -R to avoid breaking the build on FreeBSD. |From Dennis Lindroos in PR 49375. | |--- configure.orig 2014-02-11 15:38:00.000000000 +0000 |+++ configure -------------------------- Patching file configure using Plan A... Hunk #1 succeeded at 11021 (offset 2974 lines). Hunk #2 succeeded at 10790 (offset 1953 lines). done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/shells/bash/patches/patch-examples_loadables_Makefile.in => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/shells/bash/patches/patch-examples_loadables_Makefile.in Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-examples_loadables_Makefile.in,v 1.1 2022/11/25 23:29:47 adam Exp $ | |Correctly install shared objects (e.g. unstripped on some platforms). | |--- examples/loadables/Makefile.in.orig 2022-11-25 23:21:05.000000000 +0000 |+++ examples/loadables/Makefile.in -------------------------- Patching file examples/loadables/Makefile.in using Plan A... Hunk #1 succeeded at 281. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/shells/bash/patches/patch-examples_loadables_getconf.c => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/shells/bash/patches/patch-examples_loadables_getconf.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-examples_loadables_getconf.c,v 1.4 2024/03/16 12:24:36 nia Exp $ | |Handle _SC_RTSIG_MAX not being defined (NetBSD 9) as well as other missing |definitions (_SC_REALTIME_SIGNALS, _SC_TIMER_MAX, _SC_CPUTIME, |_SC_THREAD_CPUTIME, SC_DELAYTIMER_MAX, _SC_SIGQUEUE_MAX) on earlier OS |versions. | |--- examples/loadables/getconf.c.orig 2021-12-03 16:46:22.000000000 +0000 |+++ examples/loadables/getconf.c -------------------------- Patching file examples/loadables/getconf.c using Plan A... Hunk #1 succeeded at 269. Hunk #2 succeeded at 335. Hunk #3 succeeded at 374. Hunk #4 succeeded at 753. Hunk #5 succeeded at 840. Hunk #6 succeeded at 862. Hunk #7 succeeded at 892. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/shells/bash/patches/patch-lib_malloc_malloc.c => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/shells/bash/patches/patch-lib_malloc_malloc.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-lib_malloc_malloc.c,v 1.3 2022/10/03 12:50:27 wiz Exp $ | |Fix array subscript with char index. | |https://lists.gnu.org/archive/html/bug-bash/2020-03/msg00056.html | |--- lib/malloc/malloc.c.orig 2022-04-18 16:37:56.000000000 +0000 |+++ lib/malloc/malloc.c -------------------------- Patching file lib/malloc/malloc.c using Plan A... Hunk #1 succeeded at 299. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/shells/bash/patches/patch-support_shobj-conf => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/shells/bash/patches/patch-support_shobj-conf Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-support_shobj-conf,v 1.3 2022/10/03 12:50:27 wiz Exp $ | |Spell -fPIC correctly. | |--- support/shobj-conf.orig 2019-12-13 14:51:17.000000000 +0000 |+++ support/shobj-conf -------------------------- Patching file support/shobj-conf using Plan A... Hunk #1 succeeded at 114. done ===> Creating toolchain wrappers for bash-5.2.37 ===> Configuring for bash-5.2.37 /usr/bin/rm -f /home/pbulk/build/shells/bash/work/bash-5.2/y.tab.c => Modifying GNU configure scripts to avoid --recheck => Replacing config-guess with pkgsrc versions => Replacing config-sub with pkgsrc versions => Replacing install-sh with pkgsrc version => Adding run-time search paths to pkg-config files. INFO: [subst.mk:_pkgconfig] Nothing changed in "support/bash.pc.in". => Fixing locale directory references. INFO: [subst.mk:pkglocaledir] Nothing changed in "doc/Makefile.in". INFO: [subst.mk:pkglocaledir] Nothing changed in "examples/loadables/Makefile.in". INFO: [subst.mk:pkglocaledir] Nothing changed in "examples/loadables/Makefile.inc.in". INFO: [subst.mk:pkglocaledir] Nothing changed in "examples/loadables/perl/Makefile.in". INFO: [subst.mk:pkglocaledir] Nothing changed in "lib/glob/Makefile.in". INFO: [subst.mk:pkglocaledir] Nothing changed in "lib/malloc/Makefile.in". INFO: [subst.mk:pkglocaledir] Nothing changed in "lib/readline/Makefile.in". INFO: [subst.mk:pkglocaledir] Nothing changed in "lib/sh/Makefile.in". INFO: [subst.mk:pkglocaledir] Nothing changed in "lib/termcap/Makefile.in". INFO: [subst.mk:pkglocaledir] Nothing changed in "lib/tilde/Makefile.in". INFO: [subst.mk:pkglocaledir] Nothing changed in "support/Makefile.in". => Checking for portability problems in extracted files WARNING: [check-portability] => Found $RANDOM: WARNING: [check-portability] tests/run-all:21: SUFFIX=`${THIS_SH} -c 'echo $(( $RANDOM + $BASHPID ))'` Explanation: =========================================================================== The variable $RANDOM is not required for a POSIX-conforming shell, and many implementations of /bin/sh do not support it. It should therefore not be used in shell programs that are meant to be portable across a large number of POSIX-like systems. =========================================================================== WARNING: [check-portability] => Found $RANDOM: WARNING: [check-portability] tests/run-minimal:25: SUFFIX=`${THIS_SH} -c 'echo $(( $RANDOM + $BASHPID ))'` Explanation: =========================================================================== The variable $RANDOM is not required for a POSIX-conforming shell, and many implementations of /bin/sh do not support it. It should therefore not be used in shell programs that are meant to be portable across a large number of POSIX-like systems. =========================================================================== checking build system type... x86_64-sun-solaris2.11 checking host system type... x86_64-sun-solaris2.11 Beginning configuration for bash-5.2-release for x86_64-sun-solaris2.11 checking for x86_64-sun-solaris2.11-gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether the compiler supports GNU C... yes checking whether gcc accepts -g... yes checking for gcc option to enable C11 features... none needed checking for stdio.h... yes checking for stdlib.h... yes checking for string.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for strings.h... yes checking for sys/stat.h... yes checking for sys/types.h... yes checking for unistd.h... yes checking for wchar.h... yes checking for minix/config.h... no checking for sys/param.h... yes checking for xlocale.h... yes checking for sys/time.h... yes checking whether it is safe to define __EXTENSIONS__... yes checking whether _XOPEN_SOURCE should be defined... no checking for special C compiler options needed for large files... no checking for _FILE_OFFSET_BITS value needed for large files... no checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... (cached) /usr/xpg4/bin/grep checking for egrep... (cached) /usr/xpg4/bin/grep -E checking whether gcc needs -traditional... no checking for a BSD-compatible install... /opt/pkg/bin/bsdinstall -c -o pbulk -g pbulk checking for x86_64-sun-solaris2.11-ar... no checking for ar... ar checking for x86_64-sun-solaris2.11-ranlib... no checking for ranlib... ranlib checking for bison... /opt/pkg/bin/bison -y checking whether make sets $(MAKE)... yes checking for an ANSI C-conforming const... yes checking for inline... inline checking whether byte ordering is bigendian... no checking for preprocessor stringizing operator... yes checking for long double... yes checking whether char is unsigned... no checking for working volatile... yes checking for C/C++ restrict keyword... __restrict__ checking for a race-free mkdir -p... ././support/install.sh -c -d checking for a sed that does not truncate output... /usr/bin/sed checking whether NLS is requested... yes checking for msgfmt... /home/pbulk/build/shells/bash/work/.tools/bin/msgfmt checking for gmsgfmt... /home/pbulk/build/shells/bash/work/.tools/bin/msgfmt checking for xgettext... /home/pbulk/build/shells/bash/work/.tools/bin/xgettext checking for msgmerge... /home/pbulk/build/shells/bash/work/.tools/bin/msgmerge checking whether we are using the GNU C Library 2 or newer... no checking whether the -Werror option is usable... yes checking for simple visibility declarations... yes checking for size_t... yes checking for stdint.h... yes checking for working alloca.h... yes checking for alloca... yes checking for getpagesize... yes checking for symlink... yes checking for uselocale... yes checking for vprintf... yes checking for alarm... yes checking for fpurge... no checking for __fpurge... yes checking for snprintf... yes checking for vsnprintf... yes checking for working mmap... yes checking whether integer division by zero raises SIGFPE... yes checking for inttypes.h... yes checking for unsigned long long int... yes checking for inttypes.h... (cached) yes checking whether the inttypes.h PRIxNN macros are broken... no checking for ld used by gcc... /bin/ld checking if the linker (/bin/ld) is GNU ld... no checking for shared library run path origin... done checking 32-bit host C ABI... no checking for 64-bit host... yes checking for the common suffixes of directories in the library search path... lib/64,lib/amd64 checking whether imported symbols can be declared weak... yes checking for pthread.h... yes checking for pthread_kill in -lpthread... yes checking for multithread API to use... posix checking for pthread_rwlock_t... yes checking whether pthread_rwlock_rdlock prefers a writer to a reader... yes checking for gcc options needed to detect all undeclared functions... none needed checking for iconv... yes checking for working iconv... yes checking for iconv declaration... extern size_t iconv (iconv_t cd, const char * *inbuf, size_t *inbytesleft, char * *outbuf, size_t *outbytesleft); checking for argz.h... no checking for inttypes.h... (cached) yes checking for limits.h... yes checking for unistd.h... (cached) yes checking for sys/param.h... (cached) yes checking for getcwd... yes checking for getegid... yes checking for geteuid... yes checking for getgid... yes checking for getuid... yes checking for mempcpy... no checking for munmap... yes checking for stpcpy... yes checking for strcasecmp... yes checking for strdup... yes checking for strtoul... yes checking for tsearch... yes checking for argz_count... no checking for argz_stringify... no checking for argz_next... no checking for __fsetlocking... yes checking for localeconv... yes checking whether feof_unlocked is declared... no checking whether fgets_unlocked is declared... no checking for bison... bison checking version of bison... 3.8.2, ok checking for long long int... yes checking for wchar_t... yes checking for wint_t... yes checking whether wint_t is too small... no checking for intmax_t... yes checking whether printf() supports POSIX/XSI format strings... yes checking whether we are using the GNU C Library >= 2.1 or uClibc... no checking for stdint.h... (cached) yes checking for SIZE_MAX... yes checking for stdint.h... (cached) yes checking for working fcntl.h... yes checking whether uselocale works... yes checking for fake locale system (OpenBSD)... no checking for Solaris 11.4 locale system... no checking for getlocalename_l... no checking for CFPreferencesCopyAppValue... no checking for CFLocaleCopyCurrent... no checking for CFLocaleCopyPreferredLanguages... no checking for flexible array members... yes checking for x86_64-sun-solaris2.11-ar... ar checking for ptrdiff_t... yes checking for features.h... no checking for stddef.h... yes checking for stdlib.h... (cached) yes checking for string.h... (cached) yes checking for asprintf... yes checking for fwprintf... yes checking for newlocale... yes checking for putenv... yes checking for setenv... yes checking for setlocale... yes checking for snprintf... (cached) yes checking for strnlen... yes checking for uselocale... (cached) yes checking for wcslen... yes checking for wcsnlen... yes checking for mbrtowc... yes checking for wcrtomb... yes checking whether _snprintf is declared... no checking whether _snwprintf is declared... no checking whether getc_unlocked is declared... yes checking for nl_langinfo and CODESET... yes checking for LC_MESSAGES... yes checking for CFPreferencesCopyAppValue... (cached) no checking for CFLocaleCopyCurrent... (cached) no checking for CFLocaleCopyPreferredLanguages... (cached) no checking whether included gettext is requested... no checking for GNU gettext in libc... yes checking whether to use NLS... yes checking where the gettext function comes from... libc checking for dirent.h that defines DIR... yes checking for library containing opendir... none required checking for sys/mkdev.h... yes checking for inttypes.h... (cached) yes checking for unistd.h... (cached) yes checking for stdlib.h... (cached) yes checking for stdarg.h... yes checking for varargs.h... no checking for limits.h... (cached) yes checking for string.h... (cached) yes checking for memory.h... yes checking for locale.h... yes checking for termcap.h... yes checking for termio.h... yes checking for termios.h... yes checking for dlfcn.h... yes checking for stdbool.h... yes checking for stddef.h... (cached) yes checking for stdint.h... (cached) yes checking for netdb.h... yes checking for pwd.h... yes checking for grp.h... yes checking for strings.h... (cached) yes checking for regex.h... yes checking for syslog.h... yes checking for ulimit.h... yes checking for sys/pte.h... yes checking for sys/stream.h... yes checking for sys/select.h... yes checking for sys/file.h... yes checking for sys/ioctl.h... yes checking for sys/mman.h... yes checking for sys/param.h... (cached) yes checking for sys/random.h... yes checking for sys/socket.h... yes checking for sys/stat.h... (cached) yes checking for sys/time.h... (cached) yes checking for sys/times.h... yes checking for sys/types.h... (cached) yes checking for sys/wait.h... yes checking for netinet/in.h... yes checking for arpa/inet.h... yes checking for sys/ptem.h... yes checking for sys/resource.h... yes checking for working alloca.h... (cached) yes checking for alloca... (cached) checking for uid_t in sys/types.h... yes checking for working chown... yes checking whether getpgrp requires zero arguments... yes checking for working strcoll... yes checking for __setostype... no checking for wait3... yes checking for mkfifo... yes checking for dup2... yes checking for eaccess... no checking for fcntl... yes checking for getdtablesize... yes checking for getentropy... yes checking for getgroups... yes checking for gethostname... yes checking for getpagesize... (cached) yes checking for getpeername... no checking for getrandom... yes checking for getrlimit... yes checking for getrusage... yes checking for gettimeofday... yes checking for kill... yes checking for killpg... yes checking for lstat... yes checking for pselect... yes checking for readlink... yes checking for select... yes checking for setdtablesize... no checking for setitimer... yes checking for tcgetpgrp... yes checking for uname... yes checking for ulimit... yes checking for waitpid... yes checking for rename... yes checking for bcopy... yes checking for bzero... yes checking for confstr... yes checking for faccessat... yes checking for fnmatch... yes checking for getaddrinfo... no checking for gethostbyname... no checking for getservbyname... no checking for getservent... no checking for inet_aton... yes checking for imaxdiv... yes checking for memmove... yes checking for pathconf... yes checking for putenv... (cached) yes checking for raise... yes checking for random... yes checking for regcomp... yes checking for regexec... yes checking for setenv... (cached) yes checking for setlinebuf... yes checking for setlocale... (cached) yes checking for setvbuf... yes checking for siginterrupt... yes checking for strchr... yes checking for sysconf... yes checking for syslog... yes checking for tcgetattr... yes checking for times... yes checking for ttyname... yes checking for tzset... yes checking for unsetenv... yes checking for vasprintf... yes checking for asprintf... (cached) yes checking for isascii... yes checking for isblank... yes checking for isgraph... yes checking for isprint... yes checking for isspace... yes checking for isxdigit... yes checking for getpwent... yes checking for getpwnam... yes checking for getpwuid... yes checking for mkstemp... yes checking for mkdtemp... yes checking for arc4random... yes checking for getcwd... (cached) yes checking for memset... yes checking for strcasecmp... (cached) yes checking for strcasestr... yes checking for strerror... yes checking for strftime... yes checking for strnlen... (cached) yes checking for strpbrk... yes checking for strstr... yes checking for strtod... yes checking for strtol... yes checking for strtoul... (cached) yes checking for strtoll... yes checking for strtoull... yes checking for strtoumax... yes checking for dprintf... no checking for strchrnul... yes checking for strdup... (cached) yes checking for libaudit.h... no checking whether AUDIT_USER_TTY is declared... no checking whether confstr is declared... yes checking whether printf is declared... yes checking whether sbrk is declared... yes checking whether setregid is declared... yes checking whether strcpy is declared... yes checking whether strsignal is declared... yes checking for setresuid... no checking for setresgid... no checking whether strtold is declared... yes checking for broken strtold... no checking whether strtol is declared... yes checking whether strtoll is declared... yes checking whether strtoul is declared... yes checking whether strtoull is declared... yes checking whether strtoumax is declared... yes checking for working mktime... no checking for argz.h... (cached) no checking for errno.h... yes checking for fcntl.h... yes checking for malloc.h... yes checking for stdio_ext.h... yes checking for working mmap... (cached) yes checking for __argz_count... no checking for __argz_next... no checking for __argz_stringify... no checking for dcgettext... yes checking for mempcpy... (cached) no checking for munmap... (cached) yes checking for mremap... no checking for stpcpy... (cached) yes checking for strcspn... yes checking for wctype.h... yes checking for wchar.h... (cached) yes checking for langinfo.h... yes checking for mbstr.h... no checking for mbrlen... yes checking for mbscasecmp... no checking for mbscmp... no checking for mbsnrtowcs... yes checking for mbsrtowcs... yes checking for mbschr... no checking for wcrtomb... (cached) yes checking for wcscoll... yes checking for wcsdup... yes checking for wcwidth... yes checking for wctype... yes checking for wcswidth... yes checking whether mbrtowc and mbstate_t are properly declared... (cached) yes checking for iswlower... yes checking for iswupper... yes checking for towlower... yes checking for towupper... yes checking for iswctype... yes checking for wchar_t in wchar.h... yes checking for wctype_t in wctype.h... yes checking for wint_t in wctype.h... yes checking for wcwidth broken with unicode combining characters... no checking for locale_charset... yes checking size of wchar_t... 4 checking for dlopen in -ldl... yes checking for dlopen... yes checking for dlclose... yes checking for dlsym... yes checking for getpeername in -lsocket... yes checking for t_open in -lnsl... yes checking for gethostbyname in socket library... yes checking type of array argument to getgroups... gid_t checking for off_t... yes checking for mode_t... yes checking for uid_t in sys/types.h... (cached) yes checking for pid_t... yes checking for size_t... (cached) yes checking for uintptr_t... yes checking for ssize_t... yes checking for time_t... yes checking for long long int... (cached) yes checking for unsigned long long int... (cached) yes checking for sig_atomic_t in signal.h... yes checking size of char... 1 checking size of short... 2 checking size of int... 4 checking size of long... 8 checking size of char *... 8 checking size of size_t... 8 checking size of double... 8 checking size of long long... 8 checking for u_int... yes checking for u_long... yes checking for bits16_t... no checking for u_bits16_t... no checking for bits32_t... no checking for u_bits32_t... no checking for bits64_t... no checking for ptrdiff_t... (cached) yes checking whether stat file-mode macros are broken... no checking whether #! works in shell scripts... yes checking if dup2 fails to clear the close-on-exec flag... no checking whether pgrps need synchronization... no checking for type of signal functions... posix checking for sys_errlist and sys_nerr... yes checking whether sys_siglist is declared... no checking for sys_siglist in system C library... no checking for _sys_siglist in signal.h or unistd.h... yes checking for _sys_siglist in system C library... yes checking for clock_t... yes checking for sigset_t... yes checking for socklen_t... yes checking for quad_t... yes checking for type of struct rlimit fields... rlim_t checking for intmax_t... yes checking for uintmax_t... yes checking size of intmax_t... 8 checking for struct termios.c_line... no checking for struct termio.c_line... yes checking for struct dirent.d_ino... checking for struct dirent.d_ino... yes yes checking for struct dirent.d_fileno... checking for struct dirent.d_fileno... no no checking for struct dirent.d_namlen... checking for struct dirent.d_namlen... no no checking for struct winsize in sys/ioctl.h and termios.h... termios.h checking for struct timeval in sys/time.h and time.h... yes checking for struct stat.st_blocks... yes checking whether struct tm is in sys/time.h or time.h... time.h checking for struct tm.tm_zone... no checking whether tzname is declared... yes checking for tzname... yes checking for struct timezone in sys/time.h and time.h... yes checking for offset of exit status in return status from wait... 8 checking for struct timespec in ... yes checking for struct stat.st_atim.tv_nsec... yes checking whether struct stat.st_atim is of type struct timespec... yes checking for sbrk... yes checking for working sbrk... yes checking for the existence of strsignal... yes checking if opendir() opens non-directories... no checking whether ulimit can substitute for getdtablesize... yes checking whether fpurge is declared... no checking to see if getenv can be redefined... yes checking if getcwd() will dynamically allocate memory with 0 size... yes checking for presence of POSIX-style sigsetjmp/siglongjmp... present checking whether or not strcoll and strcmp differ... no checking for standard-conformant snprintf... yes checking for standard-conformant vsnprintf... yes checking for usable strtoimax... checking for strtoimax... yes checking whether strtoimax is declared... yes yes checking for standard-conformant putenv declaration... yes checking for standard-conformant unsetenv declaration... yes checking for printf floating point output in hex notation... yes checking whether fnmatch can be used to check bracket equivalence classes... no checking if signal handlers must be reinstalled when invoked... no checking for presence of necessary job control definitions... present checking for presence of named pipes... present checking whether termios.h defines TIOCGWINSZ... yes checking for TIOCSTAT in sys/ioctl.h... no checking for FIONREAD in sys/ioctl.h... no checking whether WCONTINUED flag to waitpid is unavailable or available but broken... no checking for speed_t in sys/types.h... no checking whether getpw functions are declared in pwd.h... yes checking for unusable real-time signals due to large values... no checking for tgetent... no checking for tgetent in -ltermcap... yes checking which library has the termcap functions... using libtermcap checking whether /dev/fd is available... standard checking whether /dev/stdin stdout stderr are available... present checking for default mail directory... /var/mail checking shared object configuration for loadable builtins... supported configure: creating ./config.status config.status: creating Makefile config.status: creating builtins/Makefile config.status: creating lib/readline/Makefile config.status: creating lib/glob/Makefile config.status: creating lib/intl/Makefile config.status: creating lib/malloc/Makefile config.status: creating lib/sh/Makefile config.status: creating lib/termcap/Makefile config.status: creating lib/tilde/Makefile config.status: creating doc/Makefile config.status: creating support/Makefile config.status: creating po/Makefile.in config.status: creating examples/loadables/Makefile config.status: creating examples/loadables/Makefile.inc config.status: creating examples/loadables/Makefile.sample config.status: creating examples/loadables/perl/Makefile config.status: creating support/bash.pc config.status: creating support/bashbug.sh config.status: creating config.h config.status: executing po-directories commands config.status: creating po/POTFILES config.status: creating po/Makefile config.status: executing stamp-h commands