Bug#935115: passing variable assignments to functions (was Re: Bug#935115: bash: [regression] passing variable assignments to functions broken in POSIX mode, violating POSIX)

2020-10-15 Thread Usama Makhzoum
looks like it has been fixed, i can't reproduce in either unstable, testing or stable by the moment of now.

Bug#935115: bash: [regression] passing variable assignments to functions broken in POSIX mode, violating POSIX

2019-08-19 Thread Thorsten Glaser
Hi Chet, >There is a problem with bash-5.0 when the variable is declared local in >the interposed function, and I need to fix that, but that's not a posix ah, okay, I didn’t test what removing the “local” would do. Debian is a special beast: it requires of a /bin/sh to behave like a POSIX shell

Bug#935115: bash: [regression] passing variable assignments to functions broken in POSIX mode, violating POSIX

2019-08-19 Thread Chet Ramey
On 8/19/19 11:47 AM, Thorsten Glaser wrote: > Package: bash > Version: 5.0-4 > Severity: critical > Justification: breaks unrelated software > > The expected output is: > > dbc_mysql_createdb: _dbc_nodb(1)= # initially not set / empty > dbc_mysql_exec_command: _dbc_nodb=yes # MUST be

Bug#935115: bash: [regression] passing variable assignments to functions broken in POSIX mode, violating POSIX

2019-08-19 Thread Thorsten Glaser
Package: bash Version: 5.0-4 Severity: critical Justification: breaks unrelated software Found this gem in #934027: tglase@tglase:~ $ cat testscript dbc_mysql_createdb(){ local ret l_dbname _dbc_nodb echo "dbc_mysql_createdb: _dbc_nodb(1)=$_dbc_nodb" _dbc_nodb="yes"