On 10/18/19 3:14 PM, Ansgar wrote: > On Fri, 2019-10-18 at 14:22 +0200, Sebastiaan Couwenberg wrote: >> On 10/18/19 2:11 PM, Bastian Blank wrote: >>> On Fri, Oct 18, 2019 at 01:53:22PM +0200, Bas Couwenberg wrote: >>>> Please remove icinga2 from armel, mips64el, mipsel & s390x to unblock >>>> testing migration due to missing builds. >>> >>> Those builds fail with different errors. Please handle them properly >>> first. >> >> Why? >> >> These are architectures where icinga2 is unlikely to actually be used. > > I think the build failure on mipsel, armel is missing the `-latomic` > linker flag on these architectures (and possible some others). See [1] > and [2] for similar issues and patches. > > [1] https://bugs.debian.org/914667 > [2] https://bugs.debian.org/907106 > > It probably reasonable to try and see if that workaround is enough.
Thanks for the tip, it doesn't solve the issue unfortunately, see: https://buildd.debian.org/status/fetch.php?pkg=icinga2&arch=armel&ver=2.11.1-2%7Eexp1&stamp=1571416691&raw=0 -latomic is simply added again, it was already present in the previous build: https://buildd.debian.org/status/fetch.php?pkg=icinga2&arch=armel&ver=2.11.1-1&stamp=1571395555&raw=0 > For mips64el and s390x build-dependencies are missing (libboost- > context-dev). Removal from these architectures seems reasonable in > this case; I've not looked why libboost-context-dev (or really > libboost-context1.67-dev) isn't built on these architectures. icinga2 should be removed from armel & mipsel as well. It will return there once the boost and gcc issues are fixed in their respective packages. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1