Hi! [ CCing Étienne Mollier for the patch provided. ]
On Mon, 2019-08-05 at 14:02:31 +0200, Chris Hofstaedtler wrote: > Control: tags -1 + help confirmed > * Laurent Bigonville <bi...@debian.org> [190805 13:19]: > > On 5/08/19 12:22, Chris Hofstaedtler wrote: > > > * Laurent Bigonville <bi...@debian.org> [190805 10:20]: > > > > The unmount bash completion complains about "awk: line 18: function > > > > gensub never defined" when trying to complete a device > > > Can you confirm that your /usr/bin/awk is not gawk? If so, which one > > > is it? > > bigon@edoras:~$ ls -la /usr/bin/awk /etc/alternatives/awk > > lrwxrwxrwx 1 root root 13 fév 1 2019 /etc/alternatives/awk -> > > /usr/bin/mawk > > lrwxrwxrwx 1 root root 21 fév 1 2019 /usr/bin/awk -> /etc/alternatives/awk > > > > So I only have "mawk" installed: > > > > ii mawk 1.3.3-17+b3 amd64 a pattern > > scanning and text processing language > > Okay, kinda like I thought. > > I'm not sure if, for bash-completion, a Depends: gawk is warranted > from Package: mount, which has Priority: required. This would pull > in gawk on pretty much every system (...). While the package ended up with a Recommends instead of a Depends, which is indeed better, it still seems weird that mount being a required package, will pull in an awk implementation (which is part of the essential set, via the awk virtual through base-files) where our current preferred implementation is mawk (also required), while gawk is optional. This change seems to be fighting our current defaults somehow? > Carrying a local patch to revert the change doesn't sound > sustainable. I'm not an awk expert to come up with a patch that > would implement the same functionality for mawk. Etienne could you try to submit this upstream, so that there's no need to carry such patch in Debian? Thanks, Guillem
