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

2012-08-06 Thread Raphael Hertzog
Hi, On Fri, 13 May 2011, Raphael Hertzog wrote: On Fri, 13 May 2011, David Kalnischkies wrote: Further more it breaks applications listening on the hooks (apt-listbugs comes to mind) as most of they act on scheduled 'Conf' messages -- which doesn't exist if APT doesn't plan them

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

2011-05-14 Thread Julian Andres Klode
On Fri, 2011-05-13 at 16:41 +0200, Raphael Hertzog wrote: 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:

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

2011-05-14 Thread Raphael Hertzog
On Fri, 13 May 2011, Raphael Hertzog wrote: On Fri, 13 May 2011, David Kalnischkies wrote: I personally use them for quiet a while now in this combination with no issues*, but the differences is barely noticeable - also thanks to the need for DPkg::TriggersPending=true (needed to fix dpkg

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

2011-05-14 Thread Raphael Hertzog
Hi, On Fri, 13 May 2011, Phillip Susi wrote: On 5/13/2011 10:41 AM, Raphael Hertzog wrote: That's not the recommended combination currently, man apt.conf gives: DPkg::NoTriggers true; PackageManager::Configure smart; DPkg::ConfigurePending true;

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

2011-05-13 Thread Raphael Hertzog
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

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

2011-05-13 Thread David Kalnischkies
On Fri, May 13, 2011 at 16:41, Raphael Hertzog hert...@debian.org wrote:          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

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

2011-05-13 Thread Phillip Susi
On 5/13/2011 10:41 AM, Raphael Hertzog wrote: That's not the recommended combination currently, man apt.conf gives: DPkg::NoTriggers true; PackageManager::Configure smart; DPkg::ConfigurePending true; DPkg::TriggersPending true; I actually had the

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

2011-05-13 Thread Raphael Hertzog
On Fri, 13 May 2011, David Kalnischkies wrote: I personally use them for quiet a while now in this combination with no issues*, but the differences is barely noticeable - also thanks to the need for DPkg::TriggersPending=true (needed to fix dpkg bug #526774) I have put that bug in my TODO