clone 627190 -1 reassign -1 libperl-apireference-perl 0.05-1 affects -1 padre retitle 627190 needs to build-depend on libperl-apireference-perl that surely supports the current Perl thanks
-=| Salvatore Bonaccorso, Wed, May 18, 2011 at 04:51:03PM +0200 |=-
> Source: padre
> Version: 0.76.ds1-1
> Severity: serious
> Tags: wheezy sid
> Justification: FTBFS
>
> Hi
>
> padre FTBFS in wheezy and unstable with:
>
> > dh build
> > dh_testdir
> > debian/rules override_dh_auto_configure
> > make[1]: Entering directory
> > `/build/salvi-padre_0.76.ds1-1-amd64-5wpAOM/padre-0.76.ds1'
> > perl -MPerl::APIReference -MConfig -e 'print
> > Perl::APIReference->new(perl_version =>
> > $Config{version})->as_yaml_calltips() . "\n";' >
> > ./share/languages/perl5/perlapi_current.yml
> > Bad perl version (Can't locate Perl/APIReference/V5_012_003.pm in @INC
> > (@INC contains: /etc/perl /usr/local/lib/perl/5.12.3
> > /usr/local/share/perl/5.12.3 /usr/lib/perl5 /usr/share/perl5
> > /usr/lib/perl/5.12 /usr/share/perl/5.12 /usr/local/lib/site_perl .) at
> > (eval 1) line 1.
> > ) at -e line 1
> > make[1]: *** [share/languages/perl5/perlapi_current.yml] Error 2
This is a bug in libperl-apireference-perl. The part of debian/rules
that ensures that all V*.pm files are generated from PODs is assuming
that each and every .pm is generated from POD. Therefore it removes
all V*.pm files and generates one .pm file for each POD in data/.
However, since Perl 5.12.0÷5.12.3 have the same API, the .pm files for
5.12.1÷5.12.3 are just wrappers that inherit from the 5.12.0 file.
They have no corresponding source POD .bz in data/.
The net result is that the .pm files for 5.12.1÷5.12.3 are missing
from the package, although upstream supplies them.
Fix is coming soon. Padre still needs to build-depend on fixed
libperl-apireference-perl. This is why I clone the bug instead of
reassigning.
signature.asc
Description: Digital signature
