Bash completions provided by nvme-cli producing syntax error

  • Open
  • quality assurance status badge
Details
One participant
  • elaexuotee
Owner
unassigned
Submitted by
elaexuotee
Severity
normal
E
E
elaexuotee wrote on 21 Jan 2022 03:57
(address . bug-guix@gnu.org)
30KYCNRKNXCTW.2WCA6W5H9EJOC@wilsonb.com
Hello Guix,

Installing nvme-cli into my user profile causes the following error to show at
bash login:

bash: 'intel': syntax error: operand expected (error token is "'intel'")

Starting bash with xtrace enabled places the error at
share/bash-completion/completions/nvme:11:

readonly _plugin_subcmds=(
[intel]="id-ctrl internal-log lat-stats \
set-bucket-thresholds lat-stats-tracking \
...

With a cursory glance, that looks like perfectly valid bash. Sourcing the file
directly produces a different set of errors:

$ guix shell --pure nvme-cli
bash-5.1$ source /gnu/store/z3jasjly9s8lmb7scwqbsqfxd0cj5a26-profile/share/bash-completion/completions/nvme
bash: supported-log-pages: command not found
bash: --clear-host-side-blks: command not found
bash: /gnu/store/z3jasjly9s8lmb7scwqbsqfxd0cj5a26-profile/share/bash-completion/completions/nvme: line 1387: unexpected EOF while looking for matching `"'
bash: /gnu/store/z3jasjly9s8lmb7scwqbsqfxd0cj5a26-profile/share/bash-completion/completions/nvme: line 1406: syntax error: unexpected end of file

Is anyone else seeing the original error?

Unrelated, but I also notice that the outputs contain dracut definitions. Might
be worth tightening this package up a little?

Cheers,
B. Wilson
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 53404@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 53404
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch