On Fri, Jun 12, 2009 at 05:51:11PM +0200, Raphael Hertzog wrote:
> On Wed, 10 Jun 2009, Bastian Blank wrote:
> > In the other case I call it via a python script. The python interpreter
> > collects SIGPIPE by default and the setting is persistent in the child
> > processes. So the SIGPIPE is now collected by bzip2 and converted
> > into an error:
> We have had this in other packages like git-buildpackage which is also in
> python (see http://bugs.debian.org/525411). The problem has been fixed in
> the python script and not somewhere else.
Please explain.
> tar and any other program (dpkg-source) should be able to rightfully make
> the assumption that SIGPIPE is not modified unless it modifies it itself.
Please explain where this is specified. You can only rely on
_documented_ behaviour and signal(7) specifies:
| During an execve(2), the dispositions of handled signals are reset to
| the default; the dispositions of ignored signals are left unchanged.
Bastian
--
Those who hate and fight must stop themselves -- otherwise it is not stopped.
-- Spock, "Day of the Dove", stardate unknown
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
