[Pkg-nagios-devel] icinga2 backport?
sebastic at xs4all.nl
Wed Oct 10 17:57:28 BST 2018
On 10/10/18 6:30 PM, Chris Boot wrote:
> On 05/10/2018 05:45, Sebastiaan Couwenberg wrote:
>>> Thanks. With the -backports branches now in the package repository, and
>>> the updated Vcs-Git URLs, feel free to upload them.
>> Don't forget to push your tags.
> Hi Bas,
> I pushed the tags once I got the ACCEPTED messages, just in case the
> backports team rejected them.
> I see, however, that the builds of icinga2 on armel and armhf have
> failed. I'm in unfamiliar territory here with C++ and Boost libraries;
> is this something you've seen before, or do I need to do some digging on
> a porterbox?
I'm only aware of issues on MIPS* for which a patch is present:
The FTBFS on armel is caused by a test failure:
20/90 Test #19: base-base_dictionary/remove
.............................................***Failed 0.08 sec
Running 1 test case...
unknown location(0): fatal error: in "base_dictionary/remove": memory
access violation at address: 0x000026f8: no mapping at fault address
/<<PKGBUILDDIR>>/test/base-dictionary.cpp(128): last checkpoint
*** 1 failure is detected in the test module "Master Test Suite"
On armhf all the tests fail due to memory access violations.
I don't know if people actually use icinga2 on those architectures, but
I consider it reasonable to ignore test failures on those architectures,
at least until a users of icinga2 on those architectures actually
complains about icinga2 not working correctly.
For those kind of issues I usually use something like:
DEB_BUILD_ARCH ?= $(shell dpkg-architecture -qDEB_BUILD_ARCH)
ifneq (,$(filter $(DEB_BUILD_ARCH),armel armhf))
dh_auto_test || echo "Ignoring test failures"
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 833 bytes
Desc: OpenPGP digital signature
More information about the Pkg-nagios-devel