Hi Raphael, thanks for the heads up! On Fri, Apr 24, 2009 at 04:03:03PM +0200, Raphael Hertzog wrote: > On Fri, 24 Apr 2009, Michael Meskes wrote: > > > This looks very much like your comment on 523329 (and the error message > > > is identical) so I'm reassigning it to dpkg-dev since I can't see how > > > git-buildpackage could be involved. > > > > Sorry, I hit send before finishing the report. I had some private > > conversation > > with Buxy already and this seems to be a different bug. He pointed me to > > signal > > handling by git-buildpackage/python. > > The SIGPIPE signal handler is not the default one when git-buildpackage > calls dpkg-buildpackage and this explains the failure because gunzip is > not killed by the signal as dpkg-source expect it. Python sets the signal handler to SIG_IGN which has caused trouble for others too (http://bugs.python.org/issue1652).
> I don't know if python does it behind your back, or if git-buildpackage > does it on purpose but you should reset the signal handler before calling > dpkg-buildpackage. I have fixed this in git-buildpackage but am worried that every other python scripts that invokes dpkg-source has to be fixed as well. Wouldn't it make sense to set the correct signal mask on the child forked by dpkg-source to unzip the package? Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
