[DRE-maint] Bug#759924: ruby-fast-gettext: FTBFS: ERROR: Test "ruby2.1" failed: /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- protected_attributes (LoadError)

[Lucas Nussbaum]

Source: ruby-fast-gettext
Version: 0.8.1-1
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20140830 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):
> /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- protected_attributes (LoadError)
> 	from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require'
> 	from /«PKGBUILDDIR»/debian/ruby-fast-gettext/usr/lib/ruby/vendor_ruby/fast_gettext/translation_repository/db_models/translation_key.rb:1:in `<top (required)>'
> 	from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require'
> 	from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require'
> 	from /«PKGBUILDDIR»/debian/ruby-fast-gettext/usr/lib/ruby/vendor_ruby/fast_gettext/translation_repository/db.rb:52:in `require_models'
> 	from /«PKGBUILDDIR»/spec/fast_gettext/translation_repository/db_spec.rb:6:in `<top (required)>'
> 	from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require'
> 	from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55: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.1" failed: 

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/08/30/ruby-fast-gettext_0.8.1-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. The build
was done with DEB_BUILD_OPTIONS="parallel=4", so if your packaging tries
to support this, it might be a good idea to explore whether this might
be the cause of the failure.