Bug#626599: Use --no-triggers by default and let dpkg find out the configuration order

[Raphael Hertzog <hertzog@debian.org>]

Package: apt
Version: 0.8.14.1

On Mon, 01 Nov 2010, Joey Hess wrote:
> Phillip Susi wrote:
> > I've noticed triggers being invoked repeatedly during upgrades rather
> > than once at the end, as they are supposed to.  I started looking at
> > /var/log/dpkg.log to try and figure out why.
> 
> Becaue apt has not been changed to tell dpkg to defer trigger processing,
> and to them run them all at the end. Or rather, it has, see
> http://bugs.debian.org/473461 -- but they do not have the options
> enabled by default.
> 
> DPkg
> {
>    // let apt aggressivly use dpkg triggers
>    NoTriggers "true";
>    NoConfigure "true";
>    ConfigurePending "true";

That's not the recommended combination currently, man apt.conf gives:
          DPkg::NoTriggers "true";
          PackageManager::Configure "smart";
          DPkg::ConfigurePending "true";
          DPkg::TriggersPending "true";

Since we're at the start of the wheezy cycle, I believe it's a good time
to enable those options. Dear apt maintainers, can you do that please ?

I also like that the options tell APT to rely on dpkg to configure stuff
in the correct order instead of doing it itself and getting it wrong in
some cases... cf the numerous bug reports here:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/541595

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Follow my Debian News ▶ http://RaphaelHertzog.com (English)
                      ▶ http://RaphaelHertzog.fr (Français)