Bug#988975: bash-completion: Wrong completion after some certain words such as TZ, TERM and LANG

2021-08-28 Thread Gabriel F. T. Gomes 
Control: tags -1 + fixed-upstream

Koichi Murase kindly pointed out that this has already been fixed upstream:

  https://github.com/scop/bash-completion/issues/590#issuecomment-906045204

This patch has not been integrated into a release, yet:

  $ git describe --tags 79a504a
  2.11-81-g79a504a4

I'll downstream the patch soon.


Thanks

Bug#988975: bash-completion: Wrong completion after some certain words such as TZ, TERM and LANG

2021-08-25 Thread Gabriel F. T. Gomes 
Control: tags -1 + confirmed upstream

The change in behavior is caused by the following upstream commit:

  
https://github.com/scop/bash-completion/commit/d1756f06ef9bffb1b4621c4e63e47e181ddf1086

which got released in upstream version 2.10.

Bug reported submitted upstream as 
https://github.com/scop/bash-completion/issues/590


Cheers,
Gabriel

On Sat, 22 May 2021 17:59:29 +0800
WHR  wrote:

> Package: bash-completion
> Version: 1:2.11-2
> Severity: important
> X-Debbugs-Cc: msl023...@gmail.com
> 
> This version has a bug that didn't exist in previous Debian release (Buster).
> The completion becomes wrong after certain words; for exmaple I want to
> search for word 'TERM' in a file, so I typed (^ indicates cursor position):
> 
> grep -F TERM 
>  ^
> 
> however the completion here doesn't give the expected result, of listing
> files in the working directory, but instead:
> 
> $ grep -F TERM 
> Display all 1750 possibilities? (y or n)
> 9termhp2  screen.linux-m1
> Etermhp236screen.linux-m1b
> Eterm-256color   hp2382a  screen.linux-m2
> Eterm-88colorhp2392   screen.minitel1
> MtxOrb   hp2397a  screen.minitel1-nb
> ...
> 
> It appears that bash wrongly completed this as the TERM environmet variable,
> which is obviously incorrect here.
> 
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.19.147-rivoreo-amd64 (SMP w/4 CPU threads)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
> Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> 
> -- no debconf information

Bug#988975: bash-completion: Wrong completion after some certain words such as TZ, TERM and LANG

2021-05-22 Thread WHR 
Package: bash-completion
Version: 1:2.11-2
Severity: important
X-Debbugs-Cc: msl023...@gmail.com

This version has a bug that didn't exist in previous Debian release (Buster).
The completion becomes wrong after certain words; for exmaple I want to
search for word 'TERM' in a file, so I typed (^ indicates cursor position):

grep -F TERM 
 ^

however the completion here doesn't give the expected result, of listing
files in the working directory, but instead:

$ grep -F TERM 
Display all 1750 possibilities? (y or n)
9termhp2  screen.linux-m1
Etermhp236screen.linux-m1b
Eterm-256color   hp2382a  screen.linux-m2
Eterm-88colorhp2392   screen.minitel1
MtxOrb   hp2397a  screen.minitel1-nb
...

It appears that bash wrongly completed this as the TERM environmet variable,
which is obviously incorrect here.

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.147-rivoreo-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

-- no debconf information