[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Minor problems with bash-3.2-33.el5_11.4

From: Tajthy, Tamas
Subject: RE: Minor problems with bash-3.2-33.el5_11.4
Date: Mon, 6 Oct 2014 13:55:56 +0200

Dear Chet,

Thanks for your kind answer! Then I'm going to try to open these bugs for 
RedHat and Debian.

Good byte! Tamás

-----Original Message-----
From: Chet Ramey [mailto:address@hidden
Sent: Monday, October 06, 2014 1:52 PM
To: Tajthy, Tamas; address@hidden
Cc: address@hidden
Subject: Re: Minor problems with bash-3.2-33.el5_11.4

On 10/6/14, 4:04 AM, Tajthy, Tamas wrote:
> Hi,
> I have a minor issue with the newest bash-3.2-33.el5_11.4 (RedHat) package. 
> Same happens on Debian Wheezy (unfortunately I do not know that version 
> number now).
> I usually define in my .bash_profile some functions called "..", "...", 
> "...." and so on. After the latest  package was installed I continuously get 
> error messages shown above when I start a (sub-)bash from the login bash:
> bash: error importing function definition for `BASH_FUNC_..'
> bash: error importing function definition for `BASH_FUNC_...'
> bash: error importing function definition for `BASH_FUNC_....'
> etc...  And these functions cannot be used in the child bash. But no problem 
> is shown when bash is a login shell (called as "bash -l") and the definition 
> is read from the .bash_profile.

You should open a bug report with Red Hat and Debian.  They used a stricter 
version of the patches that result in bash refusing to import shell functions 
whose names are not valid shell identifiers.  The official patches I released, 
while imposing this requirement early (bash32-052), allow names that are not 
valid identifiers when the shell is not running in Posix mode (as of 

``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU    address@hidden    http://cnswww.cns.cwru.edu/~chet/

This email message and any attachments are for the sole use of the intended 
recipients and may contain proprietary and/or confidential information which 
may be privileged or otherwise protected from disclosure. Any unauthorized 
review, use, disclosure or distribution is prohibited. If you are not an 
intended recipient, please contact the sender by reply email and destroy the 
original message and any copies of the message as well as any attachments to 
the original message. Local registered entity information: 

reply via email to

[Prev in Thread] Current Thread [Next in Thread]