From: Zac Medico <zmedico@gentoo.org>
Date: Tue, 1 Feb 2011 04:33:48 +0000 (-0800)
Subject: EbuildFetcher: use default SIGINT/TERM handlers
X-Git-Tag: v2.1.9.36~39
X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=f5c551e10d28855266f8e5d6beccf8a52d2e8417;p=portage.git

EbuildFetcher: use default SIGINT/TERM handlers

This seems to fix bug #353239.
---

diff --git a/pym/_emerge/EbuildFetcher.py b/pym/_emerge/EbuildFetcher.py
index d19307806..eb27647d1 100644
--- a/pym/_emerge/EbuildFetcher.py
+++ b/pym/_emerge/EbuildFetcher.py
@@ -5,6 +5,7 @@ import traceback
 
 from _emerge.SpawnProcess import SpawnProcess
 import copy
+import signal
 import sys
 import portage
 from portage import os
@@ -95,6 +96,11 @@ class EbuildFetcher(SpawnProcess):
 
 		portage.process._setup_pipes(fd_pipes)
 
+		# Use default signal handlers in order to avoid problems
+		# killing subprocesses as reported in bug #353239.
+		signal.signal(signal.SIGINT, signal.SIG_DFL)
+		signal.signal(signal.SIGTERM, signal.SIG_DFL)
+
 		# Force consistent color output, in case we are capturing fetch
 		# output through a normal pipe due to unavailability of ptys.
 		portage.output.havecolor = self._settings.get('NOCOLOR') \