Your message dated Tue, 6 Jan 2009 10:40:24 -0500
with message-id <[email protected]>
and subject line problem not dash specific
has caused the Debian Bug report #510353,
regarding dash: failure interpreting '<' and '>' in test expressions
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
510353: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=510353
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dash
Version: 0.5.4-12
Severity: normal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hey, Gerrit. As I fumble through the bash/sh -> dash/sh transition,
I'm noticing some trouble with test expressions that use '<' or '>'.
It appears that these characters are being treated as file redirection
operators as opposed to comparison operators:
servo:/tmp/cdtemp.XcoaZB 0$ dash -l
$ test a < b
dash: cannot open b: No such file
$ ls
$ test a > b
$ ls
b
$
However, the dash(1) man page indicates that these characters are
legitimate for use in test expressions:
s1 < s2 True if string s1 comes before s2 based on
the ASCII value of their characters.
s1 > s2 True if string s1 comes after s2 based on
the ASCII value of their characters.
Maybe I'm missing something, but I can't figure out what.
Thanks, as always, for maintaining such important packages.
jamie.
- -- System Information:
Debian Release: 5.0
APT prefers testing
APT policy: (500, 'testing'), (200, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages dash depends on:
ii libc6 2.7-16 GNU C Library: Shared libraries
dash recommends no packages.
dash suggests no packages.
- -- debconf information:
* dash/sh: true
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iQIcBAEBAgAGBQJJW9aJAAoJEO00zqvie6q8tz0P/jftOiVYfWYUuCokiRglnPPr
FmwF07RyEaZcVvOUH4fWt+j3gCTRmAee/vtOM6mw+ldwAWabE17IK7QQovxSVHjf
KihM/Js/xQViSChI+AkZTQN+RO6df1xGwI51BLOH22I5cG/sjFxLarN8KQ3p7tF5
J+SxD1Fhoyz0tqjmzgC52xYGiHZ6k1GnuCXy9HkaT/R+s+S2BtffCo7C8shZjuqm
vWX0UWwPj+GU1tcOuBTarodUt9Rv659TNEI2oDiXXHDmJCC0yKJMZLyL4rF9VUdP
7KbdwtCTKQggrN9uZ9MQS5JQj0E03D4N7RkMzXoS+PqfNzvTJ/dpfzhY2/CUL1uo
vky5+0+NCvW+c0sH6gcXq/a2boTdSnywavek5nfb5D90Fn5cuEsxz/DQPcEiFjqz
0Qml729mt/O+0BDV+CTViadqPWr+w/B4wrInqxTgwl+nJA934He1dvGocou2gJRg
60IaixKFfYYGKiNJV7XIzztFlx4HpbWcHhPC2R9MXrkDstEsgJUpKYr5Gvr8yQNp
NZIKblpRjEfi61KTL1f0jo/uEeiVgysvwXYzyZ5C3NJUphKftOazycbEuQqebC8W
2LN4xaT+Zrtfn25s/YLhecWWzvyn2XXz2mY2Ow4KaElz/jIHI5HdfB9/HkzYBnSE
I84ErkC/i5iTPFLYWd2Y
=M97S
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
tags 510353 +wontfix
thanks
Hey, Gerrit. I just realized that bash behaves the same way, so it's
not just dash specific. Furthermore, both bash and dash behave as
expected if the characters are properly escaped:
servo:~ 0$ bash
servo:~ 0$ test a < b
bash: b: No such file or directory
servo:~ 1$ test a '<' b
servo:~ 0$ test b '<' a
servo:~ 1$ test b \< a
servo:~ 1$ exit
exit
servo:~ 1$ dash -l
$ test a < b
dash: cannot open b: No such file
$ test a '<' b
$ echo $?
0
$ test b \< a
$ echo $?
1
$
I am closing this bug since I believe it was made in error. Very
sorry for wasting time on this.
I would like to note, though, that both the bash and dash
documentation could maybe be imporoved to note that the characters
need to be escaped in this context. It's not unimaginable that bash
and dash could interpret the naked < and > characters as comparison
operators when used with the test buildin function, since redirection
makes no sense in this context.
jamie.
signature.asc
Description: Digital signature
--- End Message ---
