Praveen A escreveu isso aí: > 2011/9/20 Praveen A <pravi.a@gmail.com>: > > 2011/9/20 Cédric Boutillier <cedric.boutillier@gmail.com>: > >> I had a similar problem with ruby-pdf-reader (the spec were not included > >> at all). Since the files are actually in upstream repositry, you could > >> probably base your package on the tarball extracted from github instead > >> of the gem. > > > > I thought about it, but they didn't tag the latest version :( Latest > > gem version is 1.1.2 but github has only 1.1.1 tag. One option is to > > package 1.1.1 version using github tarball, but I will wait a few days > > if they fix it upstream or at least respond to the bug. > > Upstream fixed it and made a new release already - that was pretty > impressive! I re-based git repo to new version. > > Now there is another failure. But gem2deb didn't catch it as a failure > - I think it is a bug in gem2deb. > > or is it actually expected to fail? Can someone confirm it? > > /usr/bin/ruby1.8 -I/usr/lib/ruby/vendor_ruby > /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb > Running tests for ruby1.8 using debian/ruby-tests.rb... > ................... > > Cutest::AssertionFailed: "\e[01;36m\n\nCutest::AssertionFailed: > \e[1;33mexpression returned false\n\n\e[00m\e[00m- assert > false\e[01;30m ./test/fixtures/failure.rb +2\n\e[00m\n" != > "\e[01;36m\n\nCutest::AssertionFailed: \e[1;33mexpression returned > false\n\n\e[00m- assert false\e[01;30m test/fixtures/failure.rb > +2\n\e[00m\n" > > - assert_equal(stdout, expected) ./test/run.rb +32 If you run that command manually, what is the exit status? -- Antonio Terceiro <terceiro@debian.org>
Attachment:
signature.asc
Description: Digital signature