Your message dated Mon, 7 Aug 2017 11:52:10 +0900 with message-id <20170807025209.lp2xeybexza7g...@lilith.infoblue.home> and subject line Re: ruby-serverspec: FTBFS: can't satisfy 'net-ssh (< 4.0, >= 2.7)', already activated 'net-ssh-4.1.0' (Gem::LoadError) has caused the Debian Bug report #869177, regarding ruby-serverspec: FTBFS: can't satisfy 'net-ssh (< 4.0, >= 2.7)', already activated 'net-ssh-4.1.0' (Gem::LoadError) 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.) -- 869177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869177 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: ruby-serverspec Version: 2.37.2-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170721 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 [serverspec.gemspec]: No such file or directory - git > GEM_PATH=debian/ruby-serverspec/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\ \"serverspec\" > /usr/lib/ruby/2.3.0/rubygems/specification.rb:1436:in `block in > activate_dependencies': can't satisfy 'net-ssh (< 4.0, >= 2.7)', already > activated 'net-ssh-4.1.0' (Gem::LoadError) > 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>' > bcrypt_pbkdf (1.0.0) > bigdecimal (1.2.8) > did_you_mean (1.0.0) > diff-lcs (1.3) > ffi (1.9.10) > io-console (0.4.5) > json (1.8.3) > minitest (5.10.2) > multi_json (1.12.1) > net-scp (1.2.1) > net-ssh (4.1.0) > net-telnet (0.1.1) > power_assert (0.2.7) > psych (2.1.0) > rake (12.0.0) > rbnacl (5.0.0) > rdoc (4.2.1) > rspec (3.5.0) > rspec-core (3.5.3) > rspec-expectations (3.5.0) > rspec-its (1.2.0) > rspec-mocks (3.5.0) > rspec-support (3.5.0) > specinfra (2.66.0) > test-unit (3.2.5) > thread_order (1.1.0) > ERROR: Test "ruby2.3" failed: The full build log is available from: http://aws-logs.debian.net/2017/07/21/ruby-serverspec_2.37.2-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.
--- End Message ---
--- Begin Message ---Control: unblock -1 by 869175 Control: affects 869175 ruby-serverspec serverspec-runner fixed by ruby-specinfra. -- Regards, dai GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668Esignature.asc
Description: PGP signature
--- End Message ---