From: elaexuotee--- via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 53404@debbugs.gnu.org
Subject: bug#53404: Bash completions provided by nvme-cli producing syntax error
Date: Fri, 21 Jan 2022 11:57:44 +0900 [thread overview]
Message-ID: <30KYCNRKNXCTW.2WCA6W5H9EJOC@wilsonb.com> (raw)
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
reply other threads:[~2022-01-21 2:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=30KYCNRKNXCTW.2WCA6W5H9EJOC@wilsonb.com \
--to=bug-guix@gnu.org \
--cc=53404@debbugs.gnu.org \
--cc=elaexuotee@wilsonb.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).