Bug#835498: checkbashisms treats 'command' incorrectly

2020-03-12 Thread jnqnfe
control: severity -1 important Debian policy v4.1.5 (July 2018) updated from SUSv3 to POSIX.1-2017 (aka SUSv4). This should presumably (without double checking the specifics of this version) mean that the way is clear for checkbashisms to be modified to accept `command -v` etc. Please address

Bug#835498: checkbashisms treats 'command' incorrectly

2020-03-12 Thread John Crawley
On 2016-08-26 14:38, Adam D. Barratt wrote: > On 2016-08-26 11:47, Eero Vuojolahti wrote: >> Secondly, there are no optional flags listed in the 2008/2013 version >> of the 'command' specification. In the older (2004) standard, the |-v| >> and |-V| options were part of the 'user portability'

Bug#835498: checkbashisms treats 'command' incorrectly

2016-08-26 Thread Eero Vuojolahti
Package: devscripts Version: 2.16.7 contents of test.sh: #!/bin/sh command -v ls command -V ls command -p -v -a ls command -p -a -v ls command -pa ls command -ap ls command -p -a ls command -pV -a ls exit 0 Output from 'checkbashisms test.sh': possible bashism in test.sh line 2 ('command' with