0001423: [ ! a = b ] vs. [ a != b ] - BusyBox Bug and Patch Tracking

BusyBox Bug and Patch Tracking

Viewing Issue Simple Details [ Jump to Notes ]

[ View Advanced ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0001423

[BusyBox] Standards Compliance

major

always

07-05-07 12:08

07-11-07 16:13

Reporter

jfree

View Status

public

Assigned To

BusyBox

Priority

normal

Resolution

fixed

Status

closed

Product Version

Summary

0001423: [ ! a = b ] vs. [ a != b ]

Description

There is a discrepency (== error?) in ash's handling of the following:

ash
===
# [ ! a = b ]
# echo $?
1

# [ a != b ]
# echo $?
0

bash
====
$ [ ! a = b ]
$ echo $?
0

$ [ a != b ]
$ echo $?
0

On Thu, Jul 05, 2007 at 12:51:24PM -0400, Paul Smith wrote:
...
> According to the POSIX standard, this form is valid and ash's answer is
> wrong.
...
> This should be fixed in ash, because it's a bug... but I wonder why you
> just don't use the much more common (and hence more likely to work
> properly) "[ a != b ]"?

More info:

Regressing against i386 BusyBox v1.1.3 (Debian 1:1.1.3-4) :

        $ busybox [ ! a = b ]
        $ echo $?
        0

Additional Information

Attached Files

Relationships

Notes
(0002592) vda 07-11-07 16:13	Fixed in 1.6.1

Issue History
Date Modified	Username	Field	Change
07-05-07 12:08	jfree	New Issue
07-05-07 12:08	jfree	Status	new => assigned
07-05-07 12:08	jfree	Assigned To	=> BusyBox
07-11-07 16:13	vda	Status	assigned => closed
07-11-07 16:13	vda	Note Added: 0002592
07-11-07 16:13	vda	Resolution	open => fixed