Update bash to the current 4.4 patch set with the info file changes...
Index: bash.info =================================================================== RCS file: /cvsroot/fink/dists/10.9-libcxx/stable/main/finkinfo/shells/bash.info,v retrieving revision 1.4 diff -u -r1.4 bash.info --- bash.info 9 Nov 2016 20:04:48 -0000 1.4 +++ bash.info 14 Nov 2016 00:51:15 -0000 @@ -1,7 +1,7 @@ Info4: << Package: bash Version: 4.4 -Revision: 1 +Revision: 2 Description: The GNU Bourne Again Shell License: GPL Maintainer: Benjamin Reed <bash@fink.raccoonfink.com> @@ -24,7 +24,20 @@ Source: mirror:gnu:%n/%n-%v.tar.gz Source-MD5: 148888a7c95ac23705559b6f477dfe25 +Source2: mirror:gnu:%n/%n-4.4-patches/bash44-001 +Source2-MD5: 817d01a6c0af6f79308a8b7b649e53d8 +Source3: mirror:gnu:%n/%n-4.4-patches/bash44-002 +Source3-MD5: 765e14cff12c7284009772e8e24f2fe0 +Source4: mirror:gnu:%n/%n-4.4-patches/bash44-003 +Source4-MD5: 49e7da93bf07f510a2eb6bb43ac3e5a2 +Source5: mirror:gnu:%n/%n-4.4-patches/bash44-004 +Source5-MD5: 4557d674ab5831a5fa98052ab19edaf4 + PatchScript: << + #!/bin/sh -ev + for file in ../bash44-*; do + patch -p0 < $file + done sed -e 's:@PREFIX@:%p:g' %{PatchFile} | patch -p1 << PatchFile: %n.patch
Tested on 10.11 with 'fink -m'.
Last edit: Jack Howarth 2016-11-14
Opps. Added missing fifth bug fix patch...
Tested on 10.11 with 'fink -m'.
Info file for bash-4.4-2
Bug fixes include
Bash-4.4 changed the way the history list is initially allocated to reduce
the number of reallocations and copies. Users who set HISTSIZE to a very
large number to essentially unlimit the size of the history list will get
memory allocation errors
Bash-4.4 warns when discarding NUL bytes in command substitution output
instead of silently dropping them. This patch changes the warnings from
one per NUL byte encountered to one warning per command substitution.
Specially-crafted input, in this case an incomplete pathname expansion
bracket expression containing an invalid collating symbol, can cause the
shell to crash.
There is a race condition that can result in bash referencing freed memory
when freeing data associated with the last process substitution.
Under certain circumstances, a simple command is optimized to eliminate a
fork, resulting in an EXIT trap not being executed.