[Cupt-devel] Bug#766758: apt: does not process pending triggers

Eugene V. Lyubimkin jackyf at debian.org
Sat Nov 15 09:43:02 UTC 2014


Hello!

[ some CC's dropped, please tell if I missed someone ]

Did not touch trigger stuff for a while, let's see if I catched up what
happens here:

2014-11-15 00:28, Guillem Jover:
> [...]
> Only apt seems to be affected. dselect properly uses “dpkg transactions”
> and as such queues all configuration in a final «--configure --pending»
> call. And cupt seems to behave correctly by calling dpkg with
> «--triggers-only --pending», but Eugene might know for sure.

Cupt calls '--triggers-only --pending' in the end of run when
"trigger deferring" (i.e. '--no-triggers') is enabled, which is the
default (both in wheezy and jessie).

Do I read your explanation [1] correctly that '--triggers-only
--pending' needs to be invoked (in the end) always, since dpkg may
choose not to process triggers not just because '--no-triggers' is
passed, but also because dependencies of a 'triggers-pending' package
are not satisfied right at that time?

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766758#69

-- 
Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com
C++ GNU/Linux userspace developer, Debian Developer



More information about the Cupt-devel mailing list