Reading my own comments to the blog post years later is fun:
> rsyslog decided at some point between 2018 and 2020 to break the config file format that had been in use for years before that mystery point in time. I don't know exactly when they did it, I only know when it dawned on me that I wasn't getting logwatch emails anymore. I don't know if they added any new feature which justified breaking the configs, and I do not care, and I will not read their docs or notes to find out. I will only downgrade, version lock, and submit bugs that I know to be facetious to cause someone the grief of having to click on them to close them. It is the distro's job to provide me a working core component and if the provider of said component breaks it, it is the responsibility of the distro to not ship their changes until they figure out a migration that doesn't require me to hand-write new configs.
My position remains unchanged, I will never remove the apt version lock on rsyslog.
> rsyslog decided at some point between 2018 and 2020 to break the config file format that had been in use for years before that mystery point in time. I don't know exactly when they did it, I only know when it dawned on me that I wasn't getting logwatch emails anymore. I don't know if they added any new feature which justified breaking the configs, and I do not care, and I will not read their docs or notes to find out. I will only downgrade, version lock, and submit bugs that I know to be facetious to cause someone the grief of having to click on them to close them. It is the distro's job to provide me a working core component and if the provider of said component breaks it, it is the responsibility of the distro to not ship their changes until they figure out a migration that doesn't require me to hand-write new configs.
My position remains unchanged, I will never remove the apt version lock on rsyslog.