[DRE-maint] Bug#918595: ruby-seed-fu FTBFS with rals 5.2.0

Adrian Bunk bunk at debian.org
Mon Jan 7 17:54:00 GMT 2019


Source: ruby-seed-fu
Version: 2.3.7-1
Severity: serious
Tags: ftbfs
Forwarded: https://github.com/mbleigh/seed-fu/issues/132

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-seed-fu.html

...

Failures:

  1) SeedFu::Seeder should raise an ActiveRecord::RecordNotSaved exception if any records fail to save
     Failure/Error: expect { SeededModel.seed(:fail_to_save => true, :title => "Foo") }.to raise_error(ActiveRecord::RecordNotSaved)
       expected ActiveRecord::RecordNotSaved but nothing was raised
     # ./spec/seeder_spec.rb:173:in `block (2 levels) in <top (required)>'

  2) SeedFu::Writer should successfully write some seeds out to a file and then import them back in
     Failure/Error: FileUtils.rm(@file_name)

     NameError:
       uninitialized constant FileUtils
     # ./spec/writer_spec.rb:9:in `block (2 levels) in <top (required)>'

  3) SeedFu::Writer should support chunking
     Failure/Error: FileUtils.rm(@file_name)

     NameError:
       uninitialized constant FileUtils
     # ./spec/writer_spec.rb:9:in `block (2 levels) in <top (required)>'

  4) SeedFu::Writer should support specifying the output to use 'seed_once' rather than 'seed'
     Failure/Error: FileUtils.rm(@file_name)

     NameError:
       uninitialized constant FileUtils
     # ./spec/writer_spec.rb:9:in `block (2 levels) in <top (required)>'

Deprecation Warnings:

Using `should` from rspec-expectations' old `:should` syntax without explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or explicitly enable `:should` with `config.expect_with(:rspec) { |c| c.syntax = :should }` instead. Called from /build/1st/ruby-seed-fu-2.3.7/spec/runner_spec.rb:7:in `block (2 levels) in <top (required)>'.


If you need more of the backtrace for any of these deprecations to
identify where to make the necessary changes, you can configure
`config.raise_errors_for_deprecations!`, and it will turn the
deprecation warnings into errors, giving you the full backtrace.

1 deprecation warning total

Finished in 0.30367 seconds (files took 1.58 seconds to load)
17 examples, 4 failures



More information about the Pkg-ruby-extras-maintainers mailing list