On Wed, Jun 04, 2008 at 09:31:15PM +0200, Andreas Tille wrote: > Package: menu > Version: 2.1.39 > Severity: normal > > Hi, > > when bug #484167 was filed against cdd-common package I wondered how to > prevent the problem reasonably.
We should report #484167 the problem to the dpkg developpers. > So I inspected menu.postinst and found the > snippet > > triggered) > # This is triggered by any installation of a menu file and by > # any call to update-menus made in a package maintainer script. > update-menus --trigger > exit 0 > > and I wondered whether I could easily detect whether cdd-menu was > called in a trigger process and some extra options / environment > variables were set to be able to detect that a trigger was caused. > Unfortunately the option --trigger is not documented in > > man update-menus > > Please provide some information about the effect of this command line. update-menus --trigger should only ever be called in menu.postinst. It cause menu not to check the dpkg lock to work around the fact that dpkg does not release the dpkg lock while running trigger. I did not document it because it should be removed in the future. 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]
