Bug#917592: libterm-termkey-perl: FTBFS (failing tests)

[Santiago Vila]

Package: src:libterm-termkey-perl
Version: 0.16-3
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:

--------------------------------------------------------------------------------
[...]
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   dh_auto_configure -a
	perl -I. Build.PL --installdirs vendor --config "optimize=-g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" --config "ld=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro"
Use of uninitialized value $cflags in split at Build.PL line 42.
Created MYMETA.yml and MYMETA.json
Creating new 'Build' script for 'Term-TermKey' version '0.16'
   dh_auto_build -a
	perl Build
Building Term-TermKey
x86_64-linux-gnu-gcc -I/usr/lib/x86_64-linux-gnu/perl/5.28/CORE -DVERSION="0.16" -DXS_VERSION="0.16" -fPIC -c -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o lib/Term/TermKey.o lib/Term/TermKey.c
lib/Term/TermKey.xs: In function 'XS_Term__TermKey_set_buffer_size':
lib/Term/TermKey.xs:525:13: warning: too many arguments for format [-Wformat-extra-args]

[... snipped ...]

ok 6 - $key->col after mouse press
ok
t/07position.t ...... 
1..4
ok 1 - getkey yields RES_KEY after cursor position report
ok 2 - $key->type_is_position after cursor position report
ok 3 - $key->line after cursor position report
ok 4 - $key->col after cursor position report
ok
t/08modereport.t .... 
1..10
ok 1 - getkey yields RES_KEY after ANSI mode report
ok 2 - $key->type_is_modereport after ANSI mode report
ok 3 - $key->initial after ANSI mode report
ok 4 - $key->mode after ANSI mode report
ok 5 - $key->value after ANSI mode report
ok 6 - getkey yields RES_KEY after DEC mode report
ok 7 - $key->type_is_modereport after DEC mode report
ok 8 - $key->initial after DEC mode report
ok 9 - $key->mode after DEC mode report
ok 10 - $key->value after DEC mode report
ok
t/09unknown_csi.t ... 
1..7
ok 1 - getkey yields RES_KEY after unrecognised CSI > v
ok 2 - $key->type_is_unknown_csi after unrecognised CSI > v
ok 3 - $cmd for unrecognised CSI > v
ok 4 - @args for unrecognised CSI > v
ok 5 - getkey yields RES_KEY after unrecognised CSI ? Sp w
ok 6 - $cmd for unrecognised CSI ? Sp w
ok 7 - @args for unrecognised CSI ? Sp w
ok
t/99pod.t ........... skipped: Test::Pod 1.00 required for testing POD

Test Summary Report
-------------------
t/05flags.t       (Wstat: 11 Tests: 2 Failed: 0)
  Non-zero wait status: 11
  Parse errors: Bad plan.  You planned 4 tests but ran 2.
Files=11, Tests=100,  1 wallclock secs ( 0.03 usr  0.01 sys +  0.50 cusr  0.04 csys =  0.58 CPU)
Result: FAIL
Failed 1/11 test programs. 0/100 subtests failed.
dh_auto_test: perl Build test --verbose 1 returned exit code 255
make[1]: *** [debian/rules:7: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:4: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2
--------------------------------------------------------------------------------

The build was made in my autobuilder with "dpkg-buildpackage -B"
but it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libterm-termkey-perl.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and affects,
so that this is still visible in the BTS web page for this package.

Thanks.