There's a regression when purging dbconfig-common itself, marked "Pending"
already:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=476949
It's probably as simple as adding "|| true" to the rmdir added to
debian/dbconfig-common.postrm. Here's the chunk that caused it:
--- dbconfig-common-1.8.36/debian/dbconfig-common.postrm 2007-06-18
19:07:57.000000000 +0200
+++ dbconfig-common-1.8.38/debian/dbconfig-common.postrm 2008-03-07
00:02:37.000000000 +0100
@@ -5,6 +5,9 @@
if [ $1 = "purge" ]; then
rm -f /etc/dbconfig-common/config || true
rmdir /etc/dbconfig-common || true
+ # purge the default logfile/logdir
+ rm -f /var/log/dbconfig-common/dbc.log
+ rmdir --ignore-fail-on-non-empty /var/log/dbconfig-common
# This might fail if a user has chosen not to purge a database
rmdir --ignore-fail-on-non-empty /var/lib/dbconfig-common || true
fi
The full debdiff is attached.
I'll ask the author about the new upload, but I can provide this particular fix
also in a debdiff against 1.8.38.
Apart from that, I've tested installing and purging postfix-policyd,
which worked fine.
** Attachment added: "pbuilder build log"
http://launchpadlibrarian.net/13825552/pbuilder.log
--
Please sync dbconfig-common 1.8.38 (universe) from Debian unstable (main).
https://bugs.launchpad.net/bugs/216106
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
