tag 375945 confirmed
thanks
I have duplicated this bug, and traced it to bogosity induced by debhelper's
dh_installdebconf adding code in the postrm scripts on the wrong place.
This bug has been fixed in the 2.4.0-1 upload (this is a duplicate of
#362952), but I missed fixing it in the
backports branch, sorry about that.
I will upload fixed packages ASAP. To clean up the purge of amavisd-new,
you'll be required to either reinstall amavisd-new from the new packages and
immediately purge it, or you will have to manually edit
/var/lib/dpkg/info/amavisd-new.postrm:
1. Add this just after the first purge) line:
[ -r /usr/share/debconf/confmodule ] && {
. /usr/share/debconf/confmodule
db_purge || true
db_stop || true
}
2. Remove any other ". /usr/share/debconf/confmodule" and db_* command calls
in the file.
3. run dpkg --purge amavisd-new.
That should clean up the mess.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
