Source: pcre2 Version: 10.34-1 Severity: serious Hi,
pcre2 FTBFS on armel: https://buildd.debian.org/status/fetch.php?pkg=pcre2&arch=armel&ver=10.34-1&stamp=1574962559&raw=0 FAIL: RunTest ============= PCRE2 C library tests using test data from ./testdata PCRE2 version 10.34 2019-11-21 ---- Testing 8-bit library ---- Test 0: Unchecked pcre2test argument tests (to improve coverage) OK Test 1: Main non-UTF, non-UCP functionality (compatible with Perl >= 5.10) OK Segmentation fault ** pcre2test failed - check testtry FAIL RunTest (exit status: 1) ============================================================================ Testsuite summary for PCRE2 10.34 ============================================================================ # TOTAL: 3 # PASS: 2 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 ============================================================================ See ./test-suite.log ============================================================================ The missing armel build and the binary upload prevent pcre2 from migrating to testing, blocking other packages. If pcre2 used a symbols file instead of dh_makeshlibs -V, this would be less of an issue, as it wouldn't block other packages from testing migration. Regards, Michael -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
