Your message dated Sat, 8 Aug 2020 13:15:42 -0300
with message-id <20200808131542.1035b169@vostok>
and subject line Re: Bug#741273: Add updated information
has caused the Debian Bug report #741273,
regarding bash-completion BROKEN with 'nounset'
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
741273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741273
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bash-completion
Version: 1:2.0-1
Severity: important
Dear Maintainer,
Debian's bash-completion (not upstream) is broken when 'nounset' is set. This
should not happen. Bash 4.2 includes a [[ -v var ]] test, or a variety of
alternatives are described at: http://mywiki.wooledge.org/BashFAQ/083
Example (trying to complete from '/et'):
$ set -u
$ cd /et-bash: !ref: unbound variable
-bash: !ref: unbound variable
-bash: words[i]: unbound variable
$
This should have behaved exactly the same as if 'nounset' was not set.
-- System Information:
Debian Release: 7.0
APT prefers stable
APT policy: (900, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.9.1 (SMP w/16 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages bash-completion depends on:
ii bash 4.2+dfsg-0.1
ii dpkg 1.16.10
bash-completion recommends no packages.
bash-completion suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1:2.11-1
Fixed upstream with several commits as reported at:
https://github.com/scop/bash-completion/issues/44
--- End Message ---
