Package: libmicrohttpd Version: 0.9.37+dfsg-1 Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu ubuntu-patch wily
Hello, A while ago the test suite was disabled during package because it fails on kfreebsd. However, that's bad because it doesn't tell us when the package regresses on other architectures, nor does it tell you when it starts succeeding on kfreebsd. It would be much better to always run the tests, and just not make them fatal on kfreebsd. Debdiff attached. (Background: We now use libmicrohttpd in systemd for remote journal support, and I'd like to get this package in the best shape possible). Thanks for considering, Martin -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
* debian/rules: Run the test suite and make it fatal on non-kfreebsd (where
it's known to fail).
diff -Nru libmicrohttpd-0.9.37+dfsg/debian/rules
libmicrohttpd-0.9.37+dfsg/debian/rules
--- libmicrohttpd-0.9.37+dfsg/debian/rules 2014-07-08 14:35:40.000000000
+0200
+++ libmicrohttpd-0.9.37+dfsg/debian/rules 2015-08-28 08:54:02.000000000
+0200
@@ -1,5 +1,12 @@
#!/usr/bin/make -f
+# test suite is known to fail on kfreebsd, don't fail build on that
+TESTSUITE_FAIL_CMD=exit 1
+ifneq ($(filter $(DEB_BUILD_ARCH), kfreebsd-amd64 kfreebsd-i386),)
+TESTSUITE_FAIL_CMD=exit 0
+endif
+
+
%:
dh ${@} --with autoreconf
@@ -10,7 +17,7 @@
rm -f debian/tmp/usr/lib/*/*.la
override_dh_auto_test:
- # disabled
+ dh_auto_test || $(TESTSUITE_FAIL_CMD)
override_dh_install:
dh_install --fail-missing
signature.asc
Description: Digital signature
