ports/129349: [PATCH]shells/bash: update to 3.2.48

bf bf2006a at yahoo.com
Mon Dec 1 21:00:06 UTC 2008


>Number:         129349
>Category:       ports
>Synopsis:       [PATCH]shells/bash: update to 3.2.48
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          update
>Submitter-Id:   current-users
>Arrival-Date:   Mon Dec 01 21:00:04 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     bf
>Release:        7-STABLE i386
>Organization:
-
>Environment:
>Description:
Bugs announced as fixed by the new patches:

--Bash-3.2 changed the behavior of the [[ command's `=~' operator when the
right-hand side was quoted:  it matched the quoted portions as strings.
This patch introduces a new shell option: compat31.  When enabled, it
restores the bash-3.1 behavior with respect to evaluating quoted arguments
to the =~ operator.

--When using the `set' builtin to list all shell variables, the shell uses
the wrong variable when computing the length of a variable's value.

--Bash saved and restored the value of `set -o history' while sourcing files,
preventing users from turning off history with `set +o history' in .bashrc.

--An operator precedence error prevented the bash arithmetic evaluator from
parsing conditional commands correctly.

--Side effects caused by setting function-local versions of variables bash
handles specially persisted after the function returned.

--The presence of invisible characters in a prompt longer than the screenwidth
with invisible characters on the first and last prompt lines caused readline
to place the cursor in the wrong physical location.

--When short-circuiting execution due to the `break' or `continue' builtins,
bash did not preserve the value of $?.

--Bash did not compute the length of multibyte characters correctly when
performing array element length references (e.g., ${#var[subscript]}).

--When using the `.' (source) builtin, under certain circumstances bash was
too careful in discarding state to preserve internal consistency.  One
effect was that assignments to readonly variables would cause entire scripts
to be aborted instead of execution of the offending command.  This behavior
was introduced by bash-3.2 patch 20.

--When invoked as `bash -c', bash did not execute an EXIT trap when the last
command in the executed list was a command run from the file system.

>How-To-Repeat:

>Fix:


Patch attached with submission follows:

diff -ruN bash.orig/Makefile bash/Makefile
--- bash.orig/Makefile	2008-08-21 02:18:22.000000000 -0400
+++ bash/Makefile	2008-11-25 09:47:37.651389000 -0500
@@ -7,7 +7,7 @@
 #
 
 PORTNAME=		bash
-PATCHLEVEL=		39
+PATCHLEVEL=		48
 PORTVERSION=		3.2.${PATCHLEVEL:S/^0//g}
 PORTREVISION?=	1
 CATEGORIES=		shells
diff -ruN bash.orig/distinfo bash/distinfo
--- bash.orig/distinfo	2008-05-03 22:34:52.000000000 -0400
+++ bash/distinfo	2008-11-25 09:50:27.823482000 -0500
@@ -118,5 +118,32 @@
 MD5 (bash/bash32-039) = e240c34f979b64bcb83c5f6567110bb1
 SHA256 (bash/bash32-039) = 46d427fd5b1509ec7dd980c07efd88634fde61cf07ab221dcbde9e1021bd2817
 SIZE (bash/bash32-039) = 5034
+MD5 (bash/bash32-040) = 06e6df263398807fa032707fb7b77b5f
+SHA256 (bash/bash32-040) = c9e0387eb4a2904126864d24de0699cdb6070789e1c02287a3b81ea96bf945aa
+SIZE (bash/bash32-040) = 1403
+MD5 (bash/bash32-041) = 373ae081d658dc85bc1058c4759d6669
+SHA256 (bash/bash32-041) = cc551fa57d613efea30ab2404fe724793a3d10f012b030e611d2c6449e463bcd
+SIZE (bash/bash32-041) = 4446
+MD5 (bash/bash32-042) = 9c9ebc6bfc33a0215277ee17a276eb5a
+SHA256 (bash/bash32-042) = fd0df54d03034e104b6377f249624bda0271aa874190a46e9d41fc49ad3caaef
+SIZE (bash/bash32-042) = 1209
+MD5 (bash/bash32-043) = b87fb9ea16a64ca41b6676e9a7eb7a33
+SHA256 (bash/bash32-043) = 43df7d2d7d61d3a8f0e14bc86d4f55b6d2e64829ba0829a78f5214d186087af7
+SIZE (bash/bash32-043) = 1658
+MD5 (bash/bash32-044) = 07e0229ce5879bfbd26a8146070fd366
+SHA256 (bash/bash32-044) = 204b5ecaaa5de334c3cfbce6dfd8a9d3770b09024ab4724d86080fbf501ded69
+SIZE (bash/bash32-044) = 5565
+MD5 (bash/bash32-045) = 1ad07965a8a93f3556ee1ab18b97cde2
+SHA256 (bash/bash32-045) = 3250e6c6d5d6884e31beaa2f521d2a1af9c2f701a4c0e67a7cd011b6ad8f082b
+SIZE (bash/bash32-045) = 1338
+MD5 (bash/bash32-046) = f7b1e19fcad54c2286bc0ed614aad9bf
+SHA256 (bash/bash32-046) = fc829e92fa951c34368d83272d746f5c0ed345a7ad037f93322347eed00a1e1f
+SIZE (bash/bash32-046) = 1275
+MD5 (bash/bash32-047) = 550690766de770116c34dbdf74e59184
+SHA256 (bash/bash32-047) = 623d4a958d2b022a15929a4de7403766ff07b295a185987b4d1e6cf3b70ea106
+SIZE (bash/bash32-047) = 1981
+MD5 (bash/bash32-048) = 4cc593e7b789b23b37a5397e092d3954
+SHA256 (bash/bash32-048) = 74cb56764274f393676f68738eb22a3ed8fa388c0487feeadf0d78a45b549749
+SIZE (bash/bash32-048) = 1948
 MD5 (bash/FAQ) = IGNORE
 SHA256 (bash/FAQ) = IGNORE


>Release-Note:
>Audit-Trail:
>Unformatted:



More information about the freebsd-ports-bugs mailing list