Forwarded to Debian. More information in the bug there.
Since the cause appears to be a mismatch between upstream's expectation of how to run the test suite vs. the information provided in the packaging to dh_ruby in debian/ruby-test-files.yaml, I felt it best to see what the Debian maintainer wants to do here.
In the meantime, using a dh_override_auto_test of "rspec" seemed like the best minimal patch to use in Ubuntu, since it's a trivial change to debian/rules and runs the test suite the same way that I believe upstream are running it. Whichever path Debian chooses, we can resync.
Forwarded to Debian. More information in the bug there.
Since the cause appears to be a mismatch between upstream's expectation of how to run the test suite vs. the information provided in the packaging to dh_ruby in debian/ ruby-test- files.yaml, I felt it best to see what the Debian maintainer wants to do here.
In the meantime, using a dh_override_ auto_test of "rspec" seemed like the best minimal patch to use in Ubuntu, since it's a trivial change to debian/rules and runs the test suite the same way that I believe upstream are running it. Whichever path Debian chooses, we can resync.