Hi! On Thu, 2015-10-08 at 18:54:59 +0200, Jérémy Bobbio wrote: > Source: dpkg > Version: 1.18.3 > Severity: normal > Tags: patch
> scripts/t/mk.t will shell out to dpkg-architecture.pl and > dpkg-buildpackage.pl. Both scripts are called from the current > development tree. But they will use Perl modules to compute some of > their values. As PERL5LIB is not set, system modules are going to > be used instead of the one from the development tree. > > This makes it impossible to have the tests pass when there is a change > in the default dpkg-buildflags values in a new version. > > The attached patch sets the PERL5LIB environment variable which fixes > the problem. Ah indeed, this is a regression. I've fixed it globally instead, please see the attached patch, and let me know if this works for you? Thanks, Guillem
From 9e49c6876c9892c8e5d4ed0e628656cd5d16dd8e Mon Sep 17 00:00:00 2001 From: Guillem Jover <guil...@debian.org> Date: Fri, 9 Oct 2015 16:55:35 +0200 Subject: [PATCH] build: Set PERL5LIB to the local modules directory for the test suite MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Regression introduced in commit 34b26c7db232b300991df5fb6f52707b381df28f. Some functional tests are passing through makefile and exec barriers, where the lib parameter for TAP::Harness is lost. Reintroduce the explicit setting of PERL5LIB so that it gets inherited for all subprocesses. Closes: #801329 Reported-by: Jérémy Bobbio <lu...@debian.org> Stable-Candidate: 1.17.x --- check.am | 1 + 1 file changed, 1 insertion(+) diff --git a/check.am b/check.am index 837a76b..0a13eaa 100644 --- a/check.am +++ b/check.am @@ -31,6 +31,7 @@ check-local: $(test_data) $(test_programs) $(test_scripts) srcdir=$(srcdir) builddir=$(builddir) \ CC=$(CC) \ PERL_DL_NONLAZY=1 \ + PERL5LIB="$(top_srcdir)/scripts" \ PERL5OPT=$(TEST_COVERAGE) \ $(PERL) -MTAP::Harness -e $(TEST_RUNNER) \ $(addprefix $(builddir)/,$(test_programs)) \ -- 2.6.1
