Re: Latest cogito broken with bash-3.1

From: Marcel Holtmann <marcel@holtmann.org>
Date: Dec 12, 2005, 09:30 UTC
Message-ID: <1134379801.1468.5.camel@blade>
In-Reply-To: <20051212002631.GW22159@pasky.or.cz>

Hi Petr,

Show 14 quoted lines

> > There exists also another problem with the new bash. It is the broken
> > pipe error from cg-log.
> > 
> > cg-log: line 141: echo: write error: Broken pipe
> > 
> > The line number varies depending how much you scrolled and when you
> > scrolled to the end no broken pipe error comes up. Do you have any idea
> > on how to deal with this. I saw your comment about that bash is broken
> > and the extra trap command, but it doesn't help. I never saw that
> > problem with older versions of bash.
> 
>   Then that's quite funny, one-line broken pipe message has been always
> there (in the past it looked much worse, we thankfully managed to bring
> it down to this at least).

I have some machines where I stopped installing the latest bash version and they don't have this problem. With bash-2.05b.0 and bash-3.00.16 I never (and really mean never) saw this problem.

It is not related to this, but the make-3.81beta3 breaks all my Debian package rules and I don't have the slightest idea why. It seems that they try to fix some Posix issues and make it worse then any better :(

Regards

Marcel