[DRE-maint] Bug#888194: ruby-safe-yaml: FTBFS on ruby2.5: uninitialized constant SafeYAML::Parse::Date::DateTime
Chris West (Faux)
debian at fau.xxx
Tue Jan 23 20:40:48 UTC 2018
Source: ruby-safe-yaml
Version: 1.0.4-1
Severity: important
User: debian-ruby at lists.debian.org
Usertags: ruby2.5
Dear Maintainer,
This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.
There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition
Build log excerpt:
Finished in 0.00114 seconds (files took 0.12105 seconds to load)
2 examples, 0 failures
/usr/bin/ruby2.5 /usr/bin/gem2deb-test-runner
┌──────────────────────────────────────────────────────────────────────────────┐
│ Checking Rubygems dependency resolution on ruby2.5 │
└──────────────────────────────────────────────────────────────────────────────┘
GEM_PATH=debian/ruby-safe-yaml/usr/share/rubygems-integration/all:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all ruby2.5 -e gem\ \"safe_yaml\"
┌──────────────────────────────────────────────────────────────────────────────┐
│ Run tests for ruby2.5 from debian/ruby-tests.rb │
└──────────────────────────────────────────────────────────────────────────────┘
RUBYLIB=/build/ruby-safe-yaml-1.0.4/debian/ruby-safe-yaml/usr/lib/ruby/vendor_ruby:. GEM_PATH=debian/ruby-safe-yaml/usr/share/rubygems-integration/all:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all ruby2.5 debian/ruby-tests.rb
/build/ruby-safe-yaml-1.0.4/lib/safe_yaml/parse/date.rb:22:in `<class:Date>': uninitialized constant SafeYAML::Parse::Date::DateTime (NameError)
Did you mean? SafeYAML::Parse::Date::DATE_MATCHER
from /build/ruby-safe-yaml-1.0.4/lib/safe_yaml/parse/date.rb:3:in `<class:Parse>'
from /build/ruby-safe-yaml-1.0.4/lib/safe_yaml/parse/date.rb:2:in `<module:SafeYAML>'
from /build/ruby-safe-yaml-1.0.4/lib/safe_yaml/parse/date.rb:1:in `<top (required)>'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
from /build/ruby-safe-yaml-1.0.4/lib/safe_yaml/load.rb:14:in `<top (required)>'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
from /build/ruby-safe-yaml-1.0.4/spec/spec_helper.rb:29:in `<top (required)>'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
from /build/ruby-safe-yaml-1.0.4/spec/libyaml_checker_spec.rb:1:in `<top (required)>'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1435:in `load'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1435:in `block in load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1433:in `each'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1433:in `load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:100:in `setup'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:86:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:71:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:45:in `invoke'
from /usr/bin/rspec:4:in `<main>'
Ruby 2.5.0, YAML: syck (3.0.2) (libyaml: N/A), Monkeypatch: true
debian/ruby-tests.rb:16:in `block in <main>': unhandled exception
from debian/ruby-tests.rb:14:in `each'
from debian/ruby-tests.rb:14:in `<main>'
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install /build/ruby-safe-yaml-1.0.4/debian/ruby-safe-yaml returned exit code 1
debian/rules:6: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
Full build log:
https://rbuild.fau.xxx/2018-01-23/ruby-safe-yaml.log
Please fix it!
Cheers,
Chris.
More information about the Pkg-ruby-extras-maintainers
mailing list