[DRE-maint] Bug#795717: ruby-thor: FTBFS: ArgumentError: wrong number of arguments (0 for 1+)
Chris Lamb
lamby at debian.org
Sun Aug 16 12:20:11 UTC 2015
Source: ruby-thor
Version: 0.19.1-1
Severity: serious
Justification: fails to build from source
Dear Maintainer,
ruby-thor fails to build from source on unstable/amd64:
[..]
┌──────────────────────────────────────────────────────────────────────────────┐
│ Run tests for ruby2.1 from debian/ruby-tests.rake
│
└──────────────────────────────────────────────────────────────────────────────┘
RUBYLIB=/tmp/buildd/ruby-thor-0.19.1/debian/ruby-thor/usr/lib/ruby/vendor_ruby:.
rake2.1 -f debian/ruby-tests.rake
/usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*_spec.rb
..................WARNING: Using the `raise_error` matcher without
providing a specific error or message risks false positives, since
`raise_error` will match when Ruby raises a `NoMethodError`,
`NameError` or `ArgumentError`, potentially allowing the expectation
to pass without even executing the method you are intending to call.
Instead consider providing a specific error class or message. This
message can be supressed by setting:
`RSpec::Expectations.configuration.warn_about_potential_false_positives
= false`. Called from
/tmp/buildd/ruby-thor-0.19.1/spec/actions_spec.rb:124:in `block (4
levels) in <top (required)>'.
.....................................................................................F.......WARNING:
Using the `raise_error` matcher without providing a specific error or
message risks false positives, since `raise_error` will match when
Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`,
potentially allowing the expectation to pass without even executing
the method you are intending to call. Instead consider providing a
specific error class or message. This message can be supressed by
setting:
`RSpec::Expectations.configuration.warn_about_potential_false_positives
= false`. Called from
/tmp/buildd/ruby-thor-0.19.1/spec/group_spec.rb:31:in `block (3
levels) in <top (required)>'.
...................................................**.......................................................................................................................................................................
Pending: (Failures listed here are expected and do not affect your
suite's status)
1) The library itself has no malformed whitespace
# Temporarily skipped with xit
# ./spec/quality_spec.rb:51
2) The library itself uses double-quotes consistently in specs
# Temporarily skipped with xit
# ./spec/quality_spec.rb:64
Failures:
1) Thor::Command#run runs a command by calling a method in the given
instance
Failure/Error: expect(dub).to receive(:can_has).and_return {
|*args| args }
ArgumentError:
wrong number of arguments (0 for 1+)
# ./spec/command_spec.rb:61:in `block (3 levels) in <top
(required)>'
Finished in 2.44 seconds (files took 0.75741 seconds to load)
331 examples, 1 failure, 2 pending
Failed examples:
rspec ./spec/command_spec.rb:59 # Thor::Command#run runs a command by
calling a method in the given instance
/usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*_spec.rb failed
ERROR: Test "ruby2.1" failed. Exiting.
dh_auto_install: dh_ruby --install
/tmp/buildd/ruby-thor-0.19.1/debian/ruby-thor returned exit code 1
debian/rules:15: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit
status 2
[..]
The full build log is attached or can be viewed here:
https://reproducible.debian.net/logs/unstable/amd64/ruby-thor_0.19.1-1.build1.log.gz
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` lamby at debian.org / chris-lamb.co.uk
`-
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ruby-thor.0.19.1-1.unstable.amd64.log.txt
URL: <http://lists.alioth.debian.org/pipermail/pkg-ruby-extras-maintainers/attachments/20150816/f8964964/attachment-0001.txt>
More information about the Pkg-ruby-extras-maintainers
mailing list