btmgmt --index broken #639
Comments
github-actions bot
pushed a commit
to tedd-an/bluez-upstream-test
that referenced
this issue
Oct 30, 2023
The newly added option -i/--init-script introduced a short option namespace collision with btmgmt's --index, both of which use '-i'. As a result, a provided --index is treated as a file name: $ sudo btmgmt --index 0 info Unable to open 0: No such file or directory (2) Fix this by using '-s' for --init-script. Fixes: bluez/bluez#639 Signed-off-by: Juerg Haefliger <juerg.haefliger@canonical.com>
github-actions bot
pushed a commit
to BluezTestBot/bluez
that referenced
this issue
Oct 30, 2023
The newly added option -i/--init-script introduced a short option namespace collision with btmgmt's --index, both of which use '-i'. As a result, a provided --index is treated as a file name: $ sudo btmgmt --index 0 info Unable to open 0: No such file or directory (2) Fix this by using '-s' for --init-script. Fixes: bluez#639 Signed-off-by: Juerg Haefliger <juerg.haefliger@canonical.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Commit f2f7c74 ("shared/shell: Add support for -i/--init-script")
introduced a short option namespace collision with btmgmt's --index option,
both of which use
-i.As a result, a provided --index is treated as an init-script...
The text was updated successfully, but these errors were encountered: