I'd send it to your vendor. If appropriate they can send it upstream.
Chet
I've sent this to a debian person following advice on the Arch list I initially
asked. I probably won't get used as I imagine they'll want a more general
approach to all the various versions of the bash fixes.
On Sunday, September 28, 2014 3:50:07 AM UTC+1, Chet Ramey wrote:
BASH PATCH REPORT
..
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRUc
If I use the Arch linux [testing]
On Sunday, September 28, 2014 4:38:24 PM UTC+1, beck...@gmail.com wrote:
..
If I use the Arch linux [testing] bash-4.3.027-1 which is uses this patch
then I have a patch against the at(1) source which converts exported
functions into something that sh can parse and allows exported
I currently have this problem with the latest bash from Arch linux which is
biting my at(1) commands. Exported functions make the environment
non-parseable.
##
robin@bunyip:~
$ export -nf psg hsg #clean out my exported functions
On Saturday, September 27, 2014 3:51:23 PM UTC+1, Andreas Schwab wrote:
becker...@gmail.com writes:
$ (env;echo echo 'hello') | bash
You cannot expect that the output of env is parsable by a shell. First
and foremost, it lacks any kind of quoting.
env may not be the issue,
