[DRE-maint] Bug#728626: ruby-em-spec: FTBFS: ERROR: Test "ruby2.0" failed: /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:51:in `require': cannot load such file -- rubyeventmachine (LoadError)

[David Suárez]

Source: ruby-em-spec
Version: 0.2.6-1
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20131103 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  fakeroot debian/rules binary
> dh binary --buildsystem=ruby --with ruby
>    dh_testroot -O--buildsystem=ruby
>    dh_prep -O--buildsystem=ruby
>    dh_auto_install -O--buildsystem=ruby
> /usr/lib/ruby/vendor_ruby/gem2deb.rb:17: warning: setting Encoding.default_external
>   Entering dh_ruby --install
> Invalid gemspec in [em-spec.gemspec]: No such file or directory - git ls-files
> install -d /«PKGBUILDDIR»/debian/ruby-em-spec/usr/lib/ruby/vendor_ruby
> install -D -m644 /«PKGBUILDDIR»/lib/ext/fiber18.rb /«PKGBUILDDIR»/debian/ruby-em-spec/usr/lib/ruby/vendor_ruby/ext/fiber18.rb
> install -D -m644 /«PKGBUILDDIR»/lib/em-spec/bacon.rb /«PKGBUILDDIR»/debian/ruby-em-spec/usr/lib/ruby/vendor_ruby/em-spec/bacon.rb
> install -D -m644 /«PKGBUILDDIR»/lib/em-spec/version.rb /«PKGBUILDDIR»/debian/ruby-em-spec/usr/lib/ruby/vendor_ruby/em-spec/version.rb
> install -D -m644 /«PKGBUILDDIR»/lib/em-spec/test.rb /«PKGBUILDDIR»/debian/ruby-em-spec/usr/lib/ruby/vendor_ruby/em-spec/test.rb
> install -D -m644 /«PKGBUILDDIR»/lib/em-spec/rspec.rb /«PKGBUILDDIR»/debian/ruby-em-spec/usr/lib/ruby/vendor_ruby/em-spec/rspec.rb
> /usr/bin/ruby1.9.1 -I/usr/lib/ruby/vendor_ruby /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb
> /usr/bin/ruby1.9.1 -I"lib:test" -I"/usr/lib/ruby/vendor_ruby" "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/test_spec.rb" 
> Run options: 
> 
> # Running tests:
> 
> .........
> 
> Finished tests in 8.011672s, 1.1234 tests/s, 0.6241 assertions/s.
> 
> 9 tests, 5 assertions, 0 failures, 0 errors, 0 skips
> /usr/bin/ruby2.0 -I/usr/lib/ruby/vendor_ruby /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb
> /usr/bin/ruby2.0 -I"lib:test" -I"/usr/lib/ruby/vendor_ruby" "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/test_spec.rb" 
> Unable to load the EventMachine C extension; To use the pure-ruby reactor, require 'em/pure_ruby'
> /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:51:in `require': cannot load such file -- rubyeventmachine (LoadError)
> 	from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:51:in `require'
> 	from /usr/lib/ruby/vendor_ruby/eventmachine.rb:8:in `<top (required)>'
> 	from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:51:in `require'
> 	from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:51:in `require'
> 	from /«PKGBUILDDIR»/test/test_spec.rb:5:in `<top (required)>'
> 	from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:51:in `require'
> 	from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:51:in `require'
> 	from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:15:in `block in <main>'
> 	from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:4:in `select'
> 	from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:4:in `<main>'
> rake aborted!
> Command failed with status (1): [ruby -I"lib:test" -I"/usr/lib/ruby/vendor_ruby" "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/test_spec.rb" ]
> -e:1:in `<main>'
> Tasks: TOP => default => test
> (See full trace by running task with --trace)
> ERROR: Test "ruby2.0" failed: 
> dh_auto_install: dh_ruby --install /«PKGBUILDDIR»/debian/ruby-em-spec returned exit code 1
> make: *** [binary] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/11/03/ruby-em-spec_0.2.6-1_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.