** Description changed: [impact] The nvme-cli tool includes a bash completion script, but it drops it in the wrong location. This prevents it from actually being sourced and so the nvme tool doesn't do param autocompletion. [test case] install the nvme-cli package and try to auto-complete any of its params. They do not auto-complete. [regression potential] moving where this bash autocompletion file is only has the potential to break nvme's autocompletion. As that does not currently work at all, the regression potential seems low. + [scope] + + fixed upstream in commit df3a06243da0433d8737cdbfa0e3ac101a3a330e + + that is included starting in version 1.7, so Eoan and later are already + fixed. This package does not provide any bash completion script in + Xenial. So only Bionic needs fixing. + [other info] bash completion files appear to be managed inside the 'bash-completion' pkg, and only rarely are managed directly by owning packages. Those that do should drop their scripts into /usr/share/bash- completion/completions/, not /usr/share/bash_completion.d/. The Makefile in Eoan and later does place the bash completion file into the correct subdir; only Bionic needs updating.
** Description changed: [impact] The nvme-cli tool includes a bash completion script, but it drops it in the wrong location. This prevents it from actually being sourced and so the nvme tool doesn't do param autocompletion. [test case] install the nvme-cli package and try to auto-complete any of its params. They do not auto-complete. [regression potential] moving where this bash autocompletion file is only has the potential to break nvme's autocompletion. As that does not currently work at all, the regression potential seems low. [scope] fixed upstream in commit df3a06243da0433d8737cdbfa0e3ac101a3a330e that is included starting in version 1.7, so Eoan and later are already fixed. This package does not provide any bash completion script in Xenial. So only Bionic needs fixing. [other info] - - bash completion files appear to be managed inside the 'bash-completion' - pkg, and only rarely are managed directly by owning packages. Those - that do should drop their scripts into /usr/share/bash- - completion/completions/, not /usr/share/bash_completion.d/. - - The Makefile in Eoan and later does place the bash completion file into - the correct subdir; only Bionic needs updating. ** Description changed: [impact] The nvme-cli tool includes a bash completion script, but it drops it in the wrong location. This prevents it from actually being sourced and so the nvme tool doesn't do param autocompletion. [test case] install the nvme-cli package and try to auto-complete any of its params. They do not auto-complete. + + check if the bash auto-completion script is correctly located at: + /usr/share/bash-completion/completions/nvme [regression potential] moving where this bash autocompletion file is only has the potential to break nvme's autocompletion. As that does not currently work at all, the regression potential seems low. [scope] fixed upstream in commit df3a06243da0433d8737cdbfa0e3ac101a3a330e that is included starting in version 1.7, so Eoan and later are already fixed. This package does not provide any bash completion script in Xenial. So only Bionic needs fixing. [other info] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800544 Title: nvme-cli drops bash completion file in wrong location To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvme-cli/+bug/1800544/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
