Skip Menu |

This queue is for tickets about the CGI-ValidOp CPAN distribution.

Report information
The Basics
Id: 121781
Status: new
Priority: 0/
Queue: CGI-ValidOp

People
Owner: Nobody in particular
Requestors: gregoa [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



From: gregoa [...] cpan.org
Subject: libcgi-validop-perl: FTBFS on May 1st (?)
We have the following bug reported to the Debian package of CGI-ValidOp (https://bugs.debian.org/861952): It doesn't seem to be a bug in the packaging, so you may want to take a look. Thanks! (Please also check the next message in the bug tracker) ------8<-----------8<-----------8<-----------8<-----------8<----- Package: src:libcgi-validop-perl Version: 0.56-2 Severity: important Hello Gregor et al. I tried to build this package in stretch with "dpkg-buildpackage -A" but it failed: -------------------------------------------------------------------------------- [...] t/16check_date.t .......... [...] Test Summary Report ------------------- t/16check_date.t (Wstat: 256 Tests: 607 Failed: 1) Failed test: 506 Non-zero exit status: 1 Files=24, Tests=3133, 3 wallclock secs ( 0.39 usr 0.13 sys + 2.26 cusr 0.36 csys = 3.14 CPU) Result: FAIL Failed 1/24 test programs. 1/3133 subtests failed. Makefile:844: recipe for target 'test_dynamic' failed make[1]: *** [test_dynamic] Error 255 make[1]: Leaving directory '/<<PKGBUILDDIR>>' dh_auto_test: make -j1 test TEST_VERBOSE=1 returned exit code 2 debian/rules:7: recipe for target 'build-indep' failed make: *** [build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2 -------------------------------------------------------------------------------- The build was made on 2017-05-01 and the error says expected: '2017-04-31' which does not exist, as April has only 30 days. This suggests a date-related bug. I have not tried to reproduce it by building it again on May 1st. Maybe this could be done by using libfaketime, but I think a better strategy would be to look at the code and the error message and try to guess how it may happen. Thanks. ------8<-----------8<-----------8<-----------8<-----------8<----- Thanks for considering, gregor herrmann, Debian Perl Group