Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#61528 - [syslog-ng] Package configuration header puts syslog-ng into “compatibility mode”
Attached to Project:
Arch Linux
Opened by Bogdan Szczurek (thebodzio) - Friday, 25 January 2019, 00:53 GMT
Last edited by Florian Pritz (bluewind) - Friday, 06 March 2020, 12:51 GMT
Opened by Bogdan Szczurek (thebodzio) - Friday, 25 January 2019, 00:53 GMT
Last edited by Florian Pritz (bluewind) - Friday, 06 March 2020, 12:51 GMT
|
DetailsDescription:
Current configuration file provided with syslog-ng package puts syslog-ng into “compatibility mode”. Additional info: 3.19.1-1 Steps to reproduce: Start syslog-ng and take a look at system logs. To get rid of this bug it is enough to set @version directive in syslog-ng.conf to 3.19. Perhaps some automatic modification should be applied during package creation process to take care of this problem? After all changing, this minor detail manually each time a new version is released is quite tedious. |
This task depends upon

Still happening with syslog-ng 3.20.1-1

This will continue to be updated manually because automatically updating the version could cause problems when a default or the behaviour of an option changes. Our example configuration is simple, but configuration schema changes should still be reviewed and the version should be bumped manually to ensure that any change does not cause unexpected problems.