On Wed, Jun 04, 2008 at 08:42:36AM +0200, Andreas Tille wrote: > On Tue, 3 Jun 2008, Jeffrey Austen wrote: > Ahh, I think here is the problem. I just purged my cdd-common and > can now reproduce this. I'm afraid that the new trigger feature of > dpkg is causing this problem. If I understood things right the > trigger feature should cause to build menus *after* packages are > installed, but obviosely it causes the contrary and starts calling > the menu building stuff in the middle of installation process which > somehow leads to undefined results if not all files are installed > correctly. > > While it would be easily possible to verify that /etc/cdd/cdd.conf > exists inside /usr/share/menu/cdd-menu I would have to do some > reasonable action in this case which would be to throw an error > because this should definitely not happen and thus I rather think > that either the menu package is broken because of working at the > wrong point in time or the dpkg trigger feature does not properly.
AFAICT from the documentation the dpkg triggers work as intended, although maybe not as desired by you ;) File triggers are activated on creation or modification of the triggering file by dpkg, so during unpack or removal. A possible solution might be to change your menu file script to ignore the missing conffile and activate the trigger again manually in your postinst with dpkg-trigger. Gruesse, -- Frank Lichtenheld <[EMAIL PROTECTED]> www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
