Your message dated Sun, 3 Mar 2019 23:36:37 +0100 with message-id <[email protected]> and subject line Re: Bug#484669: trigger processing runs too often has caused the Debian Bug report #484669, regarding trigger processing runs too often to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 484669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=484669 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: dpkg Version: 1.14.19 Severity: wishlist On Wed, 04 Jun 2008, Joey Hess wrote: > The triggered script is called once at the end of the dpkg run, and once > after the set of changed packages are unpacked. (I'm not sure why the > latter call happens.) We should investigate this and document the reason if there's any. Otherwise we should make dpkg smarter. Did you observe this while using apt or while directly using dpkg -i and/or dpkg --unpack? Cheers -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/
--- End Message ---
--- Begin Message ---Version: 1.19.3 Hi! On Thu, 2008-06-05 at 14:48:33 +0200, Josselin Mouette wrote: > Le jeudi 05 juin 2008 à 14:26 +0200, Raphael Hertzog a écrit : > > Package: dpkg > > Version: 1.14.19 > > Severity: wishlist > > On Wed, 04 Jun 2008, Joey Hess wrote: > > > The triggered script is called once at the end of the dpkg run, and once > > > after the set of changed packages are unpacked. (I'm not sure why the > > > latter call happens.) > > > > We should investigate this and document the reason if there's any. > > Otherwise we should make dpkg smarter. > > > > Did you observe this while using apt or while directly using dpkg -i > > and/or dpkg --unpack? I think this is largely fixed now. Any remaining duped trigger processing should happen only due to dependency requirements to be able to proceeed configuring other packages. > You can see it as soon as dpkg is called to install more than one > package: > > dpkg -i /var/cache/apt/archives/python-glade2_2.12.1-5_amd64.deb > /var/cache/apt/archives/python-gtk2_2.12.1-5_amd64.deb > (Reading database ... 191198 files and directories currently installed.) > Preparing to replace python-glade2 2.12.1-5 (using > .../python-glade2_2.12.1-5_amd64.deb) ... > Unpacking replacement python-glade2 ... > Preparing to replace python-gtk2 2.12.1-5 (using > .../python-gtk2_2.12.1-5_amd64.deb) ... > Unpacking replacement python-gtk2 ... > Setting up python-gtk2 (2.12.1-5) ... > Processing triggers for python-support ... > Setting up python-glade2 (2.12.1-5) ... > > I would have expected the trigger to be run after all postinsts. If I > cannot rely on it, I will have to modify python-support to use an > explicit trigger instead of a file trigger. So, with menu installed on a stretch system, the following: # dpkg -i hexer_1.0.3-1_i386.deb libnpth0_1.3-1_i386.deb (Reading database ... 42569 files and directories currently installed.) Preparing to unpack hexer_1.0.3-1_i386.deb ... Unpacking hexer (1.0.3-1) over (1.0.3-1) ... Preparing to unpack libnpth0_1.3-1_i386.deb ... Unpacking libnpth0:i386 (1.3-1) over (1.3-1) ... Setting up hexer (1.0.3-1) ... Setting up libnpth0:i386 (1.3-1) ... Processing triggers for man-db (2.7.6.1-2) ... Processing triggers for menu (2.1.47+b1) ... Processing triggers for libc-bin (2.24-11+deb9u4) ... seems about right. Doing instead this: # dpkg --no-triggers --unpack \ hexer_1.0.3-1_i386.deb libnpth0_1.3-1_i386.deb (Reading database ... 42569 files and directories currently installed.) Preparing to unpack hexer_1.0.3-1_i386.deb ... Unpacking hexer (1.0.3-1) over (1.0.3-1) ... Preparing to unpack libnpth0_1.3-1_i386.deb ... Unpacking libnpth0:i386 (1.3-1) over (1.3-1) ... # dpkg --configure --pending Setting up libnpth0:i386 (1.3-1) ... Processing triggers for menu (2.1.47+b1) ... Processing triggers for libc-bin (2.24-11+deb9u4) ... Processing triggers for man-db (2.7.6.1-2) ... Setting up hexer (1.0.3-1) ... Processing triggers for menu (2.1.47+b1) ... does not. But doing the same on a buster/sid system: # dpkg --no-triggers --unpack \ hexer_1.0.5-3_amd64.deb libnpth0_1.6-1_amd64.deb (Reading database ... 286311 files and directories currently installed.) Preparing to unpack hexer_1.0.5-3_amd64.deb ... Unpacking hexer (1.0.5-3) over (1.0.5-3) ... Preparing to unpack libnpth0_1.6-1_amd64.deb ... Unpacking libnpth0:amd64 (1.6-1) over (1.6-1) ... # dpkg --configure --pending Setting up libnpth0:amd64 (1.6-1) ... Setting up hexer (1.0.5-3) ... Processing triggers for man-db (2.8.5-2) ... Processing triggers for menu (2.1.47+b1) ... Processing triggers for libc-bin (2.28-8) ... is what we'd expect. Several other changes might have happened since 2008 to improve things, but that last one is coming from dpkg 1.19.3 This is due to the following change: ,--- dpkg (1.19.3) unstable; urgency=medium [ Guillem Jover ] … * dpkg: Introduce a new dependency try level for trigger processing. This completely defers trigger processing until after the dependency cycle breaking level, so to avoid generating artificial trigger cycles, when we end up trying to process triggers with yet unsatisifiable dependencies. Closes: #810724, #854478, #911620 … -- Guillem Jover <[email protected]> Tue, 22 Jan 2019 14:26:04 +0100 `--- So, given the above, I'm just going to close this report. If there are still apparent unnecessary trigger processing happening, please file a new report and we can check how to improve things or whether it's actually required. Thanks, Guillem
--- End Message ---
