Source: ruby-eventmachine Version: 1.0.3-3 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130620 qa-ftbfs Justification: FTBFS on amd64
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory `/«PKGBUILDDIR»/ext/fastfilereader' > /usr/bin/install -c -m 0755 fastfilereaderext.so > /«PKGBUILDDIR»/debian/ruby-eventmachine/usr/lib/ruby/vendor_ruby/1.9.1/x86_64-linux > installing default fastfilereaderext libraries > make[1]: Leaving directory `/«PKGBUILDDIR»/ext/fastfilereader' > dh_installchangelogs -pruby-eventmachine /«PKGBUILDDIR»/CHANGELOG.md upstream > /usr/bin/ruby1.8 -I/usr/lib/ruby/vendor_ruby > /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb > ./tests/em_test_helper.rb:54: warning: already initialized constant > TIMEOUT_INTERVAL > Loaded suite debian/ruby-tests > Started > make: *** wait: No child processes. Stop. > make: *** Waiting for unfinished jobs.... > make: *** wait: No child processes. Stop. > E: Caught signal ‘Terminated’: terminating immediately > .....................................Build killed with signal TERM after 60 > minutes of inactivity > ──────────────────────────────────────────────────────────────────────────────── > Build finished at 20130621-0732 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/06/20/ruby-eventmachine_1.0.3-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
