On Wed, 2013-03-13 at 21:57 +0100, Cédric Boutillier wrote: > On Wed, Mar 13, 2013 at 05:36:50PM +0000, Christopher Baines wrote: > > I have now managed to setup cowbuilder and attempt to reproduce the > > failing you mention here [2], I have tried building the package (from > > the git repo, reset to before I apply the relevant patch), in testing > > and sid for amd64 and i386, but I have not seen anything in the output > > that looks to me like a failing test. What cowbuilder setup did you > > use to produce the test failure? > > That is because the tests are not run: when building with > git-buildpackage, I have the following message: > > /usr/bin/ruby1.8 -I/usr/lib/ruby/vendor_ruby /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb > No examples matching ./spec/*_spec.rb could be found > /usr/bin/ruby1.9.1 -I/usr/lib/ruby/vendor_ruby /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb > No examples matching ./spec/*_spec.rb could be found > > In debian/ruby-tests.rake, the regular expression for the tests does not > match any file. Changing it to './spec/**/*_spec.rb' make the tests run, > but fail (two of them) with Ruby1.9 without the encoding fixing patch. > With the three patches, they all pass. This is fixed now on github. https://github.com/cbaines/ruby-dbf The only possible issue I know of with the dbf package, is that the related tests for the ruby-georuby [1] package fail, when run in a chroot environment. I have also been looking at the other two packages osmlib-base, and sys-proctable. I have contacted the upstream developers for osmlib-base about the project, as the gem release does not include the latest code (latest being a year old, and from another developer). The sys-proctable gem seems to break gem2deb for me, and I have not looked in to this further yet, but am planning to in the next free moment. 1: https://github.com/cbaines/ruby-georuby
Attachment:
signature.asc
Description: This is a digitally signed message part