Re: Bug#774844: xfonts-traditional: fails to upgrade from 'wheezy': Can't locate File/Find.pm in @INC
On 2015-01-19 09:14, Niko Tyni wrote:
> On Sun, Jan 18, 2015 at 10:37:19PM +0100, Andreas Beckmann wrote:
>> Package: perl-modules
>> Breaks: xfonts-traditional (<< 1.7~)
> Unfortunately that doesn't help with partial upgrades. Nothing prevents
> upgrading and configuring xfonts-traditional first, and only then
> upgrading the rest of the system.
OK, how can we prevent trigger processing for xfonts-traditional if
perl-modules is not usable?
Package: xfonts-traditional
Depends: dpkg (>= 1.17.triggerfixed), perl-modules
seems to work in my manual test.
dpkg/jessie seems not to run trigproc if the direct dependency
perl-modules is not configured (dpkg/wheezy does)
dpkg/jessie (and dpkg/wheezy) run trigproc if the direct dependency perl
is confgured, but the indirect dependency perl-modules is only unpacked.
Maybe this leads to a rule like:
If maintainer scripts (including triggers!) use some module
from perl-modules, the package needs to depend on perl-modules.
An indirect dependency through perl is not sufficient.
Andreas
Reply to: