Source: ruby-cucumber-rails Version: 1.4.3-1 Severity: serious Tags: buster sid User: [email protected] Usertags: qa-ftbfs-20170720 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/ruby2.3 /usr/bin/gem2deb-test-runner > > ┌──────────────────────────────────────────────────────────────────────────────┐ > │ Checking Rubygems dependency resolution on ruby2.3 > │ > └──────────────────────────────────────────────────────────────────────────────┘ > > GEM_PATH=debian/ruby-cucumber-rails/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all > ruby2.3 -e gem\ \"cucumber-rails\" > /usr/lib/ruby/2.3.0/rubygems/specification.rb:2287:in `raise_if_conflicts': > Unable to activate rails-dom-testing-1.0.6, because nokogiri-1.8.0 conflicts > with nokogiri (~> 1.6.0) (Gem::ConflictError) > from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1408:in `activate' > from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1442:in `block in > activate_dependencies' > from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1428:in `each' > from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1428:in > `activate_dependencies' > from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1410:in `activate' > from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1442:in `block in > activate_dependencies' > from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1428:in `each' > from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1428:in > `activate_dependencies' > from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1410:in `activate' > from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1442:in `block in > activate_dependencies' > from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1428:in `each' > from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1428:in > `activate_dependencies' > from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1410:in `activate' > from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:68:in `block > in gem' > from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:67:in > `synchronize' > from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:67:in `gem' > from -e:1:in `<main>' > actionmailer (4.2.7.1) > actionpack (4.2.7.1) > actionview (4.2.7.1) > activejob (4.2.7.1) > activemodel (4.2.7.1) > activerecord (4.2.7.1) > activesupport (4.2.7.1) > addressable (2.4.0) > arel (6.0.3) > atomic (1.1.16) > bigdecimal (1.2.8) > blankslate (3.1.3) > builder (3.2.2) > bundler (1.15.1) > capybara (2.10.2) > concurrent-ruby (1.0.0) > cucumber (2.4.0) > cucumber-core (1.5.0) > cucumber-wire (0.0.1) > did_you_mean (1.0.0) > diff-lcs (1.3) > erubis (2.7.0) > fuubar (2.0.0) > gherkin (4.0.0) > globalid (0.3.6) > hike (1.2.1) > i18n (0.7.0) > io-console (0.4.5) > json (2.1.0, 1.8.3) > launchy (2.3.0) > loofah (2.0.3) > mail (2.6.4) > mime-types (2.6.1) > minitest (5.10.2) > molinillo (0.5.0) > multi_json (1.12.1) > multi_test (0.1.2) > net-http-persistent (2.9.4) > net-telnet (0.1.1) > nokogiri (1.8.0) > pkg-config (1.2.3) > polyglot (0.3.4) > power_assert (0.2.7) > psych (2.1.0) > rack (1.6.4) > rack-test (0.6.3) > rails (4.2.7.1) > rails-deprecated_sanitizer (1.0.3) > rails-dom-testing (1.0.6) > rails-html-sanitizer (1.0.3) > railties (4.2.7.1) > rake (12.0.0) > rdoc (4.2.1) > rspec (3.5.0) > rspec-core (3.5.3) > rspec-expectations (3.5.0) > rspec-mocks (3.5.0) > rspec-support (3.5.0) > ruby-progressbar (1.4.2) > sprockets (3.7.0) > sprockets-rails (2.3.2) > test-unit (3.2.5) > thor (0.19.4) > thread_order (1.1.0) > thread_safe (0.3.5) > tilt (2.0.1) > treetop (1.6.7) > tzinfo (1.2.2) > xpath (2.0.0) > ERROR: Test "ruby2.3" failed. The full build log is available from: http://aws-logs.debian.net/2017/07/20/ruby-cucumber-rails_1.4.3-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.
