address@hidden: Bug#720865: pspp: FTBFS with perl 5.18: test failures]

[Ben Pfaff]

I see that there are some important bugs that may be related to the
Debian packaging and, in any case, the Debian packaging is quite dated.
Do you have any plans to prepare a newer version for upload?

Thanks,

Ben.

----- Forwarded message from Dominic Hargreaves <address@hidden> -----

Date: Sun, 25 Aug 2013 20:27:02 +0100
From: Dominic Hargreaves <address@hidden>
To: address@hidden
Subject: Bug#720865: pspp: FTBFS with perl 5.18: test failures
User-Agent: Mutt/1.5.21 (2010-09-15)

Source: pspp
Version: 0.7.9+git20120620-1.2
Severity: serious
Justification: transition imminent
User: address@hidden
Usertags: perl-5.18-transition
Tags: sid jessie

This package FTBFS with perl 5.18:

Perl module tests

947: Perl create system file                         ok
948: Perl writing cases to system files              ok
949: Perl write variable parameters                  ok
950: Perl dictionary survives system file            ok
951: Perl read system file                           FAILED (perl-module.at:370)
952: Perl copying system files                       ok
953: Perl value formatting                           ok
954: Perl opening nonexistent file                   ok
955: Perl missing values                             ok
956: Perl custom attributes                          FAILED (perl-module.at:696)
957: Perl Pspp.t                                     FAILED (perl-module.at:707)
ERROR: 956 tests were run,
3 failed unexpectedly.


Please ask address@hidden if you need help with preparing
or testing a change; if you have a suitable test i386 system you can
install perl 5.18 by adding experimental to your sources as well as the
repository at <http://people.debian.org/~dom/perl/test/perl-5.18.0/>

You can also find more about the perl 5.18 transition, which we hope
to start tomorrow[1], at <http://bugs.debian.org/712615>.

Thanks for your work!

Cheers,
Dominic.

[1] apologies for the late appearance of this bug report; earlier
test coverage did not cover this package, possibly because of issues
in build-dependencies


----- End forwarded message -----