Bug#855931: ruby-eventmachine: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity

2017-03-08 Thread Antonio Terceiro
On Mon, Mar 06, 2017 at 01:12:12PM +0100, Lucas Nussbaum wrote: > On 04/03/17 at 12:49 +0530, Pirate Praveen wrote: > > On Thu, 23 Feb 2017 14:28:20 +0100 Lucas Nussbaum wrote: > > > During a rebuild of all packages in stretch (in a stretch chroot, not a > > > sid chroot), your

Bug#855931: ruby-eventmachine: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity

2017-03-06 Thread Lucas Nussbaum
On 04/03/17 at 12:49 +0530, Pirate Praveen wrote: > On Thu, 23 Feb 2017 14:28:20 +0100 Lucas Nussbaum wrote: > > During a rebuild of all packages in stretch (in a stretch chroot, not a > > sid chroot), your package failed to build on amd64. > > I could not reproduce it on a

Bug#855931: ruby-eventmachine: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity

2017-03-03 Thread Pirate Praveen
On Thu, 23 Feb 2017 14:28:20 +0100 Lucas Nussbaum wrote: > During a rebuild of all packages in stretch (in a stretch chroot, not a > sid chroot), your package failed to build on amd64. I could not reproduce it on a freshly created stretch chroot with sbuild. sbuild -d stretch

Bug#855931: ruby-eventmachine: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity

2017-02-23 Thread Lucas Nussbaum
Source: ruby-eventmachine Version: 1.0.7-4 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170221 qa-ftbfs Justification: FTBFS in stretch on amd64 Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a sid chroot), your package