Unfortunately, I wasn't able to produce a patch. After some digging in dpkg source code I failed to find a needed function that processes triggers for dependencies.
Here's some thoughts...
Usually libcupt generates sequence of 'dpkg --no-triggers
{install|remove|unpack|configure} ...' calls for upgrade-like actions, and
sometimes here and there dpkg processes triggers for some packages, probably,
to fully satisfy depends while configuring. This probably means that dpkg has
a way to realize 'triggery'-uncompleteness of some packages, but not for all
cases. The fix for this bug should just place the same code that used for
'Depends' to somewhere around src/processarc.c:275 while Pre-Depends are
checked. Maybe, the function looked for is 'trig_file_interests_ensure', which
is called just after Pre-Depends checks, but since there are no any comments
around and function have no arguments nor return value (global vars?) I cannot
realize whether is this true.
--
Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com
C++/Perl developer, Debian Maintainer
signature.asc
Description: OpenPGP digital signature
