on apt-get upgrade and as soon as sympa packages are concerned, I would expect the config file sympa.conf not to be updated without notice.
Actual behavior
with apt-get upgrade, the config file sympa.conf is updated based on the values from /etc/dbconfig-common/sympa.conf without further interaction or notice to the user. At least on my system (6.2.16~dfsg-3+deb9u1 to 6.2.16~dfsg-3+deb9u2) the upgrade process overwritten the db_name parameter this way.
Version
6.2.16 shipped by debian Stretch
Installation method
APT
Expected behavior
on
apt-get upgrade
and as soon as sympa packages are concerned, I would expect the config filesympa.conf
not to be updated without notice.Actual behavior
with
apt-get upgrade
, the config filesympa.conf
is updated based on the values from/etc/dbconfig-common/sympa.conf
without further interaction or notice to the user. At least on my system (6.2.16~dfsg-3+deb9u1
to6.2.16~dfsg-3+deb9u2
) the upgrade process overwritten thedb_name
parameter this way.Additional information
This issue is about the same as the post at https://listes.renater.fr/sympa/arc/sympa-fr/2018-12/msg00012.html . I'm not 100% it's a bug. If it's not, any explanation is welcome :)