On Tue, 3 Jun 2008, Jeffrey Austen wrote:


Could it be because
/usr/share/menu/cdd-menu is before /etc/cdd/cdd.conf in the
file list?


This should not be IMHO.


Here is something else I tried which shows the error
occurs during the unpack phase, even if unpacking twice in a row.

purge package then
# dpkg --unpack /var/cache/apt/archives/cdd-common_0.5.1_all.deb
Selecting previously deselected package cdd-common.
(Reading database ... 133829 files and directories currently
installed.)
Unpacking cdd-common (from .../cdd-common_0.5.1_all.deb) ...
Processing triggers for menu ...


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.

To clarify this I hereby ask for help on debian-devel - perhaps
somebody is able to explain how and why the triggers for menu are
started at this point in time when not all files of a package are
unpacked.


/usr/share/menu/cdd-menu: line 11: /etc/cdd/cdd.conf: No such file or
directory
Processing triggers for man-db ...
# dpkg --unpack /var/cache/apt/archives/cdd-common_0.5.1_all.deb
(Reading database ... 133854 files and directories currently
installed.)
Preparing to replace cdd-common 0.5.1 (using
.../cdd-common_0.5.1_all.deb) ...
Unpacking replacement cdd-common ...
Processing triggers for menu ...
/usr/share/menu/cdd-menu: line 11: /etc/cdd/cdd.conf: No such file or
directory
Processing triggers for man-db ...
# dpkg --configure --pending
Setting up cdd-common (0.5.1) ...


Thanks for your input on this issue

Andreas.

--
http://fam-tille.de


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

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/


--
To UNSUBSCRIBE, email to debian-dpkg-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

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/


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org