This update for syslog-ng fixes the following issues:
{
"binaries": [
{
"syslog-ng-java": "3.35.1-bp154.3.3.1",
"syslog-ng-python": "3.35.1-bp154.3.3.1",
"syslog-ng-devel": "3.35.1-bp154.3.3.1",
"syslog-ng-smtp": "3.35.1-bp154.3.3.1",
"syslog-ng-geoip": "3.35.1-bp154.3.3.1",
"syslog-ng-redis": "3.35.1-bp154.3.3.1",
"syslog-ng": "3.35.1-bp154.3.3.1",
"libevtlog-3_35-0": "3.35.1-bp154.3.3.1",
"syslog-ng-mqtt": "3.35.1-bp154.3.3.1",
"syslog-ng-sql": "3.35.1-bp154.3.3.1",
"syslog-ng-snmp": "3.35.1-bp154.3.3.1",
"syslog-ng-curl": "3.35.1-bp154.3.3.1"
}
]
}
{
"binaries": [
{
"syslog-ng-java": "3.35.1-bp154.3.3.1",
"syslog-ng-python": "3.35.1-bp154.3.3.1",
"syslog-ng-devel": "3.35.1-bp154.3.3.1",
"syslog-ng-smtp": "3.35.1-bp154.3.3.1",
"syslog-ng-geoip": "3.35.1-bp154.3.3.1",
"syslog-ng-redis": "3.35.1-bp154.3.3.1",
"syslog-ng": "3.35.1-bp154.3.3.1",
"libevtlog-3_35-0": "3.35.1-bp154.3.3.1",
"syslog-ng-mqtt": "3.35.1-bp154.3.3.1",
"syslog-ng-sql": "3.35.1-bp154.3.3.1",
"syslog-ng-snmp": "3.35.1-bp154.3.3.1",
"syslog-ng-curl": "3.35.1-bp154.3.3.1"
}
]
}