Bug#963408: pmtools: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2

Niko Tyni ntyni at debian.org
Mon Jun 22 20:13:15 BST 2020


On Sun, Jun 21, 2020 at 11:35:22PM +0200, gregor herrmann wrote:
> On Sun, 21 Jun 2020 22:11:05 +0200, Lucas Nussbaum wrote:

> > > #                   'pod2text: unable to format /usr/lib/x86_64-linux-gnu/perl-base/Carp.pm
 
> Interesting bug, and not found in cpantesters.
> 
> I note that /usr/lib/x86_64-linux-gnu/perl-base/Carp.pm (from
> perl-base) indeed has no POD, but /usr/share/perl/5.30.3/Carp.pm
> (from perl-modules-5.30) does. And bin/pman finds the first one.
> 
> I wonder why this pops up now? Can this be related to the recent
> changes of @INC in src:perl?

Yes. The .pm files in perl-base have their POD documentation stripped away
(see debian/stripdoc in src:perl). Those are now first on @INC even when
libperl5.30 are perl-modules-5.30 are installed (see #962138).

Looks like /usr/bin/perldoc finds the second Carp.pm when the first
doesn't contain any POD documentation, but the pmtools build can't.

Not sure what to do about this bug. As an isolated corner case we can
patch around it, but the fact is we're slightly more visibly deviated from
upstream than we used to be. We'll see if more things like these crop up.

We could also stop stripping the docs in perl-base. Statistics about how
much space it's saving now would be useful if we want to consider that.

Copying perl at pdo as a heads up.
-- 
Niko



More information about the Perl-maintainers mailing list