[Pkg-clamav-devel] Bug#868092: Acknowledgement (clamav-freshclam: clean up legacy conf files)

[Christoph Anton Mitterer]

On Tue, 2017-08-22 at 21:40 +0200, Sebastian Andrzej Siewior wrote:
> How do you know that it is a conffile / config file managed by dpkg?

On legacy(!) installations (i.e. such that have been upgraded from
versions where it was still a conffile) it will show up e.g. here:
dpkg-query -W -f='${Conffiles}\n' | grep 'obsolete$'

or in:
/var/lib/dpkg/info/<packagename>.conffiles


> We
> use ucf to manage conf files. And this was the case since git 
> remembers…

hmm not sure how it got that status then... it had it at least on all
my systems (which are quite a lot >100).



> > 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".
> 
> Okay, so you are saying that there are side effects during upgrade.

Well I say that when the change from "conffile" to "manually managed
configuration file" has been made, it wasn't "unregistered" as a
conffile... and this should be repeated (so whenever people upgrade
next time, it would be cleaned up).


Cheers,
Chris.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5930 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-clamav-devel/attachments/20170822/b753f552/attachment.bin>