Bug#737734: ruby-rspec-core debian package breaks rspec-puppet

[Cédric Boutillier]

Package: ruby-rspec-core
Followup-For: Bug #737734
Control: retitle -1 wrong file_path metadata, breaking file_path filters
Control: tag -1 pending


Hi,

ruby-rspec-puppet is broken because of its conditional inclusion of
modules in examples, using file_path filters.
RSpec file_path metadata were wrong because of a Regexp that does not
match the installation path of RSpec in Debian.

The fix should also fix some issues in the display of spec results.

Cheers,

Cédric


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#737734: ruby-rspec-core debian package breaks rspec-puppet

[Laurent Bigonville]

Package: ruby-rspec-core
Version: 2.14.7-1
Severity: important

Hi,

rspec-puppet seems to be broken when using rspec-core debian package.

When using the rspec-core gem, everything is working fine.

  1) foo 
 Failure/Error: Unable to find matching line from backtrace
 NoMethodError:
   undefined method `contain_class' for 
#RSpec::Core::ExampleGroup::Nested_1:0x00029357e0
 # /usr/lib/ruby/vendor_ruby/rspec/matchers/method_missing.rb:9:in 
`method_missing'
 # ./spec/classes/foo_spec.rb:5:in `block (2 levels) in top (required)'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:114:in `instance_eval'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:114:in `block in run'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:254:in 
`with_around_each_hooks'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:111:in `run'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:390:in `block in 
run_examples'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:386:in `map'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:386:in 
`run_examples'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:371:in `run'
 # /usr/lib/ruby/vendor_ruby/rspec/core/command_line.rb:28:in `block (2 
levels) in run'
 # /usr/lib/ruby/vendor_ruby/rspec/core/command_line.rb:28:in `map'
 # /usr/lib/ruby/vendor_ruby/rspec/core/command_line.rb:28:in `block in run'
 # /usr/lib/ruby/vendor_ruby/rspec/core/reporter.rb:58:in `report'
 # /usr/lib/ruby/vendor_ruby/rspec/core/command_line.rb:25:in `run'
 # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:80:in `run'
 # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:17:in `block in autorun'

A simple test case is attached to this bug.

Cheers,

Laurent Bigonville

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.12-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages ruby-rspec-core depends on:
ii  ruby  1:1.9.3.1
ii  ruby-rspec-expectations   2.14.2-1
ii  ruby-rspec-mocks  2.14.3-1
ii  ruby1.9.1 [ruby-interpreter]  1.9.3.484-2
ii  ruby2.0 [ruby-interpreter]2.0.0.484-1

ruby-rspec-core recommends no packages.

Versions of packages ruby-rspec-core suggests:
ii  ruby-rspec  2.14.1-1

-- no debconf information


foo.tar.gz
Description: application/gzip