Package: dbconfig-common
Version: 1.8.31
Severity: normal
Tags: patch
While doing a torture test with the webcalendar package some days ago
(install / deinstall / purge / keep the database / install again / etc), I
ran into a problem with dbconfig-common. For some reason that I cannot
replicate now, the dpkg/prerm script was failing ungracefully. I tracked
down the problem and fixed it with the patch attached below. It simply adds
"|| true" after a call to db_fset.
BTW, I noticed that there are several other calls to db_fset not followed by
"|| true" in the dbconfig-common scripts. Although I think that it is a
good safety measure to add "|| true", I am not sure this is really needed
for db_fset calls. However, note that the problem arose with the
$dbc_package/dbconfig-remove debconf question, which does not belong to the
dbconfig-common package.
Rafael Labossiere
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.17-2-686 (SMP w/1 CPU core)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Versions of packages dbconfig-common depends on:
ii debconf [debconf-2.0] 1.4.72 Debian configuration management sy
ii ucf 2.007 Update Configuration File: preserv
dbconfig-common recommends no packages.
-- debconf information excluded
diff -Naur dbconfig-common-1.8.31-orig/dpkg/prerm
dbconfig-common-1.8.31/dpkg/prerm
--- dbconfig-common-1.8.31-orig/dpkg/prerm 2006-10-10 11:42:34.000000000
+0200
+++ dbconfig-common-1.8.31/dpkg/prerm 2007-04-12 10:25:21.000000000 +0200
@@ -35,7 +35,7 @@
if [ "$dbc_remove" ]; then
db_set $dbc_package/dbconfig-remove "$dbc_remove"
fi
- db_fset $dbc_package/dbconfig-remove seen false
+ db_fset $dbc_package/dbconfig-remove seen false || true
db_input high $dbc_package/dbconfig-remove || true
db_go || true
db_get $dbc_package/dbconfig-remove && dbc_remove="$RET"
