Control: found -1 2:1.7.0-1
On Wed, 22 Jan 2020 at 23:28:37 +0100, Guilhem Moulin wrote:
> If that's a regression it's older than 2:2.0.3-1, AFAICT stretch has
> the same problem.
Before 2:1.7.0-1 the completion file was copied into
/etc/bash_completion.d, which AFAICT bash traverses and sources
Control: tag -1 moreinfo
Control: severity -1 minor
On Wed, 22 Jan 2020 at 23:08:32 +0100, Christoph Anton Mitterer wrote:
> in .bashrc, and that's enough for all other completions... e.g. the one
> for cryptsetup work (more or less).
~$ foo looks for /usr/share/bash-completion/completions/foo
On Wed, 2020-01-22 at 22:53 +0100, Guilhem Moulin wrote:
> Did you source /usr/share/bash-completion/completions/cryptdisks?
Well not manually... I do have
if ! shopt -oq posix; then
if [ -f /usr/share/bash-completion/bash_completion ]; then
. /usr/share/bash-completion/bash_completion
Control: tag -1 moreinfo
On Wed, 22 Jan 2020 at 22:31:49 +0100, Christoph Anton Mitterer wrote:
> Instead of possible device target names it just completes to
> the files of the local directories.
Works fine here, also as non-root. In a sid chroot:
~$ dd if=/dev/zero of=/tmp/disk.img bs=1M
Source: cryptsetup
Version: 2:2.2.2-2
Severity: normal
Hi.
I think since "fixing" #827200 in 2:2.0.3-1 bash completion for
cryptdisks_stop/start doesn't seem to work anymore at all.
Instead of possible device target names it just completes to
the files of the local directories.
Cheers,
Chris
5 matches
Mail list logo
