Hello,
Brian May <[EMAIL PROTECTED]> writes:
> What version were you upgrading from?
It's probably a classical sarge->etch upgrade.
This user complains about problem in upgrade path
but I tkink this problem is a "feature", like we can
see in postinst:
--8<------------------------
#
# Conffile upgrade handling
#
# from sarge amavisd-new (1.0) and previous
# disable the config file, initscript will refuse to run
db_fset amavisd-new/outdated_config_style_warning seen false || true
for i in /etc/amavisd.conf /etc/amavis/amavisd.conf ; do
if [ -e "$i" ] ; then
mv "$i" "${i}.disabled" || true
db_input high amavisd-new/outdated_config_style_warning || true
db_go || true
fi
done
--8<------------------------
...and /etc/init.d/amavisd-new:
--8<------------------------
check_noncompatible_upgrade() {
for i in /etc/amavisd.conf /etc/amavis/amavisd.conf ; do
if [ -e "${i}.disabled" ] ; then
echo "Found incompatible config file flag!" >&2
echo "Due to safety concerns, amavisd-new will not be started." >&2
echo "Refer to /usr/share/doc/amavisd-new/README.Debian for
instructions." >&2
exit 1
fi
done
}
--8<------------------------
Regards,
--
Gregory Colpart <[EMAIL PROTECTED]> GnuPG:1024D/C1027A0E
Evolix - Informatique et Logiciels Libres http://www.evolix.fr/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
