Bug#1049412: logcheck: Does not respect removal of /etc/logcheck/header.txt in bullseye

2023-09-10 Thread Richard Lewis
On Tue, 15 Aug 2023 19:54:26 +0200 Santiago Vila wrote: > In preinst, do something like this: > > if upgrading-from-previous-version-whatever-is-coded >if [ ! -f /etc/logcheck/header.txt ]; then > touch /etc/logcheck.header.was.removed.txt >fi > fi > > Then in postinst, do something

Bug#1049412: logcheck: Does not respect removal of /etc/logcheck/header.txt in bullseye

2023-08-15 Thread Santiago Vila
So: Do you have any preference about the way you would like to fix this? One way is to go back to the old behaviour, but maybe it's not necessary if you want to keep using the conffile mechanism. Maybe this would also work: In preinst, do something like this: if upgrading-from-previous-version-

Bug#1049412: logcheck: Does not respect removal of /etc/logcheck/header.txt in bullseye

2023-08-15 Thread Richard Lewis
On Tue, 15 Aug 2023, 13:15 Santiago Vila, wrote: > > On a Debian 11 system where logcheck is installed, removing > /etc/logcheck/header.txt and then upgrading to Debian 12 > makes such file to reappear again. > > > thanks - i agree this is a bug and a patch to fix it would be great :) In the mea

Bug#1049412: logcheck: Does not respect removal of /etc/logcheck/header.txt in bullseye

2023-08-15 Thread Santiago Vila
Package: logcheck Version: 1.4.2 Dear maintainer: On a Debian 11 system where logcheck is installed, removing /etc/logcheck/header.txt and then upgrading to Debian 12 makes such file to reappear again. This is against Debian Policy, which says changes in configuration files (which I believe it