Re: Bash-3.2 Official Patch 20

2008-08-19 Thread Chet Ramey
> > BASH PATCH REPORT > > = > > > > Bash-Release: 3.2 > > Patch-ID: bash32-020 > > > > Bug-Reported-by:Ian A Watson <[EMAIL PROTECTED]> > > Bug-Reference-ID: > > >[EMAIL PROTECTED]> Bug-Reference-URL: > > > > Bug-Description:

Re: Bash-3.2 Official Patch 20

2007-08-26 Thread Chet Ramey
Mike Frysinger wrote: > what i meant was that for some reason, i didnt get the readonly error after > modifying one of those four values, but the script stopped parsing at the > same spot since it was a readonly var ... > > (UID=1) > -bash: UID: readonly variable > > (BASH_ARGV=""; UID=1; echo

Re: Bash-3.2 Official Patch 20

2007-08-25 Thread Mike Frysinger
On Saturday 25 August 2007, Chet Ramey wrote: > Mike Frysinger wrote: > > a side note ... if you change any of BASH_{ARGC,ARGV,LINENO,SOURCE} > > before setting a readonly variable, bash will not spit out the error > > message about the variable being readonly ... > > (UID=1) > > -bash: UID: readon

Re: Bash-3.2 Official Patch 20

2007-08-25 Thread Chet Ramey
Mike Frysinger wrote: > a side note ... if you change any of BASH_{ARGC,ARGV,LINENO,SOURCE} before > setting a readonly variable, bash will not spit out the error message about > the variable being readonly ... > (UID=1) > -bash: UID: readonly variable > (BASH_ARGC= UID=1) > > this regression s

Re: Bash-3.2 Official Patch 20

2007-08-25 Thread Mike Frysinger
On Saturday 25 August 2007, Chet Ramey wrote: > Mike Frysinger wrote: > >> Bug-Description: > >>> In some cases of error processing, a jump back to the top-level > >>> processing loop from a builtin command would leave the shell in an > >>> inconsistent state. > >> > >> this appears to break handl

Re: Bash-3.2 Official Patch 20

2007-08-25 Thread Chet Ramey
Mike Frysinger wrote: >> Bug-Description: >>> >>> In some cases of error processing, a jump back to the top-level >>> processing loop from a builtin command would leave the shell in an >>> inconsistent state. >> this appears to break handling of read only variables in source statements > > this m

Re: Bash-3.2 Official Patch 20

2007-08-25 Thread Mike Frysinger
On Saturday 25 August 2007, Mike Frysinger wrote: > On Friday 24 August 2007, Chet Ramey wrote: > > BASH PATCH REPORT > > = > > > > Bash-Release: 3.2 > > Patch-ID: bash32-020 > > > > Bug-Reported-by:Ian A Watson <[EMAIL PROTECTED

Re: Bash-3.2 Official Patch 20

2007-08-25 Thread Mike Frysinger
On Friday 24 August 2007, Chet Ramey wrote: >BASH PATCH REPORT >= > > Bash-Release: 3.2 > Patch-ID: bash32-020 > > Bug-Reported-by: Ian A Watson <[EMAIL PROTECTED]> > Bug-Reference-ID: > [EMAIL PROTECTED]> Bug-Referen

Bash-3.2 Official Patch 20

2007-08-24 Thread Chet Ramey
BASH PATCH REPORT = Bash-Release: 3.2 Patch-ID: bash32-020 Bug-Reported-by:Ian A Watson <[EMAIL PROTECTED]> Bug-Reference-ID: <[EMAIL PROTECTED]> Bug-Reference-URL: Bug-Description: In some cases of error pr