Re: Bash-4.4-beta2 available for download

[Greg Wooledge]

On Tue, Jul 12, 2016 at 09:38:51PM -0400, Chet Ramey wrote:
> The second beta release of bash-4.4 is now available with the URL
> 
> ftp://ftp.cwru.edu/pub/bash/bash-4.4-beta2.tar.gz
> 
> and via git from
> 
> http://git.savannah.gnu.org/cgit/bash.git/?h=bash-4.4-testing

I have been utterly unable to retrieve the file from the FTP server,
from three different machines (two of them firewalled, one of them a
non-firewalled VPS).  Passive mode times out, and active mode gives a
"bind: address already in use" error.  geirha suggested:

http://git.savannah.gnu.org/cgit/bash.git/snapshot/bash-4.4-beta2.tar.gz

so I tried that.  But there is some doubt about whether this is the
same as the ftp.cwru.edu tarball.  (Maybe post an SHA-1 for it?)

Whichever tarball it is that I got, it builds on HP-UX 10.20 with gcc 3.3
(but not with gcc 2.7.2, which is no big deal since that's not the gcc
I typically use).  Testing to begin.

Re: Bash-4.4-beta2 available for download

[Chet Ramey]

On 7/13/16 10:00 AM, Greg Wooledge wrote:
> On Tue, Jul 12, 2016 at 09:38:51PM -0400, Chet Ramey wrote:
>> The second beta release of bash-4.4 is now available with the URL
>>
>> ftp://ftp.cwru.edu/pub/bash/bash-4.4-beta2.tar.gz
>>
>> and via git from
>>
>> http://git.savannah.gnu.org/cgit/bash.git/?h=bash-4.4-testing
> 
> I have been utterly unable to retrieve the file from the FTP server,
> from three different machines (two of them firewalled, one of them a
> non-firewalled VPS).  Passive mode times out, and active mode gives a
> "bind: address already in use" error.  

Strange.  I had no trouble getting it from ftp.cwru.edu or ftp.gnu.org.

geirha suggested:
> 
> http://git.savannah.gnu.org/cgit/bash.git/snapshot/bash-4.4-beta2.tar.gz
> 
> so I tried that.  But there is some doubt about whether this is the
> same as the ftp.cwru.edu tarball.  (Maybe post an SHA-1 for it?)

It's not different, just laid onto the testing branch so you can get diffs.

Chet
-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRUc...@case.eduhttp://cnswww.cns.cwru.edu/~chet/

Re: Bash-4.4-beta2 available for download

[Chris F.A. Johnson]

On Tue, 12 Jul 2016, Chet Ramey wrote:


The second beta release of bash-4.4 is now available with the URL

ftp://ftp.cwru.edu/pub/bash/bash-4.4-beta2.tar.gz


 I get nothing. wget just hangs:

$ wget ftp://ftp.cwru.edu/pub/bash/bash-4.4-beta2.tar.gz
--2016-07-13 10:46:45--  ftp://ftp.cwru.edu/pub/bash/bash-4.4-beta2.tar.gz
   => 'bash-4.4-beta2.tar.gz'
Resolving ftp.cwru.edu (ftp.cwru.edu)... 50.17.163.19, 52.87.62.244
Connecting to ftp.cwru.edu (ftp.cwru.edu)|50.17.163.19|:21... connected.
Logging in as anonymous ... Logged in!
==> SYST ... done.==> PWD ... done.
==> TYPE I ... done.  ==> CWD (1) /pub/bash ... done.
==> SIZE bash-4.4-beta2.tar.gz ... 8932859
==> PASV ...



--
Chris F.A. Johnson, 

Re: Bash-4.4-beta2 available for download

[Chet Ramey]

On 7/13/16 10:49 AM, Chris F.A. Johnson wrote:
> On Tue, 12 Jul 2016, Chet Ramey wrote:
> 
>> The second beta release of bash-4.4 is now available with the URL
>>
>> ftp://ftp.cwru.edu/pub/bash/bash-4.4-beta2.tar.gz
> 
>  I get nothing. wget just hangs:

It looks like a problem with the AWS load balancer.  For now, get it from
ftp.gnu.org.

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRUc...@case.eduhttp://cnswww.cns.cwru.edu/~chet/

Re: Bash-4.4-beta2 available for download

[Chet Ramey]

On 7/13/16 10:58 AM, Chet Ramey wrote:
> On 7/13/16 10:49 AM, Chris F.A. Johnson wrote:
>> On Tue, 12 Jul 2016, Chet Ramey wrote:
>>
>>> The second beta release of bash-4.4 is now available with the URL
>>>
>>> ftp://ftp.cwru.edu/pub/bash/bash-4.4-beta2.tar.gz
>>
>>  I get nothing. wget just hangs:
> 
> It looks like a problem with the AWS load balancer.  For now, get it from
> ftp.gnu.org.

I was able to retrieve a copy from ftp.cwru.edu using wget (passive mode)
and an ftp client (extended passive mode).  Try it again and let me know
the results.

Chet

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRUc...@case.eduhttp://cnswww.cns.cwru.edu/~chet/

Re: Bash-4.4-beta2 available for download

[Greg Wooledge]

On Wed, Jul 13, 2016 at 11:39:50AM -0400, Chet Ramey wrote:
> I was able to retrieve a copy from ftp.cwru.edu using wget (passive mode)
> and an ftp client (extended passive mode).  Try it again and let me know
> the results.

wget ftp://ftp.cwru.edu/pub/bash/bash-4.4-beta2.tar.gz worked for me
now, after failing earlier this morning.

Re: Bash-4.4-beta2 available for download

[Greg Wooledge]

On Wed, Jul 13, 2016 at 11:45:10AM -0400, Greg Wooledge wrote:
> On Wed, Jul 13, 2016 at 11:39:50AM -0400, Chet Ramey wrote:
> > I was able to retrieve a copy from ftp.cwru.edu using wget (passive mode)
> > and an ftp client (extended passive mode).  Try it again and let me know
> > the results.
> 
> wget ftp://ftp.cwru.edu/pub/bash/bash-4.4-beta2.tar.gz worked for me
> now, after failing earlier this morning.

And, out of curiosity, the difference between the two tarballs (one
from git/savannah, one from the "cwru.edu" amazon s3 ftp server):

wooledg@wooledg:/tmp$ diff -ru bash-4.4-beta2 bash-4.4-beta2-cwru
Only in bash-4.4-beta2: CHANGES-4.4
Only in bash-4.4-beta2/CWRU: -i
Only in bash-4.4-beta2: .gitignore
Only in bash-4.4-beta2-cwru: parser-built

Looks like the code is the same.  Good.  I don't have to rebuild it.

Re: Bash-4.4-beta2 available for download

[Chris F.A. Johnson]

On Wed, 13 Jul 2016, Chet Ramey wrote:


On 7/13/16 10:58 AM, Chet Ramey wrote:

On 7/13/16 10:49 AM, Chris F.A. Johnson wrote:

On Tue, 12 Jul 2016, Chet Ramey wrote:


The second beta release of bash-4.4 is now available with the URL

ftp://ftp.cwru.edu/pub/bash/bash-4.4-beta2.tar.gz


 I get nothing. wget just hangs:


It looks like a problem with the AWS load balancer.  For now, get it from
ftp.gnu.org.


I was able to retrieve a copy from ftp.cwru.edu using wget (passive mode)
and an ftp client (extended passive mode).  Try it again and let me know
the results.


It worked this time. Thanks.

--
Chris F.A. Johnson, 

man page confusion about array with no members: var=()

[idallen]

Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' 
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu' 
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' -DSHELL 
-DHAVE_CONFIG_H   -I.  -I../. -I.././include -I.././lib  -Wdate-time 
-D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wall
uname output: Linux idallen-oak 4.4.0-28-generic #47-Ubuntu SMP Fri Jun 24 
10:09:13 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Machine Type: x86_64-pc-linux-gnu

Bash Version: 4.3
Patch Level: 46
Release Status: release

Description:
The BASH man pags says "When there are no array members,
${name[@]} expands to nothing." and then later "An array variable
is considered set if a subscript has been assigned a value.".

The first sentence tells me that ${name[@]} is a valid use of a
variable that exists but has no members, but the second sentence
implies that if the array has no members it is considered "unset"
and thus ${name[@]} would not be a valid use of the name.

These are contradictory statements.  Using ${name[@]} with
no array members generates an "unbound variable" error under
"nounset"; it does not expand to "nothing".

The reason ${name[@]} expands to nothing is not because it's
a valid use of ${name[@]}, it's because any use of an unset
variable expands to nothing, unless, as I do, you run with
"nounset" enabled and it causes an error.

To fit current behaviour, the first man page sentence above should
be changed to say: When there are no array members, the array
name is considered unset and ${name[@]} will expand to nothing or
generate an "unbound variable" error under the "nounset" option.

I'd prefer that BASH change the behaviour of var=() to not give
an "unbound variable" error on ${name[@]}, but changing the man
page is probably easier than changing the current behaviour.

Repeat-By:
#!/bin/bash -u

# make BASH complain about unset variables
set -o nounset

echo 'ONE: set var= and try $var and ${var[@]} - both work without 
error'
unset var
var=
( echo "ONE: [$var]" )
( echo "ONE: [${var[@]}]" )

echo 'TWO: set var=() and try again - both fail with "unbound variable"'
unset var
var=()
( echo "TWO: [$var]" )
( echo "TWO: [${var[@]}]" )

The Manual about the MAIL environment is misleading

[ikrabbe . ask]

Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: x86_64-pc-linux-gnu-gcc
Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' 
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu' 
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' -DSHELL 
-DHAVE_CONFIG_H   -I. -I./include -I. -I./include -I./lib  
-DDEFAULT_PATH_VALUE='/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin'
 -DSTANDARD_UTILS_PATH='/bin:/usr/bin:/sbin:/usr/sbin' 
-DSYS_BASHRC='/etc/bash/bashrc' -DSYS_BASH_LOGOUT='/etc/bash/bash_logout' 
-DNON_INTERACTIVE_LOGIN_SHELLS -DSSH_SOURCE_BASHRC -DUSE_MKTEMP -DUSE_MKSTEMP 
-O2 -pipe
uname output: Linux laptop 4.6.1jun2016 #24 SMP Sat Jun 18 09:56:03 CEST 2016 
x86_64 Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz GenuineIntel GNU/Linux
Machine Type: x86_64-pc-linux-gnu

Bash Version: 4.3
Patch Level: 42
Release Status: release

Description:
In a bash session where the MAIL variable is not explicitly set, the 
MAIL variable might be auto-set through a compile time definition of 
DEFAULT_MAIL_DIRECTORY. There is no method (no method I know of) to find about 
about these compile time definitions and / or configuration flags.
To find out about this bevaiour I needed to read the source code and 
finally found this line in CHANGES:

hhh. Improved the mail checking code so it won't check (and possibly 
cause an
 NFS file system mount) until MAILPATH or MAIL is given a value -- 
there
 is no default if DEFAULT_MAIL_DIRECTORY is not defined at compile 
time.


Repeat-By:
Install bash and remove all occurences of MAIL= or similar from the 
several profile and rc files.

Fix:
Please describe the dependency of the MAIL variables on the manual 
page. If you manage to do so, add the value of DEFAULT_MAIL_DIRECTORY and it's 
effects in the generated manual pages.