On Fri, Apr 21, 2006 at 21:11:27 +0200, Michelle Konzack wrote: > Am 2006-04-21 11:06:54, schrieb Julien Cristau: > > This bug looks a lot like 314342 and friends, which have been fixed a > > long time ago: > > gzip (1.3.5-11) unstable; urgency=low > > OK, but I am using Sarge/Stable. Having a broken zgrep makes many > scripts unusable and breaks things. It should be fixed in Stable too. > It most probably won't be, because this is not a "critical bug [in the gzip package] which can lead to data loss, data corruption, or an overly broken system".
> > Line 103 of newer zgrep is not a substitution, so it seems like your > > /bin/sh is not bash and your gzip package is old (the "Bad substitution" > > bash: Oh Yes, it is > gzip: Its the newest one I find in Stable ;-) > > Sorry, but an a productionsserver with Apache, courier ssh, > php5 and more plus 6900 Domains and over 24.000 VHosts I do > not like to install UNSTABLE. > > > string appears in dash, but not in bash or sed). > > I use ONLY bash. > > > Could you send the output of "ls -l /bin/sh" and "dpkg -l gzip" on a > > machine where this problem occurs? > > ----[ cmd 'ls -l /bin/bash' ]--------------------------------------- > > -rwxr-xr-x 1 root root 625228 2004-12-19 17:53 /bin/bash > What I asked for was /bin/sh, not /bin/bash. zgrep is a #!/bin/sh script, and I believe your /bin/sh is *not* bash. Setting /bin/sh to point to bash would probably fix your problem with zgrep. Cheers, Julien Cristau
signature.asc
Description: Digital signature
