Bug#769609: apt: does not process pending triggers

[Guillem Jover <guillem@debian.org>]

Hi!

On Thu, 2014-12-11 at 08:50:23 +0100, Guillem Jover wrote:
> > Reasoning: I just tried the following sequence:
> > dpkg -i trigdepends-interest_1.0_all.deb triggerable-interest_1.0_all.deb
> > # ^ dependency                           ^ interest /usr/share/doc
> > dpkg --unpack trigdepends-interest_1.0_all.deb
> > dpkg --unpack trigstuff_1.0_all.deb
> > dpkg --configure trigstuff
> > # ^ trigstuff is iW as dependencies of trigger aren't statisfied
> > dpkg --triggers-only --pending
> 
> > My expectation I expressed in the previous mail was that the last
> > command here would fail as a pending trigger can't be run. It doesn't,
> > so my biggest concern with dpkg::TriggersPending isn't really existing,
> > but I still think that running it all the time isn't needed if we can
> > just do the more general ConfigurePending once.
> 
> That should properly fail now with 1.17.22, so yeah always using
> «--confiure --pending» is the more correct and general option anyway.

Actually, just to make sure, the pending actions are performed only
once per apt run (and not once after every dpkg command) right? That's
at least how I read it from skimming over apt-pkg/deb/dpkgpm.cc, but I
think I might have gotten confused by the wording you used in some of
these mails. Hmm, after rechecking I think it's just --triggers-only
--pending that gets injected after every explicit «--configure pkgname»
right?

If «--confiure --pending» would get executed after every dpkg invocation,
that would unfortunately mean it's not safe, due to the broken
intermediate states; otherwise, perfect, and sorry for the noise! (It
probably would be nice to clarify both a bit in apt.conf(5)? And probably
change DPkg::TriggersPending do a single call after the end as in
DPkg::ConfigurePending :)

Thanks,
Guillem