Bug#869064: ruby-factory-girl-rails: FTBFS: ERROR: Test "ruby2.3" failed: Invalid gemspec in [factory_girl_rails.gemspec]: No such file or directory - git
Hi, On Thu, 20 Jul 2017 09:25:46 +0200 Lucas Nussbaumwrote: > Source: ruby-factory-girl-rails > Version: 4.7.0-1 > Severity: serious > Tags: buster sid > User: debian...@lists.debian.org > 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. > From https://ci.debian.net/packages/r/ruby-factory-girl/unstable/amd64/ , it seems the package has been built correctly for quite some time. To be honest, I don't see it ever failing in that list, apart from some tempfails. Also, I wasn't able to reproduce this locally. Hence, closing this issue. signature.asc Description: OpenPGP digital signature
Bug#869064: ruby-factory-girl-rails: FTBFS: ERROR: Test "ruby2.3" failed: Invalid gemspec in [factory_girl_rails.gemspec]: No such file or directory - git
Source: ruby-factory-girl-rails Version: 4.7.0-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org 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): > Invalid gemspec in [factory_girl_rails.gemspec]: No such file or directory - > git > GEM_PATH=debian/ruby-factory-girl-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\ \"factory_girl_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 `' > actionpack (4.2.7.1) > actionview (4.2.7.1) > activesupport (4.2.7.1) > atomic (1.1.16) > bigdecimal (1.2.8) > blankslate (3.1.3) > builder (3.2.2) > did_you_mean (1.0.0) > erubis (2.7.0) > factory_girl (4.7.0) > i18n (0.7.0) > io-console (0.4.5) > json (2.1.0, 1.8.3) > loofah (2.0.3) > minitest (5.10.2) > net-telnet (0.1.1) > nokogiri (1.8.0) > pkg-config (1.2.3) > power_assert (0.2.7) > psych (2.1.0) > rack (1.6.4) > rack-test (0.6.3) > 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) > test-unit (3.2.5) > thor (0.19.4) > thread_safe (0.3.5) > tzinfo (1.2.2) > ERROR: Test "ruby2.3" failed: The full build log is available from: http://aws-logs.debian.net/2017/07/20/ruby-factory-girl-rails_4.7.0-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.