Bug#1106336: debfoster: bash tab completion says "have: command not found"

Control: tags 1106336 + patch Hi Marc-- On Sat 2025-05-24 10:48:09 +0200, Marc Haber wrote: > Try this patch: > > --- original2025-05-24 10:45:01.169219431 +0200 > +++ /usr/share/bash-completion/completions/debfoster2025-05-24 > 10:45:35.865115014 +0200 > @@ -3,7 +3,7 @@ > # Provided b

Bug#1106336: debfoster: bash tab completion says "have: command not found"

Try this patch: --- original2025-05-24 10:45:01.169219431 +0200 +++ /usr/share/bash-completion/completions/debfoster2025-05-24 10:45:35.865115014 +0200 @@ -3,7 +3,7 @@ # Provided by Eric Hansander in # -have debfoster && +_com

Bug#1106336: debfoster: bash tab completion says "have: command not found"

Hi Marc-- Thanks for the quick feedback here. On Fri 2025-05-23 07:14:10 +0200, Marc Haber wrote: > have used to be defined for bash_completion snippets and got deprecated > some time one year ago. Sadly without any warning or obvious informaion, > and now it's gone. That seems unfortunate :(

Bug#1106336: debfoster: bash tab completion says "have: command not found"

Control: tags -1 help Thanks On Fri, May 23, 2025 at 01:54:13PM -0400, Daniel Kahn Gillmor wrote: but i don't know the history of bash-completion well enough to know what this means, or whether/how to rewrite this completion script myself. Neither do I. Tagging this bug help, but I might get a

Bug#1106336: debfoster: bash tab completion says "have: command not found"

On Thu, May 22, 2025 at 11:20:43PM -0400, Daniel Kahn Gillmor wrote: In bash, if i type /usr/sbin/debfoster and then hit TAB, i see the following error on stderr (four times): bash: have: command not found The bash tab completion rules do indeed try to call something named "have" -- but maybe t

Bug#1106336: debfoster: bash tab completion says "have: command not found"

Package: debfoster Version: 2.8-1 Severity: normal In bash, if i type /usr/sbin/debfoster and then hit TAB, i see the following error on stderr (four times): bash: have: command not found The bash tab completion rules do indeed try to call something named "have" -- but maybe they're ancient? `