Bug#976704: po4a: Missing dependency on libpod-parser-perl

[Niko Tyni]

On Sun, Apr 25, 2021 at 09:40:02PM +0300, Adrian Bunk wrote:
> Control: reassign -1 perl 5.32.0-6
> Control: retitle -1 perl needs Breaks on more perl-modules-* packages
> Control: severity -1 serious
> Control: affects -1 po4a
> 
> On Mon, Dec 07, 2020 at 09:24:57AM +0100, Helge Kreutzmann wrote:
> >...
> > Versions of packages po4a depends on:
> >...
> > ii  perl                                    5.32.0-5
> > ii  perl-modules-5.22 [libpod-parser-perl]  5.22.2-5
> >...
> 
> 5.32 != 5.22
> 
> #976666 already fixed the same problem for perl-modules-5.24.

Indeed. As discussed there, certain versions of perl-modules-* in the
past Provided virtual packages such as libpod-parser-perl, without making
sure that those bundled modules were usable with the current /usr/bin/perl
on the system. This property broke later when perl was upgraded.

Versions earlier than 5.22 were not affected, and the issue was fixed
in perl-modules-5.26 5.26.2-5 with #899110. 5.24 (which was in stretch)
is already handled but I missed the other versions.

So this only happens with packages that were never in a stable
release. Not sure if that affects the severity. It should be easy to
fix by adding

 Breaks: perl-modules-5.22, perl-modules-5.26 (<< 5.26.2-5)

Any regressions seem improbable given these are leftovers from a time
before the current stable release.

Ubuntu has released with both 5.22 and an affected version of 5.26.
Haven't heard of similar issues there but a fix would possibly help
their users too (at least eventually.)

In general the coinstallability of older libperl5.xx and perl-modules-5.xx
packages with current ones is desirable to ease upgrades of packages
linking against libperl, such as postgresql.
-- 
Niko Tyni   ntyni at debian.org