Package: amanda-common Version: 1:3.3.9-2 Severity: serious X-Debbugs-Cc: p...@packages.debian.org
This package contains binary Perl modules but doesn't depend on perlapi-* (currently perlapi-5.24.1). Quoting the Debian Perl Policy 4.4.2 ("Binary and Other Architecture Dependent Modules"): Additionally, all binary modules (regardless of their installation directory) and any other modules installed into $Config{vendorarch} must depend on the expansion of perlapi-$Config{debian_abi} using the Config module. If $Config{debian_abi} is empty or not set, $Config{version} must be used. This used to work (since #582220) but seems to have regressed recently with 1:3.3.9-1 that switched to dh-style debian/rules, dropping the 'dh_perl -a usr/lib/amanda/perl' call. The default dh behaviour doesn't know where to look for the private directory (which currently seems to be /usr/lib/<triplet>/amanda/perl). Possibly something like override_dh_perl: dh_perl /usr/lib/*/amanda/perl will do the trick. Note that this is the root cause for #839603 / #839392: if the package had had the correct dependencies, it would have been automatically binNMU'd by the release team along with the other 600+ packages during the Perl 5.24 transition. Even when this is fixed, partial upgrades of amanda-common from 1:3.3.9-1 without upgrading perl will be a problem, particularly as Ubuntu has made a release with something based on 1:3.3.9-1. It looks like we need to add a Breaks on the perl side to make sure broken combinations can't happen. -- Niko Tyni nt...@debian.org