Comment 5 for bug 1400669

Follow up to my previous note:

I have been working on a similar installation problem with the udev package and received some help from Martin Pitt. Based upon his suggestions, I ran the following command:

# env DPKG_MAINTSCRIPT_PACKAGE=spamassassin DPKG_MAINTSCRIPT_NAME=postinst sh -ex /var/lib/dpkg/info/spamassassin.postinst configure ; echo $?
+ set -e
+ [ configure = triggered ]
+ [ configure = configure ]
+ getent passwd debian-spamd
+ mkdir -p /var/lib/spamassassin
+ stat -c %U /var/lib/spamassassin
+ OWNER=debian-spamd
+ stat -c %G /var/lib/spamassassin
+ GROUP=debian-spamd
+ dpkg-statoverride --list /var/lib/spamassassin/sa-update-keys
+ [ debian-spamd:debian-spamd != debian-spamd:debian-spamd ]
+ test -d /var/lib/spamassassin/sa-update-keys
+ su - debian-spamd -c sa-update --gpghomedir /var/lib/spamassassin/sa-update-keys --import /usr/share/spamassassin/GPG.KEY
+ deb-systemd-helper debian-installed spamassassin.service
+ deb-systemd-helper unmask spamassassin.service
+ deb-systemd-helper --quiet was-enabled spamassassin.service
+ deb-systemd-helper update-state spamassassin.service
+ [ -x /etc/init.d/spamassassin ]
+ update-rc.d spamassassin defaults 19 21
+ [ -x /etc/init.d/spamassassin ]
+ invoke-rc.d spamassassin start
SpamAssassin Mail Filter Daemon: disabled, see /etc/default/spamassassin
0

OK, that looks promising. Now, when I returned to synaptic and installed another unrelated package, it then proceded to configure both spamassassin and sa-compile! There must be a flag somewhere that doesn't get updated when this manual command is run, so the package manager still thinks it needs to be performed. In any event, this appears to have cleared the problems and make the packages as properly installed. Unfortunately, I'm still unclear as to the source of the original problem.