On Fri, Jun 16, 2017 at 12:33:55PM +0200, Franz Georg Koehler wrote: > After the latest upgrade to 4.2.8-3+deb8u2, frontend fails to run the postinst > script sucessfully and exists with code 10 instead. This prevents the > completion of the upgrade. > > Might be related to the configuration. Hoever, I do not see what exactly is > the problem? Actually, there is nothing that frontend would need to do? > > root@orion:/etc/request-tracker4# /usr/share/debconf/frontend > /var/lib/dpkg/info/request-tracker4.postinst configure 4.2.8-3+deb8u1 > debconf (db): making DbDriver of type File
[snip many lines of debconf debug output] > debconf (db configdb): passing to config .. > debconf (developer): --> 0 ok > debconf (developer): <-- CAPB backup > debconf (developer): --> 0 multiselect escape backup > debconf (developer): <-- REGISTER dbconfig-common/database-type > request-tracker4/database-type > debconf (developer): --> 10 No such template, "dbconfig-common/database-type" > debconf (developer): <-- GET request-tracker4/dbconfig-install > debconf (developer): --> 10 request-tracker4/dbconfig-install doesn't exist > debconf (db configdb): trying to > setflag(request-tracker4/handle-siteconfig-permissions seen true) .. > debconf (db configdb): passing to config .. > root@orion:/etc/request-tracker4# echo $? > 10 > > oot@orion:/etc/request-tracker4# apt-get -f install > Paketlisten werden gelesen... Fertig > Abh??ngigkeitsbaum wird aufgebaut. > Statusinformationen werden eingelesen.... Fertig > 0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert. > 1 nicht vollst??ndig installiert oder entfernt. > Nach dieser Operation werden 0 B Plattenplatz zus??tzlich benutzt. > request-tracker4 (4.2.8-3+deb8u2) wird eingerichtet ... > + branch_version=4 > + branch_priority=250 > + warn > + fmt -60 > + sed s/^/**WARNING** / > **WARNING** > **WARNING** If you are using mod_perl or any form of persistent perl > **WARNING** process such as FastCGI, you will need to restart your > **WARNING** web server and any persistent processes now. > **WARNING** > **WARNING** For mod_perl this means > **WARNING** > **WARNING** invoke-rc.d apache2 stop && invoke-rc.d apache2 start > **WARNING** > + find /var/cache/request-tracker4/mason_data -type f -print0 > + xargs -r0 rm -f > + . /usr/share/debconf/confmodule > + [ ! ] > + PERL_DL_NONLAZY=1 > + export PERL_DL_NONLAZY > + [ ] > + exec /usr/share/debconf/frontend > /var/lib/dpkg/info/request-tracker4.postinst configure 4.2.8-3+deb8u1 > dpkg: Fehler beim Bearbeiten des Paketes request-tracker4 (--configure): > Unterprozess installiertes post-installation-Skript gab den Fehlerwert 10 > zur??ck > Fehler traten auf beim Bearbeiten von: > request-tracker4 > needrestart is being skipped since dpkg has failed > E: Sub-process /usr/bin/dpkg returned an error code (1) Hi, Thanks for this detailed bug report and I'm sorry that you have run into problems particularly during a security update. As far as I can tell this was a latent problem rather than one caused by the update directly, as the Debian post-config code wasn't touched in the update. It must be quite an edge case for it to not have been noticed before. The problem seems to be that some dbconfig-common debconf questions are not set by the time they are used in the postinst. This should happen in the package preconfiguration script but apparently isn't. Please could you take a copy of the debconf database (/var/cache/debconf/config.dat) and then run /var/lib/dpkg/info/request-tracker4.config by hand, having first edited the first line to read #!/bin/sh -x This might shed some light on why this is happening. Please compare the saved copy of the config database, eg: diff -u /path/to/backup/config.dat /var/lib/debconf/config.dat to see if anything changes. Thanks, Dominic