[debbugs-tracker] bug#30379: closed ([PATCH] gnu: bash: Don't specify default configuration filenames.)

[GNU bug Tracking System]

Your message dated Sun, 10 Jun 2018 13:01:21 +0800
with message-id <address@hidden>
and subject line Re: Status: [PATCH] gnu: bash: Don't specify default 
configuration filenames.
has caused the debbugs.gnu.org bug report #30379,
regarding [PATCH] gnu: bash: Don't specify default configuration filenames.
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
30379: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=30379
GNU Bug Tracking System
Contact address@hidden with problems

--- Begin Message --- Subject: [PATCH] gnu: bash: Don't specify default configuration filenames. Date: Wed, 07 Feb 2018 12:39:09 +0100 User-agent: mu4e 0.9.18; emacs 25.1.1

0001-gnu-bash-Don-t-specify-default-configuration-filenam.patch
Description: Text Data

Dear guix,

In bug #29337 I reported a “problem” with our Bash package:  It reads
/etc/bashrc even when it shouldn't, according to its own documentation.
I also compared the behavior of Bash on CentOS to that of Bash on Guix
with the following test:

> On CentOS 7, the following happens (yes, I added the echo-statement to
> /etc/bashrc on CentOS as well):
> $ env - bash --init-file <(echo "echo \"Goodbye, world\"") -i
> Goodbye, world
>
> On GuixSD:
> $ env - bash --init-file <(echo "echo \"Goodbye, world\"") -i
> Hello, world
> Goodbye, world

I attached the proposed patch (removing -DSYS_BASHRC).  May I push this
to core-updates now, or should I wait for the next core-updates cycle?

Thanks!

Kind regards,
Roel Janssen

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: Status: [PATCH] gnu: bash: Don't specify default configuration filenames.
>
>
>
>
> Date: 
>
> Sun, 10 Jun 2018 13:01:21 +0800
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)
>
>
>
>
> Already landed in master, closing :-)
>
>
> --- End Message ---