Bug#548493: test-yesno.sh failure

2009-09-28 Thread Jim Meyering
Bruno Haible wrote: Jim Meyering wrote: # Test with seekable stdin; the followon process must see remaining data. -cat EOF ${p}in.tmp +cat EOF |tr @ '\177' ${p}in.tmp This can be simplified to: tr @ '\177' EOF ${p}in.tmp Of course! Thanks. I've pushed this: From

Bug#548493: test-yesno.sh failure

2009-09-27 Thread Jim Meyering
Kurt Roeckx wrote: Source: coreutils Version: 7.5-1 ... Build-Depends: gettext (= 0.10.37), debhelper, dh-buildinfo, texinfo (= 4.2), groff, dpatch, libattr1-dev | not+linux-gnu, libacl1-dev | not+linux-gnu, libselinux1-dev (= 1.32) | not+linux-gnu, gperf, bison [...] Toolchain package

Bug#548493: test-yesno.sh failure

2009-09-27 Thread Kurt Roeckx
On Sun, Sep 27, 2009 at 08:51:48AM +0200, Jim Meyering wrote: Thanks for the report. Does the following change fix it? If so, please tell me what version of bash it's using so I can add that to the commit log. Note that /bin/sh points to dash, not bash. And the same version of dash seems

Bug#548493: test-yesno.sh failure

2009-09-27 Thread Bruno Haible
Jim Meyering wrote: # Test with seekable stdin; the followon process must see remaining data. -cat EOF ${p}in.tmp +cat EOF |tr @ '\177' ${p}in.tmp This can be simplified to: tr @ '\177' EOF ${p}in.tmp Bruno -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a

Bug#548493: test-yesno.sh failure

2009-09-27 Thread Jim Meyering
Kurt Roeckx wrote: On Sun, Sep 27, 2009 at 08:51:48AM +0200, Jim Meyering wrote: Thanks for the report. Does the following change fix it? If so, please tell me what version of bash it's using so I can add that to the commit log. Note that /bin/sh points to dash, not bash. And the same

Bug#548493: test-yesno.sh failure

2009-09-27 Thread Kurt Roeckx
On Sun, Sep 27, 2009 at 11:03:42PM +0200, Jim Meyering wrote: Thanks for the details. Here's a patch that's more likely to work. That this failure is specific to the sparc build is a strong indication that it is a bug in dash or the compiler. Maybe a sign-extension bug? I'm seeing this on