Bug#607844: [buildd-tools-devel] Bug#607844: weird interaction between setsid and SIGTSTP

2012-10-22 Thread Roger Leigh
reassign 607844 upstart retitle 607844 upstart: Use separate controlling terminal for tests tags 607844 + fixed-upstream thanks On Mon, Oct 22, 2012 at 03:04:24PM +0100, James Hunt wrote: I've just committed a fix for this bug. See: https://bugs.launchpad.net/upstart/+bug/888910 Thanks.

Bug#607844: [buildd-tools-devel] Bug#607844: weird interaction between setsid and SIGTSTP

2011-05-31 Thread Kees Cook
Hi Roger, On Mon, May 30, 2011 at 07:41:16PM +0100, Roger Leigh wrote: I was wondering whether or not this is still an issue for upstart? As far as I understand, the build is failing because we run dpkg-buildpackage without a controlling TTY. This has been the historical behaviour of

Bug#607844: [buildd-tools-devel] Bug#607844: weird interaction between setsid and SIGTSTP

2011-05-30 Thread Roger Leigh
On Wed, Dec 22, 2010 at 02:17:45PM -0800, Kees Cook wrote: While trying to build upstart in Ubuntu using the latest sbuild, one of the unit tests failed. This was reduced to a test of raise(SIGTSTP), which wasn't actually stopping the process. In tracking this down, I isolated it as far as

Bug#607844: [buildd-tools-devel] Bug#607844: weird interaction between setsid and SIGTSTP

2010-12-29 Thread Roger Leigh
On Wed, Dec 22, 2010 at 02:17:45PM -0800, Kees Cook wrote: While trying to build upstart in Ubuntu using the latest sbuild, one of the unit tests failed. This was reduced to a test of raise(SIGTSTP), which wasn't actually stopping the process. In tracking this down, I isolated it as far as