Hello,
After two days of +1 maint, I worked on/resolved the following issues. Most time was spent figuring out what's wrong with iotjs (or rather it's vendorized dependency on jerryscript), as I've had worked on this before it was almost 100 days old and it was not resolved in the meantime. After quite some back and forth with upstream (https://github.com/jerryscript-project/jerryscript/issues/4431) I figured out that the "-D_FORTIFY_SOURCE=2 -O2" flags triggered compiler errors on s390x. This did not happen with the upstream build, because they use -Os (which disables fortification). So as a workaround I changed the package's CMake flags in debian/rules:
CMAKE_OPTIONS+=-DCMAKE_BUILD_TYPE=MinSizeRelautopkgtest:
OK - dnspython vs python-ecdsa/amd64 (passes locally)
OK - dgit vs groff/armhf (FAIL timed out)
OK - django-ldapdb vs python-django/armhf (passes locally)
OK - libhtml-formfu-perl vs libreadonly-perl/armhf ("unknown" version)
OK - linux-show-player vs python-rtmidi/amd64,arm64,i386,ppc64el,s390x ("unknown" version) => state "Neutral"
OK - patroni vs postgresql-common/s390x (adding etcd trigger)
OK - dgit vs groff/armhf (FAIL timed out)
OK - django-ldapdb vs python-django/armhf (passes locally)
OK - libhtml-formfu-perl vs libreadonly-perl/armhf ("unknown" version)
OK - linux-show-player vs python-rtmidi/amd64,arm64,i386,ppc64el,s390x ("unknown" version) => state "Neutral"
OK - patroni vs postgresql-common/s390x (adding etcd trigger)
FTBFS:
OK - iotjs/s390x (vendorized jerryscript)
Merge:
OK - intel-vaapi-drivers, sync DFSG version. Shaders are available in multiverse as intel-vaapi-driver-shaders.
OK - libfiu, merged, keep failing dh_auto_tests disabled
OK - intel-vaapi-drivers, sync DFSG version. Shaders are available in multiverse as intel-vaapi-driver-shaders.
OK - libfiu, merged, keep failing dh_auto_tests disabled
Cheers,
Lukas
