Re: Latest cogito broken with bash-3.1

[Marcel Holtmann <marcel@holtmann.org>]

Hi Petr,

> > > > 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.
> 
>   this might be some Debian patches then. Indeed, with bash-3.00.16 on
> both systems, the line is shown on my home Gentoo system but not on my
> Debian machine at work. On RHEL at kernel.org the line is not printed
> either. Hmm. So either it's not really bash what emits this (but what
> then?) or most of the distributions override that stupid bash behaviour
> with a patch already. And Debian didn't foreport the patch to bash-3.1.

I just verified that on my Ubuntu Dapper system where I had a copy of
the old bash package lying around. The bash-3.0 works fine, but the
bash-3.1 produces this error. So it is definitely bash related.

Regards

Marcel