Description of problem: On my machine I have a bash shell variable called "TOP" defined: $ echo $TOP 0 (Note this is not an environment variable). This breaks various things, in this case the lowRISC initialization script. The variable comes from gluster bash completion script /etc/bash_completion.d/gluster Version-Release number of selected component (if applicable): glusterfs-cli-3.8.0-0.2.rc2.fc24.x86_64 How reproducible: 100% Steps to Reproduce: 1. echo $TOP
All 3.8.x bugs are now reported against version 3.8 (without .x). For more information, see http://www.gluster.org/pipermail/gluster-devel/2016-September/050859.html
(In reply to Richard W.M. Jones from comment #0) > Description of problem: > > On my machine I have a bash shell variable called "TOP" defined: > > $ echo $TOP > 0 > > (Note this is not an environment variable). This breaks > various things, in this case the lowRISC initialization script. > Can you please direct towards this initialization script? And how severe is the issue? > The variable comes from gluster bash completion script > /etc/bash_completion.d/gluster > > Version-Release number of selected component (if applicable): > > glusterfs-cli-3.8.0-0.2.rc2.fc24.x86_64 > > How reproducible: > > 100% > > Steps to Reproduce: > 1. echo $TOP
(In reply to Anoop C S from comment #2) > Can you please direct towards this initialization script? As stated in the original description: /etc/bash_completion.d/gluster from the package glusterfs-cli. In the source, this file is called extras/command-completion/gluster.bash > And how severe is the issue? Annoying more than severe. However it prevents building all the RISC-V upstream software.
It looks like "TOP" is not the only variable that leaks: From <glusterfs.git>/extras/command-completion/gluster.bash: 285 declare FINAL_LIST='' 286 declare LIST='' 287 declare -i TOP=0
This bug is getting closed because the 3.8 version is marked End-Of-Life. There will be no further updates to this version. Please open a new bug against a version that still receives bugfixes if you are still facing this issue in a more current release.
WTF? Please fix your bugs.
(In reply to Richard W.M. Jones from comment #6) > WTF? Please fix your bugs. There will not be any updates to the 3.8 version. Bug 1425325 has already been opened to get the fix in other maintained versions. Sorry for the confusion, maybe the comment should mention to check or look at bugs that are marked in the 'depends on' field.