On Tue, 27 Jun 2023, 22:01 Andreas Beckmann, <a...@debian.org> wrote:
> Control: tag -1 patch > > On 27/06/2023 19.21, Richard Lewis wrote: > > header.txt has not been modified since 2015. > > I've found three versions (with sightly different spelling): > * lenny > * squeeze, wheezy, jessie > * stretch .. today > > > it is a simple yext file that is installed with debian/logcheck.install > > > > the only change is that it used to be installed into /usr/share but got > > moved to /etc to be a conffile in 2021. This didnt trigger any piuparts > > issues and there was no change to the contents of header.txt. > > It has been copied during initial install only and was never upgraded. thank-you - i believe understand this now for reasons unknown, when debian introduced header.txt in 2014 it shipped header.txt in /usr/share/logcheck and copied it to /etc/logcheck in postinst on initial install. Only the file in /etc is ever used. editorial changes were then made, but these only made it into the copy in /usr/share and no steps were taken to update the file in /etc. So those upgrading have been using the old version, while new installs got the new version. This is probably against the spirit of policy but it doesnt look like anyone noticed. In bookworm logcheck puts header.txt file directly into /etc/logcheck like any other conffile. because the content hasnt changed since stretch, this didnt cause immediate issues. But people who first installed at an old version will get a confusing conffile prompt on upgrade to bookworm even though they had never edited the file and had upgraded to every stable release..wow! thank-you for this i have learned something Luckily the header.txt is purely cosmetic - so there shouldnt be other bugs from this! >
