Hi Jose! (I'm not subscribed to this bug report, please CC me or use 736498-submit...@bugs.debian.org)
> Before
> split and conversion to format version 3 the source didn't build the
> simple test suite (dh_auto_test) as it does now. Moreover, it never
> built successfully on s390x and hurd-i386[0].
The reason why Osmo can't migrate to testing is that libgringotts2 built
successfully in src:gringotts for all architectures before the package
split. Now the system assumes that the new package introduces a
regression and blocks all reverse dependencies from reentering testing.
In my opinion the best way forward is to contact the developers of
libgringotts and fix the test suite upstream.
You can also choose to revert your change to enable the test suite or
you can choose to disable it only on s390x.
Something like that in debian/rules:
DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)
override_dh_auto_test:
ifneq (s390x,$(DEB_HOST_ARCH))
dh_auto_test
endif
You might possibly want to contact your sponsor and ask him, if he can
test your patch/fixes on a s390x porter box.
I would probably disable the test suite on s390x, if that's the only
reason for the current FTBFS, upload a new and fixed revision and close
this bug report. Then I would open a new bug report with a lower
severity and look into the issue again and try to fix it permanently.
As far as we know there were never complains about libgringotts on s390x
thus I think just disabling the suite on s390x should suffice for the
moment.
Regards,
Markus
signature.asc
Description: OpenPGP digital signature
