On Mon, May 30, 2011 at 10:51:34AM +0200, Raphaël Hertzog wrote: > Package: debhelper > Version: 8.1.6 > Severity: normal > > I noticed that a simple package install triggers the menu trigger twice: > ---- > Preparing to replace zim 0.52-1 (using .../archives/zim_0.52-1_all.deb) ... > Unpacking replacement zim ... > Processing triggers for shared-mime-info ... > Processing triggers for menu ... > Processing triggers for desktop-file-utils ... > Processing triggers for man-db ... > Processing triggers for hicolor-icon-theme ... > Processing triggers for python-support ... > Processing triggers for gnome-menus ... > Setting up zim (0.52-1) ... > Processing triggers for python-support ... > Processing triggers for menu ... > ---- > > The first one is because of the file trigger that dpkg activates. The second > one is because update-menus is called in the postinst. And update-menus runs > "dpkg-trigger --by-package=menu /usr/share/menu" if it sees that the dpkg lock > is active.
Hello Raphaël, This is an old, known, issue, see bug #518919. Menu must be triggered after the package is configured, not before. Currently the only way to achieve that is to add a call to dpkg-trigger in the package postint. This is the purpose of the debhelper snippet. See wishlist bug #556104 against dpkg. Cheers, -- Bill. <[email protected]> Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
