Bug#868092: Acknowledgement (clamav-freshclam: clean up legacy conf files)
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/.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.
smime.p7s
Description: S/MIME cryptographic signature
Bug#868092: Acknowledgement (clamav-freshclam: clean up legacy conf files)
On 2017-08-20 21:50:32 [+0200], Christoph Anton Mitterer wrote: > Hey. Hi, > 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). How do you know that it is a conffile / config file managed by dpkg? We use ucf to manage conf files. And this was the case since git remembers… > 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. > 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. Okay. > > Thanks, > Chris. Sebastian
Bug#868092: Acknowledgement (clamav-freshclam: clean up legacy conf files)
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
Bug#868092: Acknowledgement (clamav-freshclam: clean up legacy conf files)
On 2017-07-12 01:54:01 [+0200], Christoph Anton Mitterer wrote: > On Wed, 2017-07-12 at 01:39 +0200, Christoph Anton Mitterer wrote: > > Sorry, haven't seen it was created via debconf =) > > Reverting this... it's still technically a bug, even though you create > the file, as it's marked as a conffile in dpkg, which it no longer is. > > So please clean up =) I am confused. Could you describe step by step what happens and when it got wrong? There is a postrm script for freshclam which (should) remove the file in question. Sebastian
Bug#868092: Acknowledgement (clamav-freshclam: clean up legacy conf files)
Control: reopen -1 On Wed, 2017-07-12 at 01:39 +0200, Christoph Anton Mitterer wrote: > Sorry, haven't seen it was created via debconf =) Reverting this... it's still technically a bug, even though you create the file, as it's marked as a conffile in dpkg, which it no longer is. So please clean up =) smime.p7s Description: S/MIME cryptographic signature
