Bill Allombert wrote: > Hello Joey, > > Can you have a look at bug #484167 about triggers and menu ? > It seems dpkg is running the menu trigger before the the triggering > package is configured.
Right, dpkg can run the trigger at any time it choses after unpacking the package, and currently it seems to do so before configuration, though I'm not sure why that choice was made. I hadn't considered that this could break some executable menu files that depend on their package being configured when I made menu use triggers. However, thinking about it some more, packages like cdd-common were already broken before menu became triggerized. The breakage just wasn't as likely to show up, but could occur: dpkg --unpack a-game.deb cdd-common.deb dpkg --configure --pending IIRC dpkg --configure --pending configures in alphabetical order. So a-game would be confgured first, when cdd-common was unpacked but not yet configured. If a-game uses menu, then update-menus runs, running cdd-common's menu program, which would fail the same as it does with triggers. I think you could probably also cause the same problem by just installing both packages with dpkg at once, since it would unpack both and then configure a-game first. -- see shy jo
signature.asc
Description: Digital signature
