Re: [Help] Re: Bug#484167: cdd-common: missing directory when installing
- To: Andreas Tille <tillea@rki.de>
- Cc: Jeffrey Austen <jausten@tntech.edu>, Debian Developers <debian-devel@lists.debian.org>, 484167@bugs.debian.org, debian-dpkg@lists.debian.org, Custom Debian Distribution Team <debian-custom@lists.debian.org>
- Subject: Re: [Help] Re: Bug#484167: cdd-common: missing directory when installing
- From: Frank Lichtenheld <djpig@debian.org>
- Date: Wed, 4 Jun 2008 15:21:17 +0200
- Message-id: <[🔎] 20080604132117.GP23774@mail-vs.djpig.de>
- Mail-followup-to: Andreas Tille <tillea@rki.de>, Jeffrey Austen <jausten@tntech.edu>, Debian Developers <debian-devel@lists.debian.org>, 484167@bugs.debian.org, debian-dpkg@lists.debian.org, Custom Debian Distribution Team <debian-custom@lists.debian.org>
- In-reply-to: <[🔎] alpine.DEB.1.10.0806040833280.29066@wr-linux02>
- References: <1212435608l.5063l.0l@cerf> <alpine.DEB.1.10.0806030810520.15291@wr-linux02> <1212513501l.2279l.1l@cerf> <[🔎] alpine.DEB.1.10.0806040833280.29066@wr-linux02>
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 <djpig@debian.org>
www: http://www.djpig.de/
Reply to: