Hey. Nothing special, I never manually changed the config, only via debconf.
What seems to be the case here is the following: /etc/logrotate.d/clamav-freshclam seems to have been once a "conffile" (i.e. a config file managed by dpkg). Later however, this seems to have been changed, and while the file is still there (and used), it's no longer a dpkg-managed "conffile". However, when (at some version) the switch was done from dpkg-managed "conffile" to non-dpkg-managed configuration file,... dpkg wasn't told about this change, and still thinks (on legacy installations) that the file would be a "conffile". Not fully sure what is the "best" way to handle such cases,... perhaps you could ask at debian-devel? I think one could possible to something like: - backup the current file to some location - use dpkg-maintscript-helper rm_conffile to get the conffile unregistered - move the backup to the original location => thus everything should stay as is, but the conffile be unregistered But as I've said... rather ask some package maintenance experts for help on this. Thanks, Chris.
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Pkg-clamav-devel mailing list Pkg-clamav-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-clamav-devel
