Your message dated Wed, 2 Apr 2014 22:56:32 +0200
with message-id <20140402205632.GA25850@spin>
and subject line not found in ruby-activesupport-3.2 from the rails-3.2 source 
package
has caused the Debian Bug report #738375,
regarding ruby-bootstrap-sass: FTBFS: ERROR: Test "ruby1.9.1" failed.
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 ow...@bugs.debian.org
immediately.)


-- 
738375: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738375
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-bootstrap-sass
Version: 2.3.1.0-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140208 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/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/compilation_test.rb" 
> Warning: you should require 'minitest/autorun' instead.
> Warning: or add 'gem "minitest"' before 'require "minitest/autorun"'
> From:
>   /usr/lib/ruby/1.9.1/test/unit.rb:3:in `<top (required)>'
>   /«PKGBUILDDIR»/test/test_helper.rb:3:in `<top (required)>'
>   /«PKGBUILDDIR»/test/compilation_test.rb:1:in `<top (required)>'
>   /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:15:in `block in <main>'
>   /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:4:in `select'
>   /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:4:in `<main>'
> MiniTest::Unit::TestCase is now Minitest::Test. From 
> /usr/lib/ruby/1.9.1/test/unit/testcase.rb:8:in `<module:Unit>'
> /usr/lib/ruby/1.9.1/test/unit.rb:328:in `autorun': uninitialized class 
> variable @@installed_at_exit in Test::Unit::Runner (NameError)
>       from /usr/lib/ruby/1.9.1/test/unit.rb:640:in `<top (required)>'
>       from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>       from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>       from /«PKGBUILDDIR»/test/test_helper.rb:3:in `<top (required)>'
>       from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>       from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>       from /«PKGBUILDDIR»/test/compilation_test.rb:1:in `<top (required)>'
>       from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>       from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36: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/compilation_test.rb" ]
> -e:1:in `<main>'
> Tasks: TOP => default => test
> (See full trace by running task with --trace)
> ERROR: Test "ruby1.9.1" failed.

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/02/08/ruby-bootstrap-sass_2.3.1.0-2_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 ---
Hi,

This transient bug was caused by a dependency problem with
minitest/test-unit in activesupport-3.2 (v. 3.2.16-2).
It has been solved by the upload of the rails-3.2 package providing
ruby-activesupport-3.2 3.2.16-3+0 and higher.

Cheers,

Cédric

--- End Message ---

Reply via email to