Hello, Adam Heath, 2002-02-08 17:17-0600:
I haven't actually seen a problem in the real world, but it's possible that one could arise.
This is just an update to point out that it has been seen in the real world, as I just ran into that issue while packaging pluxml (#630467).
pluxml is a blog engine, so upcoming my package installs some configuration for apache2 or lighttpd and then reloads these daemons. No problem in postinst, where at the end of the script:
1. I call db_stop; 2. dh_installdebconf adds nothing; 3 the script exists fine.But in postrm, things happen differently. I remove the configuration from apache2 or lighttpd, reload these daemons, and at the end of the script:
1. I call db_stop; 2. dh_installdebconf inserts some code that sources /usr/share/debconf/confmodule again, which starts debconf (I do not know the dirty details) and calls db_purge; 3. the script stalls, or rather, exists, but stays defunct with a debconf wrapper waiting for nothing, as it seems.I solved that problem by moving my call to db_stop after the #DEBHELPER# placeholder.
Would there be a problem in adding a call to db_stop after db_purge, in the code added to postrm by dh_installdebconf? Otherwise, that problem could be mitigated by adding a notice in dh_installdebconf(1) and probably in debconf-devel(7) too, telling people to put their call to db_stop after the debhelper placeholder, as I did.
Librement, -- ,--. : /` ) Tanguy Ortolo <xmpp:tan...@ortolo.eu> | `-' Debian Developer <irc://irc.oftc.net/Tanguy> \_
signature.asc
Description: Digital signature
