Le 24 février 2012 11:24, Cédric Boutillier
<cedric.boutillier@gmail.com> a écrit :
It seems that the behavior of MiniTest::Unit.after_tests was broken, du
https://github.com/seattlerb/minitest/pull/84
This should be fixed in the latest version of minitest. So hopefully,
you can remove the workaround when a newer version of ruby-minitest is
uploaded.
Thanks for the link.
In the mean time, perhaps you could also add the removal of tests/tmp in
override_dh_clean. Indeed, git-buildpackage will complain when trying to
build the package twice, because there are files in tests/tmp left over
after the tests for ruby1.9.1.
According to the manpage of dh_clean I should add a d/clean file to list
additional files to be cleaned. Should I create d/clean as part of
ruby-minitest_after_tests patch so I do not forget to delete when ruby-minitest
is fixed or is it a bad idea?
It is better not to tag the debian version in the repo before the actual
upload, because otherwise, the package goes of the radar of the Package
Entropy Tracker (http://pet.debian.net/pkg-ruby-extras/pet.cgi), as it
is then considered as being already uploaded.
Ok.
I noticed also that Lintian mentions that you could remove the '.' at
the end of the short description, and that a patch is missing its DEP-3
header.
Corrected.
Cédric