Ville Skyttä

(Keeping open for a bit even though #508 was merged as a reminder to work on filing reports about the packaging issues.)

Another option for the documented maintainer workaround would be to do the on-the-fly `have` definition/undefinition, but even though cleaner in a way, that'd require them to patch it in instead...

@inconstante FYI the discussion above

@siteshwar FYI too

> If we are going to recommend patching the completion scripts, is there a better alternative than defining have in each script? By patching I meant maintainers could patch our...

BTW I guess lintian could be extended to check some issues we've uncovered here. It already checks for shebangs in them and the use if /etc/bash_completion.d dir, but could do...

(Recent example of transitioning to upstream is in 4d8e152039311e2bebf3d3ecb875e570b3171865)

Agreed.

I wonder if this is a bash version thing; I cannot reproduce even with bash-completion version 2.4 any more, with bash 5.2.21(1)-release.

I've run into this problem myself over the years multiple times, but at the moment I'm out of ideas how to attempt reproducing it. Will close now, I'm sure it...