Your message dated Wed, 1 Jan 2014 15:03:03 +0100
with message-id <[email protected]>
and subject line Re: ruby-hpricot: 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 -- fast_xs
has caused the Debian Bug report #725557,
regarding ruby-hpricot: 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 -- fast_xs (LoadError)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
725557: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725557
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: ruby-hpricot
Version: 0.8.6-3
Severity: serious
Tags: jessie sid
User: [email protected]
Usertags: qa-ftbfs-20131006 qa-ftbfs ruby2-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory `/«PKGBUILDDIR»/ext/hpricot_scan'
> /usr/bin/install -c -m 0755 hpricot_scan.so ./.gem.20131005-13585-15so5bd
> installing default hpricot_scan libraries
> make[1]: Leaving directory `/«PKGBUILDDIR»/ext/hpricot_scan'
> dh_installchangelogs -pruby-hpricot /«PKGBUILDDIR»/CHANGELOG upstream
> /usr/bin/ruby1.9.1 -I/usr/lib/ruby/vendor_ruby 
> /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb
> Run options: 
> 
> # Running tests:
> 
> ....................................................................................
> 
> Finished tests in 1.690554s, 49.6878 tests/s, 3656.7886 assertions/s.
> 
> 84 tests, 6182 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/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:51:in `require': 
> cannot load such file -- fast_xs (LoadError)
>       from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:51:in 
> `require'
>       from 
> /«PKGBUILDDIR»/debian/ruby-hpricot/usr/lib/ruby/vendor_ruby/hpricot/builder.rb:2: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»/debian/ruby-hpricot/usr/lib/ruby/vendor_ruby/hpricot.rb:26: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_alter.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 debian/ruby-tests.rb:3:in `block in <main>'
>       from debian/ruby-tests.rb:3:in `each'
>       from debian/ruby-tests.rb:3:in `<main>'
> ERROR: Test "ruby2.0" failed: 
> dh_auto_install: dh_ruby --install /«PKGBUILDDIR»/debian/tmp returned exit 
> code 1
> make: *** [binary] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/10/06/ruby-hpricot_0.8.6-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.

--- End Message ---
--- Begin Message ---
Fixed with a binNMU to ruby-fast-xs, and an upload of ruby-hpricot
0.8.6-4.

--- End Message ---

Reply via email to